Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
drnic opened this issue Jun 21, 2016 · 2 comments

Comments

@drnic
Copy link
Contributor

drnic commented Jun 21, 2016

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
Copy link
Collaborator

concourse-bot commented Jun 21, 2016

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
Copy link
Contributor Author

drnic commented Jun 21, 2016

Implementation might also enable support for #23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants