[Pulp-dev] Moving to Github Actions

David Davis daviddavis at redhat.com
Tue Feb 4 15:24:27 UTC 2020

Over the past year, we've experienced several growing pains with using
Travis as our CI/CD environment. Perhaps the biggest has been the
limitation of having only 3 concurrent job runners[0] across our entire
Pulp organization. At times, it has slowed development by bottlenecking the
merging of PRs and delayed numerous releases of Pulp.

Last year, Github introduced Github Actions which offers open source
projects 20 concurrent jobs[1]. I've filed an issue here to get feedback on
moving our repos and plugins to Github Actions:


Also, @fao89 has opened a couple PoC PRs to demonstrate using Github


You'll notice for example that the ansible-pulp build time went from more
than 1 hour[2] to 27 minutes[3] as all the jobs ran in parallel on Github

Unless there are objections, we plan to merge the ansible-pulp PR this week
since it's CI configuration is independent from other pulp and plugin repos
(ie it doesn't use the plugin_template's Travis files).

We're hoping though to get feedback on whether we should move pulpcore and
plugin repos to Github Actions. If so, should we provide plugins with the
option to continue using Travis if they want?

If there's no objections by February 11, 2020, we'll proceed with moving
pulp_file to Github Actions and look at updating plugin_template.

[0] https://travis-ci.com/plans
[2] https://travis-ci.org/pulp/ansible-pulp/builds/645651353
[3] https://github.com/fabricio-aguiar/ansible-pulp/actions/runs/33601847

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200204/eead1be7/attachment.htm>

More information about the Pulp-dev mailing list