opendevstack / opendevstack/ods-jenkins-shared-library
Release manager workspace checkout sits on stale data (e.g. deleted tags)
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 81
- Forks
- 59
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 3
Description
this creates a LOT of problems - e.g. if you remove a tag in bitbucket - and it's left here - it will be pushed back later by
We should alwys and only use git as the source of truth
@michaelsauter - was there any reason to not do this?
@metmajer fyi - this is the reason why one cannot cleanup doc history
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
Read vars/odsOrchestrationPipeline.groovy at lines 69-75 and src/org/ods/services/GitService.groovy at line 238, then trace how the release manager workspace is checked out and later used. Reproduce the stale-tag scenario and verify that the workspace reflects Git's current state without restoring deleted tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, groovy
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100