Release CI x64 reconfiguration
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Currently on the release CI we have three x64 machines:
These three machines service two builds:
We have observed long build times, usually due to ccache invalidation/not being populated. For the latter the theory is that having three machines may be actively working against ccache since for a given build only two of the three machines would be used (so the third will not have an updated ccache cache).
I'm going to take the second IBM hosted release machine offline, leaving one Digital Ocean hosted and one IBM hosted machine. For now we'll keep both labels on both machines, but reserve the option to pin each of the remaining machines to one of the build types.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the three release machine configurations and the rhel8-release-sources and rhel8-x64-release job configurations linked in the issue. Confirm the second IBM machine is taken offline while the DigitalOcean and remaining IBM machines retain both labels; verify both release jobs still run with the reduced machine pool.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100