cirruslabs
Create builds on creation of a release
Expected Behavior
When a release is created from an existing tag Cirrus CI should create a new build
Real Behavior
Build is only created when a new tag and a new release are created simultaniously
Related Info
See #451 for details
Hey,
Possibly related (I can open a new issue if not): The documentation for $CIRRUS_TAG makes it sound like a separate build is triggered when the new tag is pushed. I was wanting to check this variable from a task, to alter behavior e.g. with artifact and upload filenames/locations. But it seems if tags are pushed after the release-commit-containing PR merges, no build has $CIRRUS_TAG set (or I couldn't find it). Same problem?
@cevich what is "release-commit-containing PR" in your case? You merge a PR and then create a tag?
@fkorotkov well, not me personally, but yes there will be a PR with a "release version X.Y.Z" commit. The PR may have more than one commit, as well, e.g. "update release notes". Sometime later, a sha gets tagged. Worse, humans are involved (yuck!) so there's no predicting this workflow will even be consistent :confounded:
It seems it should work as expected: once you create a tag, there will be a push webhook event that you've pushed refs/tags/X.Y.Z and Cirrus will create an additional build for X.Y.Z with $CIRRUS_TAG == 'X.Y.Z'.
Hmmm, so it's possible I'm just not seeing it. I looked under https://cirrus-ci.com/github/<owner>/<repo>/master and also w/o master. Would the build show up somewhere else?
Either way...sounds like I'm having a different issue from this one.
@cevich creation time of such tag build will be timestamp of the last change on the branch. You can try a direct link: mmm, so it's possible I'm just not seeing it. I looked under https://cirrus-ci.com/github/<owner>/<repo>/<tag>
Hmm, nothing at all shows up there. I'll open a new issue for this since it's not related to this one...#481
Hey, I am trying to understand why this task didn't upload to it's release:
https://cirrus-ci.com/task/5980768460603392 https://cirrus-ci.com/github/adventuregamestudio/ags/v.3.5.1.8
https://github.com/adventuregamestudio/ags/blob/14bf1498e2a50f94f3ca9d376aedd9f4b351da4e/.cirrus.yml#L365
Seeing this bug report is related from a bug report related to our project, is it related to different time of creation of tag and release? (I am here from following #451 )
The person that created the release confirmed me it was done entirely on GitHub Release web interface, so I don't know if it could fail similarly even in this case or if it's a different issue.
