RE: Nodes Not Coming Back Online

[John Mellor]

Samual stated:

Ø  the master does not bring an additional node online for a newly triggered 
job if there is already a node online which matches that label

I have the same general setup using VMware slaves that boot as required.  I’m 
on Jenkins 1.656 and about a dozen slaves, with the git plugin and 2 monitor 
plugins at back revs due to some bugs.  I use a generic label on each job that 
matches the label on multiple matching slaves.  Except for four bugs, this 
works as expected and fires up another slave when the slave that it previously 
ran on is busy.  E.g: if I want to build in a Docker image, I run it on any one 
of 4 slaves that have the “Dockerhost” label.

There are 4 annoying bugs that are not fixed at this point:

1.   After a network outage of a master node reboot, the VMware slaves do 
not fire up automatically.  I have to manually bring them online once before 
things work as expected.

2.   It can take up to about 5 minutes for Jenkins to notice that a slave 
is bootable, and actually do so.

3.   The slave node monitor plugins (all of them that I’ve tried) have no 
concept of how to handle a node that is down because it is idle.  The all mark 
this as a critical issue when it is actually expected behaviour.

4.   If you take a slave manually offline to debug something, after a few 
minutes it will mark it as unreachable instead of intentionally offlined.  This 
causes some unexpected monitoring issues as a consequence.  The slave status 
checking is obviously in the wrong place in the scheduling logic.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of samuel.e.bro...@gmail.com
Sent: July-19-16 16:30
To: Jenkins Users
Subject: Nodes Not Coming Back Online

The system with which I am working uses nodes that are brought online as 
needed, and taken offline if they are not immediately used again (within two 
minutes) when a job is complete.

Using the “restrict where this job can be run” or the Parameterized Build 
(using a label), the master does not bring an additional node online for a 
newly triggered job if there is already a node online which matches that label. 
 This is not the desired behavior.  Right now, this blocks the build queue by 
making the new job wait until the job already running on the online node is 
finished (multiple hours in some cases).



I need the master to bring a node (with matching label) online for a new job 
unless there is already a FREE node online matching that label.  Jenkins knows 
these jobs are waiting too, because the logs show "Launching machine X 
because it has been in demand for 1 hr 28 min".
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/89cf70ae-f350-479e-b2f3-dafb20322061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ec0dcc67e393490cb3659d95c1c0b052%40mbx02cmb01p.esentire.local.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate credentials

[Stephen Connolly]

JENKINS_HOME/secrets

Specifically you will want JENKINS_HOME/secrets/master.key and
JENKINS_HOME/secrets/hudson.util.Secret

On 19 July 2016 at 19:50, Fadi Al-Farah  wrote:

> Right, but where are those keys stored at? ${JENKINS_HOME} is on a
> seperate volume which I literally detach and re-attach on the new VM.. So
> those keys have to be outside the ${JENKINS_HOME}, but where?
>
> On Tuesday, July 19, 2016 at 2:02:21 PM UTC-4, Stephen Connolly wrote:
>>
>> I would have migrated the encryption keys that way the encrypted values
>> would be the same
>>
>> On Tuesday 19 July 2016, Fadi Al-Farah  wrote:
>>
>>> Hello,
>>>
>>> How do I successfully migrate credentials from one box to another?
>>> Because, the credentials in ${JENKINS_HOME}/credentials.xml are hashed.
>>>
>>> Please help, as it's really becoming a tedious job to re-enter all the
>>> credentials after migrating.
>>>
>>> Fadi
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/e15aa263-2d7e-44f2-bfb3-ef1ca89df4d9%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Sent from my phone
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/2b247c96-9240-4a64-9feb-3a5008420e84%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw8tLamdhtwr%2BDOz9zs3WuaPwJALQ_048MuvtGot1%2B0Cw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Nodes Not Coming Back Online

[samuel . e . browne]

 

The system with which I am working uses nodes that are brought online as 
needed, and taken offline if they are not immediately used again (within 
two minutes) when a job is complete.

Using the “restrict where this job can be run” or the Parameterized Build 
(using a label), the master does not bring an additional node online for a 
newly triggered job if there is already a node online which matches that 
label.  This is not the desired behavior.  Right now, this blocks the build 
queue by making the new job wait until the job already running on the 
online node is finished (multiple hours in some cases).

 
I need the master to bring a node (with matching label) online for a new 
job unless there is already a FREE node online matching that label.  
Jenkins knows these jobs are waiting too, because the logs show "Launching 
machine X because it has been in demand for 1 hr 28 min".

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/89cf70ae-f350-479e-b2f3-dafb20322061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate credentials

