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

concourse / github-release-resource

a resource for github releases

Apache License 2.0

57 stars 58 forks source link

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

Open drnic opened 8 years ago

drnic commented 8 years ago

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?

concourse-bot commented 8 years ago

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.

drnic commented 8 years ago

Implementation might also enable support for #23