Actions
Story #6065
closed[EPIC] Move to Github Actions
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Right now we use Travis for our CI/CD environment. We depend on it for not only testing our code but also for compiling docs, releasing to pypi, etc. The problem is that we're limited to 3 concurrent jobs in Travis while Github Actions offers 20 jobs[0]. Also, the job time limit in Travis is 50 minutes vs 6 hours for Github Actions.
Plan¶
- Move ansible-pulp and rpm_prerequisites to Github Actions and collect data for a while
- Move a plugin like pulp_file or pulp_npm to Github Actions
- Test out the plugin (including performing some releases)
- Move the plugin_template to Github Actions
- Update plugins with new plugin_template Github Actions changes
Updated by fao89 over 3 years ago
One advantage of GH actions is:
- the more plugins we move to GH actions we will have fewer plugins competing for travis
Updated by daviddavis almost 3 years ago
- Status changed from NEW to CLOSED - WONTFIX
We have no immediate plans to move to Actions. Closing out and we can refile later.
Actions