rhobs / rhobs/observability-operator
Discuss tools setup for CI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
Currently the tools we need for CI have no defined install policy. For some tools we install specific versions and make sure that version is used. For other tools we install latest or similar and sometimes check that the version we want is actually executed. I.e. for some tools the version is never actually checked.
Currently the main purpose of the versions defined in Makefile.tools is to cache tools for github actions and update the cache if necessary. This topic came up in #239.
We should agree on a policy to either pin specific version or use latest.
Contributor guide
No contributing guide indexed for this repository
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 Makefile.tools and the GitHub Actions tool-installation setup first, then read issue #239 for the related context. Compare how tool versions are installed and checked today. Done means the project has an agreed policy for pinning or using latest versions and the affected CI setup follows it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100