[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-59159 Please delete these two files so that it doesn't show up in google search Change By: Kevin Yu Please help delete these two files on Jenkins Jira so that it doesn't show up in Google search anymore. It has some information regarding our company's internal information: {code:java} ' [^ https://issues.jenkins-ci.org/secure/attachment/44565/ config-2.8.1.xml ] ' ' https://issues.jenkins-ci.org/secure/attachment/44564/config-0.17.xml' {code} Thank you very much Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201596.1567202985000.3525.1567203720149%40Atlassian.JIRA.
[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-59159 Please delete these two files so that it doesn't show up in google search Change By: Kevin Yu Please help delete these two files on Jenkins Jira so that it doesn't show up in Google search anymore. It has some information regarding our company's internal information: ' [^config-2.8.1.xml] ' [^ ' https://issues.jenkins-ci.org/secure/attachment/44564/ config-0.17.xml ] ' Thank you very much Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201596.1567202985000.3524.1567203060063%40Atlassian.JIRA.
[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search
Title: Message Title Kevin Yu created an issue Jenkins / JENKINS-59159 Please delete these two files so that it doesn't show up in google search Issue Type: Task Assignee: Unassigned Components: core Created: 2019-08-30 22:09 Priority: Minor Reporter: Kevin Yu Please help delete these two files on Jenkins Jira so that it doesn't show up in Google search anymore. It has some information regarding our company's internal information: [^config-2.8.1.xml] [^config-0.17.xml] Thank you very much Add Comment
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Environment: Jenkins ver. 2. 46 138 . 2 4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.196280.1544821771000.14072.1559064540220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu commented on JENKINS-55210 Re: Same downstream build is triggered by two different upstream jobs This issue happened again with the exact same symptom on version 2.138.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.196280.1544821771000.14071.1559063700049%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56223) Jenkins discard-old-build caused open file handles
Title: Message Title Kevin Yu commented on JENKINS-56223 Re: Jenkins discard-old-build caused open file handles Is there any update on this issue? Our system is having the same problem at the moment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Attachment: samejob.png Attachment: samejob1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Attachment: samejob.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Attachment: samejob1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Summary: Same downstream build is triggered by two different upstream jobs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream Change By: Kevin Yu [Symptom] There are two upstream jobs, which triggered the same downstream job. When both upstream jobs are triggered at the same time, seems like there's a race condition, which would caused the same build in downstream job triggered only once, by both upstream jobs.[Expected behaviour]Downstream job should be triggered twice, each with different BUILD_NUMBER.Please see screenshoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream Change By: Kevin Yu There are two upstream jobs, which triggered the same downstream job. When both upstream jobs are triggered at the same time, seems like there's a race condition, which would caused the same build in downstream job triggered only once, by both upstream jobs. [ Expected behaviour ]Downstream job should be the downstream job is triggered twice , each with different BUILD_NUMBER .Please see screenshoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream
Title: Message Title Kevin Yu created an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream Issue Type: Bug Assignee: Unassigned Attachments: samejob.png, samejob1.png Components: core Created: 2018-12-14 21:09 Environment: Jenkins ver. 2.46.2 Priority: Major Reporter: Kevin Yu There are two upstream jobs, which triggered the same downstream job. When both upstream jobs are triggered at the same time, seems like there's a race condition, which would caused the same build in downstream job triggered only once, by both upstream jobs. Expected behaviour should be the downstream job is triggered twice. Please see screenshoot Add Comment