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.

Sign up for GitHub

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

Jump to bottom

Convert to multi-node pipeline #2

Open
jumpinjackie opened this issue Nov 23, 2016 · 0 comments
Open

Convert to multi-node pipeline #2

jumpinjackie opened this issue Nov 23, 2016 · 0 comments

Comments

@jumpinjackie
Copy link
Owner

jumpinjackie commented Nov 23, 2016 •
edited
Loading

According to best practices, each unique configuration ([Release|Debug] & [x86|x64]) should be an individual node.

In terms of our pipeline that means,

  • Remove configuration/platform build parameters
  • Each stage should have a root parallel construct with each branch being the node for that particular configuration/platform. Within each sub-node is the stage body (with any unique changes for that particular configuration/platform). Use the stash/unstash mechanism to pass any required files between nodes on different stages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jumpinjackie