Jenkins: Concurrent Build in jenkins template
I have two issues. 1. I'd like to be able to set up concurrentBuild to true in my job configuration. My aim as a result is to have job with checked option Execute concurrent builds if necessary. 2. Also I would like to have a unchecked option Restrict where this project can be run. In my code are used tags from website http://evgeny-goldin.com/wiki/Jenkins-maven-plugin Problem is appearing because for node 'concurrentBuild is throwing following exception: [ERROR] Failed to execute goal com.github.goldin:jenkins-maven-plugin:0.2.5:generate (generate-jenkins-jobs) on project srw-job-generator: Unable to parse configuration of mojo com.github.goldin:jenkins-maven-plugin:0.2.5:generate for parameter concurrentBuild: Cannot configure instance of com.github.goldin.plugins.jenkins.Job from false' No matter where this line will be placement the result is the same error. I also saw that the table 'job' from mentioned website not contain appriopriate tag associated with concurrentBuild and that is a problem. In another cases everything working as I expected (according with description from mentioned website). I try put concurrentBuild to section job but it not working. I have to set up this value for concurrentBuild to true by using my template. Below is a created job (mannualy). I would like to recive equal job by using my template. project actions/ description/ keepDependenciesfalse/keepDependencies properties/ scm class=hudson.scm.NullSCM/ canRoamtrue/canRoam disabledfalse/disabled blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding triggers/ concurrentBuildtrue/concurrentBuild builders/ publishers/ buildWrappers/ /project I can add that my job inherited from abstract job. My abstract job is below: job idAbstract_Job/id //My abstract JOB abstracttrue/abstract jobTypefree/jobType numToKeep20/numToKeep node/ jdkNamejdk1.6.0_26/jdkName scmTypenone/scmType /job and this is my pom: generationPomhttp://github.com/evgeny-goldin/maven-plugins-test/blob/master/jenkins-maven-plugin/standalone/pom.xml/generationPom Someone can help? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins Clearcase Plugin Not detecting changes and triggering continually on erroneous-ConfigSpec change detection
Hi Phil, Your load rule is incorrect. Indeed it should be relative to the view path, so start with the job name Le 20 mai 2014 20:40, Phil Lord lordph...@gmail.com a écrit : Vincent, Setting the view path per your suggestion improved things! Now the lshistory command displays the changes that occurred (as shown below), but the plugin reports No changes Phil Checking if there are changes in history [tester] $ cleartool lsview plord_HnwTester_working_view * plord_HnwTester_working_view \\pbympnas1\wc_ccs05_view1\WINT_NG\HARRIS\plord\plord_HnwTester_working_view.vws [tester] $ cleartool startview plord_HnwTester_working_view [plord_HnwTester_working_view] $ cleartool lshistory -all -since 20-may-14.18:18:22utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\ \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester 20140520.142136 lstarr01 M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\testprocedures\build10\TestCase_Build_10_4.java \main\dev3.0\38 create version checkin configureForCstStart now writes the CST configuration XML 20140520.142121 lstarr01 M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\TestCase.java \main\dev3.0\287 create version checkin configureForCstStart now writes the CST configuration XML Done. Took 2.4 sec No changes On Tuesday, May 20, 2014 8:24:43 AM UTC-4, Phil Lord wrote: Hi, I'm experiencing two issues using the Jenkins ClearCase plugin. It does not detect changes in the VOB and it continually triggers a build when the config spec specified in Jenkins does not match the config spec defined for the current View in ClearCase. See details below. Thanks in advance for your help!! Phil Jenkins 1.5.10 Jenkins-Clearcase Plugin 1.5 Windows 7 When Config spec field under Project-Configure-Soucre Code Managermen matches the config spec of the View Tag, the SCM Poll does not trigger a build, but when config spec of the View Tag does not match the Jenkins Project's config spec, a build is triggered each time the poll runs. See Base ClearCase Polling Logs below. The other issue is that changes to the ClearCase VOB are not being detected and/or build not triggered. If I enter the command found in the log (below), at the cleartool command line, it shows the files that were modified. lshistory -all -since 19-may-14.00:21:25utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\ \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_ view\wint_hat\Source\Test_Automation\HNW_Tester_ EclipseWorkspace\HNWTester\src\com\harris\hnw\tester When CONFIG SPECS DONT MATCH - Base ClearCase Polling Log Started on May 18, 2014 8:06:24 PM Checking if build is running Checking if a build has already happened Checking if revision state is known Checking if we have a build with a valid workspace *** get view CSPEC *** [tester] $ cleartool catcs -tag plord_HnwTester_working_view element * CHECKEDOUT # - LABEL #element * HNW_3.0_00.04.06 #element * HNW_3.0_00.06.09 # -AI BRANCH #element * .../dev3.0/ai0603/LATEST #element * /main/dev3.0/LATEST -mkbranch ai0603 # -PTR BRANCH #element * .../dev3.0/ptr0677/LATEST #element * /main/dev3.0/LATEST -mkbranch ptr0677 # - DEV BRANCH element * .../dev3.0/LATEST element * /main/LATEST -mkbranch dev3.0 #- MAIN LATEST -- element default_config_spec /main/LATEST element *.doc /main/LATEST element *.ppt /main/LATEST element *.xls /main/LATEST element *.mdb /main/LATEST element *.pdf /main/LATEST element *.mdl /main/LATEST element *.ptl /main/LATEST element *.cat /main/LATEST element *.vsd /main/LATEST element *.docx /main/LATEST element *.pptx /main/LATEST element *.xlsx /main/LATEST element /wint-ng/HNW/Bin/... /main/LATEST element /wint-ng/HNW/CFE/... /main/LATEST element /wint-ng/HNW/COTS/... /main/LATEST element /wint-ng/HNW/Tools/... /main/LATEST element /wint-ng/Test/... /main/LATEST element Documents/... /main/LATEST ** [WARNING] CSPEC configured != catcs (view) REASON: New config spec detected. Done. Took 0.28 sec Changes found When CONFIG SPECS DO MATCH - Base ClearCase Polling Log Started on May 18, 2014 8:26:24 PM Checking if build is running Checking if a build has already happened Checking if revision state is known Checking if we have a build with a valid workspace *** get view CSPEC *** [tester] $ cleartool catcs -tag plord_HnwTester_working_view element * CHECKEDOUT # - LABEL
Re: Jenkins Clearcase Plugin Not detecting changes and triggering continually on erroneous-ConfigSpec change detection
I meant vob name (stupid phone) Le 21 mai 2014 10:46, Vincent Latombe vincent.lato...@gmail.com a écrit : Hi Phil, Your load rule is incorrect. Indeed it should be relative to the view path, so start with the job name Le 20 mai 2014 20:40, Phil Lord lordph...@gmail.com a écrit : Vincent, Setting the view path per your suggestion improved things! Now the lshistory command displays the changes that occurred (as shown below), but the plugin reports No changes Phil Checking if there are changes in history [tester] $ cleartool lsview plord_HnwTester_working_view * plord_HnwTester_working_view \\pbympnas1\wc_ccs05_view1\WINT_NG\HARRIS\plord\plord_HnwTester_working_view.vws [tester] $ cleartool startview plord_HnwTester_working_view [plord_HnwTester_working_view] $ cleartool lshistory -all -since 20-may-14.18:18:22utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\ \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester 20140520.142136 lstarr01 M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\testprocedures\build10\TestCase_Build_10_4.java \main\dev3.0\38 create version checkin configureForCstStart now writes the CST configuration XML 20140520.142121 lstarr01 M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\TestCase.java \main\dev3.0\287 create version checkin configureForCstStart now writes the CST configuration XML Done. Took 2.4 sec No changes On Tuesday, May 20, 2014 8:24:43 AM UTC-4, Phil Lord wrote: Hi, I'm experiencing two issues using the Jenkins ClearCase plugin. It does not detect changes in the VOB and it continually triggers a build when the config spec specified in Jenkins does not match the config spec defined for the current View in ClearCase. See details below. Thanks in advance for your help!! Phil Jenkins 1.5.10 Jenkins-Clearcase Plugin 1.5 Windows 7 When Config spec field under Project-Configure-Soucre Code Managermen matches the config spec of the View Tag, the SCM Poll does not trigger a build, but when config spec of the View Tag does not match the Jenkins Project's config spec, a build is triggered each time the poll runs. See Base ClearCase Polling Logs below. The other issue is that changes to the ClearCase VOB are not being detected and/or build not triggered. If I enter the command found in the log (below), at the cleartool command line, it shows the files that were modified. lshistory -all -since 19-may-14.00:21:25utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\ \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_ view\wint_hat\Source\Test_Automation\HNW_Tester_ EclipseWorkspace\HNWTester\src\com\harris\hnw\tester When CONFIG SPECS DONT MATCH - Base ClearCase Polling Log Started on May 18, 2014 8:06:24 PM Checking if build is running Checking if a build has already happened Checking if revision state is known Checking if we have a build with a valid workspace *** get view CSPEC *** [tester] $ cleartool catcs -tag plord_HnwTester_working_view element * CHECKEDOUT # - LABEL #element * HNW_3.0_00.04.06 #element * HNW_3.0_00.06.09 # -AI BRANCH #element * .../dev3.0/ai0603/LATEST #element * /main/dev3.0/LATEST -mkbranch ai0603 # -PTR BRANCH #element * .../dev3.0/ptr0677/LATEST #element * /main/dev3.0/LATEST -mkbranch ptr0677 # - DEV BRANCH element * .../dev3.0/LATEST element * /main/LATEST -mkbranch dev3.0 #- MAIN LATEST -- element default_config_spec /main/LATEST element *.doc /main/LATEST element *.ppt /main/LATEST element *.xls /main/LATEST element *.mdb /main/LATEST element *.pdf /main/LATEST element *.mdl /main/LATEST element *.ptl /main/LATEST element *.cat /main/LATEST element *.vsd /main/LATEST element *.docx /main/LATEST element *.pptx /main/LATEST element *.xlsx /main/LATEST element /wint-ng/HNW/Bin/... /main/LATEST element /wint-ng/HNW/CFE/... /main/LATEST element /wint-ng/HNW/COTS/... /main/LATEST element /wint-ng/HNW/Tools/... /main/LATEST element /wint-ng/Test/... /main/LATEST element Documents/... /main/LATEST ** [WARNING] CSPEC configured != catcs (view) REASON: New config spec detected. Done. Took 0.28 sec Changes found When CONFIG SPECS DO MATCH - Base ClearCase Polling Log Started on May 18, 2014 8:26:24 PM Checking if build is running Checking if a build has already happened Checking if revision state is known Checking if we have a build with a valid workspace *** get view CSPEC
Jenkins variables+phing
Hey, If the user has not entered values to its variables, how jenkins can provides default values if someone has an idea please don't hesitate to help me. Best regards, HAJAR -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins Clearcase Plugin Not detecting changes and triggering continually on erroneous-ConfigSpec change detection
Vincent, You the man! It's working! I championed Jenkins and was getting a lot of unwanted viability due to it not working, but now they'll focus on the next fire. Thanks again Vincent! Ciao! Phil On Wednesday, May 21, 2014 4:47:29 AM UTC-4, Vincent Latombe wrote: I meant vob name (stupid phone) Le 21 mai 2014 10:46, Vincent Latombe vincent...@gmail.comjavascript: a écrit : Hi Phil, Your load rule is incorrect. Indeed it should be relative to the view path, so start with the job name Le 20 mai 2014 20:40, Phil Lord lord...@gmail.com javascript: a écrit : Vincent, Setting the view path per your suggestion improved things! Now the lshistory command displays the changes that occurred (as shown below), but the plugin reports No changes Phil Checking if there are changes in history [tester] $ cleartool lsview plord_HnwTester_working_view * plord_HnwTester_working_view \\pbympnas1\wc_ccs05_view1\WINT_NG\HARRIS\plord\plord_HnwTester_working_view.vws [tester] $ cleartool startview plord_HnwTester_working_view [plord_HnwTester_working_view] $ cleartool lshistory -all -since 20-may-14.18:18:22utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\ \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester 20140520.142136 lstarr01 M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\testprocedures\build10\TestCase_Build_10_4.java \main\dev3.0\38 create version checkin configureForCstStart now writes the CST configuration XML 20140520.142121 lstarr01 M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\TestCase.java \main\dev3.0\287 create version checkin configureForCstStart now writes the CST configuration XML Done. Took 2.4 sec No changes On Tuesday, May 20, 2014 8:24:43 AM UTC-4, Phil Lord wrote: Hi, I'm experiencing two issues using the Jenkins ClearCase plugin. It does not detect changes in the VOB and it continually triggers a build when the config spec specified in Jenkins does not match the config spec defined for the current View in ClearCase. See details below. Thanks in advance for your help!! Phil Jenkins 1.5.10 Jenkins-Clearcase Plugin 1.5 Windows 7 When Config spec field under Project-Configure-Soucre Code Managermen matches the config spec of the View Tag, the SCM Poll does not trigger a build, but when config spec of the View Tag does not match the Jenkins Project's config spec, a build is triggered each time the poll runs. See Base ClearCase Polling Logs below. The other issue is that changes to the ClearCase VOB are not being detected and/or build not triggered. If I enter the command found in the log (below), at the cleartool command line, it shows the files that were modified. lshistory -all -since 19-may-14.00:21:25utc+ -fmt '\%Nd\ \%u\ \%En\ \%Vn\ \%e\ \%o\ \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_ view\wint_hat\Source\Test_Automation\HNW_Tester_ EclipseWorkspace\HNWTester\src\com\harris\hnw\tester When CONFIG SPECS DONT MATCH - Base ClearCase Polling Log Started on May 18, 2014 8:06:24 PM Checking if build is running Checking if a build has already happened Checking if revision state is known Checking if we have a build with a valid workspace *** get view CSPEC *** [tester] $ cleartool catcs -tag plord_HnwTester_working_view element * CHECKEDOUT # - LABEL #element * HNW_3.0_00.04.06 #element * HNW_3.0_00.06.09 # -AI BRANCH #element * .../dev3.0/ai0603/LATEST #element * /main/dev3.0/LATEST -mkbranch ai0603 # -PTR BRANCH #element * .../dev3.0/ptr0677/LATEST #element * /main/dev3.0/LATEST -mkbranch ptr0677 # - DEV BRANCH element * .../dev3.0/LATEST element * /main/LATEST -mkbranch dev3.0 #- MAIN LATEST -- element default_config_spec /main/LATEST element *.doc /main/LATEST element *.ppt /main/LATEST element *.xls /main/LATEST element *.mdb /main/LATEST element *.pdf /main/LATEST element *.mdl /main/LATEST element *.ptl /main/LATEST element *.cat /main/LATEST element *.vsd /main/LATEST element *.docx /main/LATEST element *.pptx /main/LATEST element *.xlsx /main/LATEST element /wint-ng/HNW/Bin/... /main/LATEST element /wint-ng/HNW/CFE/... /main/LATEST element /wint-ng/HNW/COTS/... /main/LATEST element /wint-ng/HNW/Tools/... /main/LATEST element /wint-ng/Test/... /main/LATEST element Documents/... /main/LATEST ** [WARNING] CSPEC configured != catcs (view) REASON: New config spec detected. Done. Took 0.28 sec Changes found When CONFIG SPECS DO
4-5min delay at end of job on slave
We are experiencing a 4-5minute delay on a linux slave at the end of a job. We though it was sending mail but with or without the email step doesn't make a difference. It is not the 'Archiving artifacts' step because it usually takes 15-20s There is not step after the sending mail. The log entries below from different jobs will illustrate. *00:45:20.995* Archiving artifacts*00:45:37.263* Sending e-mails to: xox...@xoxoxoxoxo.xo*00:49:19.280* Finished: SUCCESS *00:18:05.538* Archiving artifacts*00:21:41.815* Finished: SUCCESS *00:44:13.036* Archiving artifacts*00:44:17.691* Checking for post-build*00:44:17.691* Performing post-build step*00:44:17.691* Checking if email needs to be generated*00:44:17.691* Email was triggered for: Success*00:44:17.691* Sending email for trigger: Success*00:44:17.691* Overriding default server settings, creating our own session*00:44:17.700* messageContentType = text/html; charset=UTF-8*00:44:17.702* Adding recipients from recipient list*00:44:17.704* Adding developers*00:44:17.704* Sending to requester*00:44:17.708* Successfully created MimeMessage*00:44:17.708* Sending email to: xox...@xoxoxoxoxo.xo*00:49:18.196* Finished: SUCCESS Does anyone have any ideas of what this can be? 5minutes dead time is causing headaches. Corneil -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: errors...with Clear Tool
I am now realizing the issue is with my load rule..I do not have global configurations set, because the view path constantly changes. Something I'm trying to get the devs to straighten out...but..I need some help with the load rules. Please help. On Tuesday, April 22, 2014 9:19:07 AM UTC-4, Chanda Norton wrote: I receive this error. Started by user anonymous http://localhost:8080/user/null Building remotely on Slave http://localhost:8080/computer/Slave in workspace c:\jenkins\workspace\test2 [_lexdev2_ClearCase_Stg_VIEW_TSGDEV_cnorton_niyah_view.vws] $ cleartool lsview -cview -s [INFO] computeChangeLogBeforeCheckout = false [INFO] computeChangeLogAfterCheckout = true [test2] $ cleartool lsview Niyah.vws cleartool: Error: No matching entries found for view tag Niyah.vws. FATAL: Base ClearCase failed. exit code=1 [test2] $ cleartool mkview -snapshot -tag Niyah.vws -vws null\Niyah.vws.vws _lexdev2_ClearCase_Stg_VIEW_TSGDEV_cnorton_niyah_view.vws cleartool: Error: storage directory must be in UNC style (e.g. \\host\share\...) FATAL: Base ClearCase failed. exit code=1java.io.IOException http://stacktrace.jenkins-ci.org/search?query=java.io.IOException: cleartool did not return the expected exit code. Command line=mkview -snapshot -tag Niyah.vws -vws null\Niyah.vws.vws _lexdev2_ClearCase_Stg_VIEW_TSGDEV_cnorton_niyah_view.vws, actual exit code=1 I have been trying to get this work for months...using Base Clear Case plugin.. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins daemon does not start correctly
This is not a bug (and actually might be lead to unexpected behavior on a lot of instances). Set your environment variables elsewhere, e.g. within Jenkins in the global and node configuration pages. On 21.05.2014, at 15:49, Sapientlife bpmi...@gmail.com wrote: Hi, Jenkins daemon is not starting up correctly. Looking at /etc/init.d/jenkins, it calls daemon from /etc/init.d/functions The daemon function does this: cgroup $nice runuser -s /bin/bash $user -c $corelimit /dev/null 21 ; $* If you look at the man page for runuser: -, -l, --login make the shell a login shell, uses runuser-l PAM file instead of default one, clears all envvars except for TERM, initializes HOME, SHELL, USER, LOGNAME and PATH Note that daemon does not add -login to the command. Without the -l runuser is not reading the .bash_profile of the jenkins user. Is there a fix for this because it is causing Jenkins to not launch builds with the correct environment variables. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins daemon does not start correctly
Hi Daniel, The problem I having though with this behavior is that when a build is started from the Jenkins GUI the shell that the build runs in does not get access to our SCM AccuRev no matter where we edit the environment variables .bashrc/.bash_profile, /etc/profile, /etc/sysconfig/jenkins ... On Wednesday, May 21, 2014 9:49:38 AM UTC-4, Sapientlife wrote: Hi, Jenkins daemon is not starting up correctly. Looking at /etc/init.d/jenkins, it calls “daemon” from “/etc/init.d/functions” The daemon function does this: cgroup $nice runuser -s /bin/bash $user -c $corelimit /dev/null 21 ; $* If you look at the man page for runuser: -, -l, --login make the shell a login shell, uses runuser-l PAM file instead of default one, clears all envvars except for TERM, initializes HOME, SHELL, USER, LOGNAME and PATH Note that daemon does not add –login to the command. Without the -l runuser is not reading the .bash_profile of the jenkins user. Is there a fix for this because it is causing Jenkins to not launch builds with the correct environment variables. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Reinstall jenkins (upgrade)...
We recently had an old Hudson-Jenkins install (running on Windows Server 2k8 R2) go bad (Jenkins service refusing to start - copying back war file did not resolve as it used to when this would happen) and were unable to resolve the issue. This installation pre-dates anyone currently on this project and I have to admit I am clueless as to how it is setup and works, so troubleshooting has been difficult. I installed a fresh version of Jenkins (windows installer, latest) and moved over our jobs folder but am not able to get packages to build. Jenkins starts, it sees the previous jobs and their properties seem intact, and Jenkins can see our SVN repositories and seems to be able to read them. However, when we try to build it just doesn't see changes and doesn't output any builds. I tried several means of 'upgrading' - installing new version fresh and moving over the jobs folder - installing new version on top of old version in its location, and various degrees of switching war files and other folders and files back on top of a new install. All yield the same result - Jenkins runs, sees the SVN repository, has the jobs info - but produces no builds. Any suggestions? If you had a bad install (old version, probably 2+ years) and wanted to just install fresh and move the stuff over what all needs to move (jobs folder, obviously ... but what else)? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: SVN Tagging Plugin Issue
Hello Keeps happening to me on Jenkins ver. 1.564 Em sexta-feira, 16 de maio de 2014 09h49min17s UTC-3, Rawad hajou escreveu: reply 2014-05-16 11:59 GMT+02:00 rwdolb [via Jenkins CI] [hidden email]http://user/SendEmail.jtp?type=nodenode=4701312i=0 : Hello Chris, I have the same problem when i try to tag a successful build. In fact i upgrade my svn plugin version from 1.39 to 2.3 Firstly i got the problem when job try to checkout/update (No credential to try. Authentication failed ). Then i set the credential and the problem was fixed. BUT, the tag problem isn't, i have always this problem (No credential to try. Authentication failed ) when i try to tag manually (tag this build link). Did you find a solution to your problem? Thanks a lot and please excuse for my bad English. chris.beech wrote Yeah, it did - I gave up in the end and installed Win32SVN (SVN v1.7) and now I can see what changes were made. I don't think Jenkins plays nice with SVN v1.8 which was VisualSVN. I still had the tagging problem in Win32SVN until I permitted anonymous read access, so there's something fishy still going on. The SVN Tagging Plugin says it's using the credentials stored as part of the SVN configuration but if that were the case I wouldn't be having any problems - Googling around others have also had problems so I think it's a plugin issue. Thanks, Chris -- If you reply to this email, your message will be added to the discussion below: http://jenkins-ci.361315.n4.nabble.com/SVN-Tagging-Plugin-Issue-tp4693946p4701294.html To unsubscribe from SVN Tagging Plugin Issue, click here. NAMLhttp://jenkins-ci.361315.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- Cordialement, Rawad HAJOU -- View this message in context: Re: SVN Tagging Plugin Issuehttp://jenkins-ci.361315.n4.nabble.com/SVN-Tagging-Plugin-Issue-tp4693946p4701312.html Sent from the Jenkins users mailing list archivehttp://jenkins-ci.361315.n4.nabble.com/Jenkins-users-f361316.htmlat Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Rewrote documentation for forwarding ports with iptables
I was setting up a new Jenkins instance this morning, and decided to go the route of running it on 8080/8443, and using iptables to forward 80-8080 and 443-8443. I found this page on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables However, it assumed some things, and left out some preliminary steps you may need to take. So, I rewrote the page in an attempt to be more thorough about what is required to get this kind of configuration working. I left the original page at the end of the document (the Alternate Solution section), in case my solution didn't work for someone and the previous one would. If someone that understands iptables configuration could glance over it and make sure everything looks correct, I would appreciate it. Hope it helps someone out there. -Scott -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins daemon does not start correctly
On 21.05.2014, at 17:52, Sapientlife bpmi...@gmail.com wrote: no matter where we edit the environment variables To explain what I meant by the following: within Jenkins in the global and node configuration pages Try to set them here if building on the master node: http://jenkins/configure Global properties » Environment variables Or here if building on a slave named foo: http://jenkins/computer/foo/configure Node Properties » Environment variables -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: (email-ext plugin) e-mail notification for new static analysis issues
Ah, thanks - that's what I was missing. --Ryan On Monday, 19 May 2014 12:14:34 UTC-4, slide wrote: If you click on the list of triggers to add, there should be a Script Trigger, add that and then define the groovy in the configuration for that trigger. Thanks, slide On Mon, May 19, 2014 at 9:12 AM, Ryan Shoemaker ryan.sh...@gmail.comjavascript: wrote: Hi, I'm trying to figure out how to configure the email-ext plugin to generate an e-mail whenever someone introduces a new static analysis issue (identified by findbugs, pmd, and checkstyle plugins). I found a mention of this on the static analysis plugin pagehttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-insand asked my question there, but Ulli suggested I try the group instead. The plugin page indicates that it is possible to add an email-ext trigger for new static analysis issues, but I can't figure out how to accomplish that. Here's a copy of my question on the wiki page: Can anyone provide more detail about how to accomplish this: In case you want to send notification emails to users introducing new warnings or violations but without failing a build you can use this groovy trigger script for the [Email-Ext Plug-in|]. I've got the Email-Ext plug-in installed and I can see where to add a post-build e-mail to my job and how to add a trigger, but I don't see where I'm supposed to specify the groovy trigger script. It seems like I've only got a specific set of pre-configured e-mail triggers to work with. Also, right now I'm using the static analysis core plugin with checkstyle, pmd, and findbugs, but not the analysis collector plugin. Thanks, --Ryan -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Reinstall jenkins (upgrade)...
Also, for the sake of adding more information - it looks like the original installation was done manually - there was a .hudson folder and Hudson folder in root of C: and a folder for ANT at C:\apache-ant-1.8.4 - before the 'clean' install I backed up all those then removed then - so now the clean install is at C:\Hudson. The old XML files from the previous installation (at what was C:Hudson) are shown below: https://lh6.googleusercontent.com/-b3ShbKy-udM/U3zp0POtS6I/CPY/E1w0B_tGU-Q/s1600/Hudson-Jenkins+XML.jpg (note shown, but there - Jenkins.xml, Hudson.xml, config.xml, and nodemonitor.xml) I am going to try moving all files form the old directory back on top of this fresh install leaving just the new jenkins.war and jenkins.exe - will advise but I believe I tried that already to no avail. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Reinstall jenkins (upgrade)...
OK, I fixed it by doing the following ... 1) Clean install of latest Jenkins to same location as old install (in my case C:\Hudson) 2) Shut down Jenkins service, deleted all files in C:Hudson (post install) 3) Restored all Hudson-Jenkins files/folders from my backup (C:\.Hudson, C:\Hudson, C:\apache-ant-1.8.4) 4) Started Jenkins service and working normally again. I am guessing that there is something the installer does, perhaps JAVA based, that manually uninstalling and reinstalling the service wasn't catching. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Getting error when trying to run perl script from Jenkins
Hi team, I am new to Jenkins and configured one job to trigger one automation perl script. Jenkins is configured and running from unix user named as Jenkins and this perl script is present in another user. Using ssh plugin to initiate it and getting below error: SSH: EXEC: connected x test_auto.pl, 149076 bytes, 292 tape blocks 458 INCREMENTAL NUM : 458 368 Can't locate pcmif.pm in @INC (@INC contains: . /usr/perl5/5.8.4/lib/sun4-solaris-64int /usr/perl5/5.8.4/lib /usr/perl5/site_perl/5.8.4/sun4-solaris-64int /usr/perl5/site_perl/5.8.4 /usr/perl5/site_perl /usr/perl5/vendor_perl/5.8.4/sun4-solaris-64int /usr/perl5/vendor_perl/5.8.4 /usr/perl5/vendor_perl) at ./test_auto.pl line 28. Can someone help me to find out reason why it is not able to find all environment variables which are already setup in another user. Why it is searching few files in these area? Seeking for quick answer or clue. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Spawned process is not killed
I run Jenkins 1.554.1 on Windows server. I found if I stopped one job manually, the spawned process is not killed. And when I re-run the job, some files are locked by the spawned process. But I found this document, Jenkins should already have the feature to kill spawned process, is there any advise to check the reason? thanks. https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Spawned-process-is-not-killed-tp4702936.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting error when trying to run perl script from Jenkins
Did the perl script work on its own.. I mean without Jenkins? Thanks, Subbu On Thu, May 22, 2014 at 5:19 AM, Vivek Jauhari vivekjauh...@gmail.comwrote: Hi team, I am new to Jenkins and configured one job to trigger one automation perl script. Jenkins is configured and running from unix user named as Jenkins and this perl script is present in another user. Using ssh plugin to initiate it and getting below error: SSH: EXEC: connected x test_auto.pl, 149076 bytes, 292 tape blocks 458 INCREMENTAL NUM : 458 368 Can't locate pcmif.pm in @INC (@INC contains: . /usr/perl5/5.8.4/lib/sun4-solaris-64int /usr/perl5/5.8.4/lib /usr/perl5/site_perl/5.8.4/sun4-solaris-64int /usr/perl5/site_perl/5.8.4 /usr/perl5/site_perl /usr/perl5/vendor_perl/5.8.4/sun4-solaris-64int /usr/perl5/vendor_perl/5.8.4 /usr/perl5/vendor_perl) at ./test_auto.plline 28. Can someone help me to find out reason why it is not able to find all environment variables which are already setup in another user. Why it is searching few files in these area? Seeking for quick answer or clue. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Add version and build number to Artifactory directory in repository
Thanks I have found the solution: release/=$JOB_NAME/build-$BUILD_NUMBER -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
