github-release-resource icon indicating copy to clipboard operation
github-release-resource copied to clipboard

Create release as a pre-release, upload all files, then change to published release

Open drnic opened this issue 8 years ago • 2 comments

The moment that a release is created (non pre-release) then any other concourse pipeline that watches it can trigger - except that the release might not yet be finished. If the finished release includes several large files, then it is possible for downstream pipelines to trigger too early.

Perhaps if we create the release as a pre-release, then upload files, then switch to a final release we will have happy downstream pipelines?

drnic avatar Jun 21 '16 04:06 drnic

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

  • [ ] #121916769 Create release as a pre-release, upload all files, then change to published release

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

concourse-bot avatar Jun 21 '16 04:06 concourse-bot

Implementation might also enable support for #23

drnic avatar Jun 21 '16 04:06 drnic