Cake.Recipe Support running on multiple Azure Pipelines

With support for Azure Pipelines comes the ability to have multiple jobs in a build, which e.g. run on different platform. This means that e.g. artifacts are created and published multiple times in a single build. Without a unique name they will be overwritten with the one from the latest job. There should therefore be a way to make them unique for each job.

Oct 16 '19 19:10 pascalberger

Cake.Issues.Recipe has solved this with a BuildIdentifier parameter, which can be set in the build script to define a different value for different runs.

Oct 16 '19 19:10 pascalberger

Cake.Recipe should set IssuesParameters.BuildIdentifier for proper Cake.Issues.Recipe configuration

Oct 18 '19 20:10 pascalberger

@pascalberger can you suggest what this BuildIdentifier should be set to? Do you have any examples? Thanks

Jul 10 '20 18:07 gep13

@gep13 For Cake.Issues.Recipe integration tests it is set here:

https://github.com/cake-contrib/Cake.Issues.Recipe/blob/798396d6931c20f58d631c0b7529ab00ed82338c/tests/integration/build.cake#L34

This results in the following artifacts:

https://dev.azure.com/cake-contrib/Cake.Issues.Recipe/_build/results?buildId=4930&view=artifacts&type=publishedArtifacts

Sep 27 '20 18:09 pascalberger

I renamed the issue a bit, as saying multiple platforms could be a bit misleading. IMO that would suggest that Cake.Recipe can't run on different OS's, which it can do.

Oct 05 '20 21:10 AdmiringWorm

Issue is not only limited to Azure Pipelines, but any CI system where builds run in different configurations

Oct 05 '20 21:10 pascalberger

There are only two build providers that I know of that could exhibit this problem. Azure pipelines and GitHub actions (which don't support artefacts upload within the cake script).

Other build providers, I have experience with uses artefacts in separation based on the current run.

Oct 05 '20 21:10 AdmiringWorm