[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Willem Verstraeten commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) Igor: what do you mean with the 'fake working copy' option? I can find a 'custom workspace' option, is that it ? Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? 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
[JIRA] (JENKINS-15737) MultiJob plugin does not take account current parameters
Benjamin Kemper commented on JENKINS-15737 MultiJob plugin does not take account current parameters I have encountered this also on 1.6. Downgraded manually to 1.5 and it works fine. 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
[JIRA] (JENKINS-15831) Switch line colors in graph
Mickael Istria created JENKINS-15831 Switch line colors in graph Issue Type: Improvement Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 15/Nov/12 8:23 AM Description: Currently, on coverage trend graph, covered is red and missed is blue. However, on the class views (on both Jacoco Jenkins plugin, Jacoco HTML reports, Sonar...) and in general understanding, red usually means not-covered. So it would be better to switch color on graph, so red would means uncovered and blue would mean covered. Project: Jenkins Priority: Major Reporter: Mickael Istria 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
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d edited a comment on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ I think the change needed to be done in class WorkspaceList : /** * The token that combines the project name and unique number to create unique workspace directory. */ private static final String COMBINATOR = System.getProperty(WorkspaceList.class.getName(),"@"); 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
[JIRA] (JENKINS-15825) Exception not caught before saving build
vjuranek commented on JENKINS-15825 Exception not caught before saving build Changed priority, as this commits was reverted, see comment under https://github.com/jenkinsci/jenkins/commit/51f715162eba4dd1c4e081ec15c7ceb12e813ca5 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
[JIRA] (JENKINS-15825) Exception not caught before saving build
vjuranek updated JENKINS-15825 Exception not caught before saving build Change By: vjuranek (15/Nov/12 8:32 AM) Priority: Critical Trivial 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
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
Beat Morf commented on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly I am using Jenkins ver 1.489 and cppcheck plugin 1.11 and have the same issue! 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
Mads Nielsen commented on JENKINS-15821 Cannot install prqa-plugin Hey Frank, Any update on your issue? Did it help swtiching to the latest version. The errors you're seeing is somoething i've only seen happening when people have upgraded existing jenkins installations, starting from scratch with no existing jobs of prqa-type gives me no issues. Regards, Mads 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
[JIRA] (JENKINS-15832) Create Node by jenkinsapi return 500
Chen-Hsien Wu
created JENKINS-15832
Create Node by jenkinsapi return 500
Issue Type:
Bug
Assignee:
kalpanab
Components:
nodenamecolumn
Created:
15/Nov/12 8:54 AM
Description:
when using jenkinsapi(python) to create node, it always return "Status Code: 500
Exception: java.lang.NullPointerException"
So, I tried to use REST API by typing url, for example,
http://(baseurl)/jenkins/computer/doCreateItem?json={...}name=AAA
then I found that when name variable is given, status 500 occurred;
otherwise Jenkins shows a page to notify "name" is required.
Any suggestion for this?
Thanks a million
Environment:
Cent OS 6.3 x86_64
Project:
Jenkins
Priority:
Major
Reporter:
Chen-Hsien Wu
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
[JIRA] (JENKINS-15827) Exception if configuring an existing project
Harald Haß updated JENKINS-15827 Exception if configuring an existing project Change By: Harald Haß (15/Nov/12 9:48 AM) Priority: Major Critical 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
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
John McCabe commented on JENKINS-15801 Allow root of relative paths to be specified I had a look at https://issues.jenkins-ci.org/browse/JENKINS-14064 again after your comment @Ulli; I'd seen it before when I was searching for a possible solution. It's a similar issue but, as far as I can see, solving that would be a lot more difficult than this suggestion 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
XYZ commented on JENKINS-15821 Cannot install prqa-plugin Hello Mads, I tried the newest Version and it doesn't work again. You're right, I have upgraded the jenkins installation. I'll try now to reinstall Jenkins... 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
[JIRA] (JENKINS-15833) exception with latest Conditional buildstep plugin, with jenkins version 1.490
Oded Maimon commented on JENKINS-15833 exception with latest Conditional buildstep plugin, with jenkins version 1.490 i think this issue is related to this bug: https://issues.jenkins-ci.org/browse/JENKINS-6797 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
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Alex Klein commented on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Hi Henri, well, getting it all running took me a couple of days and a lot of research. Maybe it is related to my setup because I wanted the nodes to run on a windows server and have vboxwebsrv run as a scheduled task (so it gets fired up when the server is rebooted). As far as I get it, one has to: Create the node in Jenkins first (otherwise the java web start stuff later on won't work). Then manually (i.e. with GUI) launch the virtual box instance on the windows server In that instance go to jenkins webpage and then somewhere (forgot where) click on that link to get the java web start stuff installed within the virtual box. then shutdown the virtual machine and create the scheduled task to start vboxwebsrv One fun part is that when vboxwebsrv is started as a scheduled task, one will not see the UI at all (because it as run under the service account). So before setting up the scheduled task, one first has to get the JAVA web start up and running. Also, non of the other start up methods seemed to be able to connect from Jenkins to virtual box correctly! I always got the node to fire up the virtual box but never to actually start the build. I believe there were also problems as the scheduled task runs under the service account and therefore cannot access the usually virtualbox configuration folder (I remember something about having to create a virtual link). Also there seems to be no proper console output if the node is running in headless mode. Speaking of which, I did not find a proper explanation what the specific start up modes do. Plus there were some refresh issues where the vboxwebsrv was correctly detected but there were no machines in the list below it to select. I first had to save it without setting anything, then go back to the page and there the machine was suddenly listed. All in all, it was extremely difficult and frustrating! Granted, I haven't really done much with Jenkins before, but getting everything except for the virtualbox-plugin running was pretty easy. I hope to someday find the time to re-create all the steps at home and write a step-by-step guide and post it in my personal blog. But at my company, everything is working right now so I unfortunately don't have time to de-install everything just for the purpose of documentation. Alex 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Michael Clarke commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Could you attach your RLOG output as a text document please? 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
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) what do you mean with the 'fake working copy' option It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did to for having changes information on build's page. It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option. Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves 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
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko edited a comment on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) what do you mean with the 'fake working copy' option It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did to for having changes information on build's page. It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option. Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves - only master (on linux) is fine. 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
[JIRA] (JENKINS-14482) com.cloudbees.plugins.flow.JobExecutionFailureException
Orest Ivasiv commented on JENKINS-14482 com.cloudbees.plugins.flow.JobExecutionFailureException I have the same issue with Build Flow Plugin 0.5. In my case Job "Test1" ends with "Finished: FAILED" 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
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko edited a comment on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) what do you mean with the 'fake working copy' option It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did it for having changes information on build's page. It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option. Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves - only master (on linux) is fine. 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
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra commented on JENKINS-15309 NPE (isEmpty) from main.groovy What about authenticated? Do you have the JOB: DISCOVER permission set there? If so, try removing it 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
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley commented on JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. In this case, the upstream job was not run on the master but a slave. If you look at the screenshot of the job output, you will see the value of NODE_LABELS is not master, but the name of the slave which the job is running on. All of the other environment variables are correctly passed to the downstream job except this one. 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
[JIRA] (JENKINS-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Remi Carton commented on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) Same issue here on 1.489 / 1.490 with CVS. 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
XYZ commented on JENKINS-15821 Cannot install prqa-plugin Hello Mads, after reinstallation of Jenkins the plugin works. Thanks for your fast support. Regards, Frank BTW, I'am using QAC-8.0-R and QACPP-2.5.1-R. I can't found in the installation the tool "qaw". What does this tool? 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
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. I have the same issue with Jenkins 1.488. And it appears to be the same problem as JENKINS-12967. 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
Mads Nielsen commented on JENKINS-15821 Cannot install prqa-plugin Hey Frank, Qaw is a command line wrapper provided by PRQA we use it to generate reports and analysis. I'll direct them to this discussion, they should be able to help you get the tool so you can start using the plugin. Regards, Mads 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
[JIRA] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
fvck_u fvck_u commented on JENKINS-6890 clone-workspace-scm doesnt work when source job is a matrix job. I have 2 jobs in my stream, after the first one is completed the 2nd one fails with the same error: Building in workspace C:\Users\myname\.jenkins\workspace\MyJob02 ERROR: MyJob01's most recent build matching the criteria 'Any' doesn't have a workspace snapshot attached. Please run another build in MyJob01 to get the workspace snapshot generated and attached. Finished: FAILURE But when I check the build result: c:\Users\myname\.jenkins\jobs\MyJob01\configurations\builds\2012-11-14_15-46-11\workspace.tar.gz It seems that clone-workspace-scm searches the workspace.tar.gz archive in a wrong folder 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
[JIRA] (JENKINS-13039) Max # of builds to keep not deleting old builds
Thomas B commented on JENKINS-13039 Max # of builds to keep not deleting old builds Same issue here too. In addition job.logRotate() encounters "delete" exceptions on a few % of my build (it manages to delete the build but think it's still here ...) and since I've stacked 800+ builds (instead of 4) it's pretty enoying Using version Jenkins ver. 1.489 on Linux 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
[JIRA] (JENKINS-15716) Error loading class on slave
Jesse Glick resolved JENKINS-15716 as Duplicate Error loading class on slave Change By: Jesse Glick (15/Nov/12 4:24 PM) Status: Open Resolved Resolution: Duplicate 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
[JIRA] (JENKINS-6604) Possible race condition in RemoteClassLoader renders slave unusable
Jesse Glick commented on JENKINS-6604 Possible race condition in RemoteClassLoader renders slave unusable https://github.com/jenkinsci/remoting/pull/8 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
Jason Masters commented on JENKINS-15821 Cannot install prqa-plugin Hi Frank, I will send you download instructions for QAW (and QAR which is also required) in a separate email. QAW is a windows zip archive which you need to unzip somewhere (I suggest under the existing PRQA directory). QAR has a normal windows installer. Once installed you need to add the paths to these programs (for example C:\PRQA\qaw-2.3.2;c:\PRQA\QAR-1.2\bin ) to the path of the environment where Jenkins runs. Please let me know how you get on. Regards, Jason Masters PRQA 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
[JIRA] (JENKINS-15815) Shortcut to navigate between Next/Previous Build
jieryn commented on JENKINS-15815 Shortcut to navigate between Next/Previous Build 12:31:24 +jieryn : orrc: w/r/t JENKINS-15815 how about j/k n/v to move up and down in the list of builds, o to open 12:33:22 + orrc : jieryn: ah you mean from the job page? 12:33:29 +jieryn : the Build History box, make it orange background to indicate, just like within a view where j/k n/v move around the "active" job to do an action on 12:33:38 + orrc : jieryn: I was meaning that while I'm on the page build #3, it would be nice to have a single shortcut to move to #2 or #4 12:33:46 +jieryn : ah! 12:33:56 +jieryn : yep, that would be useful 12:33:59 + orrc : now that I read my JIRA, that wasn't so clear! 12:34:13 +jieryn : i think both of those ideas would be useful 12:34:19 + orrc : yeah :) 12:34:38 +jieryn : so if you are on a non-run page, it will do the view style to visually move you around in the BuildHistory, but if you are on a specific run, j/k n/v to move up and down in the list of all runs 12:34:54 + orrc : sounds good 12:35:00 +jieryn : ok, hope to try it this wknd, good idea :) 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
Re: [JIRA] (JENKINS-15778) SVN Options Failure after upgrading Jenkins
hello, Have you seen these and do they help resolve your issue please? http://issues.tmatesoft.com/issue/SVNKIT-176 http://trumaze.blogspot.com/2012/09/eclipse-svn-badrecordmac.html thanks mike tobias -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-15778-SVN-Options-Failure-after-upgrading-Jenkins-tp4645589p4646284.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
Farzad Valad commented on JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs The only AbstractCvs thing I see are four classes named AbstractCvs$1.class, AbstractCvs$2.class,... in the path jenkins\plugins\cvs\WEB-INF\classes\hudson\scm. Is it possible the problem is initializing the plugin and has nothing to do with jobs? I used to have CVS Plugin 1.6 then upgraded to 2.4 and then to 2.7. 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
[JIRA] (JENKINS-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
cjo9900 commented on JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. I think you have hit the issue that has already been fixed in commit https://github.com/jenkinsci/parameterized-trigger-plugin/commit/16586248c382ef417e0aaa1d2cdb00baee87ec18 which has not yet been released. Where the Environment variables are not correct, due to using the Dependancy Graph to trigger the downstream builds which always runs on master therefore gets the node labels from there, rather than from the slave that the job ran on. 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
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
CJ Barker updated JENKINS-15567 Ubuntu /etc/default/jenkins contains syntax error in sample command line arg Change By: CJ Barker (15/Nov/12 7:08 PM) URL: https://github.com/jenkinsci/jenkins/pull/619 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
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
CJ Barker resolved JENKINS-15567 as Fixed Ubuntu /etc/default/jenkins contains syntax error in sample command line arg See fix in github pull request #619 https://github.com/jenkinsci/jenkins/pull/619 Change By: CJ Barker (15/Nov/12 7:08 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
CJ Barker updated JENKINS-15567 Ubuntu /etc/default/jenkins contains syntax error in sample command line arg See fix in github pull request #619 https://github.com/jenkinsci/jenkins/pull/619 Change By: CJ Barker (15/Nov/12 7:07 PM) Assignee: CJBarker Fix Version/s: current Affects Version/s: current URL: https://github.com/jenkinsci/jenkins/pull/619 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
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
CJ Barker assigned JENKINS-15567 to Jerry Preissler Ubuntu /etc/default/jenkins contains syntax error in sample command line arg Pull request 619 pending approval. Assigned to reporter for verification. Change By: CJ Barker (15/Nov/12 7:10 PM) Assignee: CJBarker JerryPreissler 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
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
Pierre-Etienne Messier commented on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly My bad! I didn't notice that there is a second "Advanced..." button showing up when you first clicked on the first Advanced button! After checking the Graph configuration checkboxes, it works now! Suggestion: you should probably just add a paragraph on the Wiki to document how to configure the plugin and/or add some default configuration so that it shows lines! Thanks for your time! 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
[JIRA] (JENKINS-15834) It's not possible to specify multiple property files in parametrised trigger
cjo9900 created JENKINS-15834 Its not possible to specify multiple property files in parametrised trigger Issue Type: Bug Assignee: cjo9900 Components: parameterized-trigger Created: 15/Nov/12 7:11 PM Description: Due to the correction of JENKINS-8916, where only one type of parameter can be added at a time. It's not possible to specify multiple property files anymore. See comments in linked issue. Environment: Parameterized trigger 2.14+ on Jenkins ~1.480+ Project: Jenkins Priority: Major Reporter: cjo9900 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
[JIRA] (JENKINS-15525) ProjectSet parser isn't working
Ralf Eisele
reopened JENKINS-15525
ProjectSet parser isnt working
If the cvs module name contains a "-" then the regexp pattern fails. The following pattern corrects this:
private static final Pattern PSF_PATTERN = Pattern.compile("project reference=\"^,+,((:a-z+(a-z|A-Z|0-9|\\.+)" +
"(0-9+)?)?(/|a-z|A-Z|_|0-9+)),(/|A-Z|a-z|0-9|_|\\-|\\.+),(A-Z|a-z|0-9|_|\\-|\\.+)(,(.*?)){0,1}\"/");
Change By:
Ralf Eisele
(15/Nov/12 8:01 PM)
Resolution:
Fixed
Status:
Resolved
Reopened
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
[JIRA] (JENKINS-15525) ProjectSet parser isn't working
Ralf Eisele
edited a comment on JENKINS-15525
ProjectSet parser isnt working
If the cvs module name contains a "-" then the regexp pattern fails. The following pattern corrects this:
private static final Pattern PSF_PATTERN = Pattern.compile("project reference=\"[^,]+,((:[a-z]+:)([a-z|A-Z|0-9|\\.]+)" +
"(:([0-9]+)?)?([/|a-z|A-Z|_|0-9]+)),([/|A-Z|a-z|0-9|_|\\-|\\.]+),([A-Z|a-z|0-9|_|\\-|\\.]+)(,(.*?)){0,1}\"/");
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
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
Jerry Preissler edited a comment on JENKINS-15567 Ubuntu /etc/default/jenkins contains syntax error in sample command line arg Looks got to me. +1 and 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
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
Jerry Preissler assigned JENKINS-15567 to CJ Barker Ubuntu /etc/default/jenkins contains syntax error in sample command line arg Change By: Jerry Preissler (15/Nov/12 8:21 PM) Assignee: JerryPreissler CJBarker 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (15/Nov/12 9:36 PM) Attachment: Jenkins_console_build17_out.txt 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (15/Nov/12 9:37 PM) Attachment: rlog_of_solaris_cli.txt 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (15/Nov/12 9:37 PM) Attachment: Jenkins_console_build17_out.txt 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
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
jan_ruzicka commented on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly I run into same issue. Option under the second Advanced button are all checked. First time after changing configuration, the trend was showing historical data. The trend information disappeared after a new build finished. The cpp check plugin shows tabular information with a few cpp check findings. 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Attached 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
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
jan_ruzicka edited a comment on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly I run into same issue. Option under the second Advanced button are all checked. First time after changing configuration, the trend was showing historical data. The trend information disappeared after a new build finished. The cpp check plugin shows tabular information with a few cpp check findings. It actually looks fine now ... I don't know what happened. 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
[JIRA] (JENKINS-15835) Maven Dependecy Support
cforce created JENKINS-15835 Maven Dependecy Support Issue Type: New Feature Assignee: wolfs Components: depgraph-view Created: 15/Nov/12 10:26 PM Description: Please add new levele in tree, which shows maven artifacts and maven dependencies below jobs. Edges can show type of depedency (runtime, complie time,..) Project: Jenkins Priority: Major Reporter: cforce 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
[JIRA] (JENKINS-15836) Slave's Name should be trimmed of spaces at the beginning and end of the Name on Save
Brendan Brewster created JENKINS-15836 Slaves Name should be trimmed of spaces at the beginning and end of the Name on Save Issue Type: Improvement Affects Versions: current Assignee: Peter Hayes Attachments: Project Config.png Components: dashboard-view Created: 16/Nov/12 12:22 AM Description: Hello, thank you all for Jenkins. It is a wonderful project. We had one major problem setting up Jenkins that can be easily fixed: When you create a Slave and accidentally add a space at the end of the Name, it is impossible to tell by looking at the name that it contains whitespace. If you try to use the Slave's Name such as in a Label _expression_ when restricting where a project can be run, you are told "There's no slave/cloud that matches this assignment." It is very hard to work out that the problem is an extra space in the Slave's Name. You COULD enter the Slave's Name as "Blah " in the Label _expression_, but the real problem is you accidentally added a space to the name that should be removed. We believe there is no good reason to allow spaces at the end (or beginning?) of a Slave's Name and we request that you trim the Slave's Name of spaces when you Create and Save a Slave's configuration. Many thanks! Project: Jenkins Labels: slave Priority: Minor Reporter: Brendan Brewster 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
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Loren Keagle commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs I'm seeing a similar stack trace randomly. I can generally restart Jenkins and everything will be find for another day or so. Running 1.489 on Windows Server 2008, all 64 bit. Here's a snippet of the failure from the build log: Time Elapsed 00:04:10.80 Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure locks-and-latches Releasing all the locks locks-and-latches All the locks released Archiving artifacts Recording test results Processing tests results in file(s) BinaryFiles/Exe/*/_results.trx BinaryFiles\Exe\Win32\Debug\UnitTests\gui\test_results.trx BinaryFiles\Exe\Win32\Release\UnitTests\gui\test_results.trx Description set: ERROR: Publisher hudson.tasks.Mailer aborted due to exception java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #94 EXACT: lo=8,hi=0,size=9,size2=9 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:297) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1015) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1514) at hudson.model.User.getProjects(User.java:444) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:530) at hudson.tasks.MailSender.buildCulpritList(MailSender.java:407) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:367) at hudson.tasks.MailSender.createFailureMail(MailSender.java:226) at hudson.tasks.MailSender.getMail(MailSender.java:153) at hudson.tasks.MailSender.execute(MailSender.java:99) at hudson.tasks.Mailer.perform(Mailer.java:115) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1541) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Finished: FAILURE 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal updated JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Change By: Akhil Mittal (16/Nov/12 12:28 AM) Attachment: screen_shot.doc 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine I have found the cause of this behaviour - change log disappears if in SCM config of job "Show all CVS output" is checked to yes. As soon as I uncheck "Show all CVS output" I cant see any changes in the change log. I reckon what’s happening CVS update stdout is redirected to log if the box is checked otherwise CVS update stdout is getting parsed and chages are stripped off from cvs update log and put in the changelog. This is not the right behaviour as one expects verbose CVS update command with stdout stderr as is in the log without being doctored to reflect the true picture as well as the changes in the change log if you are checking show all cvs output box. I am building a build pipeline for CI deployment from dev - test - uat - staging - prod for a legacy app COBOL where each component is compiled to its own binary (i.e. for every foo.cbl there is foo.so) unlike Java where entire workspace is compiled package to a monolithic binary (.ear or .war etc). It's a component driven migration where there is need to compile only the programs updated by cvs and packaging only the updated components their corresponding binaries. For this I need to pass list of CVS updated components which I can get from CVS update log and pass it to the build script. I was hoping to see them as args passed to Shell in '$*' in post build but nothing there, as I think Jenkins concept is compile the entire workspace not a component driven migration. Also noticed that the warnings of warnings of cvs command are not displayed in the log regardless of box checked or not. Warnings of CVS update are important for situations where lot of components of repository becomes obsolete and you remove tag e.g PROD from them in cvs, next update will remove the obsoleted sources from the filesystem but you still need to know what sources are removed from the filesystem to delete components dependencies and binaries from the filesystem as they are not checked in CVS generally. eg. cvs update: warning: srcmgr/logs/blah.log is not (any longer) pertinent Long story short we should be able to see cvs update stdout/stderr as is returned by Shell in the log in verbose mode and needless to say changes in the change log. 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
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
Beat Morf commented on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly I had the same problem - didn't notice all configurations! Cheers 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
