Investigate alternative jenkins access for backups
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
The backup server relies on an individual contributors token to access jenkins, which is brittle if that contributor becomes emeritus.
Lets investigate a service account token for that purpose.
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
Start by reviewing the backup server's current Jenkins authentication and how the individual contributor token is used. Identify the service-account-token approach to investigate, and consider the work complete when a documented, maintainable alternative has been evaluated and its required changes are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100