[Fadi Al-Farah]

Right, but where are those keys stored at? ${JENKINS_HOME} is on a seperate 
volume which I literally detach and re-attach on the new VM.. So those keys 
have to be outside the ${JENKINS_HOME}, but where?

On Tuesday, July 19, 2016 at 2:02:21 PM UTC-4, Stephen Connolly wrote:
>
> I would have migrated the encryption keys that way the encrypted values 
> would be the same
>
> On Tuesday 19 July 2016, Fadi Al-Farah  
> wrote:
>
>> Hello,
>>
>> How do I successfully migrate credentials from one box to another? 
>> Because, the credentials in ${JENKINS_HOME}/credentials.xml are hashed.
>>
>> Please help, as it's really becoming a tedious job to re-enter all the 
>> credentials after migrating.
>>
>> Fadi
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/e15aa263-2d7e-44f2-bfb3-ef1ca89df4d9%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Sent from my phone
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2b247c96-9240-4a64-9feb-3a5008420e84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate credentials

[Stephen Connolly]

I would have migrated the encryption keys that way the encrypted values
would be the same

On Tuesday 19 July 2016, Fadi Al-Farah  wrote:

> Hello,
>
> How do I successfully migrate credentials from one box to another?
> Because, the credentials in ${JENKINS_HOME}/credentials.xml are hashed.
>
> Please help, as it's really becoming a tedious job to re-enter all the
> credentials after migrating.
>
> Fadi
>
> --
> 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
> 
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e15aa263-2d7e-44f2-bfb3-ef1ca89df4d9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my phone

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxso%3D1zpwX-D4FLSw1YcE%3D2%2BPX53FbL09DbVutRyO06OA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate credentials

[Fadi Al-Farah]

I even posted this question on Stackoverflow 

.

On Tuesday, July 19, 2016 at 2:00:24 PM UTC-4, Fadi Al-Farah wrote:
>
> Hello,
>
> How do I successfully migrate credentials from one box to another? 
> Because, the credentials in ${JENKINS_HOME}/credentials.xml are hashed.
>
> Please help, as it's really becoming a tedious job to re-enter all the 
> credentials after migrating.
>
> Fadi
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6752738e-7f00-48cd-99fb-6d9cba70726b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Migrate credentials

[Fadi Al-Farah]

Hello,

How do I successfully migrate credentials from one box to another? Because, 
the credentials in ${JENKINS_HOME}/credentials.xml are hashed.

Please help, as it's really becoming a tedious job to re-enter all the 
credentials after migrating.

Fadi

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e15aa263-2d7e-44f2-bfb3-ef1ca89df4d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins fresh install, can't create new job

[Slide]

Sounds like a bug!

On Tue, Jul 19, 2016 at 9:35 AM  wrote:

