[JIRA] [nodelabelparameter] (JENKINS-23001) Build Queue Graph Does Not Show Jobs In The Queue When Use NodeLabel Parameter
tim johnston created JENKINS-23001 Build Queue Graph Does Not Show Jobs In The Queue When Use NodeLabel Parameter Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 13/May/14 3:29 PM Description: The build queue graph in Jenkins does not properly show jobs which are in the queue when the job is using the node label parameter. To reproduce: create a label in Jenkins called LabelX create a job which contains a nodelabel parameter and give it the value "LabelX". Make sure that the job can run concurrently and that the option "Restrict where this project can be run" is not clicked. execute enough instances of the job so that there are some jobs in the build queue click LabelX and then click on load statistics Expected: the queued jobs should be represented in the graph with the grey line Actual: the queued jobs are not displayed properly in the graph Project: Jenkins Priority: Minor Reporter: tim johnston 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] [matrix] (JENKINS-18164) Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
tim johnston commented on JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis Some more log output. It seems like the workUnit is fine, because the two pieces of axis data displayed in hudson.model.queue.WorkUnit@e617 is correct. For some reason, it appears that task.createExecutable() is returning null. FINE: Executor #0 for QMWFCRP1 completed null in 0ms Jul 23, 2013 6:31:04 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:234) Jul 23, 2013 6:31:04 PM hudson.model.Executor FINE: Executor #0 for QMWFCRP1 is going to execute null Jul 23, 2013 6:31:04 PM hudson.model.Executor FINE: Executor #0 for QMWFCRP1 grabbed hudson.model.queue.WorkUnit@e617work=RunJTF ยป WFS_Hours_Common_SCTAndCT,All.WFS.MSS.07.00.01.parfixes from 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] [swarm] (JENKINS-18802) Can't Run Swarm As a Windows Service
tim johnston created JENKINS-18802 Cant Run Swarm As a Windows Service Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm Created: 17/Jul/13 8:59 PM Description: I am unable to get the swarm client to run properly when configured as a windows service. I configured the service using the following command line: sc create swarm binpath= "\"C:\Program Files (x86)\Java\jre7\bin\java.exe\" -Xrs -jar c:\swarm\swarm-client-1.9-jar-with-dependencies.jar -executors 2 -fsroot c:\jenkins-slave -labels myLabel -mode exclusive -name NewNode " displayname= "Jenkins Swarm" start= delayed-auto When I start the service through Services, I can see that the node becomes active when I look at the homepage on the master. Unfortunately, Windows thinks that it was unsuccessful and terminates the service with the following error: Windows could not start the Jenkins Swarm service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion. I can run the command line manually on the node and it works fine. It would be great if this was fixed so that swarm could run as a service. Environment: Windows Server 2008 Project: Jenkins Priority: Major Reporter: tim johnston 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] [swarm] (JENKINS-18802) Can't Run Swarm As a Windows Service
tim johnston updated JENKINS-18802 Cant Run Swarm As a Windows Service Change By: tim johnston (17/Jul/13 9:01 PM) Environment: WindowsServer2008 ,Thisproblemexistsonboth32bitand64bitversionsofjava.Itriedboth. 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] [matrix] (JENKINS-18164) Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
tim johnston commented on JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis The problem still exists in 1.520, although the line of the exception has changed: 27-Jun-2013 10:43:45 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:244) 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] [matrix] (JENKINS-18164) Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
tim johnston created JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 31/May/13 8:44 PM Description: I have a top level job X. In X, I am using kicking off job Y using the File Parameter Factory option in parameterized builds. The configuration files contain a property, axis_values, which is a space separated list of different axis's for job Y. Let's say that job X has one configuration file and it contains axis_values=A B C. I kick off job X, which in turn kicks one instance of job Y. Job Y iterates correctly through A, B and C. Next, I change the configuration file and I set axis_values=A B C D E. I kick off job X and job Y starts. Job Y runs correctly for A, B and C. But, job Y fails to run D and E. It says that "D appears to be cancelled" and "E appears to be cancelled". I see the following in the log: 31-May-2013 3:57:48 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:238) The only workaround that I have found is that it will work correctly if I put the new values at the start of the axis. (ie. axis_values=D E A B C) List of (possibly) relevant plugins installed; dynamic axis environment injector jenkins parameterized trigger matrix sorter node and label parameter plugin Environment: Windows Project: Jenkins Priority: Critical Reporter: tim johnston 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-13817) Jenkins Displays Accurev Password in Logs
tim johnston created JENKINS-13817: -- Summary: Jenkins Displays Accurev Password in Logs Key: JENKINS-13817 URL: https://issues.jenkins-ci.org/browse/JENKINS-13817 Project: Jenkins Issue Type: Bug Components: accurev Affects Versions: current Environment: windows Reporter: tim johnston Assignee: Scott Tatum When an accurev command fails, it displays the users' password in plain text. You can see below that the password is properly obscured (with asterisks) when the authentication takes place. Unfortunately, the password is actually displayed in the fatal network error line. Note that I manually changed it to when I pasted the text into this bug report. Error text: Started by user anonymous Building remotely on TestReport in workspace D:\jenkins-slave\workspace\Test_Report_06_04_00_Budgeting_kvh223_WFOP_Macys_ora Purging workspace... Workspace purged. Setting ACCUREV_HOME to D:\jenkins-slave\workspace Authenticating with Accurev server... [Test_Report_06_04_00_Budgeting_kvh223_WFOP_Macys_ora] $ C:\Program Files (x86)\AccuRev\bin\accurev.exe login -H engaccurev:5051 tim.johnston FATAL: network error - Can't connect to engaccurev.kronos.com for accurev: The operation completed successfully. Attempt to contact AccuRev server on engaccurev port 5051 failed. Giving up. AccuRev Error: 1 FATAL: login (C:\Program Files (x86)\AccuRev\bin\accurev.exe login -H engaccurev:5051 tim.johnston ^^^) failed with exit code 1 Archiving artifacts Recording test results Notifying upstream projects of job completion Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
