[JIRA] [parameterized-trigger] (JENKINS-18536) Remove downstream job from queue before new triggers
Markus created JENKINS-18536 Remove downstream job from queue before new triggers Issue Type: New Feature Assignee: huybrechts Components: parameterized-trigger Created: 28/Jun/13 8:48 AM Description: Given two jobs: Downstream, which has a 60s quiet period Upstream, which triggers a parameterized build on Downstream Now, if you quickly trigger Upstream 3 times, then there will be 3 Downstream jobs in the queue. They will then all run. We would like parameterized triggering in combination with downstream quiet period to behave sort of like the SVN quiet period behaves: If Upstream is triggered multiple times, then only the last triggered Downstream will remain in the queue. Summary: Before Upstream triggers Downstream, Upstream should remove any instances of Downstream from the queue. This should of course be an option and not the default behavior. Project: Jenkins Priority: Major Reporter: Markus 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] [parameterized-trigger] (JENKINS-18536) Remove downstream job from queue before new triggers
Markus
commented on JENKINS-18536
Remove downstream job from queue before new triggers
For anyone that may need the same feature. Our current work-around is a rather messy groovy script added to Upstream:
CancelDownstreamQueue.groovy
import hudson.model.*
Jenkins = Hudson.instance
def q = Jenkins.instance.queue;
if ( args.length != 2 ) {
println "ERROR - CancelDownstreamQueue.groovy - Scripts needs two arguments. Own job name and part of downstream job name to search for. Do not know if wildcards are supported."
} else {
println("Search for downstream jobs from " + args[0] + " whose name contains " + args[1]);
def thisjob = Jenkins.getInstance().getItemByFullName(args[0]);
if (thisjob == null) {
println("ERROR - CancelDownstreamQueue.groovy - Could not find this job");
}else{
//println(thisjob.getDownstreamProjects())
ListAbstractProject childs = thisjob.getDownstreamProjects()
if (childs == null) {
println("ERROR - CancelDownstreamQueue.groovy - childs is null");
}else{
for (IteratorAbstractProject iterator = childs.iterator(); iterator.hasNext();) {
AbstractProject child = iterator.next();
if (child.getFullName().contains(args[1])) {
println(" Found downstream job " + child.getFullName() + ". Searching for queued items");
q.items.findAll { it.task.name.equals(child.getFullName()) }.each {
println("Cancelling queued " + it.task.getDisplayName());
q.cancel(it.task);
}
} else {
println(" Skipping " + child.getFullName());
}
}
}
}
println("Done");
}
But the script is not 100% stable. It happens to fail (hangs or generates a java.lang.NegativeArraySizeException).
The script is started like this:
java -jar jenkins-cli.jar -s http://jenkins:8080/ groovy ./CancelDownstreamQueue.groovy $JOB_NAME SearchStringForJobsToCancel
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] [claim] (JENKINS-16671) Multiple Selective Claiming of Broken Builds
Markus commented on JENKINS-16671 Multiple Selective Claiming of Broken Builds A work-around to claiming multiple builds could be to do a post from for example curl. I've tried that but I get a 400 error and "This page expects a form submission" curl -n 'http://jenkins:8080/job/TestClaiming/lastFailedBuild/claim/claim' --data "reason=testingsticky=onSubmit=Claim" Any idea suggestion on how to post the correct data? 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] [email-ext] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Markus commented on JENKINS-14508 Default pre-send script in Jenkins Configuration Great! Thank you! 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] [claim] (JENKINS-11638) When claimed, stop sending e-mails to individuals who broke the build
Markus updated JENKINS-11638 When claimed, stop sending e-mails to individuals who broke the build I've found a solution using a pre-send script in the email-ext plugin (JENKINS-12421), so I'll downgrade this to Minor. Change By: Markus (28/May/13 6:37 AM) Priority: Major Minor 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] [configurationslicing] (JENKINS-16305) Add support for Quiet period configuration slicing
Markus updated JENKINS-16305 Add support for Quiet period configuration slicing Change By: Markus (06/May/13 12:43 PM) Description: Itwouldbegreatif thus the plugincouldsupportslicingtheQuietperiodconfigurationitem.Thanksforagreatplugin!Useitallthetime! 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.
