|Who present in meeting||David L, Rob W, Pete, Jay B|
|Details||The build stage has failed.|
|Root Cause Analysis|
The Build stage has failed with the exception:
The build stage on PR#11539 was successful. We have noticed that the PR was run with the configuration:
The change included in the PR attempts to copy the stashed m2 files into every stages input directory. This was run on a PR with mock-build, which skips the build stage, and uses stashes from a previous run for subsequent stages. On the merge to master, this tries to copy the m2 stash into the input directory of the build stage. At this point, the m2 stash does not exist, and because cp command exits with an error code if there is nothing to copy, an exception is thrown.
Revert commit from master
The mock-build=true configuration broke the build in the jenkins scripts.
The build could add a comment and task to the PP in stash that will warn the developer of the risks.