Task #4652
closed
CI infrastructure requirements
0%
Description
Pulp 3 currently uses Travis for its CI needs. Even though Travis frustrates developers from time to time, it can be described as reliable. The following is the list of features that Travis provides:
- Free for open source projects
- publicaly accessible UI
- individual VMs for each build
- about 4 jobs at a time
- allows ssh connection for jobs that need interactive debugging
The biggest limitation of Travis is the requirement that all VMs have Ubuntu as the operating system. Testing against other platforms requires using containers. We should consider switching to something other than Travis if the other service provides the following in addition to the services described above:
- ability to test on RHEL VMs
Updated by daviddavis almost 4 years ago
I would say that a hosted solution would be a requirement—or at the least, we need a low maintenance CI env. Before we switched to Travis, we were spending 2-3 FTEs or more every week maintaining Jenkins. Our team is at full capacity and we simply don't have that much time to dedicate to CI.
Updated by daviddavis almost 4 years ago
This issue was raised again today. I think it's worth spending some time on this in the near term. The two questions I have is (a) where do we start? Does it make sense to start small with a plugin? Also, (b) which platform do we use?
Updated by hairspraybeautysalon over 3 years ago
- File clipboard-201907191603-yasko.png added
Updated by dkliban@redhat.com over 3 years ago
- File deleted (
clipboard-201907191603-yasko.png)
Updated by ttereshc about 1 year ago
- Status changed from NEW to CLOSED - WONTFIX
No longer relevant. Travis is not used anymore.
.