nebula-plugins / nebula-plugins/nebula-release-plugin
`candidate` tasks not failing if tag already exists
Open
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Hello, today happened that two builds has been triggered simultaneously. Unfortunately the build for older commit won the battle and successfully pushed a tag the second one
build for older commit:
:release (Thread[Task worker for ':',5,main]) started.
:release
Task ':release' is not up-to-date because:
Task has not declared any outputs.
Tagging repository as v1.0.1-rc.1
Pushing changes in [v1.0.1-rc.1] to origin
The following authentication options are allowed (though they may not be available): [SSHAGENT, HARDCODED, PAGEANT, INTERACTIVE]
ssh-agent available
using agent proxy
:release (Thread[Task worker for ':',5,main]) completed. Took 4.259 secs.
build for newer commit:
:release (Thread[Task worker for ':',5,main]) started.
:release
Task ':release' is not up-to-date because:
Task has not declared any outputs.
Tagging repository as v1.0.1-rc.1
Pushing changes in [v1.0.1-rc.1] to origin
The following authentication options are allowed (though they may not be available): [HARDCODED, PAGEANT, INTERACTIVE, SSHAGENT]
ssh-agent available
using agent proxy
:release (Thread[Task worker for ':',5,main]) completed. Took 1.134 secs.
Is there any way how to fail a release task if the tag already exists?
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 tracing the Gradle release task's handling of existing tags and reproduce the simultaneous builds described in the issue. Done when a release attempt fails instead of successfully pushing a tag that already exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100