> I updated to 2.7.1 this morning and i have the exact same problem.
> It turns out that the new job page doesn't show when using french as the
> browser language. Using english works fine though.
>
>
> On Sunday, July 17, 2016 at 9:12:28 PM UTC+2, Baptiste Mathus wrote:
>
>> Hello, can you try with the 2.7.1 version to see it this happens too?
>> 2.13 is bleeding edge so you want to check on the LTS (long term support)
>> to sort out hypothesis.
>>
>> Thanks
>>
> Le 13 juil. 2016 2:33 PM, "Alexandre Saint-Orens" 
>> a écrit :
>>
> Hello there,
>>>
>>> I have installed on a Debian server Jenkins.
>>> Now i want to create a now job so a click on "créer un nouveau job" in
>>> english : "create a new job" (it's the same result when i click on "nouveau
>>> item" :
>>>
>>>
>>> 
>>>
>>>
>>>
>>> 
>>> And
>>> this is the page "new job" :
>>>
>>>
>>> Why there is nothing on this page ? I miss some configuration ?
>>>
>>> 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.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/5e94f990-f0d0-4f0d-ba0e-072b761e27ee%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/7f1b98c3-862b-4a34-b1c9-6e2adc4fdb46%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeMBYCmy_xDOhVbkiK2rcF%3DGaRznPThys%2B2voxjdmL-NQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins fresh install, can't create new job

[grimardsebastien]

I updated to 2.7.1 this morning and i have the exact same problem.
It turns out that the new job page doesn't show when using french as the 
browser language. Using english works fine though.

On Sunday, July 17, 2016 at 9:12:28 PM UTC+2, Baptiste Mathus wrote:
>
> Hello, can you try with the 2.7.1 version to see it this happens too? 2.13 
> is bleeding edge so you want to check on the LTS (long term support) to 
> sort out hypothesis.
>
> Thanks
>
> Le 13 juil. 2016 2:33 PM, "Alexandre Saint-Orens"  > a écrit :
>
>> Hello there,
>>
>> I have installed on a Debian server Jenkins.
>> Now i want to create a now job so a click on "créer un nouveau job" in 
>> english : "create a new job" (it's the same result when i click on "nouveau 
>> item" :
>>
>>
>> 
>>
>>
>>
>> 
>>  
>> And
>>  
>> this is the page "new job" : 
>>
>>
>> Why there is nothing on this page ? I miss some configuration ?
>>
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/5e94f990-f0d0-4f0d-ba0e-072b761e27ee%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7f1b98c3-862b-4a34-b1c9-6e2adc4fdb46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: P4 Plugin throws "Error occurred during the SSL handshake: invalid SSL session" Error

[Irfan Sayed]

you need to install the JCE and JRE with same version and have to be on the
default path when p4 need them. as per the code of p4 plugin, these two
need to be on the same version and registered.

please make sure you have these.

this will solve the issue
Regards
Irfan


On Tue, Jul 19, 2016 at 5:53 PM, Hassan Iqbal  wrote:

> I was also facing similar problem. Even after updating the JCE jars for
> java 8, SSL connection issue was coming. Reinstalling the JDK-8u92 and then
> updating the JCE solved the issue.
>
>
> On Monday, September 29, 2014 at 11:53:08 AM UTC+5:30, Shobha Dashottar
> wrote:
>>
>> I ran that test code and earlier it gave 128 . So, made a few more
>> changes like reinstalling jdk, setting the java paths in a few more files
>> for Jenkins to get the path during slave launch itself and then finally
>> copying the UnlimitedJCEPolicy jar files even though they existed in the
>> security folder.
>>
>> Looks like something was messed up in my java environment as after I ran
>> the test code it gave me the value 2147483647.  the SSL handshake error has
>> gone away too.
>>
>> Thanks Dan for your help on this. Much Appreciated.
>>
>>
>> On Friday, September 26, 2014 9:30:58 PM UTC+5:30, Dan Tran wrote:
>>>
>>>
>>> Also note, that p4jenkins uses the startup JRE to talk to perforce ( not
>>> the one configure in the job)
>>>
>>> -D
>>>
>>> On Thursday, September 25, 2014 7:11:13 PM UTC-7, Dan Tran wrote:


  run a java test with your JRE?

 private boolean isUnlimitedCryptoSupported() throws
 NoSuchAlgorithmException {
 int bits = Cipher.getMaxAllowedKeyLength("AES");
 this.getLog().info("Current encryption strength is: " + bits);
 return bits == 2147483647;

 }




 On Thursday, September 25, 2014 10:15:01 AM UTC-7, Shobha Dashottar
 wrote:
>
> I have now removed all the older jre versions from the systems leaving
> jre only in one place. I even have the JRE  home in the PATH variable.
>
> I have setup some Windows VMs now but those are too giving the same
> error. They already have the JCE jars in their installation folders.
>
> Is there some other requirement for this to work ?
>
> Thanks
> Shobha
>
> On Thursday, September 25, 2014 9:32:35 PM UTC+5:30, Dan Tran wrote:
>>
>>
>> Very likely, you patch the wrong JRE
>>
>> -D
>>
>> On Thursday, September 25, 2014 8:46:01 AM UTC-7, Shobha Dashottar
>> wrote:
>>>
>>> I am setting up a  new Jenkins server. I have been using the
>>> Perforce Plugin so far but this time I have switched to the P4 Plugin as
>>> has a good integration with the Credential Plugin to connect to the
>>> perforce server.
>>>
>>> For most of the VMs that I am connecting to it goes ahead with P4
>>> command execution without issue. So far one VM is giving issue and 
>>> throwing
>>> exception while even trying to communicate with the perforce server.
>>>
>>> P4: Unable to connect: 
>>> com.perforce.p4java.exception.ConnectionException: Error occurred 
>>> during the SSL handshake: invalid SSL session
>>> P4: Unable to use Workspace: java.lang.NullPointerException
>>> P4: Unable to close Perforce connection: java.lang.NullPointerException
>>> ERROR: Unable to update workspace: java.lang.NullPointerException
>>>
>>> After following some articles, I have added the jars from JCE for Java 
>>> 7 inside the slave VMs jre/lib/security folder.
>>> But still the error keeps popping up.
>>>
>>> Does anyone know what is going on or is missing on that VM?
>>>
>>> Thanks
>>> Shobha
>>>
>>>
>>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/d948f1e5-53b2-4a3c-bad9-70a0a3dfde5a%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CACGLCJaXPi1g_gHjQVJ2hvXw2%3DW3f25xdsr7%3D_Za1k-qkg-tgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: P4 Plugin throws "Error occurred during the SSL handshake: invalid SSL session" Error

[Hassan Iqbal]

I was also facing similar problem. Even after updating the JCE jars for 
java 8, SSL connection issue was coming. Reinstalling the JDK-8u92 and then 
updating the JCE solved the issue.

On Monday, September 29, 2014 at 11:53:08 AM UTC+5:30, Shobha Dashottar 
wrote:
>
> I ran that test code and earlier it gave 128 . So, made a few more changes 
> like reinstalling jdk, setting the java paths in a few more files for 
> Jenkins to get the path during slave launch itself and then finally copying 
> the UnlimitedJCEPolicy jar files even though they existed in the security 
> folder.
>
> Looks like something was messed up in my java environment as after I ran 
> the test code it gave me the value 2147483647.  the SSL handshake error has 
> gone away too.
>
> Thanks Dan for your help on this. Much Appreciated.
>
>
> On Friday, September 26, 2014 9:30:58 PM UTC+5:30, Dan Tran wrote:
>>
>>
>> Also note, that p4jenkins uses the startup JRE to talk to perforce ( not 
>> the one configure in the job)
>>
>> -D
>>
>> On Thursday, September 25, 2014 7:11:13 PM UTC-7, Dan Tran wrote:
>>>
>>>
>>>  run a java test with your JRE?
>>>
>>> private boolean isUnlimitedCryptoSupported() throws 
>>> NoSuchAlgorithmException {
>>> int bits = Cipher.getMaxAllowedKeyLength("AES");
>>> this.getLog().info("Current encryption strength is: " + bits);
>>> return bits == 2147483647;
>>>
>>> }
>>>
>>>
>>>
>>>
>>> On Thursday, September 25, 2014 10:15:01 AM UTC-7, Shobha Dashottar 
>>> wrote:

 I have now removed all the older jre versions from the systems leaving 
 jre only in one place. I even have the JRE  home in the PATH variable. 

 I have setup some Windows VMs now but those are too giving the same 
 error. They already have the JCE jars in their installation folders. 

 Is there some other requirement for this to work ?

 Thanks
 Shobha

 On Thursday, September 25, 2014 9:32:35 PM UTC+5:30, Dan Tran wrote:
>
>
> Very likely, you patch the wrong JRE
>
> -D
>
> On Thursday, September 25, 2014 8:46:01 AM UTC-7, Shobha Dashottar 
> wrote:
>>
>> I am setting up a  new Jenkins server. I have been using the Perforce 
>> Plugin so far but this time I have switched to the P4 Plugin as has a 
>> good 
>> integration with the Credential Plugin to connect to the perforce 
>> server.  
>>
>> For most of the VMs that I am connecting to it goes ahead with P4 
>> command execution without issue. So far one VM is giving issue and 
>> throwing 
>> exception while even trying to communicate with the perforce server.
>>
>> P4: Unable to connect: 
>> com.perforce.p4java.exception.ConnectionException: Error occurred during 
>> the SSL handshake: invalid SSL session
>> P4: Unable to use Workspace: java.lang.NullPointerException
>> P4: Unable to close Perforce connection: java.lang.NullPointerException
>> ERROR: Unable to update workspace: java.lang.NullPointerException
>>
>> After following some articles, I have added the jars from JCE for Java 7 
>> inside the slave VMs jre/lib/security folder. 
>> But still the error keeps popping up. 
>>
>> Does anyone know what is going on or is missing on that VM?
>>
>> Thanks
>> Shobha
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d948f1e5-53b2-4a3c-bad9-70a0a3dfde5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gerrit Trigger - no votes after update

[Andreas]

Hi,

I've just updated to Jenkins 2.7.1 LTS & Gerrit Trigger 2.21.1 it seems 
that the Gerrit Trigger plugin is not voting any more - can someone confirm 
this or is it likely a setup issue on my side? 

Kind Regards,
Andreas.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/55b17dc7-626a-4f58-90bb-51ecefc7cdba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Displaying information on build page that changes

[Jonathan Hodgson]

Hi,

I'm working on a pipeline job that builds several versions of my code on 
different slaves, and then will be extended to run tests, create installers 
etc.

I would like to keep the user informed of the progress of these various 
steps on the build page, and give access to log files etc as they become 
available.

Now, using the Summary Report plugin I can do this, however this will 
result in the progress of the different slaves being interleaved as and 
when they happen, because once the information is displayed, it doesn't 
change, even if I archive a new version of the xml file it is based on.

I would much rather display some sort of structure for a given step and 
fill it in as the results become available

Is there any way to do this? And if not, is there a plugin that might be a 
starting point if I wanted to work out how to implement this functionality?

regards

Jon

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f7479fce-1936-497b-9ca0-0b19c7131d21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to Jenkins 2 failed

[Mingxing Tian]

This is an FAQ. Solution is to disable AJP. See details in jira 


Quote from above link for reference

JENKINS_AJP_PORT="-1" in /etc/sysconfig/jenkins solved problem

https://stackoverflow.com/questions/38157686/migrating-to-jenkins-2-1-ajp-support-is-removed-in-winstone-3-0-due-to-jetty-9/38157687#38157687?newreg=7aa149f6d35a4daba7b42a40dc52b935

在 2016年5月13日星期五 UTC+8下午6:21:37，Marcin Wieczorek写道：
>
> Ran into the same problem and finally found this: 
> https://issues.jenkins-ci.org/browse/JENKINS-33776
>
> That solved it for me.
>
> Marcin
>
> On Thursday, May 12, 2016 at 2:48:45 AM UTC-7, David Aldrich wrote:
>>
>> Hi 
>>
>> I have tried to upgrade our Jenkins test server from 1.656 to 2.3 by 
>> copying the 2.3 war to: 
>>
>> /usr/lib/jenkins/ 
>>
>> and restarting Jenkins using: 
>>
>> sudo /etc/init.d/jenkins restart 
>>
>> Now I cannot connect to Jenkins: 
>>
>> "This site can't be reached 
>> jenkinstest. refused to connect." 
>>
>> Any suggestions please? 
>>
>> Best regards 
>>
>> David 
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f710d409-474b-4708-84d4-8bec6ae8fee6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins upgrade

[Saggam Raju]

Hi,

1. Could you please stop tomcat server(catalina.sh stop/service tomcat 
stop).
2. Take backup of old jenkins war file from tomcat/webaspps(tar czf 
jenkins.backup jenkins.war) and also take backup of jenkins home directory. 
3. Now copy your latest jenkins version to tomcat/webapps directory and 
start tomcat server. 

Thanks,
Raju.

On Monday, July 18, 2016 at 7:16:22 PM UTC+5:30, Prasu S wrote:
>
> I'm upgrading Jenkins from 1.607 version to 1.645 . I replaced the old war 
> file with 1.645 war file and restarted Jenkins Tomcat and also rebooted the 
> server but I still see old version. I tried the same steps on our test 
> instance back in April it worked fine . Why the new version is not getting 
> upgraded? Please help. Thanks in Advance..
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/058255aa-35ef-4bfa-9da7-a62f10e4b58c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins + Android: Two Problems. Please help.

[Ravi A]

Eric,
I am using "Ubuntu 14.04.4 x64 LTS Desktop" host. So I already have working 
X-windows with my host. So I assumed using Xvfb or Xvnc is NOT required 
with Jenkins job. Is it mandatory to use Xvfb or Xvnc independent of 
whether I use a "UBuntu Desktop" host or "Ubuntu Server" host ?? Kindly 
advise.

Thank you,
Ravi


On Monday, July 18, 2016 at 11:39:01 PM UTC+5:30, Eric Pyle wrote:
>
> I don't know anything about running the Android Emulator, but the error 
> seems to be "Unable to open display". You mention that you did not use any 
> Xvfb or Xvnc configuration. Maybe this is something that needs to be set up?
>
> Eric
>
> On 7/18/2016 2:05 PM, Ravi A wrote:
>
> Please neglect my Problem #1 as this problem is related to "Android". Let 
> me ask this question to "Android Google Group".
> Request you to answer my Problem #2 with a solution.
>
> Thank you,
> Ravi
>
>
> On Monday, July 18, 2016 at 11:53:06 AM UTC+5:30, Ravi A wrote: 
>>
>>
>> I am new to Android related work and Jenkins. Currently I am facing two 
>> problems as explained below and need help about these two problems. Kindly 
>> do the needful.
>>
>> I am using one "Ubuntu v14.04.4 LTS x64 Desktop Edition" based physical 
>> host (VT enabled from BIOS, Intel(R) Core(TM) i5-3470 CPU) and following 
>> software also installed.
>>
>> Gradle v2.14
>> Ant v1.9.7
>> Maven 3.3.9
>> android-sdk_r24.4.1
>> java version "1.8.0_92"
>> Android_Studio_v2.1.2.0   (android-studio-ide-143.2915827)
>> KVM/Qemu
>> Jenkins v2.7.1 CI server with following Android related "Jenkins Plugins"
>> Android Emulator Plugin v2.15
>> Android Lint Plugin v2.3
>> Gradle Plugin v1.24
>> Xvnc Plugin v1.23
>> Xvfb Plugin v1.1.3
>>
>>
>> Problem #1
>> --
>> Created on "Android VD" with AVD name as "Nexus_6_API_23" using "Android 
>> Studio" and later I could start Emulator from "Shell Command Line", but 
>> "Segmentation Fault (core dumped)" when I exit the emulator.
>>
>> ravi@ravi-dev-box:~$ emulator -list-avds
>> Nexus_6_API_23
>> ravi@ravi-dev-box:~$
>> ravi@ravi-dev-box:~$ emulator -avd Nexus_6_API_23
>> adb_server_notify: Failed to establish connection to ADB server
>> console on port 5554, ADB on port 
>> Your emulator is out of date, please update by launching Android Studio:
>>  - Start Android Studio
>>  - Select menu "Tools > Android > SDK Manager"
>>  - Click "SDK Tools" tab
>>  - Check "Android SDK Tools" checkbox
>>  - Click "OK"
>>
>> Segmentation fault (core dumped)
>> ravi@ravi-dev-box:~$
>>
>>
>> Problem #2
>> --
>> I tried to start "Android Emulator" about the same above mentioned 
>> "Nexus_6_API_23" AVD using a "Jenkins Job" which DOES NOT include any Xvfb 
>> and Xvnc related configuration. Build using this "Jenkins Job" fails as 
>> explained below (Console Output from the build).
>>
>> Started by user admin
>> [EnvInject] - Loading node environment variables.
>> Building in workspace 
>> /home/ravi/Downloads/Android/Spring/gs-gradle-android_3
>> [android] Using Android SDK: /opt/android-sdk-linux/
>> $ /opt/android-sdk-linux//platform-tools/adb start-server
>> * daemon not running. starting it now on port 5835 *
>> * daemon started successfully *
>> $ /opt/android-sdk-linux//platform-tools/adb start-server
>> [android] Starting Android emulator
>> $ /opt/android-sdk-linux//tools/emulator -engine classic -ports 5772,5773 
>> -report-console tcp:5839,max=60 -avd Nexus_6_API_23 -no-snapshot-load 
>> -no-snapshot-save
>> Error: unable to open display
>> Error: unable to open display
>> QXcbConnection: Could not connect to display
>> emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore 
>> option from your config file is ignored.
>> [android] Emulator did not appear to start; giving up
>> [android] Stopping Android emulator
>> $ /opt/android-sdk-linux//platform-tools/adb kill-server
>> [BFA] Scanning build for known causes...
>> [BFA] No failure causes found
>> [BFA] Done. 0s
>> Finished: NOT_BUILT
>>
>> Thanks A Lot In Advance,
>> Ravi
>>
>> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/e43c465b-0849-4324-93c7-090cd1b6a276%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
>
> * Eric Pyle * 
> Release Engineer 
> Lebanon 
> +1 603-277-3060 (T)
> +1 603-359-8670 (M)
> ...@cd-adapco.com 
> http://www.cd-adapco.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