[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title Leeam Dagan reopened an issue Jenkins / JENKINS-37809 Throttling based on parameters does not work in Pipelines Change By: Leeam Dagan Resolution: Duplicate Status: Resolved Reopened 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.173942.1472562343000.7298.1567706760551%40Atlassian.JIRA.
[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title Leeam Dagan commented on JENKINS-37809 Re: Throttling based on parameters does not work in Pipelines Oleg Nenashev Can this bug be reopened now? Pipeline support of TCB was added in 2.0 and 2.01 However parameter based throttling was not added, or does this instead need to be a new feature request? I am leaning towards bug because there exists no way to do parameter throttling unless using freestyle, but as referenced here https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md TCB has indeed been added to pipeline support. 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.173942.1472562343000.2965.1567113000251%40Atlassian.JIRA.
[JIRA] [multijob-plugin] (JENKINS-30952) build only on scm changes logic is reversed
Title: Message Title Leeam Dagan commented on JENKINS-30952 Re: build only on scm changes logic is reversed +1 here Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30899) Build History order not sorted properly
Title: Message Title Leeam Dagan commented on JENKINS-30899 Re: Build History order not sorted properly +1 to these 3 reports of the build history being out of order also linked em all together Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30899) Build History order not sorted properly
Title: Message Title Leeam Dagan updated an issue Jenkins / JENKINS-30899 Build History order not sorted properly Change By: Leeam Dagan Comment: +1 to these 3 reports of the build history being out of orderalsolinked em all together Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multijob-plugin] (JENKINS-26951) Multijob plug needs to reread the NextBuildNumber variable immediately before retrying a failed build step
Leeam Dagan commented on JENKINS-26951 Multijob plug needs to reread the NextBuildNumber variable immediately before retrying a failed build step I have not seen this happen recently, I had to kick of many builds at once, I will try to reproduce and comment back. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-26951) Multijob plug needs to reread the NextBuildNumber variable immediately before retrying a failed build step
Leeam Dagan created JENKINS-26951 Multijob plug needs to reread the NextBuildNumber variable immediately before retrying a failed build step Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 13/Feb/15 2:16 AM Description: Currently when I have a multiple jobs running.. Instance of Main JOB 1 Subjob a (build number 1) subjob b subjob c Instance of Main JOB 2 subjob a (build number 2) subjob b subjob c Now if subjob a failed on the first Main Job, then it would attempt to retry that subjob a and get a DEAD executor, because it fails to overwrite $Jenkins_Home\Workspace\Job\MainJob\builds\2 because its currently in USE by Main Job 2 subjob a Should be a straightforward fix, have the retry portion of the multijob plugin reread the nextbuildnumber file and consequently assign the build a number that is not currently in use. I believe it currently just increments the previous failed job number by 1 Project: Jenkins Priority: Major Reporter: Leeam Dagan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-25458) Version 1.14 forces a git checkout? unknown reasons
Leeam Dagan created JENKINS-25458 Version 1.14 forces a git checkout? unknown reasons Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 05/Nov/14 8:34 PM Description: I have my multi job setup to not need any source code management (none radio button) It would always start off and then begin the first multi job phase after upgrading to 1.14 it now forces a git checkout? no idea where its getting the proper info from to even try a git fetch but it is (my job steps were the only ones doing checkouts before). Downgrading to 1.13 (on test jenkins) restored desired behavior as well as downgrading to 1.10 on live. However now I cant seem to download 1.13 for my live implementation Looking forward to a fix The view console is all messed up in 1.10 Project: Jenkins Priority: Blocker Reporter: Leeam Dagan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-25458) Version 1.14 forces a git checkout? unknown reasons
Leeam Dagan updated JENKINS-25458 Version 1.14 forces a git checkout? unknown reasons Change By: Leeam Dagan (06/Nov/14 12:05 AM) Description: Ihavemymultijobsetuptonotneedanysourcecodemanagement(noneradiobutton)Itwouldalwaysstartoffandthenbeginthefirstmultijobphaseafterupgradingto1.14itnowforcesagitcheckout?noideawhereitsgettingtheproperinfofromtoeventryagitfetchbutitis(myjobstepsweretheonlyonesdoingcheckoutsbefore).Downgradingto1.13(ontestjenkins)restoreddesiredbehavioraswellasdowngradingto1.10onlive.HowevernowIcantseemtodownload1.13formyliveimplementationLookingforwardtoafix:)Theviewconsoleisallmessedupin1.10 Edit:found1.13archiveandinstalledthatfornow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
