Uploading a file to a parameterized job causes to identical builds to be started. It does not happen when the file parameter is left empty. Happened in freestyle jobs as well as pipeline jobs.
Uploading a file to a parameterized job causes to identical builds to be started. It does not happen when the file parameter is left empty. Happened in freestyle jobs as well as pipeline jobs.
Not installing the suggested plugins, prevents this from happening, I don't know which plugin exactly causes this issue.
Uploading a file to a parameterized job causes to identical builds to be started. It does not happen when the file parameter is left empty. Happened in freestyle jobs as well as pipeline jobs.
NotUpdate: Can be reproduced by only installing the suggested plugins, prevents this from happening, I don't know which pipeline plugin exactly causes this issue during the installation.
Even more confusing: Downstream jobs are only triggered once so that there log reads something like this
Started by upstream project "jobWithFile" build number 1 originally caused by: Started by user unknown or anonymous Started by upstream project "jobWithFile" build number 2 originally caused by: Started by user unknown or anonymous