Open pascalberger opened 5 years ago
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.
Cake.Recipe should set IssuesParameters.BuildIdentifier
for proper Cake.Issues.Recipe configuration
@pascalberger can you suggest what this BuildIdentifier should be set to? Do you have any examples? Thanks
@gep13 For Cake.Issues.Recipe integration tests it is set here:
This results in the following artifacts:
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.
Issue is not only limited to Azure Pipelines, but any CI system where builds run in different configurations
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.
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.