[JIRA] [node-iterator-api] (JENKINS-24721) No version history for node-iterator-api
Markus created JENKINS-24721 No version history for node-iterator-api Issue Type: Task Assignee: stephenconnolly Components: node-iterator-api Created: 16/Sep/14 8:17 AM Description: There is no change log/version history for the node-iterator-api. https://wiki.jenkins-ci.org/display/JENKINS/Node+Iterator+API+Plugin I prefer to review the changes before upgrading. Not a big issue, so Minor priority. Project: Jenkins Priority: Minor 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/d/optout.
[JIRA] [tasks-plugin] (JENKINS-24708) Message is missing from REST API
Markus commented on JENKINS-24708 Message is missing from REST API Yes, that should not be a problem at all. 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] [tasks-plugin] (JENKINS-24708) Message is missing from REST API
Markus created JENKINS-24708 Message is missing from REST API Issue Type: Bug Assignee: Ulli Hafner Components: tasks-plugin Created: 15/Sep/14 1:38 PM Description: The XML API does not contain the message. I installed the latest LTS Jenkins and latest TaskScanner (with dependencies) on a test server and set up a very simple job - fetch a file and scan for warnings. Output from http://localhost:8080/job/TaskScanner/2/tasksResult/ File Line Priority Type Message MyFile:278 278 Low XXX Make generic MyFile:541 541 Low XXX Assign correct drivers Output from http://localhost:8080/job/TaskScanner/2/tasksResult/api/xml?depth=1 /work/jenkins_test_slave/workspace/TaskScanner/MyFile 4 278 LOW /work/jenkins_test_slave/workspace/TaskScanner/MyFile 5 541 LOW Environment: Jenkins ver. 1.565.2 Task Scanner Plug-in 4.42 Static Analysis Collector Plug-in 1.41 Static Analysis Utilities 1.59 Project: Jenkins Priority: Minor 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/d/optout.
[JIRA] [tasks-plugin] (JENKINS-24705) Display task author from SVN or other tool
Markus created JENKINS-24705 Display task author from SVN or other tool Issue Type: New Feature Assignee: Ulli Hafner Components: tasks-plugin Created: 15/Sep/14 1:12 PM Description: It would be very useful if this very fine plugin also could show the author that added the task, fetched from SVN or any other source control tool that is used. This would make it much easier to keep get in touch with the author to discuss the task. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-24618) Absolute priority not working
Markus commented on JENKINS-24618 Absolute priority not working I have noticed exactly the same thing, running Jenkins ver. 1.565.2 as a local test server. I installed this server to solely to evaluate the priority sorter. No other plugins installed. Running Priority Sorter 2.8. One executor Launch Testjob with any priority (To occupy the executor). Launch Testjob_LowPri1 with a high priority number (i.e. low priority). This is queued, as expected Launch Testjob_HighPri1 with a low priority number (i.e. high priority). This is queued, as expected Expected result: When Testjob is done, Testjob_HighPri1 is executed, then Testjob_LowPri1. Actual result: When Testjob is done, Testjob_LowPri1 is executed, then Testjob_HighPri1. From PrioritySorter.Queue.Items sep 15, 2014 12:26:07 PM FINE PrioritySorter.Queue.Items Buildable: Id: 61, JobName: Testjob, jobGroupId: 0, reason: , priority: 10, weight: 10.0, status: BUILDABLE sep 15, 2014 12:26:07 PM FINE PrioritySorter.Queue.Items Starting: Id: 61, JobName: Testjob, jobGroupId: 0, reason: , priority: 10, weight: 10.0, status: BUILDABLE sep 15, 2014 12:26:09 PM FINE PrioritySorter.Queue.Items Buildable: Id: 62, JobName: Testjob_LowPri1, jobGroupId: -1, reason: , priority: 15, weight: 15.0, status: BUILDABLE sep 15, 2014 12:26:12 PM FINE PrioritySorter.Queue.Items Buildable: Id: 63, JobName: Testjob_HighPri1, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE From Jenkins log: sep 15, 2014 12:26:37 PM hudson.model.Run execute INFO: Testjob #11 main build action completed: SUCCESS sep 15, 2014 12:27:08 PM hudson.model.Run execute INFO: Testjob_LowPri1 #12 main build action completed: SUCCESS sep 15, 2014 12:27:38 PM hudson.model.Run execute INFO: Testjob_HighPri1 #10 main build action completed: SUCCESS 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] [claim] (JENKINS-23042) Claim report shows a max of 50 failures
Markus commented on JENKINS-23042 Claim report shows a max of 50 failures I think this is a duplicate of JENKINS-19128. 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] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
Markus closed JENKINS-24432 as Fixed SVN modules in sub directories are not removed by SVN Workspace Cleaner Great! We've installed it and tested it on a small test case. It seems to work perfectly. Thank you very much! Change By: Markus (29/Aug/14 6:41 AM) Status: Resolved Closed 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] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
Markus created JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner Issue Type: Bug Assignee: David Pärsson Components: svn-workspace-cleaner Created: 26/Aug/14 8:06 AM Description: How to reproduce: 1. Create a new Jenkins job 2. Enable "Clean up unused Subversion modules" 3. Add two modules from two location Repository URL: http://svn/repo/moduleA Local module directory: sub/moduleA Repository URL: http://svn/repo/moduleB Local module directory: sub/moduleB 4. Save job, execute it. 5. Edit job, removed moduleB 6. Save job, execute it. What is expected: moduleB is removed from workspace. Console output says "[WORKSPACE-CLEANER] Deleting directory 'moduleB' since it's not a configured module in SVN." What happens: moduleB is not removed. Environment: SVN Workspace Cleaner 1.0 Jenkins ver. 1.554.1 Cent OS 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/d/optout.
[JIRA] [configurationslicing] (JENKINS-16855) Add "Allow broken build claiming" function
Markus
commented on JENKINS-16855
Add "Allow broken build claiming" function
Great!
Since registering this issue, I've made a groovy script that runs periodically to add claiming rights to all jobs. I'll paste it in here if anyone needs it. Note that I am no groovy master so it may have bugs etc. But it works for us:
import hudson.model.*
import hudson.maven.*
import hudson.tasks.*
println("Scanning for jobs without claim rights")
for(item in Hudson.instance.items) {
println(" Checking $item.name")
hasClaim = false;
if(item instanceof FreeStyleProject) {
for(p in item.getPublishersList() )
{
if(p instanceof hudson.plugins.claim.ClaimPublisher)
{
hasClaim = true;
}
}
if (item.name.startsWith("x"))
println("Skipping utility job")
else {
if(!hasClaim)
{
println("Adding claim right to $item.name")
item.getPublishersList().add(new hudson.plugins.claim.ClaimPublisher() );
item.save()
} else {
println("Claim right already added to $item.name")
}
}
} else {
type = item.getClass().toString();
println("Skipping non-FreeStyleProject job ($type)");
}
}
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.
