[JIRA] (JENKINS-263) Preserve build order of downstream projects - Post-build Actions Build Other Projects order is not maintained
Title: Message Title Martin Ba updated an issue Jenkins / JENKINS-263 Preserve build order of downstream projects - Post-build Actions Build Other Projects order is not maintained Change By: Martin Ba Environment: Platform: All, OS: All , Version: 2.73 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-2002) Post-build Actions Build Other Projects order is not maintained
Title: Message Title Martin Ba closed an issue as Duplicate Jenkins / JENKINS-2002 Post-build Actions Build Other Projects order is not maintained Change By: Martin Ba Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-263) Preserve build order of downstream projects - Post-build Actions Build Other Projects order is not maintained
Title: Message Title Martin Ba updated an issue Jenkins / JENKINS-263 Preserve build order of downstream projects - Post-build Actions Build Other Projects order is not maintained Change By: Martin Ba Summary: Preserve build order of downstream projects - Post-build Actions Build Other Projects order is not maintained Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-2002) Post-build Actions Build Other Projects order is not maintained
Title: Message Title Martin Ba commented on JENKINS-2002 Re: Post-build Actions Build Other Projects order is not maintained Workaround: We use the PrioritySorter plugin anyway to sort our jobs, so we actually want then to be started in priority order (which you also can do dynamically with the BuildPriority parameter. This bug here prevents the starting in priority order, because jobs are run before all parallel downstream jobs are fully pushed into the queue. What I did was to set a global Quiet Period of 5 sec in the Jenkins Options, so that each and every job (unless otherwise specified(a)) will stay in the Queue for 5 sec - this is enough time so that all parallel downstream jobs get pushed into the queue together, therefore allowing the PrioritySorter Plugin to sort them accordingly. (a): Neat thing is the GUI buttons will add a delay=0sec, so that starting the inital job won't have any delay. If you have URL triggers, you can also spec. the delay there if the 5sec is hurting. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-263) Preserve build order of downstream projects
Title: Message Title Martin Ba commented on JENKINS-263 Re: Preserve build order of downstream projects Radka Nepejchalova I have found a workaround: We use the PrioritySorter plugin anyway to sort our jobs, so we actually want then to be started in priority order (which you also can do dynamically with the BuildPriority parameter. This bug here prevents the starting in priority order, because jobs are run before all parallel downstream jobs are fully pushed into the queue. What I did was to set a global Quiet Period of 5 sec in the Jenkins Options, so that each and every job (unless otherwise specified(a)) will stay in the Queue for 5 sec - this is enough time so that all parallel downstream jobs get pushed into the queue together, therefore allowing the PrioritySorter Plugin to sort them accordingly. (a): Neat thing is the GUI buttons will add a delay=0sec, so that starting the inital job won't have any delay. If you have URL triggers, you can also spec. the delay there if the 5sec is hurting. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-22294) Priority is not used in the scheduling
Title: Message Title Martin Ba commented on JENKINS-22294 Re: Priority is not used in the scheduling Adding to this: I (also) had the problem that sorting on a test job on an instance with one single executor with BuildPriority Job Param didn't happen at all. Upping the Log Levels and looking at it, it seemed the Priority Sorter Plugin only always saw the nextmost job scheduled, and didn't even see the multiple additional pending jobs. In the end, the issue was that I needed to check Execute concurrent builds if necessary for the priority sorter plugin to actually see the enqued jobs. (Also mentioned on https://stackoverflow.com/questions/24145115/jenkins-priority-sorter-plugin-how-to-use-buildpriority-parameter ) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-13966) Parameter Factories on Trigger parameterized build
Title: Message Title Martin Ba commented on JENKINS-13966 Re: Parameter Factories on Trigger parameterized build I've hit this problem too today, as I wanted to add a ParameterFactories / All Nodes for Label Factory as a post-build step. In my case, it would appear I have a simple workaround, as I do not actually require it to be a post-build-step: Since it should only run when the build is stable and there are no other post-build steps, I can easily just add it as the last build step "Trigger/call builds on other projects" where the ParameterFactories is supported. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [prioritysorter-plugin] (JENKINS-31551) "Include this Job in a Job Group" should read "Include this Job in a Priority Job Group" on a Job config page
Title: Message Title Martin Ba created an issue Jenkins / JENKINS-31551 "Include this Job in a Job Group" should read "Include this Job in a Priority Job Group" on a Job config page Issue Type: Improvement Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 13/Nov/15 7:17 PM Priority: Minor Reporter: Martin Ba When using Jobs-marked-for-inclusion to have the ability to choose a Job Group on each project page, the configuration item on the Job/Project page reads "Include this Job in a Job Group". It is not clear that this configuration item belongs to prioritysorter-plugin, since there is no reference anywhere to "priority" nor to "sorter". Also there's no help entry on the Job page for this item. ( Unlike the "Take the priority from Property on the Job" Strategy where there is a help entry on the Job page and the text entry reads "Use specific priority for this Job". ) Add Comment
[JIRA] [envinject-plugin] (JENKINS-19754) Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
Martin Ba
commented on JENKINS-19754
Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
I cannot see this on Windows. (Jenkins 1.480.3 + EnvInject plugin 1.83)
So maybe it is Linux specific or doesn't happen in my old version ...
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] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
Martin Ba commented on JENKINS-10468 Build Queue does not show the executor a build is waiting for I re-checked the issue with my updated Jenkins 1.480.3. Still the same. The build queue is showing: whyWaiting for next available executor on /why without any node info. This time, this is a local Jenkins test-instance and not even the actual build server I used originally. List of installed plugins: External Monitor Job Type Plugin LDAP Plugin pam-auth ant Token Macro Plugin javadoc build-name-setter Maven Integration plugin Dashboard View Build Pipeline Plugin Jenkins user build vars plugin Run Condition Plugin conditional-buildstep Jenkins CVS Plug-in Downstream build view Environment Injector Plugin Extended Choice Parameter Plug-In Hudson Groovy builder Jenkins Subversion Plug-in Jenkins Parameterized Trigger plugin Jenkins Multijob plugin Jython Plugin Locale plugin Priority Sorter Role-based Authorization Strategy Jenkins SSH Slaves plugin Jenkins Throttle Concurrent Builds Plug-in Jenkins Translation Assistance plugin Full queue XML: queue item action parameter nameP1/name value/ /parameter /action action cause shortDescriptionStarted by user x/shortDescription userIdx/userId userNamex/userName /cause /action blockedfalse/blocked buildabletrue/buildable id6/id inQueueSince1368438462785/inQueueSince params (StringParameterValue) P1='' /params stuckfalse/stuck task nameSingle3/name urlhttp://localhost:8080/job/Single3//url colorblue/color /task whyWaiting for next available executor on /why buildableStartMilliseconds1368438462894/buildableStartMilliseconds /item /queue 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/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
Martin Ba assigned JENKINS-10468 to Fred G Build Queue does not show the executor a build is waiting for Change By: Martin Ba (13/May/13 9:50 AM) Assignee: MartinBa FredG 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/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-14475) Conditional build steps should be available as post-build actions
Martin Ba commented on JENKINS-14475 Conditional build steps should be available as post-build actions As for if $some_build_param = "true" trigger a downstream build with parameters end Shouldn't this be doable with the ParamTriggerPlugin? You can have the parameters for the downstream job loaded from a properties file, and you can use this file as "condition", with teh checkbox that doesn't trigger if the file's missing. 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/groups/opt_out.
[JIRA] (JENKINS-14211) missing parameter file does not prevent downstream job from running even though it says it will
Martin Ba commented on JENKINS-14211 missing parameter file does not prevent downstream job from running even though it says it will I am running Jenkins 1.480.3 (LTS) and for me everything works. Specifically I tested with: Trigger parameterized build on other projects Trigger build withoput parameters [ ] (not checked) Some predefined parameters Some from a file (with Don't trigger if any files are missing x checked.) = If the file is missing, downstream build is correctly not triggered. 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/groups/opt_out.
[JIRA] (JENKINS-3230) Parameter usable as value for SCM fields
Martin Ba
commented on JENKINS-3230
Parameter usable as value for SCM fields
Adding info: This works in Jenkins 1.420 (which is what I am running) - Not sure which is the first version that implements it.
The syntax to include a parameter is ${PARAM_NAME} (note the curly brackets) I was confused for a bit because I was used the %NAME% or the $(NAME) syntax.
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
