Reputation: 2914
I have a project where I need to perform multiple builds - across different agents. I have a Visual Studio project, an Xcode project and a NPM+Gulp project where I need to combine the artefacts into a single archive.
I have set up builds for each. And my first try was to set up a Release which downloaded the artefacts from each build and packaged it all up. But I didn't figure out how to get that package from the Release. (I had tried to use the Publish Artefact step, but got and error because apparently it can only be used for a Build)
So now I'm looking at creating a separate Build that does the packaging - and then puts the result in its Artefacts. But this made me wonder if there are better ways to deal with this in Team Services?
What I also want to achieve here is to trigger builds of my VS, Xcode and NPM Builds when I push to my git repo, then have "something" kick of a packaging step when all those three builds are done. What's a good way to do that in Team Services?
Upvotes: 1
Views: 420
Reputation: 59020
The scenario you're describing sounds like you want everything to be a part of a single build, not separate builds.
Since you have some pieces that run on Windows and some that run on MacOS, you can use multi-phase builds to run different "sections" of the build across different agents.
Upvotes: 1