[JIRA] (JENKINS-59297) File parameter causes two builds to be started
Title: Message Title Samuel Melm closed an issue as Not A Defect Turns out it's an issue with firefox Jenkins / JENKINS-59297 File parameter causes two builds to be started Change By: Samuel Melm Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.g
[JIRA] (JENKINS-59297) File parameter causes two builds to be started
Title: Message Title Samuel Melm commented on JENKINS-59297 Re: File parameter causes two builds to be started 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 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201843.1568120543000.751.1568130600127%40Atlassian.JIRA.
[JIRA] (JENKINS-59297) File parameter causes two builds to be started
Title: Message Title Samuel Melm updated an issue Jenkins / JENKINS-59297 File parameter causes two builds to be started Change By: Samuel Melm 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 Update: 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 . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201843.1568120543000.652.1568122800071%40Atlassian.JIRA.
[JIRA] (JENKINS-59297) File parameter causes two builds to be started
Title: Message Title Samuel Melm updated an issue Jenkins / JENKINS-59297 File parameter causes two builds to be started Change By: Samuel Melm 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. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201843.1568120543000.644.1568120700253%40Atlassian.JIRA.
[JIRA] (JENKINS-59297) File parameter causes two builds to be started
Title: Message Title Samuel Melm created an issue Jenkins / JENKINS-59297 File parameter causes two builds to be started Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-10 13:02 Environment: jenkins docker image/ version 2.194/ suggested plugins Priority: Major Reporter: Samuel Melm 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. Add Comment
