edgexfoundry / edgexfoundry/cd-management
EdgeX DevOps: release automation fails to bump semver tag when re-releasing a repo with the same version
- Dominant language
- No language data
- Stars
- 6
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I have a git semver issue. I noticed on device-bacnet-c (https://github.com/edgexfoundry/device-bacnet-c/blob/semver/master) Jenkins didn't bump to 1.3.1-dev.1 after 1.3.0 was released back in Nov 18th so it has been stuck for a while.
The build fails to bump with this message:
14:37:23 [edgeXSemver]: ignoring command bump pre because GITSEMVER_HEAD_TAG is already set to 'v1.3.0'
https://jenkins.edgexfoundry.org/job/edgexfoundry/job/device-bacnet-c/job/master/13/consoleFull
The release build from cd-management tried bumping it too but says the same thing:
[2020-11-18T21:38:04.818Z] [edgeXSemver]: ignoring command bump -pre=dev pre because GITSEMVER_HEAD_TAG is already set to 'v1.3.0'
https://jenkins.edgexfoundry.org/blue/organizations/jenkins/edgexfoundry%2Fcd-management/detail/release/40/pipeline/312
master
1.3.0
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.