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

Package acquisition can sometimes be too parallel #3974

Closed
tothegills opened this issue Nov 27, 2017 · 3 comments
Closed

Package acquisition can sometimes be too parallel #3974

tothegills opened this issue Nov 27, 2017 · 3 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@tothegills
Copy link
Contributor

Consider:

Parallel steps:
Script 1
Script 2
Script 3

Then:
Package step

Script 1, 2 and 3 create the packages to be consumed by the package step. It ends up running like this:

Script 1, Script 2, Script 3, Package acquisition
Package step

Packages can't be found by package acquisition because they haven't been pushed yet.

Workaround
The current workaround is to add a step that does not run in parallel between the parallel script steps and the package step.

See: https://secure.helpscout.net/conversation/473629447?folderId=557080

@tothegills tothegills added area/execution kind/bug This issue represents a verified problem we are committed to solving labels Nov 27, 2017
@droyad
Copy link
Contributor

droyad commented Dec 1, 2017

Possibly related, when Aquisition fails, the next step starts running

ServerTasks-12953.log.txt

@octoreleasebot
Copy link

Release Note: Steps may now be explicitly configured to run before or after package acquisition

@lock
Copy link

lock bot commented Nov 23, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants