Parallel builds will use different workspace, so that should not be a problem.
Maybe the “@” symbol it uses to differentiate the workspace folders? I mean, when it runs parallel builds, it will use a “@” and then it will append a number to identify the builds. For instance, if we have workspace called “Test”, when running parallel builds we would get something like: “Test@2” , “Test@3” and so forth. That “@” symbol in a folder may break some scripts. Also, if the scripts that are executed were not prepared to run in parallel, they might use the very same temp folder and files, which can cause problems. On Wed, May 18, 2016 at 12:26 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > It also does a mvn clean so that should not be an issue. I am thinking more > along the line of parallel builds on the same node. > > On Wed, May 18, 2016 at 5:04 PM, Rafael Weingärtner < > rafaelweingart...@gmail.com> wrote: > > > Is Jenkins configure to clean the workspace before it starts a new build? > > > > It should have an option such as "Delete workspace before build starts". > > > > On Wed, May 18, 2016 at 12:00 PM, Will Stevens <williamstev...@gmail.com > > > > wrote: > > > > > If Jenkins has problems with fragments being left over in it's > workspace > > > which is causing following runs against other PRs to fail, how do we > fix > > > that? > > > > > > Thanks... > > > > > > > > > > > -- > > Rafael Weingärtner > > > > > > -- > Daan > -- Rafael Weingärtner
