Hi, I encountered an issue with a github deployment that has been working rather well thus far. I do a force tag with
git tag $VERSION_TAG --force -a -m "Travis build $TRAVIS_BUILD_NUMBER" and then a deployment, however on a recent job the release remained untagged and I can’t determine why, this is occurring on a -second- deploy of the same tag … which is what the
force is meant for (and has been successful in overwriting in the past)
This is the main job: https://travis-ci.org/open-horizon/horizon-deb-packager/builds/513238215
In each of the parallel jobs the tagging is successful (for example): https://travis-ci.org/open-horizon/horizon-deb-packager/jobs/513238221#L2588
But when the deployment happens, I notice it either remains untagged: https://travis-ci.org/open-horizon/horizon-deb-packager/jobs/513238221#L2643
Or is actually blank?: https://travis-ci.org/open-horizon/horizon-deb-packager/jobs/513238220#L2642
Despite the last line there being the tag update that we want (2.22.8)
This is eventually becomes the release: https://github.com/open-horizon/horizon-deb-packager/releases/tag/untagged-a18ef02177f0a25083ba
I’m not sure what’s happening, perhaps I’m doing this incorrectly? Or if this was a fluke or something else entirely. Any help would be appreciated.
Edit: Just updating that this is not a fluke, it’s consistently no longer tagging (on a second attempt). Manually deleting the release seems to be a work-around before issuing a ‘rebuild’, so perhaps I can just issue a full deletion of the release/tag before I tag it.