[Pulp-dev] Pulp 3 Release Process Questions

[Daniel Alley]

>
> Are those Travis jobs testing combinations of web servers, AMQP brokers,
> databases, etc? If not, is testing across those combinations a goal?


The travis jobs currently text a matrix of Django version (2.0 and 1.1
LTS), database (sqlite and postgresql), and python version (3.5 and 3.6).
Presumably the broker variable is about to go away, and we could
theoretically easily add web server tests in later but we don't have the
Apache / Nginx configs written yet.

I feel like if we add much more to Travis though, it's going to start
getting bogged down.  It has already gotten pretty slow at times.  We
should consider how well (or poorly) it's going to scale if we start adding
more and more tests and combinations to the Travis PR test runners.  Maybe
if some combos only ran nightly...


Let's say pulp_file is being tested. Is both it and pulpcore installed from
> source? Or is pulpcore installed from egg/wheel?


Currently, source.  Dennis added a nice feature where if you specify a Pulp
Smash or Pulp File PR in your commit, it will check out that specific pull
request and run tests against it.


What does this mean for goals like multi-host testing? That is, what does
> this mean for the case where a single Pulp 3 application is deployed across
> multiple hosts? Can that be tested with Travis?


I'm pretty sure we can't do that with Travis, although someone correct me
if I'm wrong.





On Mon, Apr 23, 2018 at 12:10 PM, Jeremy Audet <jaudet at redhat.com> wrote:

> Using Travis jobs instead of Jenkins jobs for testing Pulp 3 releases begs
> several questions:
>
>    - Are those Travis jobs testing combinations of web servers, AMQP
>    brokers, databases, etc? If not, is testing across those combinations a
>    goal?
>    - Let's say pulp_file is being tested. Is both it and pulpcore
>    installed from source? Or is pulpcore installed from egg/wheel?
>    - Who is looking at Jenkins jobs? If only QE, why have Jenkins jobs?
>    (Possible answer: So that we can trigger test runs on an as-needed basis,
>    without making new git commits.)
>    - What does this mean for goals like multi-host testing? That is, what
>    does this mean for the case where a single Pulp 3 application is deployed
>    across multiple hosts? Can that be tested with Travis? Pulp Smash is
>    architected with this in mind, and it's been a long standing goal. The
>    biggest impediment has been the use of legacy Jenkins (1.x) and nodepool,
>    and recent upgrades make this a more realistic testing target.
>
> If these questions have already been considered and answered somewhere,
> please point me to the correct resource.
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180423/6b0346fc/attachment.htm>