Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed jobs from a build flow execution, not sure yet 2013/8/6 Bob Bick bb...@netjets.com Hi, ** ** The Jenkins Build Flow Plugin is replacing our “massive” home grown build system. ** ** A couple of times a year, our build team will create a Build Flow job from a template to perform the “massive” build which can last for several days. ** ** The build team will execute the Build Flow job until all sub-jobs have been successfully built. The build team can choose to build 50% of the jobs on a given day and then build the other 50% the next day (or however they decide to break it up)… That leads to my question…. I’d like to be able to inform the builders which sub-jobs have been completed within the context of the massive Build Flow job. Currently, that information is written to the Console Log as shown below: ** ** ## ###RESULTS ### ## SUCCESS : JOB1 JOB2 JOB3 SKIPPED : NAF_WPF_NET ABORTED : FAILURE : GERMAINE UNSTABLE : NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET ## ###END RESULTS ### ## ** ** Currently, the build team must scan all the console logs in order to determine what has/has not been built, and to figure out what they still need to build. This is difficult for them since there are about 50 different projects that must be built. I am trying to find a solution that would allow them to determine what still needs to be built. Here are a couple of ideas: ** ** **1) **In the “Build History”, change the job names to include all of the sub-jobs that were successfully built for that job run (e.g. change “#21” to “#21 JOB1 JOB2 JOB3”). But, I don’t think there is a way to do that for Build Flow jobs. Does anyone know if this is possible? **2) **Write a shell script that reads the console log files. However, this is a poor solution since it does not integrate with Jenkins (i.e. run some script outside of Jenkins). **3) **Other??? ** ** Q. Can anyone think of a good way to report all of the sub-jobs that have successfully completed within the context of multiple Build Flow job runs? ** ** Thank you for taking the time to read this. ** ** Bob *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Is there a way to make discard old builds happen right now?
What version of Jenkins are you using?
On 07.08.2013, at 06:24, David Vree david.h.v...@gmail.com wrote:
This worked for me except for one thing. In a multi-module Maven project the
child modules still have all their builds on the filesystem, even though they
are gone in the UI.
On Friday, October 7, 2011 6:58:50 PM UTC-4, jdhein wrote:
On Oct 7, 4:11 am, Christopher Orr ch...@orr.me.uk wrote:
On 06/10/11 21:19, jdhein wrote:
My organization has just tons of projects in Jenkins, many of which
are not active and have not built in some time, some of them haven't
built in over 17 months. I have gone through and turned on discard
old builds with a max of 10 builds. However, it has been weeks since
changing this setting and Jenkins has not deleted the excess builds. I
am guessing I have to poke the bear by kicking off a build... only, I
don't want to do this for projects I am not directly involved with.
Is there a way to tell Jenkins to go ahead and discard the old builds
right now?
You can use the Script Console to fetch the jobs you want, and then call
logRotate() on each of them.
Probably something like this should work, not that I've tested it:
for(job in Hudson.instance.items) {
job.logRotate()
}
Take a look at the examples on the wiki for more info, and if you come
up with something good, you can add it to the
list:https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console
Regards,
Chris
Thanks, the groovy script you gave me worked like a champ with the
only change I made being to add an import:
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
Honestly, without the groovy script you gave me I would not have been
able to come up with this without investing a bunch of time
researching how Jenkins works and how to write groovy scripts. So
thanks a bunch!
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: User account considered for execution
You configured authentication to the Jenkins UI. It has nothing to do with the user account jobs are run as, which is the same account who is running Jenkins' java process. If you installed it as a service on Windows and didn't change it in Computer Management, Jenkins is running as SYSTEM. As to access permissions for the files created by Jenkins -- it's basic Windows NTFS permissions. On 07.08.2013, at 06:58, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Richard, Thanks for reply, I am bit confused again. - Consider I Logged-In to Jenkins with User account Test1 (this account is not existed on network). - When job is called, batch script will create folders remove. But Test1 doesn't have permissions (this user itself not existed on the system). Will this be successful execution if yes considering which user Jenkins created the folders? I tried this on windows, but who ever user logged in the create and deletion of folders is successful. - Started by user test user Building in workspace C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspace [workspace] $ cmd /c call C:\Windows\TEMP\hudson7256762012989360322.bat C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho Test Call from Jenkins Test Call from Jenkins C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho user executing - user executing - C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacemkdir c:\JenkinsCreatedFolder C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacermdir c:\JenkinsCreatedFolder1 C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceexit 0 Finished: SUCCESS - Thanks, Rudra On 7 August 2013 10:16, Richard Bywater rich...@byh2o.com wrote: If you are referring to which user will the shell execution happen under, it will be the user which Jenkins is running as. Richard. On Wed, Aug 7, 2013 at 4:32 PM, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/tqc-8EytDmc/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Selenium plugin with Maven projects
Hi all, I've to configure jobs of Maven projects running Selenium tests. I've found Selenium Plugin https://wiki.jenkins-ci.org/display/JENKINS/Selenium+Pluginbut I'm not able to found a reason to use it. Why use this plugin instead of configure jobs to build on slaves via labels (firefox, chrome or ie8 for instance) depending of build parameters ? Maybe I misunderstood something ? Is this plugin essential in case of Maven projects launching Selenium tests ? Thanks in advance. Michaël Pailloncy -- 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/groups/opt_out.
Re: User account considered for execution
Thanks Daniel, Got the point now. Thanks, Rudra On 7 August 2013 12:47, Daniel Beck m...@beckweb.net wrote: You configured authentication to the Jenkins UI. It has nothing to do with the user account jobs are run as, which is the same account who is running Jenkins' java process. If you installed it as a service on Windows and didn't change it in Computer Management, Jenkins is running as SYSTEM. As to access permissions for the files created by Jenkins -- it's basic Windows NTFS permissions. On 07.08.2013, at 06:58, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Richard, Thanks for reply, I am bit confused again. - Consider I Logged-In to Jenkins with User account Test1 (this account is not existed on network). - When job is called, batch script will create folders remove. But Test1 doesn't have permissions (this user itself not existed on the system). Will this be successful execution if yes considering which user Jenkins created the folders? I tried this on windows, but who ever user logged in the create and deletion of folders is successful. - Started by user test user Building in workspace C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspace [workspace] $ cmd /c call C:\Windows\TEMP\hudson7256762012989360322.bat C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho Test Call from Jenkins Test Call from Jenkins C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho user executing - user executing - C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacemkdir c:\JenkinsCreatedFolder C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacermdir c:\JenkinsCreatedFolder1 C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceexit 0 Finished: SUCCESS - Thanks, Rudra On 7 August 2013 10:16, Richard Bywater rich...@byh2o.com wrote: If you are referring to which user will the shell execution happen under, it will be the user which Jenkins is running as. Richard. On Wed, Aug 7, 2013 at 4:32 PM, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/tqc-8EytDmc/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/tqc-8EytDmc/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: User account considered for execution
Hi Daniel, Really appreciate the quick response. Just to get some more clarification regarding this, This is for Linux environment. (Didn't have enough resources to test) - The Jenkins server is started on Linux by User XYZ. - But repository is located on shared drive (\\sharedhost\sharedRepository) and not on linux file system. My understanding is, User XYZ should have permission to shared drive (\\sharedhost\sharedRepository) to checkout code and create builds. Correct me if I am wrong. Thanks, Rudra On 7 August 2013 12:59, Raghava Rudrakanth P V potturu.ru...@gmail.comwrote: Thanks Daniel, Got the point now. Thanks, Rudra On 7 August 2013 12:47, Daniel Beck m...@beckweb.net wrote: You configured authentication to the Jenkins UI. It has nothing to do with the user account jobs are run as, which is the same account who is running Jenkins' java process. If you installed it as a service on Windows and didn't change it in Computer Management, Jenkins is running as SYSTEM. As to access permissions for the files created by Jenkins -- it's basic Windows NTFS permissions. On 07.08.2013, at 06:58, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Richard, Thanks for reply, I am bit confused again. - Consider I Logged-In to Jenkins with User account Test1 (this account is not existed on network). - When job is called, batch script will create folders remove. But Test1 doesn't have permissions (this user itself not existed on the system). Will this be successful execution if yes considering which user Jenkins created the folders? I tried this on windows, but who ever user logged in the create and deletion of folders is successful. - Started by user test user Building in workspace C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspace [workspace] $ cmd /c call C:\Windows\TEMP\hudson7256762012989360322.bat C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho Test Call from Jenkins Test Call from Jenkins C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceecho user executing - user executing - C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacemkdir c:\JenkinsCreatedFolder C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspacermdir c:\JenkinsCreatedFolder1 C:\Program Files (x86)\Jenkins_1\jobs\TestCallByTestUser\workspaceexit 0 Finished: SUCCESS - Thanks, Rudra On 7 August 2013 10:16, Richard Bywater rich...@byh2o.com wrote: If you are referring to which user will the shell execution happen under, it will be the user which Jenkins is running as. Richard. On Wed, Aug 7, 2013 at 4:32 PM, Raghava Rudrakanth P V potturu.ru...@gmail.com wrote: Hi Team, I am new user of Jenkins and have a question. 1. I created job which executes the shell script. 2. Configured users using Jenkins own database and was able to login to Jenkins and execute the job. Now when the shell execution is happening which User is considered for execution? - Is this going to be login user? if yes do this user credentials should match the credentials of the enterprise user.? - Is this going to be the user who installed Jenkins? or by default will it be administrator. Thanks in advance for help. Thanks, Rudra -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/tqc-8EytDmc/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/tqc-8EytDmc/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group.
Re: Checkstyle apparently totally broken
I think the root cause is https://issues.jenkins-ci.org/browse/JENKINS-18654 It is already fixed in Jenkins core. Ulli Am 07.08.2013 um 00:43 schrieb fREW Schmidt fri...@gmail.com: Right, I have not instaled Maven, though I'll try it tomorrow and see if it fixes the problem I guess. On Tue, Aug 06, 2013 at 09:37:46PM +0200, Daniel Beck wrote: According to the wiki [1, 2], Maven plugin is an _optional_ dependency of both Checkstyle and its (only, besides Ant) mandatory dependency, Analysis Core. Is this information correct? So far, JENKINS-18922/19000 seemed to only happen when missing mandatory dependencies, like jobConfigHistory - Maven... 1: https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin#CheckstylePlugin-PluginInformation 2: https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-PluginInformation -- fREW Schmidt http://blog.afoolishmanifesto.com signature.asc Description: Message signed with OpenPGP using GPGMail
RE: trigger a build ONLY when there has been a M2_RELEASEBUILD
Currently there is no simple way, hoiwever I think you can achieve what you want with the following: 1) use a URLtrigger (XTrigger plugin) on latestRelease permalink and inspect the content to cause job B to run. 2) use a RunParameter on job B to get the parameters from the release build (I have not tried this). From https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build * To use a Run Parameter, the value should be in the format jobname#buildNumber (eg. MyRunParam=foo-job%2399 for foo-job #99) /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maven User Sent: 06 August 2013 22:26 To: jenkinsci-users@googlegroups.com Subject: trigger a build ONLY when there has been a M2_RELEASEBUILD I think I may be over engineering this one a bit (headed to post-build groovy scripting hell), but I was wondering - is there an easy way to trigger another build (with two parameters from the release plugin) when a maven release has been triggered? For instance, when you run the maven release plugin on job A, I want to call job B only if A was both successful AND if it if IS_M2RELEASEBUILD is true. I looked at all sorts of things but wondering if there's something off the shelf I can use before going back to groovy... Thanks! -- 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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Jenkins wrong output and failures
When running my tests on jenkins they fail RANDOMLY.
I made some research and I found out that the tests which fail are those
which are contained by classes with MORE THAN 4 testcases.
my test suites look like this:
class FooTest extends GenericTest {
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
}
i have 10 test classes (test suites) which contain 4 tests, one contains 5
and one 6 tests and the tests which fail are contained by the classes with
more than 4 tests.
If i remove 3 tests and all classes contain maximum 4 tests everything is
ok.
I want to know if is there any method to solve this problem avoiding
creating a new suite for the tests which are over the 4 ones.
Thank you,
Alexandra Sandulescu
--
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/groups/opt_out.
RE: Jenkins wrong output and failures
Remember that tests are not always run in the order in which they appear in the
source. My guess is that your tests are not independent, and that if they run
in a certain order, an earlier test leaves some state that causes a later test
to fail.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Alexandra Sandulescu
Sent: 07 August 2013 11:01
To: jenkinsci-users@googlegroups.com
Subject: Jenkins wrong output and failures
When running my tests on jenkins they fail RANDOMLY.
I made some research and I found out that the tests which fail are those which
are contained by classes with MORE THAN 4 testcases.
my test suites look like this:
class FooTest extends GenericTest {
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
}
i have 10 test classes (test suites) which contain 4 tests, one contains 5 and
one 6 tests and the tests which fail are contained by the classes with more
than 4 tests.
If i remove 3 tests and all classes contain maximum 4 tests everything is ok.
I want to know if is there any method to solve this problem avoiding creating a
new suite for the tests which are over the 4 ones.
Thank you,
Alexandra Sandulescu
--
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.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If you
are not the intended addressee or an authorised recipient of the addressee
please notify us of receipt by returning the e-mail and do not use, copy,
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not
necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments
are free from viruses and we cannot accept liability for any damage which you
may sustain as a result of software viruses which may be transmitted in or with
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and
Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
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/groups/opt_out.
Re: Jenkins wrong output and failures
Especially in Java 7 onwards...
On Wed, Aug 7, 2013 at 10:11 PM, matthew.web...@diamond.ac.uk wrote:
Remember that tests are not always run in the order in which they appear
in the source. My guess is that your tests are not independent, and that if
they run in a certain order, an earlier test leaves some state that causes
a later test to fail.
** **
*From:* jenkinsci-users@googlegroups.com [mailto:
jenkinsci-users@googlegroups.com] *On Behalf Of *Alexandra Sandulescu
*Sent:* 07 August 2013 11:01
*To:* jenkinsci-users@googlegroups.com
*Subject:* Jenkins wrong output and failures
** **
When running my tests on jenkins they fail RANDOMLY.
I made some research and I found out that the tests which fail are those
which are contained by classes with MORE THAN 4 testcases.
my test suites look like this:
class FooTest extends GenericTest {
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
}
i have 10 test classes (test suites) which contain 4 tests, one contains 5
and one 6 tests and the tests which fail are contained by the classes with
more than 4 tests.
If i remove 3 tests and all classes contain maximum 4 tests everything is
ok.
I want to know if is there any method to solve this problem avoiding
creating a new suite for the tests which are over the 4 ones.
Thank you,
Alexandra Sandulescu
--
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/groups/opt_out.
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If
you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: Jenkins wrong output and failures
Thank you for your answer.
All tests are run in an independent driver. and they are parallel by class.
What is interesting is that nothing goes wrong but a random test from the
classes with more than 4 methods.
Alexandra
miercuri, 7 august 2013, 13:13:24 UTC+3, Richard Bywater a scris:
Especially in Java 7 onwards...
On Wed, Aug 7, 2013 at 10:11 PM, matthew...@diamond.ac.uk
javascript:wrote:
Remember that tests are not always run in the order in which they
appear in the source. My guess is that your tests are not independent, and
that if they run in a certain order, an earlier test leaves some state that
causes a later test to fail.
** **
*From:* jenkins...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] *On Behalf Of *Alexandra
Sandulescu
*Sent:* 07 August 2013 11:01
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Jenkins wrong output and failures
** **
When running my tests on jenkins they fail RANDOMLY.
I made some research and I found out that the tests which fail are those
which are contained by classes with MORE THAN 4 testcases.
my test suites look like this:
class FooTest extends GenericTest {
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
@Test
public void Test1{ /* stuff*/}
}
i have 10 test classes (test suites) which contain 4 tests, one contains
5 and one 6 tests and the tests which fail are contained by the classes
with more than 4 tests.
If i remove 3 tests and all classes contain maximum 4 tests everything is
ok.
I want to know if is there any method to solve this problem avoiding
creating a new suite for the tests which are over the 4 ones.
Thank you,
Alexandra Sandulescu
--
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/groups/opt_out.
--
This e-mail and any attachments may contain confidential, copyright and
or privileged material, and are for the use of the intended addressee only.
If you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
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/groups/opt_out.
--
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/groups/opt_out.
Slow loading and large memory usage after 1.480.3 to 1.509.2 migration
Hello guys, I used to run a Jenkins server with about 10 jobs with full history (~ 500 builds). Debian Wheezy OpenJDK 1.7b25 Tomcat 6 In 1.480.3 Loading time was decent (1min) and memory usage as 1GB. Server start - wait for 1 min - login - dashboard After updating WAR to 1.509.2 and all plugins to latest version (like dashboard to 2.8) Loading time is horrible (10min) and memory usage is about 4.5GB Server start - wait for 5 sec - login - wait for 10 min - dashboard Navigation is faster, it seems that all data is in memory ... I have to get back to 1.480.3 because such loading time and memory consumption is not acceptable. -- 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/groups/opt_out.
[NOTICE] Credentials, SSH Credentials, SSH Agent and SSH Slaves
As part of my improvements to the Credentials plugin I am pushing a whole new set of releases of these plugins. Credentials 1.6 is backwards compatible with all previous releases. It should be safe to upgrade that one on its own. SSH Credentials 1.0 requires Credentials 1.6 and includes a change to the on-disk data format. The consequence of this is that if you upgrade to SSH Credentials 1.0 you may loose credentials if you subsequently decide you made a mistake and decide to revert back to an earlier version... this is because the SSHUserPassword credentials have been migrated to the new StandardUsernamePasswordCredentials type in Credentials 1.6. This plugin is a new Major Version due to the deprecation of quite a few methods and classes. Note that if you do not upgrade SSH Slaves to a release that uses the new method signatures you may find that the Username/password credentials cannot be located. SSH Agent 1.2 requires SSH Credentials 1.0 and Credentials 1.6 but has no other impact. SSH Slaves 1.0 requires SSH Credentials 1.0 and Credentials 1.6. Given that this plugin is widely used, it advertises a change to the on-disk data format (despite there technically not being any) to prevent people accidentally upgrading without being aware that there is a potential impact (namely the changes in SSH Credentials 1.0) This version gets a new Major Version due to the major version change of SSH Credentials. I have done quite a bit of testing, and I am quite confident that the changes are safe... *but* you need to jump with all of them in one go, in other words IF you upgrade either of SSH Slaves or SSH Credentials to 1.0 you MUST ENSURE the other is upgraded also. Thanks for listening -Stephen -- 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/groups/opt_out.
IOException: Unable to delete when building
Hi, having trouble with a build, the first one worked fine. After that i renamed my build and now i always get this error: Building in workspace /var/lib/jenkins/jobs/sit/workspace java.io.IOException: Unable to delete /usr/bin/tsort at hudson.Util.deleteFile(Util.java:255) at hudson.Util.deleteRecursive(Util.java:307) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:298) at hudson.FilePath$12.invoke(FilePath.java:1062) at hudson.FilePath$12.invoke(FilePath.java:1059) at hudson.FilePath.act(FilePath.java:906) at hudson.FilePath.act(FilePath.java:879) at hudson.FilePath.deleteRecursive(FilePath.java:1059) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.model.JDK.forNode(JDK.java:126) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:356) at hudson.model.Run.getEnvironment(Run.java:2071) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:408) at hudson.model.AbstractProject.checkout(AbstractProject.java:1406) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) [PMD] Skipping publisher since build result is FAILURE Finished: FAILURE does anyone know how to resolve this? Jenkins v1.526, Linux Debian -- 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/groups/opt_out.
Re: IOException: Unable to delete when building
Not sure if this is the issue, but I have seen similar cases when I have been inside of the workspace path somewhere when trying to build. In other words if any user is currently looking at that workspace, the build won't be able to delete. - Original Message - From: Justinas Urbanavicius justin...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Wednesday, August 7, 2013 8:09:25 AM Subject: IOException: Unable to delete when building Hi, having trouble with a build, the first one worked fine. After that i renamed my build and now i always get this error: Building in workspace /var/lib/jenkins/jobs/sit/workspace java.io.IOException: Unable to delete /usr/bin/tsort at hudson.Util.deleteFile(Util.java:255) at hudson.Util.deleteRecursive(Util.java:307) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:298) at hudson.FilePath$12.invoke(FilePath.java:1062) at hudson.FilePath$12.invoke(FilePath.java:1059) at hudson.FilePath.act(FilePath.java:906) at hudson.FilePath.act(FilePath.java:879) at hudson.FilePath.deleteRecursive(FilePath.java:1059) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.model.JDK.forNode(JDK.java:126) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:356) at hudson.model.Run.getEnvironment(Run.java:2071) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:408) at hudson.model.AbstractProject.checkout(AbstractProject.java:1406) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) [PMD] Skipping publisher since build result is FAILURE Finished: FAILURE does anyone know how to resolve this? Jenkins v1.526, Linux Debian -- 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/groups/opt_out . -- 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/groups/opt_out.
Re: IOException: Unable to delete when building
yeah, i was in the workspace folder, but after cd /root didn't work even tried closing ssh client to server it didn't help On Wed, Aug 7, 2013 at 4:21 PM, k.thiel...@comcast.net wrote: Not sure if this is the issue, but I have seen similar cases when I have been inside of the workspace path somewhere when trying to build. In other words if any user is currently looking at that workspace, the build won't be able to delete. -- *From: *Justinas Urbanavicius justin...@gmail.com *To: *jenkinsci-users@googlegroups.com *Sent: *Wednesday, August 7, 2013 8:09:25 AM *Subject: *IOException: Unable to delete when building Hi, having trouble with a build, the first one worked fine. After that i renamed my build and now i always get this error: Building in workspace /var/lib/jenkins/jobs/sit/workspace java.io.IOException: Unable to delete /usr/bin/tsort at hudson.Util.deleteFile(Util.java:255) at hudson.Util.deleteRecursive(Util.java:307) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:298) at hudson.FilePath$12.invoke(FilePath.java:1062) at hudson.FilePath$12.invoke(FilePath.java:1059) at hudson.FilePath.act(FilePath.java:906) at hudson.FilePath.act(FilePath.java:879) at hudson.FilePath.deleteRecursive(FilePath.java:1059) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.model.JDK.forNode(JDK.java:126) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:356) at hudson.model.Run.getEnvironment(Run.java:2071) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:408) at hudson.model.AbstractProject.checkout(AbstractProject.java:1406) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) [PMD] Skipping publisher since build result is FAILURE Finished: FAILURE does anyone know how to resolve this? Jenkins v1.526, Linux Debian -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/__bR8pK4j5A/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Justinas -- 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/groups/opt_out.
RE: IOException: Unable to delete when building
Is the problem that you want to delete /usr/bin/tsort and can't, or that your build is trying to do that in the first place? Unless you're actually building an operating system, deleting stuff in /usr/bin sounds like a dangerous build step, and would normally require you to run as the root user. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Justinas Urbanavicius Sent: Wednesday, August 07, 2013 9:29 AM To: jenkinsci-users@googlegroups.com Subject: Re: IOException: Unable to delete when building yeah, i was in the workspace folder, but after cd /root didn't work even tried closing ssh client to server it didn't help On Wed, Aug 7, 2013 at 4:21 PM, k.thiel...@comcast.netmailto:k.thiel...@comcast.net wrote: Not sure if this is the issue, but I have seen similar cases when I have been inside of the workspace path somewhere when trying to build. In other words if any user is currently looking at that workspace, the build won't be able to delete. From: Justinas Urbanavicius justin...@gmail.commailto:justin...@gmail.com To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Sent: Wednesday, August 7, 2013 8:09:25 AM Subject: IOException: Unable to delete when building Hi, having trouble with a build, the first one worked fine. After that i renamed my build and now i always get this error: Building in workspace /var/lib/jenkins/jobs/sit/workspace java.io.IOException: Unable to delete /usr/bin/tsort at hudson.Util.deleteFile(Util.java:255) at hudson.Util.deleteRecursive(Util.java:307) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:298) at hudson.FilePath$12.invoke(FilePath.java:1062) at hudson.FilePath$12.invoke(FilePath.java:1059) at hudson.FilePath.act(FilePath.java:906) at hudson.FilePath.act(FilePath.java:879) at hudson.FilePath.deleteRecursive(FilePath.java:1059) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.model.JDK.forNode(JDK.java:126) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:356) at hudson.model.Run.getEnvironment(Run.java:2071) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:408) at hudson.model.AbstractProject.checkout(AbstractProject.java:1406) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) [PMD] Skipping publisher since build result is FAILURE Finished: FAILURE does anyone know how to resolve this? Jenkins v1.526, Linux Debian -- 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.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/__bR8pK4j5A/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Justinas -- 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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you
Crash Dump of Unit Tests
Hi Is there a plugin to get a Crash Dump of a crashed job? If we run our Unit tests and they crash it would be nice if we could get a Crash Dump of this process. We run Jenkins on a Windows Server 2008 R2. Only Delphi and C# Jobs. Thanks for your help! Regards. -- 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/groups/opt_out.
Re: IOException: Unable to delete when building
Possible session stuck open? Maybe try a reboot of the build machine if possible? If you delete the workspace manually, will it then build, and then rebuild? - Original Message - From: Justinas Urbanavicius justin...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Wednesday, August 7, 2013 8:29:15 AM Subject: Re: IOException: Unable to delete when building yeah, i was in the workspace folder, but after cd /root didn't work even tried closing ssh client to server it didn't help On Wed, Aug 7, 2013 at 4:21 PM, k.thiel...@comcast.net wrote: Not sure if this is the issue, but I have seen similar cases when I have been inside of the workspace path somewhere when trying to build. In other words if any user is currently looking at that workspace, the build won't be able to delete. From: Justinas Urbanavicius justin...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Wednesday, August 7, 2013 8:09:25 AM Subject: IOException: Unable to delete when building Hi, having trouble with a build, the first one worked fine. After that i renamed my build and now i always get this error: blockquote Building in workspace /var/lib/jenkins/jobs/sit/workspace java.io.IOException: Unable to delete /usr/bin/tsort at hudson.Util.deleteFile(Util.java:255) at hudson.Util.deleteRecursive(Util.java:307) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:298) at hudson.FilePath$12.invoke(FilePath.java:1062) at hudson.FilePath$12.invoke(FilePath.java:1059) at hudson.FilePath.act(FilePath.java:906) at hudson.FilePath.act(FilePath.java:879) at hudson.FilePath.deleteRecursive(FilePath.java:1059) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.model.JDK.forNode(JDK.java:126) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:356) at hudson.model.Run.getEnvironment(Run.java:2071) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:408) at hudson.model.AbstractProject.checkout(AbstractProject.java:1406) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) [PMD] Skipping publisher since build result is FAILURE Finished: FAILURE does anyone know how to resolve this? Jenkins v1.526, Linux Debian -- 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/groups/opt_out . -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/__bR8pK4j5A/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out . /blockquote -- Justinas -- 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/groups/opt_out . -- 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/groups/opt_out.
Re: IOException: Unable to delete when building
tried rebooting the machine but no luck. and i don't want to delete /usr/bin/tsort the only thing the build is configured to do is to checkout the source to workspace from SCM that's it i don't know where the /usr/bin/tsrot comes from, i guest it could be where the exception originates from On Wednesday, August 7, 2013 4:09:25 PM UTC+3, Justinas Urbanavicius wrote: Hi, having trouble with a build, the first one worked fine. After that i renamed my build and now i always get this error: Building in workspace /var/lib/jenkins/jobs/sit/workspace java.io.IOException: Unable to delete /usr/bin/tsort at hudson.Util.deleteFile(Util.java:255) at hudson.Util.deleteRecursive(Util.java:307) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:298) at hudson.FilePath$12.invoke(FilePath.java:1062) at hudson.FilePath$12.invoke(FilePath.java:1059) at hudson.FilePath.act(FilePath.java:906) at hudson.FilePath.act(FilePath.java:879) at hudson.FilePath.deleteRecursive(FilePath.java:1059) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.model.JDK.forNode(JDK.java:126) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:356) at hudson.model.Run.getEnvironment(Run.java:2071) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:408) at hudson.model.AbstractProject.checkout(AbstractProject.java:1406) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) [PMD] Skipping publisher since build result is FAILURE Finished: FAILURE does anyone know how to resolve this? Jenkins v1.526, Linux Debian -- 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/groups/opt_out.
Trigger on a few git repos, but do not checkout them?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jenkins-community, is it possible to trigger on changes in more than one git repositories, but do not checkout them into the workspace? - -- DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 mailto:sl...@dresearch-fe.de Fax: +49 30 515932-299 Geschäftsführer: Dr. Michael Weber, Werner Mögle; Amtsgericht Berlin Charlottenburg; HRB 130120 B; Ust.-IDNr. DE273952058 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlICUbEACgkQlSfCk8EgCzhkugCfRPtRXlwLUDeXasN1GguQoOSI OEoAn3wboktE8cx+z09g8LFaccF5bs9W =qP1V -END PGP SIGNATURE- -- 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/groups/opt_out.
Email-ext and env inject
Hi,
Im having a little trouble sending an email using environment injection. when
I try I get a
No emails were triggered.
it seems to be injecting the variables
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties file path
'E:/email_list.txt'
[EnvInject] - Variables injected successfully.
but doesn't seem to do anything.
in the file I have the following
EMAIL=t...@test.commailto:EMAIL=t...@test.com
I have tried the following in the Project Recipient List:
$EMAIL,$EMAIL and ${ENV,var=EMAIL}
any help would be greatly appreciated...im not sure what I am doing wrong
Cheers,
Neil
--
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/groups/opt_out.
Re: trigger a build ONLY when there has been a M2_RELEASEBUILD
I ended up using a post-build groovy script (about 12 lines). It detects if it was a maven release and passes along the job name and the release version to the next job. If people care/want this, lemmie know. On Wednesday, August 7, 2013 4:29:17 AM UTC-4, James Nord (jnord) wrote: Currently there is no simple way, hoiwever I think you can achieve what you want with the following: 1) use a URLtrigger (XTrigger plugin) on latestRelease permalink and inspect the content to cause job B to run. 2) use a RunParameter on job B to get the parameters from the release build (I have not tried this). From https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build · To use a Run Parameter, the value should be in the format * jobname#buildNumber* (eg. MyRunParam=foo-job%2399 for foo-job #99) /James *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Maven User *Sent:* 06 August 2013 22:26 *To:* jenkins...@googlegroups.com javascript: *Subject:* trigger a build ONLY when there has been a M2_RELEASEBUILD I think I may be over engineering this one a bit (headed to post-build groovy scripting hell), but I was wondering - is there an easy way to trigger another build (with two parameters from the release plugin) when a maven release has been triggered? For instance, when you run the maven release plugin on job A, I want to call job B only if A was both successful AND if it if IS_M2RELEASEBUILD is true. I looked at all sorts of things but wondering if there's something off the shelf I can use before going back to groovy... Thanks! -- 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/groups/opt_out. -- 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/groups/opt_out.
RE: Build Flow Plugin - reporting capability
After doing some playing with the Jenkins Script Console, I think the best approach is to use Groovy scripting. The Jenkins FreeStyleBuild class has a getLog() method that returns a string of the log. This is the first time that I have used the Script Console, and it seems to be a nice tool. I'd like to expose the information as a nice web page in Jenkins, but assume that is not really feasible. So, right now, I am thinking to just have a the users run a groovy script with text output. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof Sent: Wednesday, August 07, 2013 2:56 AM To: jenkinsci-users@googlegroups.com Subject: Re: Build Flow Plugin - reporting capability you probably can use jenkins REST API to retrieve the list of executed jobs from a build flow execution, not sure yet 2013/8/6 Bob Bick bb...@netjets.commailto:bb...@netjets.com Hi, The Jenkins Build Flow Plugin is replacing our massive home grown build system. A couple of times a year, our build team will create a Build Flow job from a template to perform the massive build which can last for several days. The build team will execute the Build Flow job until all sub-jobs have been successfully built. The build team can choose to build 50% of the jobs on a given day and then build the other 50% the next day (or however they decide to break it up)... That leads to my question I'd like to be able to inform the builders which sub-jobs have been completed within the context of the massive Build Flow job. Currently, that information is written to the Console Log as shown below: ## ###RESULTS ### ## SUCCESS : JOB1 JOB2 JOB3 SKIPPED : NAF_WPF_NET ABORTED : FAILURE : GERMAINE UNSTABLE : NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET ## ###END RESULTS ### ## Currently, the build team must scan all the console logs in order to determine what has/has not been built, and to figure out what they still need to build. This is difficult for them since there are about 50 different projects that must be built. I am trying to find a solution that would allow them to determine what still needs to be built. Here are a couple of ideas: 1) In the Build History, change the job names to include all of the sub-jobs that were successfully built for that job run (e.g. change #21 to #21 JOB1 JOB2 JOB3). But, I don't think there is a way to do that for Build Flow jobs. Does anyone know if this is possible? 2) Write a shell script that reads the console log files. However, this is a poor solution since it does not integrate with Jenkins (i.e. run some script outside of Jenkins). 3) Other??? Q. Can anyone think of a good way to report all of the sub-jobs that have successfully completed within the context of multiple Build Flow job runs? Thank you for taking the time to read this. Bob *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- 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.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- 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/groups/opt_out.
Re: Email-ext and env inject
What ARE you getting if you are not getting what you expect? Does
env-inject make the environment variables accessible to post-build actions
(publishers)?
slide
On Wed, Aug 7, 2013 at 7:41 AM, Welsh, Neil welsh...@visa.com wrote:
**
Hi,
Im having a little trouble sending an email using environment injection.
when I try I get a
No emails were triggered.
it seems to be injecting the variables
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties file path
'E:/email_list.txt'
[EnvInject] - Variables injected successfully.
but doesn't seem to do anything.
in the file I have the following
EMAIL=t...@test.com
I have tried the following in the Project Recipient List:
$EMAIL,$EMAIL and ${ENV,var=EMAIL}
any help would be greatly appreciated...im not sure what I am doing wrong
Cheers,
Neil
--
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/groups/opt_out.
--
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/groups/opt_out.
Upgrade and Slave Nodes fail to start
Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.comwrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out.
Re: Anyone have SCM poll trigger working with dynamic base clearcase view on windows?
had a cut paste *view path *and *view tag* must be set exactly the same !!! 1. For *view tag* use the view you defined, e.g. jenkins_BRANCH_NAME 2. For *view path* use the view you defined, e.g. jenkins_BRANCH_NAME On Tuesday, June 11, 2013 5:16:18 AM UTC-4, Samuel Mackrill wrote: Thanks, I have triple checked everything and they match your suggestions, still no joy. I am suspecting it could be because we are on an ancient version of Clearcase (7.1.2.4) or due to how the views are configured. I have written a custom perl script that triggers fine on CC changes so it must be possible! Perhaps I need to raise a defect and contact the plugin authors to get this sorted? That or learn some Java :) -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.comwrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
Also from https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin Version 1.0 (Aug 7, 2013) - Upgrade to Credentials Plugin 1.0https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin and migrate to new data types. - Any existing plugins that request credentials of type SSHUserPrivateKey explicitly will be unaffected. - If an existing plugin requests credentials of type BasicSSHUserPassword the resolution mechanism will handle the mapping to a concrete StandardUsernamePasswordCredentials transparently - If an existing plugin requests credentials of the base interface type SSHUser it will not be able to locate and StandardUsernamePasswordCredentials implementations and will need to be adapted to integrate correctly with the new class tree. - SSHAuthenticator.matcher() and SSHAuthenticator.matcher(Class Connection type) can be used to retrieve a CredentialsMatcher to narrow the search for appropriate credentials. - *NOTE: This version requires the* *SSH Slaves pluginhttps://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin * *be upgraded to at least version 1.0 or it will break the installed SSH Slaves plugin.* - *NOTE: This version modifies the configuration data format from a format that can be read by version 0.4 to a format that can only be read by 1.0 or newer. It will not be possible to downgrade from 1.0 to a previous release without risking configuration data loss. * On Wed, Aug 7, 2013 at 11:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
See http://jenkins-ci.361315.n4.nabble.com/NOTICE-Credentials-SSH-Credentials-SSH-Agent-and-SSH-Slaves-td4676163.html as well. On Wed, Aug 7, 2013 at 11:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: hopefully simple pipeline question
Great idea. Thanks, that sounds like it would work! On Tue, Aug 6, 2013 at 2:28 PM, Daniel Beck m...@beckweb.net wrote: You could use the parameterized trigger plugin and use the build step as the first action in the upstream build. That way, B will be queued before A polls SCM again. If necessary, add a Quiet Period to A in its advanced project options for the time it takes A to check out from SCM (or rather, to offset the delay from build start to first build step). On 06.08.2013, at 22:55, Mishael Kim mish...@gmail.com wrote: Hi All, Job A is a build job that is triggered by SCM changes, and Job B is a downstream test job configured to use the same node and same workspace. If Job A #1 is currently running, and Job A receives another trigger from SCM (Job A #2), how do I ensure that Job B #1 (which hasn't been triggered yet) takes precedence over Job A #2 for that one executor spot available on the machine? Thanks, Mishael -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
And from https://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin : Version 1.0 (Aug 7, 2013) - Upgrade dependencies to SSH Credentials Plugin 1.0https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin and Credentials Plugin 1.6https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin and migrated code from legacy data type to the new StandardCredential based types. - *NOTE: It will not be possible to* *downgrade* *to previous releases without risking the loss of some configuration data*. On Wed, Aug 7, 2013 at 11:38 AM, Jeff predato...@gmail.com wrote: Also from https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin Version 1.0 (Aug 7, 2013) - Upgrade to Credentials Plugin 1.0https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin and migrate to new data types. - Any existing plugins that request credentials of type SSHUserPrivateKey explicitly will be unaffected. - If an existing plugin requests credentials of type BasicSSHUserPassword the resolution mechanism will handle the mapping to a concrete StandardUsernamePasswordCredentials transparently - If an existing plugin requests credentials of the base interface type SSHUser it will not be able to locate and StandardUsernamePasswordCredentials implementations and will need to be adapted to integrate correctly with the new class tree. - SSHAuthenticator.matcher() and SSHAuthenticator.matcher(Class Connection type) can be used to retrieve a CredentialsMatcher to narrow the search for appropriate credentials. - *NOTE: This version requires the* *SSH Slaves pluginhttps://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin * *be upgraded to at least version 1.0 or it will break the installed SSH Slaves plugin.* - *NOTE: This version modifies the configuration data format from a format that can be read by version 0.4 to a format that can only be read by 1.0 or newer. It will not be possible to downgrade from 1.0 to a previous release without risking configuration data loss. * On Wed, Aug 7, 2013 at 11:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at:
Re: Upgrade and Slave Nodes fail to start
I don't see a Jenkins SSH plugin but I am running the same versions of the other two plugins that you are and I'm still having no luck. On Wed, Aug 7, 2013 at 10:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
Those are upgraded as well. On Wed, Aug 7, 2013 at 10:39 AM, Jeff predato...@gmail.com wrote: And from https://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin : Version 1.0 (Aug 7, 2013) - Upgrade dependencies to SSH Credentials Plugin 1.0https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin and Credentials Plugin 1.6https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin and migrated code from legacy data type to the new StandardCredential based types. - *NOTE: It will not be possible to* *downgrade* *to previous releases without risking the loss of some configuration data*. On Wed, Aug 7, 2013 at 11:38 AM, Jeff predato...@gmail.com wrote: Also from https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin Version 1.0 (Aug 7, 2013) - Upgrade to Credentials Plugin 1.0https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin and migrate to new data types. - Any existing plugins that request credentials of type SSHUserPrivateKey explicitly will be unaffected. - If an existing plugin requests credentials of type BasicSSHUserPassword the resolution mechanism will handle the mapping to a concrete StandardUsernamePasswordCredentials transparently - If an existing plugin requests credentials of the base interface type SSHUser it will not be able to locate and StandardUsernamePasswordCredentials implementations and will need to be adapted to integrate correctly with the new class tree. - SSHAuthenticator.matcher() and SSHAuthenticator.matcher(Class Connection type) can be used to retrieve a CredentialsMatcher to narrow the search for appropriate credentials. - *NOTE: This version requires the* *SSH Slaves pluginhttps://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin * *be upgraded to at least version 1.0 or it will break the installed SSH Slaves plugin.* - *NOTE: This version modifies the configuration data format from a format that can be read by version 0.4 to a format that can only be read by 1.0 or newer. It will not be possible to downgrade from 1.0 to a previous release without risking configuration data loss. * On Wed, Aug 7, 2013 at 11:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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
Re: Upgrade and Slave Nodes fail to start
Go to http://your.jenkins.install/systemInfo and look for all the SSH plugins, and Credentials, and make sure the versions are correct. On Wed, Aug 7, 2013 at 11:42 AM, Jared Griffith jgriff...@picsauditing.comwrote: I don't see a Jenkins SSH plugin but I am running the same versions of the other two plugins that you are and I'm still having no luck. On Wed, Aug 7, 2013 at 10:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
The other plugin I forgot to mention is the Credentials Plugin that must be at v1.6 On Wed, Aug 7, 2013 at 11:42 AM, Jared Griffith jgriff...@picsauditing.comwrote: I don't see a Jenkins SSH plugin but I am running the same versions of the other two plugins that you are and I'm still having no luck. On Wed, Aug 7, 2013 at 10:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
And if all else fails, restart Jenkins for good measure. In my config, I ended up recreating my credentials via credential manager and re-assigning them. Not sure if that is required or not. On Wed, Aug 7, 2013 at 11:43 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Go to http://your.jenkins.install/systemInfo and look for all the SSH plugins, and Credentials, and make sure the versions are correct. On Wed, Aug 7, 2013 at 11:42 AM, Jared Griffith jgriff...@picsauditing.com wrote: I don't see a Jenkins SSH plugin but I am running the same versions of the other two plugins that you are and I'm still having no luck. On Wed, Aug 7, 2013 at 10:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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
Re: Upgrade and Slave Nodes fail to start
Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. On Wed, Aug 7, 2013 at 11:45 AM, Jeff predato...@gmail.com wrote: And if all else fails, restart Jenkins for good measure. In my config, I ended up recreating my credentials via credential manager and re-assigning them. Not sure if that is required or not. On Wed, Aug 7, 2013 at 11:43 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Go to http://your.jenkins.install/systemInfo and look for all the SSH plugins, and Credentials, and make sure the versions are correct. On Wed, Aug 7, 2013 at 11:42 AM, Jared Griffith jgriff...@picsauditing.com wrote: I don't see a Jenkins SSH plugin but I am running the same versions of the other two plugins that you are and I'm still having no luck. On Wed, Aug 7, 2013 at 10:37 AM, Jeff predato...@gmail.com wrote: yes...and I'm running the following versions of plugins with Jenkins v1.526: - Jenkins SSH plugin v2.3 - Jenkins SSH Slaves plugin v1.0 - SSH Credentials Plugin v1.0 I believe the last 2 are tied together and must both be at v1.0 On Wed, Aug 7, 2013 at 11:28 AM, Jared Griffith jgriff...@picsauditing.com wrote: It says that the version that I am running is not compatible with the new SSH Slaves plugin. Are you running 1.526 as well? On Wed, Aug 7, 2013 at 10:24 AM, Jeff predato...@gmail.com wrote: I just ran into thatwhen I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it. On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith jgriff...@picsauditing.com wrote: Hopefully I can get a quicker response from the group. I just upgraded Jenkins to the latest version 1.526 and now my slave nodes won't start at all. I created a ticket for it, but have yet to get a response. Trying to downgrade the application has not resolved the issue. I'm at a loss since I need all of my nodes to be working properly. Here's the ticket I created: https://issues.jenkins-ci.org/browse/JENKINS-19104 -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jeff Vincent See my
Re: Upgrade and Slave Nodes fail to start
Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Checkstyle apparently totally broken
Could you please explain what was fixed? I checked hudson.ClassicPluginStrategy on master, no relevant changes since JENKINS-18654 was integrated in 1.524, probably causing the issues I linked. This thread started on Aug 6 with Jenkins is at the latest version as is Checkstyle and all of my other plugins, which was at least 1.525. I assumed JENKINS-18654 _caused_ issues like this, but this seemed to be the first case it happened with a plugin missing that isn't a mandatory dependency of the plugin throwing. On 07.08.2013, at 10:23, Ulli Hafner ullrich.haf...@gmail.com wrote: I think the root cause is https://issues.jenkins-ci.org/browse/JENKINS-18654 It is already fixed in Jenkins core. Ulli Am 07.08.2013 um 00:43 schrieb fREW Schmidt fri...@gmail.com: Right, I have not instaled Maven, though I'll try it tomorrow and see if it fixes the problem I guess. On Tue, Aug 06, 2013 at 09:37:46PM +0200, Daniel Beck wrote: According to the wiki [1, 2], Maven plugin is an _optional_ dependency of both Checkstyle and its (only, besides Ant) mandatory dependency, Analysis Core. Is this information correct? So far, JENKINS-18922/19000 seemed to only happen when missing mandatory dependencies, like jobConfigHistory - Maven... 1: https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin#CheckstylePlugin-PluginInformation 2: https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-PluginInformation -- fREW Schmidt http://blog.afoolishmanifesto.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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
I installed the SSH plugin (it wasn't there before) and it's still not working. All of my plugin versions are what have been stated here. On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
In the update center go to the Advanced tab and you can click the Check now button in the bottom right. On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
Ok - changed the update site to http://updates.jenkins-ci.org/update-center.jsonhttp://updates.jenkins-ci.org/stable/update-center.json (took away the stable) - the v1.0 plugin shows up - jenkins 1.526 shows up - installed the v1.0 plugin - refreshed credentials - refreshed slave (i.e. deleted and readded it) - restarted; rebooted; Bingo. Joy and happiness Thanks for all your help! On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Build Flow Plugin - reporting capability
Build flows are arbitrary Groovy code (hence JENKINS-16980, which will break
this solution if ever properly implemented). So just add log parsing and such
to the end of your build flow. The following minimal example takes the current
build's log so far, and writes it into a file in a new folder in the workspace:
def reportsDir =Thread.currentThread().currentWorkspace.child('reports')
reportsDir.mkdirs()
reportsDir.child('index.html').write('pre' +
Thread.currentThread().currentExecutable.log + 'pre', 'UTF-8')
There might even be nicer solutions for determining information about what
was(n't) built, like using FlowRun's getJobsGraph().
Now, publish that folder's contents using the HTML Publisher plugin's Publish
HTML Reports post-build step.
On 07.08.2013, at 18:03, Bob Bick bb...@netjets.com wrote:
After doing some playing with the Jenkins Script Console, I think the best
approach is to use Groovy scripting.
The Jenkins FreeStyleBuild class has a getLog() method that returns a string
of the log.
This is the first time that I have used the Script Console, and it seems to
be a nice tool. I’d like to expose the information as a nice web page in
Jenkins, but assume that is not really feasible. So, right now, I am thinking
to just have a the users run a groovy script with text output.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 2:56 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed jobs
from a build flow execution, not sure yet
2013/8/6 Bob Bick bb...@netjets.com
Hi,
The Jenkins Build Flow Plugin is replacing our “massive” home grown build
system.
A couple of times a year, our build team will create a Build Flow job from a
template to perform the “massive” build which can last for several days.
The build team will execute the Build Flow job until all sub-jobs have been
successfully built. The build team can choose to build 50% of the jobs on a
given day and then build the other 50% the next day (or however they decide
to break it up)… That leads to my question…. I’d like to be able to inform
the builders which sub-jobs have been completed within the context of the
massive Build Flow job. Currently, that information is written to the Console
Log as shown below:
##
###RESULTS ###
##
SUCCESS : JOB1 JOB2 JOB3
SKIPPED : NAF_WPF_NET
ABORTED :
FAILURE : GERMAINE
UNSTABLE :
NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET
##
###END RESULTS ###
##
Currently, the build team must scan all the console logs in order to
determine what has/has not been built, and to figure out what they still need
to build. This is difficult for them since there are about 50 different
projects that must be built. I am trying to find a solution that would allow
them to determine what still needs to be built. Here are a couple of ideas:
1) In the “Build History”, change the job names to include all of the
sub-jobs that were successfully built for that job run (e.g. change “#21” to
“#21 JOB1 JOB2 JOB3”). But, I don’t think there is a way to do that for Build
Flow jobs. Does anyone know if this is possible?
2) Write a shell script that reads the console log files. However, this
is a poor solution since it does not integrate with Jenkins (i.e. run some
script outside of Jenkins).
3) Other???
Q. Can anyone think of a good way to report all of the sub-jobs that have
successfully completed within the context of multiple Build Flow job runs?
Thank you for taking the time to read this.
Bob
*** *** ***
This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use, copy or disclose to anyone the message or any information
contained in the message. If you have received the message in error, please
advise the sender by reply e-mail and delete the message.
--
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/groups/opt_out.
--
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/groups/opt_out.
*** *** ***
This message contains information which may be confidential and
Re: Build Flow Plugin - reporting capability
I expect sandboxing (JENKINS-16980) to allow accessing
AbstractBuild.getLog() for a job that has been triggered by the flow, this
is a fully valid usage.
2013/8/7 Daniel Beck m...@beckweb.net
Build flows are arbitrary Groovy code (hence JENKINS-16980, which will
break this solution if ever properly implemented). So just add log parsing
and such to the end of your build flow. The following minimal example takes
the current build's log so far, and writes it into a file in a new folder
in the workspace:
def reportsDir
=Thread.currentThread().currentWorkspace.child('reports')
reportsDir.mkdirs()
reportsDir.child('index.html').write('pre' +
Thread.currentThread().currentExecutable.log + 'pre', 'UTF-8')
There might even be nicer solutions for determining information about what
was(n't) built, like using FlowRun's getJobsGraph().
Now, publish that folder's contents using the HTML Publisher plugin's
Publish HTML Reports post-build step.
On 07.08.2013, at 18:03, Bob Bick bb...@netjets.com wrote:
After doing some playing with the Jenkins Script Console, I think the
best approach is to use Groovy scripting.
The Jenkins FreeStyleBuild class has a getLog() method that returns a
string of the log.
This is the first time that I have used the Script Console, and it seems
to be a nice tool. I’d like to expose the information as a nice web page in
Jenkins, but assume that is not really feasible. So, right now, I am
thinking to just have a the users run a groovy script with text output.
From: jenkinsci-users@googlegroups.com [mailto:
jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 2:56 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed
jobs from a build flow execution, not sure yet
2013/8/6 Bob Bick bb...@netjets.com
Hi,
The Jenkins Build Flow Plugin is replacing our “massive” home grown
build system.
A couple of times a year, our build team will create a Build Flow job
from a template to perform the “massive” build which can last for several
days.
The build team will execute the Build Flow job until all sub-jobs have
been successfully built. The build team can choose to build 50% of the jobs
on a given day and then build the other 50% the next day (or however they
decide to break it up)… That leads to my question…. I’d like to be able to
inform the builders which sub-jobs have been completed within the context
of the massive Build Flow job. Currently, that information is written to
the Console Log as shown below:
##
###RESULTS ###
##
SUCCESS : JOB1 JOB2 JOB3
SKIPPED : NAF_WPF_NET
ABORTED :
FAILURE : GERMAINE
UNSTABLE :
NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET
##
###END RESULTS ###
##
Currently, the build team must scan all the console logs in order to
determine what has/has not been built, and to figure out what they still
need to build. This is difficult for them since there are about 50
different projects that must be built. I am trying to find a solution that
would allow them to determine what still needs to be built. Here are a
couple of ideas:
1) In the “Build History”, change the job names to include all of
the sub-jobs that were successfully built for that job run (e.g. change
“#21” to “#21 JOB1 JOB2 JOB3”). But, I don’t think there is a way to do
that for Build Flow jobs. Does anyone know if this is possible?
2) Write a shell script that reads the console log files. However,
this is a poor solution since it does not integrate with Jenkins (i.e. run
some script outside of Jenkins).
3) Other???
Q. Can anyone think of a good way to report all of the sub-jobs that
have successfully completed within the context of multiple Build Flow job
runs?
Thank you for taking the time to read this.
Bob
*** *** ***
This message contains information which may be confidential and
privileged. Unless you are the addressee (or authorized to receive for the
addressee), you may not use, copy or disclose to anyone the message or any
information contained in the message. If you have received the message in
error, please advise the sender by reply e-mail and delete the message.
--
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/groups/opt_out.
--
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
Re: Upgrade and Slave Nodes fail to start
Did you loose your slave build data or no? On Wed, Aug 7, 2013 at 11:42 AM, J Arrizza cppge...@gmail.com wrote: Ok - changed the update site to http://updates.jenkins-ci.org/update-center.jsonhttp://updates.jenkins-ci.org/stable/update-center.json (took away the stable) - the v1.0 plugin shows up - jenkins 1.526 shows up - installed the v1.0 plugin - refreshed credentials - refreshed slave (i.e. deleted and readded it) - restarted; rebooted; Bingo. Joy and happiness Thanks for all your help! On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out.
Jenkins + UiAutomator Always Green
So I defined many UiAutomatorTestCase classes, each has 1 or 2 test cases at the most. Then I use Shell script on Jenkins to string these test cases into a series of tests, for example: adb shell uiautomator runtest myTest.jar -c com.myTest.TestClass1 adb shell uiautomator runtest myTest.jar -c com.myTest.TestClass2 adb shell uiautomator runtest myTest.jar -c com.myTest.TestClass3 adb shell uiautomator runtest myTest.jar -c com.myTest.TestClass4 ... so on so forth. one of the two (1/2) problems I have is that with Jenkins builds, it doesn't matter if any of these test fails, Jenkins always shows up as green, I need Jenkins stop and shows red for the build. the other (2/2) problem is that if the app crashes in one of the tests, say, TestClass2, the script will try to pick up and continue executing. What would be the best method to make the script stop? Any suggestions? Thanks -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
I'm still getting no love with my slave nodes starting. On Wed, Aug 7, 2013 at 11:42 AM, J Arrizza cppge...@gmail.com wrote: Ok - changed the update site to http://updates.jenkins-ci.org/update-center.jsonhttp://updates.jenkins-ci.org/stable/update-center.json (took away the stable) - the v1.0 plugin shows up - jenkins 1.526 shows up - installed the v1.0 plugin - refreshed credentials - refreshed slave (i.e. deleted and readded it) - restarted; rebooted; Bingo. Joy and happiness Thanks for all your help! On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
I think your old version of the SSH Slaves plugin borked up the authentication and created invalid versions that need to be cleaned out On 7 August 2013 20:20, Jared Griffith jgriff...@picsauditing.com wrote: I'm still getting no love with my slave nodes starting. On Wed, Aug 7, 2013 at 11:42 AM, J Arrizza cppge...@gmail.com wrote: Ok - changed the update site to http://updates.jenkins-ci.org/update-center.jsonhttp://updates.jenkins-ci.org/stable/update-center.json (took away the stable) - the v1.0 plugin shows up - jenkins 1.526 shows up - installed the v1.0 plugin - refreshed credentials - refreshed slave (i.e. deleted and readded it) - restarted; rebooted; Bingo. Joy and happiness Thanks for all your help! On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Slow loading and large memory usage after 1.480.3 to 1.509.2 migration
This could be the following issue, that'll be fixed in 1.509.3: https://issues.jenkins-ci.org/browse/JENKINS-16023 On 07.08.2013, at 12:48, Christopher Tarento christoma...@gmail.com wrote: Hello guys, I used to run a Jenkins server with about 10 jobs with full history (~ 500 builds). Debian Wheezy OpenJDK 1.7b25 Tomcat 6 In 1.480.3 Loading time was decent (1min) and memory usage as 1GB. Server start - wait for 1 min - login - dashboard After updating WAR to 1.509.2 and all plugins to latest version (like dashboard to 2.8) Loading time is horrible (10min) and memory usage is about 4.5GB Server start - wait for 5 sec - login - wait for 10 min - dashboard Navigation is faster, it seems that all data is in memory ... I have to get back to 1.480.3 because such loading time and memory consumption is not acceptable. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Upgrade and Slave Nodes fail to start
I have cleaned them out. I have also removed a couple of the slaves and re-added them. Still nothing. I am now getting: [08/07/13 12:30:39] [SSH] Opening SSH connection to wolfram.picsauditing.com:22. [08/07/13 12:30:39] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:982) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:516) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) [08/07/13 12:30:39] [SSH] Connection closed. On Wed, Aug 7, 2013 at 12:28 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I think your old version of the SSH Slaves plugin borked up the authentication and created invalid versions that need to be cleaned out On 7 August 2013 20:20, Jared Griffith jgriff...@picsauditing.com wrote: I'm still getting no love with my slave nodes starting. On Wed, Aug 7, 2013 at 11:42 AM, J Arrizza cppge...@gmail.com wrote: Ok - changed the update site to http://updates.jenkins-ci.org/update-center.jsonhttp://updates.jenkins-ci.org/stable/update-center.json (took away the stable) - the v1.0 plugin shows up - jenkins 1.526 shows up - installed the v1.0 plugin - refreshed credentials - refreshed slave (i.e. deleted and readded it) - restarted; rebooted; Bingo. Joy and happiness Thanks for all your help! On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.com wrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.com wrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving
Re: Upgrade and Slave Nodes fail to start
I attached them in the ticket. On Wed, Aug 7, 2013 at 12:37 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Can you sanitise and send your credentials.xml an a corresponding slave config from config.xml On 7 August 2013 20:33, Jared Griffith jgriff...@picsauditing.com wrote: I have cleaned them out. I have also removed a couple of the slaves and re-added them. Still nothing. I am now getting: [08/07/13 12:30:39] [SSH] Opening SSH connection to wolfram.picsauditing.com:22. [08/07/13 12:30:39] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:982) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:516) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) [08/07/13 12:30:39] [SSH] Connection closed. On Wed, Aug 7, 2013 at 12:28 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I think your old version of the SSH Slaves plugin borked up the authentication and created invalid versions that need to be cleaned out On 7 August 2013 20:20, Jared Griffith jgriff...@picsauditing.comwrote: I'm still getting no love with my slave nodes starting. On Wed, Aug 7, 2013 at 11:42 AM, J Arrizza cppge...@gmail.com wrote: Ok - changed the update site to http://updates.jenkins-ci.org/update-center.jsonhttp://updates.jenkins-ci.org/stable/update-center.json (took away the stable) - the v1.0 plugin shows up - jenkins 1.526 shows up - installed the v1.0 plugin - refreshed credentials - refreshed slave (i.e. deleted and readded it) - restarted; rebooted; Bingo. Joy and happiness Thanks for all your help! On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 11:30 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: You can install it manually for now: http://mirrors.jenkins-ci.org/plugins/ssh-slaves/1.0/ On Wed, Aug 7, 2013 at 12:27 PM, J Arrizza cppge...@gmail.comwrote: I uninstalled SSH Slaves plugin; restarted jenkins and the plugin manager says: Version 0.27 Installed (0.27) i.e. no mention of 1.0 The update site I'm using is http://updates.jenkins-ci.org/stable/update-center.json On Wed, Aug 7, 2013 at 11:20 AM, J Arrizza cppge...@gmail.comwrote: The v1.0 is not showing up as an upgrade possibility. How do I force the plugin to go to v1.0? On Wed, Aug 7, 2013 at 11:17 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Your ssh slaves needs to be 1.0 On the advanced tab for plugins refresh and update that plugin. On Aug 7, 2013 12:02 PM, J Arrizza cppge...@gmail.com wrote: I have similar problems but it's not coming back up: Jenkinds 1.5.18 Credentials = v1.6 SSH Slaves = v0.27 SSH Credentials = 1.0 I upgraded the plugins and all the slaves are offline - I deleted the credentials for one slave and recreated it; no joy - I deleted the slave and recreated it; no joy - I've restarted jenkins service; I've rebooted the master server; no joy Keep getting the 'NoSuchMethodError What else should I be doing to get them back up and running? Thanks John On Wed, Aug 7, 2013 at 10:47 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: Yeah, I deleted all the credential information, even went so far as to remove the plugins, restart, and upgrade/install them all again. Then I finally got it working. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails
Re: Problem with build from Checkout Strategy
Anything interesting in the build logs when this occurred? How do you know the file wasn't updated, did you view the file in the workspace? On 07.08.2013, at 21:50, DAVID HO davidt...@gmail.com wrote: Hi all, I am very new to Jenkins and also to the build process. I have just started using Jenkins at my workplace. For our build process, we have the source code store in a remote SVN server and use Maven for the build. For the build configuration, we had Checkout Strategy as Use SVN update as much as possible to save time. Recently, we ran into the problem when updating the POM file. For some reasons, the new POM files, which located on SVN, was not updated in the Jenkins' work space even though the source code was. So, to fixed this problem, I have to clear out the work space folder and start the build again. This fixed the problem. To prevent this problem from happening in the future, I have set Checkout Strategy to Always check out a fresh copy. Does anyone know why this happens? Thanks, -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Problem with build from Checkout Strategy
Daniel, Yeah, I checked the POM in workspace and realized that it was the old version. There is nothing interesting about this problem in the log, except that the build was fail because of the change in dependencies in the POM. On Wednesday, August 7, 2013 3:52:54 PM UTC-4, Daniel Beck wrote: Anything interesting in the build logs when this occurred? How do you know the file wasn't updated, did you view the file in the workspace? On 07.08.2013, at 21:50, DAVID HO davi...@gmail.com javascript: wrote: Hi all, I am very new to Jenkins and also to the build process. I have just started using Jenkins at my workplace. For our build process, we have the source code store in a remote SVN server and use Maven for the build. For the build configuration, we had Checkout Strategy as Use SVN update as much as possible to save time. Recently, we ran into the problem when updating the POM file. For some reasons, the new POM files, which located on SVN, was not updated in the Jenkins' work space even though the source code was. So, to fixed this problem, I have to clear out the work space folder and start the build again. This fixed the problem. To prevent this problem from happening in the future, I have set Checkout Strategy to Always check out a fresh copy. Does anyone know why this happens? Thanks, -- 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/groups/opt_out. -- 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/groups/opt_out.
RE: Build Flow Plugin - reporting capability
Nicolas and Daniel, thank you for the help.
Bob
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 3:02 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
I expect sandboxing (JENKINS-16980) to allow accessing AbstractBuild.getLog()
for a job that has been triggered by the flow, this is a fully valid usage.
2013/8/7 Daniel Beck m...@beckweb.netmailto:m...@beckweb.net
Build flows are arbitrary Groovy code (hence JENKINS-16980, which will break
this solution if ever properly implemented). So just add log parsing and such
to the end of your build flow. The following minimal example takes the current
build's log so far, and writes it into a file in a new folder in the workspace:
def reportsDir =Thread.currentThread().currentWorkspace.child('reports')
reportsDir.mkdirs()
reportsDir.child('index.html').write('pre' +
Thread.currentThread().currentExecutable.log + 'pre', 'UTF-8')
There might even be nicer solutions for determining information about what
was(n't) built, like using FlowRun's getJobsGraph().
Now, publish that folder's contents using the HTML Publisher plugin's Publish
HTML Reports post-build step.
On 07.08.2013, at 18:03, Bob Bick bb...@netjets.commailto:bb...@netjets.com
wrote:
After doing some playing with the Jenkins Script Console, I think the best
approach is to use Groovy scripting.
The Jenkins FreeStyleBuild class has a getLog() method that returns a string
of the log.
This is the first time that I have used the Script Console, and it seems to
be a nice tool. I'd like to expose the information as a nice web page in
Jenkins, but assume that is not really feasible. So, right now, I am thinking
to just have a the users run a groovy script with text output.
From:
jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com]
On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 2:56 AM
To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed jobs
from a build flow execution, not sure yet
2013/8/6 Bob Bick bb...@netjets.commailto:bb...@netjets.com
Hi,
The Jenkins Build Flow Plugin is replacing our massive home grown build
system.
A couple of times a year, our build team will create a Build Flow job from a
template to perform the massive build which can last for several days.
The build team will execute the Build Flow job until all sub-jobs have been
successfully built. The build team can choose to build 50% of the jobs on a
given day and then build the other 50% the next day (or however they decide
to break it up)... That leads to my question I'd like to be able to
inform the builders which sub-jobs have been completed within the context of
the massive Build Flow job. Currently, that information is written to the
Console Log as shown below:
##
###RESULTS ###
##
SUCCESS : JOB1 JOB2 JOB3
SKIPPED : NAF_WPF_NET
ABORTED :
FAILURE : GERMAINE
UNSTABLE :
NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET
##
###END RESULTS ###
##
Currently, the build team must scan all the console logs in order to
determine what has/has not been built, and to figure out what they still need
to build. This is difficult for them since there are about 50 different
projects that must be built. I am trying to find a solution that would allow
them to determine what still needs to be built. Here are a couple of ideas:
1) In the Build History, change the job names to include all of the
sub-jobs that were successfully built for that job run (e.g. change #21 to
#21 JOB1 JOB2 JOB3). But, I don't think there is a way to do that for Build
Flow jobs. Does anyone know if this is possible?
2) Write a shell script that reads the console log files. However, this
is a poor solution since it does not integrate with Jenkins (i.e. run some
script outside of Jenkins).
3) Other???
Q. Can anyone think of a good way to report all of the sub-jobs that have
successfully completed within the context of multiple Build Flow job runs?
Thank you for taking the time to read this.
Bob
*** *** ***
This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use, copy or disclose to anyone the message or any information
contained in the message. If you have received the message in error, please
advise the sender by reply e-mail and delete the message.
--
You received this message because you are subscribed to
Re: Problem with build from Checkout Strategy
Could something have modified the Pom file in the jenkins workspace? I dont think Svn update will overwrite a modified file.. Just a guess.. Geoff On 7 Aug 2013, at 21:03, DAVID HO davidt...@gmail.com wrote: Daniel, Yeah, I checked the POM in workspace and realized that it was the old version. There is nothing interesting about this problem in the log, except that the build was fail because of the change in dependencies in the POM. On Wednesday, August 7, 2013 3:52:54 PM UTC-4, Daniel Beck wrote: Anything interesting in the build logs when this occurred? How do you know the file wasn't updated, did you view the file in the workspace? On 07.08.2013, at 21:50, DAVID HO davi...@gmail.com javascript: wrote: Hi all, I am very new to Jenkins and also to the build process. I have just started using Jenkins at my workplace. For our build process, we have the source code store in a remote SVN server and use Maven for the build. For the build configuration, we had Checkout Strategy as Use SVN update as much as possible to save time. Recently, we ran into the problem when updating the POM file. For some reasons, the new POM files, which located on SVN, was not updated in the Jenkins' work space even though the source code was. So, to fixed this problem, I have to clear out the work space folder and start the build again. This fixed the problem. To prevent this problem from happening in the future, I have set Checkout Strategy to Always check out a fresh copy. Does anyone know why this happens? Thanks, -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Problem with build from Checkout Strategy
It could be a case since I am not in control of who has control to write to the POM file. On Wednesday, August 7, 2013 4:24:21 PM UTC-4, Geoff Cummings wrote: Could something have modified the Pom file in the jenkins workspace? I dont think Svn update will overwrite a modified file.. Just a guess.. Geoff On 7 Aug 2013, at 21:03, DAVID HO davi...@gmail.com javascript: wrote: Daniel, Yeah, I checked the POM in workspace and realized that it was the old version. There is nothing interesting about this problem in the log, except that the build was fail because of the change in dependencies in the POM. On Wednesday, August 7, 2013 3:52:54 PM UTC-4, Daniel Beck wrote: Anything interesting in the build logs when this occurred? How do you know the file wasn't updated, did you view the file in the workspace? On 07.08.2013, at 21:50, DAVID HO davi...@gmail.com wrote: Hi all, I am very new to Jenkins and also to the build process. I have just started using Jenkins at my workplace. For our build process, we have the source code store in a remote SVN server and use Maven for the build. For the build configuration, we had Checkout Strategy as Use SVN update as much as possible to save time. Recently, we ran into the problem when updating the POM file. For some reasons, the new POM files, which located on SVN, was not updated in the Jenkins' work space even though the source code was. So, to fixed this problem, I have to clear out the work space folder and start the build again. This fixed the problem. To prevent this problem from happening in the future, I have set Checkout Strategy to Always check out a fresh copy. Does anyone know why this happens? Thanks, -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Remove a Queue item through a Groovy script
Hello,
I want to cancel a Queue item through a groovy script.
The script I have is something like this (I do a post because it is
specified that to remove an queue item. And queue item id I obtain it from
another part of the code using json api):
def urlString = 'http://jenkins.server/queue/cancelItem'
def queryString = id= + item.id
def url = new URL(urlString)
def connection = url.openConnection()
connection.setRequestMethod(POST)
connection.setDoInput(true);
connection.setDoOutput(true);
connection.connect()
def writer = new OutputStreamWriter(connection.outputStream)
writer.write(queryString)
writer.flush()
writer.close()
def inStream = new DataInputStream(connection.getInputStream())
def buffer
while((buffer = inStream.readLine()) != null) {
println(buffer);
}
inStream.close()
connection.close()
When I execute this script the item is deleted from the queue, but I get
the following error, I think it is because in some point of the code it
'executes' the url deleting the item from the queue, so then it doesn't
exist anymore, so when it tries to do the getInputStream it throws the
error because the Source URL doesn't exist anymore
Someone has any alternative idea I could implement for this?:
Thanks for the help.
java.io.FileNotFoundException: http://localhost:8080/queue/item/18/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)
at java.net.URLConnection.getContent(Unknown Source)
at java_net_URLConnection$getContent.call(Unknown Source)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at Script1.run(Script1.groovy:23)
at groovy.lang.GroovyShell.evaluate(GroovyShell
--
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/groups/opt_out.
Re: [NOTICE] Credentials, SSH Credentials, SSH Agent and SSH Slaves
The fix to https://issues.jenkins-ci.org/browse/JENKINS-19104 is in version 1.1 of the ssh-credentials plugin. Only affects people using private keys. You can download it from http://jenkins-updates.cloudbees.com/download/plugins/ssh-credentials/1.1/ssh-credentials.hpiif you are waiting for it to show up in the OSS update center. On 7 August 2013 18:23, Larry Shatzer, Jr. lar...@gmail.com wrote: And someone just reported the same stacktrace on the users list with this ticket: JENKINS-19104 On Wed, Aug 7, 2013 at 11:22 AM, Larry Shatzer, Jr. lar...@gmail.comwrote: I'm now seeing this when it tries to connect to a SSH slave: http://pastebin.com/F5e9rTVX Also my windows slaves (setup as windows services via DCOM), are hanging on checking java version. I've now switched the critical slaves to be JNLP slaves, just to get it back up and working. On Wed, Aug 7, 2013 at 5:54 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: As part of my improvements to the Credentials plugin I am pushing a whole new set of releases of these plugins. Credentials 1.6 is backwards compatible with all previous releases. It should be safe to upgrade that one on its own. SSH Credentials 1.0 requires Credentials 1.6 and includes a change to the on-disk data format. The consequence of this is that if you upgrade to SSH Credentials 1.0 you may loose credentials if you subsequently decide you made a mistake and decide to revert back to an earlier version... this is because the SSHUserPassword credentials have been migrated to the new StandardUsernamePasswordCredentials type in Credentials 1.6. This plugin is a new Major Version due to the deprecation of quite a few methods and classes. Note that if you do not upgrade SSH Slaves to a release that uses the new method signatures you may find that the Username/password credentials cannot be located. SSH Agent 1.2 requires SSH Credentials 1.0 and Credentials 1.6 but has no other impact. SSH Slaves 1.0 requires SSH Credentials 1.0 and Credentials 1.6. Given that this plugin is widely used, it advertises a change to the on-disk data format (despite there technically not being any) to prevent people accidentally upgrading without being aware that there is a potential impact (namely the changes in SSH Credentials 1.0) This version gets a new Major Version due to the major version change of SSH Credentials. I have done quite a bit of testing, and I am quite confident that the changes are safe... *but* you need to jump with all of them in one go, in other words IF you upgrade either of SSH Slaves or SSH Credentials to 1.0 you MUST ENSURE the other is upgraded also. Thanks for listening -Stephen -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
RE: Build Flow Plugin - reporting capability
Daniel,
We run Jenkins in a multi-node environment. If the Build Flow job always runs
on the same Jenkins node, then I think your solution will work fine. But, if
they do not run on the same node, then I will not have the history of previous
job runs in order to generate a comprehensive report.
Is there a way to pin a Build Flow job to a specific node? Or, perhaps I could
publish results after each run to the master Jenkins node, that could then be
downloaded to the currently running slave (i.e. the master node keeps the
history)? I have no clue if that is even possible...
Sorry for all these newbie questions.
Thanks,
Bob
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
Sent: Wednesday, August 07, 2013 2:52 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
Build flows are arbitrary Groovy code (hence JENKINS-16980, which will break
this solution if ever properly implemented). So just add log parsing and such
to the end of your build flow. The following minimal example takes the current
build's log so far, and writes it into a file in a new folder in the workspace:
def reportsDir =Thread.currentThread().currentWorkspace.child('reports')
reportsDir.mkdirs()
reportsDir.child('index.html').write('pre' +
Thread.currentThread().currentExecutable.log + 'pre', 'UTF-8')
There might even be nicer solutions for determining information about what
was(n't) built, like using FlowRun's getJobsGraph().
Now, publish that folder's contents using the HTML Publisher plugin's Publish
HTML Reports post-build step.
On 07.08.2013, at 18:03, Bob Bick bb...@netjets.com wrote:
After doing some playing with the Jenkins Script Console, I think the best
approach is to use Groovy scripting.
The Jenkins FreeStyleBuild class has a getLog() method that returns a string
of the log.
This is the first time that I have used the Script Console, and it seems to
be a nice tool. I'd like to expose the information as a nice web page in
Jenkins, but assume that is not really feasible. So, right now, I am thinking
to just have a the users run a groovy script with text output.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 2:56 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed
jobs from a build flow execution, not sure yet
2013/8/6 Bob Bick bb...@netjets.com
Hi,
The Jenkins Build Flow Plugin is replacing our massive home grown build
system.
A couple of times a year, our build team will create a Build Flow job from a
template to perform the massive build which can last for several days.
The build team will execute the Build Flow job until all sub-jobs have been
successfully built. The build team can choose to build 50% of the jobs on a
given day and then build the other 50% the next day (or however they decide
to break it up)... That leads to my question I'd like to be able to
inform the builders which sub-jobs have been completed within the context of
the massive Build Flow job. Currently, that information is written to the
Console Log as shown below:
##
###RESULTS ###
##
SUCCESS : JOB1 JOB2 JOB3
SKIPPED : NAF_WPF_NET
ABORTED :
FAILURE : GERMAINE
UNSTABLE :
NOT BUILT: MIDTIER ESL XRDS1 RULES NAF_NET ##
###END RESULTS ###
##
Currently, the build team must scan all the console logs in order to
determine what has/has not been built, and to figure out what they still need
to build. This is difficult for them since there are about 50 different
projects that must be built. I am trying to find a solution that would allow
them to determine what still needs to be built. Here are a couple of ideas:
1) In the Build History, change the job names to include all of the
sub-jobs that were successfully built for that job run (e.g. change #21 to
#21 JOB1 JOB2 JOB3). But, I don't think there is a way to do that for Build
Flow jobs. Does anyone know if this is possible?
2) Write a shell script that reads the console log files. However, this
is a poor solution since it does not integrate with Jenkins (i.e. run some
script outside of Jenkins).
3) Other???
Q. Can anyone think of a good way to report all of the sub-jobs that have
successfully completed within the context of multiple Build Flow job runs?
Thank you for taking the time to read this.
Bob
*** *** ***
This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use,
Re: Upgrade and Slave Nodes fail to start
No, the slave's reconnected once I had the correct plugin versions. But I'm not 100% sure about losing the credentials. I had already removed them by the time I got the plugin versions set up right. On Wed, Aug 7, 2013 at 12:05 PM, Jared Griffith jgriff...@picsauditing.comwrote: Did you loose your slave build data or no? -- 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/groups/opt_out.
Re: [NOTICE] Credentials, SSH Credentials, SSH Agent and SSH Slaves
Steve, You should also mention that the v1.0 (and I assume v1.1) plugins are in in the update-center url: http://updates.jenkins-ci.org/update-center.json but not in http://updates.jenkins-ci.org/stable/update-center.json This caused me a bit of confusion, it might hit others as well. John On Wed, Aug 7, 2013 at 2:13 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The fix to https://issues.jenkins-ci.org/browse/JENKINS-19104 is in version 1.1 of the ssh-credentials plugin. Only affects people using private keys. You can download it from http://jenkins-updates.cloudbees.com/download/plugins/ssh-credentials/1.1/ssh-credentials.hpiif you are waiting for it to show up in the OSS update center. -- 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/groups/opt_out.
Re: [NOTICE] Credentials, SSH Credentials, SSH Agent and SSH Slaves
I see ssh-slaves in the stable json now. It probably takes a while for some things to propagate through the systems. On Wed, Aug 7, 2013 at 3:27 PM, J Arrizza cppge...@gmail.com wrote: Steve, You should also mention that the v1.0 (and I assume v1.1) plugins are in in the update-center url: http://updates.jenkins-ci.org/update-center.json but not in http://updates.jenkins-ci.org/stable/update-center.json This caused me a bit of confusion, it might hit others as well. John On Wed, Aug 7, 2013 at 2:13 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The fix to https://issues.jenkins-ci.org/browse/JENKINS-19104 is in version 1.1 of the ssh-credentials plugin. Only affects people using private keys. You can download it from http://jenkins-updates.cloudbees.com/download/plugins/ssh-credentials/1.1/ssh-credentials.hpiif you are waiting for it to show up in the OSS update center. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [NOTICE] Credentials, SSH Credentials, SSH Agent and SSH Slaves
Yeah the OSS update centers are not as responsive as the DB backed ones we run at CloudBees on the other hand our update centers are more resource intensive. On 7 August 2013 22:37, Larry Shatzer, Jr. lar...@gmail.com wrote: I see ssh-slaves in the stable json now. It probably takes a while for some things to propagate through the systems. On Wed, Aug 7, 2013 at 3:27 PM, J Arrizza cppge...@gmail.com wrote: Steve, You should also mention that the v1.0 (and I assume v1.1) plugins are in in the update-center url: http://updates.jenkins-ci.org/update-center.json but not in http://updates.jenkins-ci.org/stable/update-center.json This caused me a bit of confusion, it might hit others as well. John On Wed, Aug 7, 2013 at 2:13 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The fix to https://issues.jenkins-ci.org/browse/JENKINS-19104 is in version 1.1 of the ssh-credentials plugin. Only affects people using private keys. You can download it from http://jenkins-updates.cloudbees.com/download/plugins/ssh-credentials/1.1/ssh-credentials.hpiif you are waiting for it to show up in the OSS update center. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: .NET Windows Forms run by Jenkins
Can't you just enable the Jenkins service to interact with the desktop (there is a special permission for it)? This would allow it to start Windows apps with no issue. slide On Wed, Aug 7, 2013 at 3:02 PM, Samuel Pereira samu...@gmail.com wrote: Hi, I need run automated tests what use forms. .NET Windows Forms This tests are necessary for simuation flux of view like Selenium. How the jenkins is a windows services is not possible run view tests. Do you know the solution for this problem? I know what exist a plugin what is a container for Selecium`s tests. So Jenkins can run view tests. Could Somebody help me? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: No Changes - How to force build?
Any reason that using Build Now on the project page won't work for you? (If you can't see it then you'll need to modify the security settings to allow your user to use it) Richard. On Thu, Aug 8, 2013 at 2:14 PM, Mark Andrachek, Jr. mark.andrac...@gmail.com wrote: I'm attempting to setup a job, and have been making changes to the configuration to try and get the build to work. However I'm getting No Changes when I try and run a build - because the code hasn't changed in git. Is there any way to by-pass this, and force it to do a build even if it's seen the revision before? Thanks, Mark R. Andrachek, Jr. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: No Changes - How to force build?
Turns out it does work. I was just unclear on why the build was failing. I thought it was because of No Changes, because that's it told me. But further review of the console log showed why the build was actually failing. Thanks! On Wed, Aug 7, 2013 at 11:21 PM, Richard Bywater rich...@byh2o.com wrote: Any reason that using Build Now on the project page won't work for you? (If you can't see it then you'll need to modify the security settings to allow your user to use it) Richard. On Thu, Aug 8, 2013 at 2:14 PM, Mark Andrachek, Jr. mark.andrac...@gmail.com wrote: I'm attempting to setup a job, and have been making changes to the configuration to try and get the build to work. However I'm getting No Changes when I try and run a build - because the code hasn't changed in git. Is there any way to by-pass this, and force it to do a build even if it's seen the revision before? Thanks, Mark R. Andrachek, Jr. -- 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/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/vOBecXzAH10/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: Remove a Queue item through a Groovy script
There is no output. It just sends a redirect to the referer location. In your
case. that's undefined, which probably causes it to fail this way. Just ignore
any non-error response (or at least, any redirects).
On 07.08.2013, at 23:04, tiago fernandez tiaguin12...@gmail.com wrote:
Hello,
I want to cancel a Queue item through a groovy script.
The script I have is something like this (I do a post because it is
specified that to remove an queue item. And queue item id I obtain it from
another part of the code using json api):
def urlString = 'http://jenkins.server/queue/cancelItem'
def queryString = id= + item.id
def url = new URL(urlString)
def connection = url.openConnection()
connection.setRequestMethod(POST)
connection.setDoInput(true);
connection.setDoOutput(true);
connection.connect()
def writer = new OutputStreamWriter(connection.outputStream)
writer.write(queryString)
writer.flush()
writer.close()
def inStream = new DataInputStream(connection.getInputStream())
def buffer
while((buffer = inStream.readLine()) != null) {
println(buffer);
}
inStream.close()
connection.close()
When I execute this script the item is deleted from the queue, but I get the
following error, I think it is because in some point of the code it
'executes' the url deleting the item from the queue, so then it doesn't exist
anymore, so when it tries to do the getInputStream it throws the error
because the Source URL doesn't exist anymore
Someone has any alternative idea I could implement for this?:
Thanks for the help.
java.io.FileNotFoundException: http://localhost:8080/queue/item/18/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URLConnection.getContent(Unknown Source)
at java_net_URLConnection$getContent.call(Unknown Source)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at Script1.run(Script1.groovy:23)
at groovy.lang.GroovyShell.evaluate(GroovyShell
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: Build Flow Plugin - reporting capability
Pin build flows to a slave the same way you pin jobs to slaves -- using labels.
And FWIW, since build flows are light-weight tasks that use one-off executors
(i.e. it creates its own temporary executor that has no number in the list), it
can always execute on the same node. Unless the node is unavailable or
(possibly) you're using a different executor assignment strategy (e.g. Even
Load Strategy plugin), it will always execute on the same node. But I don't
know whether the node makes any difference for file accesses anyway (or just
for scheduling), the DSL could actually be evaluated on the master every time.
Regarding the second question: You can run arbitrary code. Jenkins and its
plugins are open source. You're a developer. Go nuts. The following example
simply adds the previous flow run's HTML report to the current one (a simpler
example might have been to just use `.previousBuild.logFile.text`):
def reportsDir =Thread.currentThread().currentWorkspace.child('reports')
def previousPublisher =
Thread.currentThread().currentExecutable.previousBuild.actions.find {
it.class.name == 'htmlpublisher.HtmlPublisherTarget$HTMLBuildAction' }
def oldText = new File(previousPublisher.dir(), 'index.html').text
reportsDir.mkdirs()
reportsDir.child('index.html').write('pre' +
Thread.currentThread().currentExecutable.log + '/pre' + oldText, 'UTF-8')
On 07.08.2013, at 23:19, Bob Bick bb...@netjets.com wrote:
Daniel,
We run Jenkins in a multi-node environment. If the Build Flow job always runs
on the same Jenkins node, then I think your solution will work fine. But, if
they do not run on the same node, then I will not have the history of
previous job runs in order to generate a comprehensive report.
Is there a way to pin a Build Flow job to a specific node? Or, perhaps I
could publish results after each run to the master Jenkins node, that could
then be downloaded to the currently running slave (i.e. the master node keeps
the history)? I have no clue if that is even possible...
Sorry for all these newbie questions.
Thanks,
Bob
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
Sent: Wednesday, August 07, 2013 2:52 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
Build flows are arbitrary Groovy code (hence JENKINS-16980, which will break
this solution if ever properly implemented). So just add log parsing and such
to the end of your build flow. The following minimal example takes the
current build's log so far, and writes it into a file in a new folder in the
workspace:
def reportsDir =Thread.currentThread().currentWorkspace.child('reports')
reportsDir.mkdirs()
reportsDir.child('index.html').write('pre' +
Thread.currentThread().currentExecutable.log + 'pre', 'UTF-8')
There might even be nicer solutions for determining information about what
was(n't) built, like using FlowRun's getJobsGraph().
Now, publish that folder's contents using the HTML Publisher plugin's
Publish HTML Reports post-build step.
On 07.08.2013, at 18:03, Bob Bick bb...@netjets.com wrote:
After doing some playing with the Jenkins Script Console, I think the best
approach is to use Groovy scripting.
The Jenkins FreeStyleBuild class has a getLog() method that returns a string
of the log.
This is the first time that I have used the Script Console, and it seems to
be a nice tool. I'd like to expose the information as a nice web page in
Jenkins, but assume that is not really feasible. So, right now, I am
thinking to just have a the users run a groovy script with text output.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 2:56 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed
jobs from a build flow execution, not sure yet
2013/8/6 Bob Bick bb...@netjets.com
Hi,
The Jenkins Build Flow Plugin is replacing our massive home grown build
system.
A couple of times a year, our build team will create a Build Flow job from a
template to perform the massive build which can last for several days.
The build team will execute the Build Flow job until all sub-jobs have been
successfully built. The build team can choose to build 50% of the jobs on a
given day and then build the other 50% the next day (or however they decide
to break it up)... That leads to my question I'd like to be able to
inform the builders which sub-jobs have been completed within the context of
the massive Build Flow job. Currently, that information is written to the
Console Log as shown below:
##
###RESULTS ###
Re: hopefully simple pipeline question
Yeah. I don't like this behavior either. It's 'wait for people to get their non-atomic SCM commits right', rather than 'prevent back-to-back executions' (the clock starts ticking when it enters the queue, not when the previous build is finished) -- I'd need the latter more than the former... On 08.08.2013, at 01:13, Mishael Kim mish...@gmail.com wrote: Daniel, Slight problem with adding a quiet period to A... the first manually triggered job will have to wait for that quiet period as well, even if there's nothing running in the pipeline. Not a deal breaker, but I could see this being pretty annoying. On Wed, Aug 7, 2013 at 10:39 AM, Mishael Kim mish...@gmail.com wrote: Great idea. Thanks, that sounds like it would work! On Tue, Aug 6, 2013 at 2:28 PM, Daniel Beck m...@beckweb.net wrote: You could use the parameterized trigger plugin and use the build step as the first action in the upstream build. That way, B will be queued before A polls SCM again. If necessary, add a Quiet Period to A in its advanced project options for the time it takes A to check out from SCM (or rather, to offset the delay from build start to first build step). On 06.08.2013, at 22:55, Mishael Kim mish...@gmail.com wrote: Hi All, Job A is a build job that is triggered by SCM changes, and Job B is a downstream test job configured to use the same node and same workspace. If Job A #1 is currently running, and Job A receives another trigger from SCM (Job A #2), how do I ensure that Job B #1 (which hasn't been triggered yet) takes precedence over Job A #2 for that one executor spot available on the machine? Thanks, Mishael -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
