Re: Jenkins reverse proxy (Apache) with SSL

2018-01-28 Thread Ashish Yadav
Any ideas? ☺


From:  on behalf of Ashish Yadav 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Thursday, January 25, 2018 at 7:34 PM
To: "jenkinsci-users@googlegroups.com" 
Subject: Jenkins reverse proxy (Apache) with SSL

I am running Jenkins on Centos 7 behind a reverse proxy with ssl certs.  I want 
Apache to handle the ssl certs. User -> HTTPS -> Apache -> HTTP -> Jenkins 
application. Here is what my configuration looks like.

RewriteEngine On
RewriteCond %{HTTPS} !on
RewriteRule /.* https://$0 [R=301,L]


ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLCertificateFile /etc/pki/tls/certs/localhost.crt
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
SSLCertificateChainFile /etc/pki/tls/certs/localhost.crt

Header always set Strict-Transport-Security "max-age=63072000; 
includeSubDomains"
RequestHeader set X-Forwarded-Proto https
RequestHeader set X-Forwarded-Port "443"

ProxyRequests Off
ProxyPass / http://localhost:8080/ nocanon
ProxyPassReverse / http://localhost:8080/
AllowEncodedSlashes NoDecode



I can get the following to work:

  1.  http://hostname:8080
  2.  http://hostname -reditrect to -> 
http://hostname:8080<http://hostname:8080/>
  3.  https://hostname

However, the redirect from http://hostname:8080 to https://hostname is not 
working. I stay at http://hostname:8080
The firewall port (443) is open and the server is listening.

What am I missing? ☺ I tried every combination on 
https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache but I 
can’t get the last http to https redirect to work.

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3F84EB6D-171E-4498-9249-24EA9FD93049%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/3F84EB6D-171E-4498-9249-24EA9FD93049%40firemon.com?utm_medium=email&utm_source=footer>.
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/1DB04601-50D3-4415-99D7-6F1E8E45D0AC%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins reverse proxy (Apache) with SSL

2018-01-25 Thread Ashish Yadav
I am running Jenkins on Centos 7 behind a reverse proxy with ssl certs.  I want 
Apache to handle the ssl certs. User -> HTTPS -> Apache -> HTTP -> Jenkins 
application. Here is what my configuration looks like.

RewriteEngine On
RewriteCond %{HTTPS} !on
RewriteRule /.* https://$0 [R=301,L]


ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLCertificateFile /etc/pki/tls/certs/localhost.crt
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
SSLCertificateChainFile /etc/pki/tls/certs/localhost.crt

Header always set Strict-Transport-Security "max-age=63072000; 
includeSubDomains"
RequestHeader set X-Forwarded-Proto https
RequestHeader set X-Forwarded-Port "443"

ProxyRequests Off
ProxyPass / http://localhost:8080/ nocanon
ProxyPassReverse / http://localhost:8080/
AllowEncodedSlashes NoDecode



I can get the following to work:

  1.  http://hostname:8080
  2.  https://hostname

However, the redirect from http://hostname:8080 to https://hostname is not 
working. I stay at http://hostname:8080
The firewall port (443) is open and the server is listening.

What am I missing? ☺ I tried every combination on 
https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache but I 
can’t get the last http to https redirect to work.

Also, after I go straight to the https site and manually remove the ‘s’ in 
‘https’, it doesn’t redirect as expected back to https. I get an empty response 
(no-referrer-when-downgrade).

-- 
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/3F84EB6D-171E-4498-9249-24EA9FD93049%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins fingerprint cleanup job schedule

2017-01-19 Thread Ashish Yadav
Rachel,

Thanks for looking into this. Just a few follow up questions.

In the $JENKINS_HOME/fingerprints/
I am see a lot of directories with an xml file.

1. How are these files created?
2. If I delete these, will these be auto-generated the next time the 
fingerprint job runs?
3. Do I need to stop Jenkins before deleting these or can I delete them on the 
fly?
4. If I can delete them on the fly, is a Jenkins restart required?


Thanks,

Ashish.
From: Rachel Moreno 
mailto:raquel.moreno.carm...@gmail.com>>
Date: Thursday, January 19, 2017 at 11:53 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Cc: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Subject: Re: Jenkins fingerprint cleanup job schedule

Hi Ashish,

Jenkins uses Fingerprints in order to track files with each build.

There is a plugin to force its use, but they are enabled by default in Maven 
jobs (and it cannot be disabled).

I think you could try to delete the content of the following directory (it 
keeps XML files with Fingerprints):

$JENKINS_HOME/fingerprints/

I hope be useful.

Best regards,
Rachel

On Wednesday, 18 January 2017 17:48:57 UTC+1, Ashish Yadav wrote:
Where in Jenkins is the fingerprint cleanup job or run schedule defined? What 
does this fingerprint cleanup job do?


I am seeing A LOT of these errors everything the job runs. I even restarted 
Jenkins but I am still getting these errors. I know build #93 does not exist on 
the server. Why is this job looking specifically for that one?


Jan 18, 2017 10:35:59 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Fingerprint cleanup

Jan 18, 2017 10:36:18 AM WARNING hudson.model.RunMap retrieve

could not load 
/var/lib/jenkins/jobs/8.11/jobs/ABC/jobs/workflow/modules/com.ab.workflow$ab-service/builds/93
java.io.IOException: Unable to read 
/var/lib/jenkins/jobs/8.11/jobs/ABC/jobs/workflow/modules/com.ab.workflow$ab-service/builds/93/build.xml
at hudson.XmlFile.unmarshal(XmlFile.java:165)
at hudson.model.Run.reload(Run.java:326)
at hudson.model.Run.(Run.java:314)
at hudson.model.AbstractBuild.(AbstractBuild.java:175)
at hudson.maven.AbstractMavenBuild.(AbstractMavenBuild.java:51)
at hudson.maven.MavenBuild.(MavenBuild.java:124)
at sun.reflect.GeneratedConstructorAccessor45.newInstance(Unknown 
Source)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:156)
at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:133)
at hudson.model.RunMap.retrieve(RunMap.java:223)
at hudson.model.RunMap.retrieve(RunMap.java:56)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:479)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:461)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:367)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:318)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.oldestBuild(AbstractLazyLoadRunMap.java:278)
at 
jenkins.model.lazy.LazyBuildMixIn.getFirstBuild(LazyBuildMixIn.java:231)
at hudson.model.AbstractProject.getFirstBuild(AbstractProject.java:989)
at hudson.model.AbstractProject.getFirstBuild(AbstractProject.java:145)
at hudson.model.Fingerprint.trim(Fingerprint.java:1033)
at 
hudson.model.FingerprintCleanupThread.check(FingerprintCleanupThread.java:112)
at 
hudson.model.FingerprintCleanupThread.execute(FingerprintCleanupThread.java:75)
at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:53)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.thoughtworks.xstream.io.StreamException:  : input contained no 
data
at 
com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:126)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103)
at com.thoughtworks.xstream.io.xml.XppReader.(XppReader.java:63)
at 
com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54)
at 
com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65)
at hudson.XmlFile.unmarshal(XmlFile.java:163)
... 25 more
Caused by: java.io.EOFException: input contained no data
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
at org.xmlpull.

Jenkins fingerprint cleanup job schedule

2017-01-18 Thread Ashish Yadav
Where in Jenkins is the fingerprint cleanup job or run schedule defined? What 
does this fingerprint cleanup job do?


I am seeing A LOT of these errors everything the job runs. I even restarted 
Jenkins but I am still getting these errors. I know build #93 does not exist on 
the server. Why is this job looking specifically for that one?


Jan 18, 2017 10:35:59 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Fingerprint cleanup

Jan 18, 2017 10:36:18 AM WARNING hudson.model.RunMap retrieve

could not load 
/var/lib/jenkins/jobs/8.11/jobs/ABC/jobs/workflow/modules/com.ab.workflow$ab-service/builds/93
java.io.IOException: Unable to read 
/var/lib/jenkins/jobs/8.11/jobs/ABC/jobs/workflow/modules/com.ab.workflow$ab-service/builds/93/build.xml
at hudson.XmlFile.unmarshal(XmlFile.java:165)
at hudson.model.Run.reload(Run.java:326)
at hudson.model.Run.(Run.java:314)
at hudson.model.AbstractBuild.(AbstractBuild.java:175)
at hudson.maven.AbstractMavenBuild.(AbstractMavenBuild.java:51)
at hudson.maven.MavenBuild.(MavenBuild.java:124)
at sun.reflect.GeneratedConstructorAccessor45.newInstance(Unknown 
Source)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:156)
at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:133)
at hudson.model.RunMap.retrieve(RunMap.java:223)
at hudson.model.RunMap.retrieve(RunMap.java:56)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:479)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:461)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:367)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:318)
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.oldestBuild(AbstractLazyLoadRunMap.java:278)
at 
jenkins.model.lazy.LazyBuildMixIn.getFirstBuild(LazyBuildMixIn.java:231)
at hudson.model.AbstractProject.getFirstBuild(AbstractProject.java:989)
at hudson.model.AbstractProject.getFirstBuild(AbstractProject.java:145)
at hudson.model.Fingerprint.trim(Fingerprint.java:1033)
at 
hudson.model.FingerprintCleanupThread.check(FingerprintCleanupThread.java:112)
at 
hudson.model.FingerprintCleanupThread.execute(FingerprintCleanupThread.java:75)
at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:53)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.thoughtworks.xstream.io.StreamException:  : input contained no 
data
at 
com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:126)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103)
at com.thoughtworks.xstream.io.xml.XppReader.(XppReader.java:63)
at 
com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54)
at 
com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65)
at hudson.XmlFile.unmarshal(XmlFile.java:163)
... 25 more
Caused by: java.io.EOFException: input contained no data
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at 
com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109)
... 33 more


Jan 18, 2017 10:36:18 AM INFO hudson.model.AsyncPeriodicWork$1 run

Finished Fingerprint cleanup. 19,143 ms

-- 
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/D4A4F8B8.2888D%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


LTS 1.651.1 Clarification.

2016-11-22 Thread Ashish Yadav
Looking for clarification on the OS impacted by:


LTS 1.651.1 - OPEN issues listed below.
JENKINS-26684 -linked to-> 
JENKINS-31986 - [This 
appears to only impacts Jenkins on Windows.]
However, JENKINS-31986  
states that the issue is partly related to 
JENKINS-2584 & 
JENKINS-23831

So does this mean that 
JENKINS-2584 & 
JENKINS-23831 impact other 
OS too and not just Windows? Specifically 
JENKINS-23831.

-- 
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/D459F640.278D9%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


M2+Release+Plugin

2016-11-22 Thread Ashish Yadav
I am currently using v0.14.0 of the 
M2+Release+Plugin.
 I do NOT see an update for this plugin in the 'Update Plugins' on Plugin 
Manager page. When will v0.15.0 be release? I am waiting for v0.15.0 as it 
contains the fixe for SECURITY-170

In face, there are quite a few plugins that don't have a fix available for 
SECURITY-170.
https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170


-- 
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/D459ED1B.27886%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Shell and Path variable

2016-10-03 Thread Ashish Yadav
I created a sample job in Jenkins2.0 to get the SHELL and PATH variables.

Here is the console output:

Started by user admin
Building in workspace /var/lib/jenkins/workspace/path
[path] $ /usr/bin/zsh -xe /tmp/hudson7499585998548354807.sh
+/tmp/hudson7499585998548354807.sh:2> echo /bin/bash
/bin/bash
+ echo 
/usr/java/jdk1.8.0_101/bin:/usr/java/jdk1.8.0_101/bin:/sbin:/usr/sbin:/bin:/usr/bin
/usr/java/jdk1.8.0_101/bin:/usr/java/jdk1.8.0_101/bin:/sbin:/usr/sbin:/bin:/usr/bin
Finished: SUCCESS



  1.  What is the default shell for Jenkins. I asked for zsh but still got 
/bin/bash
  2.  Why am I seeing duplicate entires for JAVA? 
[/usr/java/jdk1.8.0_101/bin:/usr/java/jdk1.8.0_101/bin]

-- 
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/D418232D.23AB4%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Missing the Job/ExtendedRead permission

2016-09-19 Thread Ashish Yadav

Any ideas on this?

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Tuesday, September 6, 2016 at 1:58 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Missing the Job/ExtendedRead permission

I implemented the Project Based Security Matrix plugin and am able to configure 
the jobs and grant permissions accordingly. I granted myself overall Admin 
access. However, there are select jobs that I can't configure at all. I don't 
even see the 'configure' link. When I try to configure or clone the job, I am 
getting 'User missing the Job/ExtendedRead permission"

Please let me know how I can resolve this or what could be causing this. Only 
select jobs are impacted. A majority of the jobs have correct project based 
permissions.

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3F47BEE.22F7A%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D3F47BEE.22F7A%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3F6E460.22FE0%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D3F6E460.22FE0%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D40541F3.23430%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Missing the Job/ExtendedRead permission

2016-09-08 Thread Ashish Yadav
Any ideas on this?

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Tuesday, September 6, 2016 at 1:58 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Missing the Job/ExtendedRead permission

I implemented the Project Based Security Matrix plugin and am able to configure 
the jobs and grant permissions accordingly. I granted myself overall Admin 
access. However, there are select jobs that I can't configure at all. I don't 
even see the 'configure' link. When I try to configure or clone the job, I am 
getting 'User missing the Job/ExtendedRead permission"

Please let me know how I can resolve this or what could be causing this. Only 
select jobs are impacted. A majority of the jobs have correct project based 
permissions.

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3F47BEE.22F7A%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D3F47BEE.22F7A%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D3F6E460.22FE0%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Missing the Job/ExtendedRead permission

2016-09-06 Thread Ashish Yadav
I implemented the Project Based Security Matrix plugin and am able to configure 
the jobs and grant permissions accordingly. I granted myself overall Admin 
access. However, there are select jobs that I can't configure at all. I don't 
even see the 'configure' link. When I try to configure or clone the job, I am 
getting 'User missing the Job/ExtendedRead permission"

Please let me know how I can resolve this or what could be causing this. Only 
select jobs are impacted. A majority of the jobs have correct project based 
permissions.

-- 
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/D3F47BEE.22F7A%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins LTS v2.7.3 startup errors

2016-09-01 Thread Ashish Yadav
Any idea why I am getting these errors even though I don’t have Role-based or 
Matrix based or Project based Matrix Authorization strategy enabled?

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, September 1, 2016 at 8:13 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Jenkins LTS v2.7.3 startup errors

I am currently running Jenkins LTS v2.7.3. I don’t have Role-based or Matrix 
based or Project based Matrix Authorization strategy enabled. At one time I 
did. However, not I have ‘logged-in users can do anything’. During the start-up 
(or restart) of Jenkins, I am seeing a lot of the following errors in the 
Jenkins log:


Sep 01, 2016 8:16:35 AM 
hudson.security.AuthorizationMatrixProperty$ConverterImpl unmarshal
WARNING: Skipping a non-existent permission
java.lang.IllegalArgumentException: Failed to parse 
'hudson.model.Item.Release:xx' --- no such permission
at 
hudson.security.AuthorizationMatrixProperty.add(AuthorizationMatrixProperty.java:265)
at 
hudson.security.AuthorizationMatrixProperty.access$400(AuthorizationMatrixProperty.java:72)
at 
hudson.security.AuthorizationMatrixProperty$ConverterImpl.unmarshal(AuthorizationMatrixProperty.java:320)
at hudson.util.XStream2$AssociatedConverterImpl.unmarshal(XStream2.java:364)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197)
at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:176)
at hudson.util.XStream2$AssociatedConverterImpl.unmarshal(XStream2.java:364)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393)
at 
hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:331)
at 
hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
at 
com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189)
at hudson.util.XStream2.unmarshal(XStream2.java:114)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1053)
at hudson.XmlFile.read(XmlFile.java:142)
at hudson.model.Items.load(Items.java:332)
at jenkins.model.Jenkins$17.run(Jenkins.java:2823)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:998)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


Where is Jenkins getting these from, if the ‘configSecurity’ page is not 
configured for any Role/Matrix/Project based security?


Thanks,

Ashish Yadav.

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3ED93AD.22E2E%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users

Jenkins LTS v2.7.3 startup errors

2016-09-01 Thread Ashish Yadav
I am currently running Jenkins LTS v2.7.3. I don't have Role-based or Matrix 
based or Project based Matrix Authorization strategy enabled. At one time I 
did. However, not I have 'logged-in users can do anything'. During the start-up 
(or restart) of Jenkins, I am seeing a lot of the following errors in the 
Jenkins log:


Sep 01, 2016 8:16:35 AM 
hudson.security.AuthorizationMatrixProperty$ConverterImpl unmarshal
WARNING: Skipping a non-existent permission
java.lang.IllegalArgumentException: Failed to parse 
'hudson.model.Item.Release:xx' --- no such permission
at 
hudson.security.AuthorizationMatrixProperty.add(AuthorizationMatrixProperty.java:265)
at 
hudson.security.AuthorizationMatrixProperty.access$400(AuthorizationMatrixProperty.java:72)
at 
hudson.security.AuthorizationMatrixProperty$ConverterImpl.unmarshal(AuthorizationMatrixProperty.java:320)
at hudson.util.XStream2$AssociatedConverterImpl.unmarshal(XStream2.java:364)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197)
at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:176)
at hudson.util.XStream2$AssociatedConverterImpl.unmarshal(XStream2.java:364)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393)
at 
hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:331)
at 
hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
at 
com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189)
at hudson.util.XStream2.unmarshal(XStream2.java:114)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1053)
at hudson.XmlFile.read(XmlFile.java:142)
at hudson.model.Items.load(Items.java:332)
at jenkins.model.Jenkins$17.run(Jenkins.java:2823)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:998)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


Where is Jenkins getting these from, if the 'configSecurity' page is not 
configured for any Role/Matrix/Project based security?


Thanks,

Ashish Yadav.

-- 
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/D3ED93AD.22E2E%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins 2.0 requirements

2016-08-30 Thread Ashish Yadav
As per https://jenkins.io/2.0/,

> Jenkins 2 now requires Servlet 3.1 to run. If you're not using the embedded 
> Winstone-Jetty, make sure your container supports Servlet 3.1 (e.g. Tomcat 8) 
> before upgrading.
> Jenkins 2 no longer supports AJP with the embedded Winstone-Jetty container, 
> so if you're using Jenkins with a reverse proxy, please make sure it uses 
> HTTP before upgrading.

How can I confirm if I meet the above requirements? I am currently running 
Jenkins LTS v1.642.3 on CentOS v7. It's the 'standard' installation of Jenkins 
from the yum repository. How do I know if I am running Servlet 3.1 or 
Winstone-Jetty?

-- 
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/D3EB1B08.22D71%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins 2.x feature options

2016-08-29 Thread Ashish Yadav
Last week, I was upgrading one of my test instance of Jenkins from 1.642.3 to 
the latest LTS release 2.7.2. After I restarted Jenkins 2x, I got a prompt 
asking me if I want to 'enable' the new Jenkins 2x features (pipeline...). 
However, when I try to update another test VM to Jenkins 2.x, I am not seeing 
that option anymore. Am I missing an upgrade step? I am upgrading from 1.642.3 
to 2.7.2 LTS on Centos 7. I also tried a 'base clean' install of 2.7.2 and am 
not seeing that 'enable features'  option.

-- 
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/D3E9D7D6.22D2B%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Building multiple times for same and old commit

2016-08-25 Thread Ashish Yadav
I am seeing Jenkins kick off the build job 3-4 times for the same commit. Is 
most cases the commit was from an earlier time.

Example:

Commit #1: 8/24/16 at 5:34pm
 - Jenkins kicks off build job as expected.

commit notification 41365xxx


Build #2: 8/25/16 at 7:58am
 - Jenkins kicks off build job for the same commit even though it already did 
it last night.

commit notification 41365xxx

Build #3: 8/25/16 at 8:03am
 - Jenkins kicks off build job for the same commit even though it already did 
it last night.

commit notification 41365xxx




What could be causing Jenkins to build for the same commit multiple times and 
at different intervals?
I am running Jenkins v1.642.3 on CentOS 7

-- 
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/D3E459F9.22C38%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: workspace not getting cleared before or after build.

2016-07-20 Thread Ashish Yadav
Does the git "Wipe out repository & force clone" behavior only remove the 
repository or the entire workspace?

From: Mark Waite mailto:mark.earl.wa...@gmail.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Wednesday, July 20, 2016 at 8:44 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: workspace not getting cleared before or after build.

The git plugin has an "Additional Behaviour" called "Wipe out repository & 
force clone".  That is available if you're using git.

The Workspace Cleanup Plugin offers before build and after build deletion of 
the workspace.  Maybe that plugin is not installed?

Mark Waite

On Wed, Jul 20, 2016 at 7:35 AM Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
I am currently running Jenkins LTS v1.642.3 on CentOS 6. In my job configs, I 
am NOT seeing any section or task to clean the workspace before build or even 
as a Post-Build activity to clean workspace after build. Did this feature get 
removed somehow?




--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3B4E819.21FC2%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D3B4E819.21FC2%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHFSWxuO8F8cxTLQ652mx1TrNcqcFQTmxqGS4iJxMCHBg%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHFSWxuO8F8cxTLQ652mx1TrNcqcFQTmxqGS4iJxMCHBg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/D3B4FF9D.21FDA%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


workspace not getting cleared before or after build.

2016-07-20 Thread Ashish Yadav
I am currently running Jenkins LTS v1.642.3 on CentOS 6. In my job configs, I 
am NOT seeing any section or task to clean the workspace before build or even 
as a Post-Build activity to clean workspace after build. Did this feature get 
removed somehow?



-- 
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/D3B4E819.21FC2%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Git+Client+Plugin

2016-06-26 Thread Ashish Yadav
This page is not showing any version information. Getting 'blank page'.

https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin


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


Features+controlled+by+system+properties

2016-06-20 Thread Ashish Yadav
How do I list the existing values of these system parameters and do I use the 
script console to get the values or via command line on the server itself?

https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties

-- 
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/D38DC309.209C9%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins LTS v1.651.3 - OPEN issues.

2016-06-07 Thread Ashish Yadav
I am currently running Jenkins LTS v1.642.3, on CentOS 6, and am planning on 
upgrading to LTS v1.651.3 when it is released tomorrow.

Jenkins LTS v1.651.3 states that the following issues have been resolved:

What's new in 1.651.3 (2016/06/08)
Cannot enable disabled dependencies. (issue 
32340)
Listed Parameters should reflect what was used when the build ran. (issue 
34858)
Remoting: Allow Jenkins admins to adjust the socket timeout. (Controlled by 
hudson.remoting.Engine.socketTimeout) (issue 
34808)
Remoting: Allow disabling the remoting protocols individually. Allows working 
around compatibility issues like 
JENKINS-34121. (Controlled 
by PROTOCOL_CLASS_NAME.disabled) (issue 
34819)


However,
Issue 32340 is related to 
issue 32580 which is still 
OPEN
Issue 34858 is related to 
issue 34753 which is still 
OPEN
Issue 34808 is related to 
issue 22722 which is 
currently IN PROGRESS
Issue 34819 is related to 
issue 33886  which is still 
OPEN
Issue 34819 is related to 
issue 34121 which is still 
OPEN


With these issues still OPEN, is it safe to upgrade to LTS v1.651.3?

-- 
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/D37C9B18.20304%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins 2.0 in LTS changelog

2016-05-17 Thread Ashish Yadav
Will Jenkins 2.0 have it's own LTS change log or will it be added to the 
existing LTS changelog [https://jenkins.io/changelog-stable/]. If it is being 
added to the existing change log, what is the ETA or timeline? I am currently 
running LTS v1.642.3

-- 
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/D360EED1.1F8EE%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins v1.642.3

2016-04-27 Thread Ashish Yadav
I am running Jenkins v.1642.3. I just saw the following in the Jenkins log. Any 
idea was causes this and how it can be resolved?


Apr 27, 2016 12:51:47 PM WARNING 
hudson.model.Descriptor$NewInstanceBindInterceptor instantiate

falling back to default instantiation hudson.plugins.git.browser.AssemblaWeb 
{"repoUrl":"","stapler-class":"hudson.plugins.git.browser.AssemblaWeb","$class":"hudson.plugins.git.browser.AssemblaWeb"}
java.lang.IllegalArgumentException: Failed to instantiate class 
hudson.plugins.git.browser.CGit from 
{"repoUrl":"","stapler-class":"hudson.plugins.git.browser.AssemblaWeb","$class":"hudson.plugins.git.browser.AssemblaWeb"}
at 
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:602)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:404)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:400)
at 
hudson.plugins.git.browser.AssemblaWeb$AssemblaWebDescriptor.newInstance(AssemblaWeb.java:96)
at 
hudson.plugins.git.browser.AssemblaWeb$AssemblaWebDescriptor.newInstance(AssemblaWeb.java:88)
at 
hudson.model.Descriptor$NewInstanceBindInterceptor.instantiate(Descriptor.java:643)
at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:675)
at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:81)
at 
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:600)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:404)
at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:697)
at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:81)
at 
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:600)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:404)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:400)
at hudson.model.Descriptor.newInstance(Descriptor.java:588)
at hudson.scm.SCMS.parseSCM(SCMS.java:64)
at hudson.model.AbstractProject.submit(AbstractProject.java:1871)
at hudson.maven.MavenModuleSet.submit(MavenModuleSet.java:1181)
at hudson.model.Job.doConfigSubmit(Job.java:1225)
at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:796)
at sun.reflect.GeneratedMethodAccessor1408.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)  at 
org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServlet

Re: StashNotifier Plugin - version info

2016-04-18 Thread Ashish Yadav
I tried multiple browsers. The page loads, but I don't see any version history 
or release notes information.

I only see this txt at the bottom of the page: "This plugin notifies an 
Atlassian Stash instance of Jenkins builds in progress and of their results. 
The build results will show up in the commit list in Stash or in a Stash pull 
request and provide immediate and easy to scan feedback about a commit. It is 
possible to navigate from build result information in Stash directly to the 
build in question. The plugin can be configured on a per-job basis, globally 
for all Jobs or both to minimize the configuration overhead."


I am trying to determine what changes were implemented between v1.8 and 
v1.10.4. I am currently running v1.8


From: Richard Bywater mailto:rich...@byh2o.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Monday, April 18, 2016 at 4:19 PM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: StashNotifier Plugin - version info

Working for me on Chrome Mac.

Richard.

On Tue, 19 Apr 2016 at 08:57 Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
This page is coming up 'blank' for me.
https://wiki.jenkins-ci.org/display/JENKINS/StashNotifier+Plugin

I am not able to view any version history. Did the page get moved?


--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D33AB402.1EEE3%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D33AB402.1EEE3%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui9476LyTYD1gZh-ou9N%3DXWBPZMq3usJ8W5uPSzHjWSJUrAg%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAMui9476LyTYD1gZh-ou9N%3DXWBPZMq3usJ8W5uPSzHjWSJUrAg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/D33AF58B.1EEFB%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


StashNotifier Plugin - version info

2016-04-18 Thread Ashish Yadav
This page is coming up 'blank' for me.
https://wiki.jenkins-ci.org/display/JENKINS/StashNotifier+Plugin

I am not able to view any version history. Did the page get moved?

-- 
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/D33AB402.1EEE3%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Git Client Plugin - Version info

2016-04-18 Thread Ashish Yadav
This page is coming up 'blank' for me.
https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin

I am not able to view any version history. Did the page get moved?

-- 
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/D33AAB46.1EEE0%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins memory leak

2016-03-24 Thread Ashish Yadav
Termination trace (log) could be due to a network connectivity issue between 
the master and the slaves. I restarted jenkins to resolve this (termination 
request) issue.

From: Andrew Barber mailto:ajbarbe...@gmail.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 24, 2016 at 9:04 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Jenkins memory leak

Our jenkins server seems to have a slow memory leak (runs out after about 5 
days).  We noticed this after upgrading from 1.596 to 1.642.1.  I already 
increased memory space for java ( -XX:MaxPermSize=512m  -Xmx512m).

I have a heap dump and histogram, but I am not sure how to proceed.  The 
histogram starts like this



num #instances #bytes  class name
--
   1:978285  187967360  [C
   2: 42467  113726864  [B
   3:   1259878   40316096  java.lang.StackTraceElement
   4:968080   23233920  java.lang.String
   5:252385   19069600  [Ljava.lang.Object;
   6:116007   12968192  [I
   7: 829856636360  [S
   8:2047136550816  java.util.concurrent.ConcurrentHashMap$Node
   9: 913235844672  java.net.URL
  10: 566395683352  [Ljava.lang.StackTraceElement;


I don't know what [C or [B is.  Perhaps a corruption?  Also, what is going on 
with StackTraceElement?

We see a lot of these in our log

WARNING: Executor #0 for XXX-build1 : executing XXX-treemake #4203 termination 
trace
hudson.model.Computer$TerminationRequest: Termination requested at Wed Mar 23 
15:17:25 PDT 2016 by Thread[jenkins.util.Timer [#2],5,main] [id=27]
at hudson.model.Computer.recordTermination(Computer.java:219)
at hudson.model.Computer.disconnect(Computer.java:481)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:611)
at 
hudson.slaves.RetentionStrategy$Demand.check(RetentionStrategy.java:270)
at 
hudson.slaves.RetentionStrategy$Demand.check(RetentionStrategy.java:178)
at 
hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:71)
at hudson.model.Queue._withLock(Queue.java:1346)
at hudson.model.Queue.withLock(Queue.java:1229)
at 
hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:62)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)



--
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/d555b38b-70e4-4f46-b189-08151d280d4b%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/D3196D4F.1E588%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Best Practices with LTS Updates

2016-03-19 Thread Ashish Yadav
I too am running jenkins v1.609.3.

However, I am concerned about upgrading to v1.642.2 due to the following which 
was 'introduced' in v1.625.3.
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09

How can I tell if this will impact me? How can I tell if this will be an issue 
if I upgrade to v1.625.3?

I am using the following plugins:

*   Maven Integration Plugin v2.7.1
*   Javadoc Plugin v1.1
*   HTML Publisher Plugin v1.3

Is there a way to upgrade to a specific version? If I do 'yum upgrade jenkins', 
I can only upgrade to v1.625.3


From: Brian Ray mailto:be_...@sbcglobal.net>>
Reply-To: 
"jenkinsci-users@googlegroups.com" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 17, 2016 at 11:01 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: Best Practices with LTS Updates

+1 to what Chris said.

Two more cents worth of advice: When I upgrade one of our Jenkins masters (on 
LTS) I first look at the changelogs to have some idea of the delta-- potential 
gotchas, new features to evangelize, etc. Aside from critical security releases 
I typically wait a day or two after the LTS release is available in the 
unlikely event that the LTS release is not S(table). That's never been the 
case, but my bias is very conservative for this particular Jenkins master.

On Wednesday, March 16, 2016 at 5:51:42 PM UTC-7, Christopher Orr wrote:
On 14/03/16 19:36, Mark Bidewell wrote:
> I am managing the Jenkins Server for my company.  Recently, we moved
> from 1.609.3 to 1.625.3.  I noticed however that the Required Core
> Dependencies for Pipe line skipped 1.625.x and went from 1.609.1 to 1.642.1.
>
> What are the best practices for selecting LTS versions to update?  Would
> an upgrade from say 1.609.3 to 1.642.2 be safe?

You're already on LTS, so there aren't many more "best practices", other
than update regularly :)

But there should generally be no problem with upgrading between releases
that are relatively close like those two are.

Regards,
Chris

--
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/b62523a0-5e08-477d-baac-498a3722%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/D3104FD1.1DFE1%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Best Practices with LTS Updates

2016-03-19 Thread Ashish Yadav
Would this work?

 "yum localinstall 
http://pkg.jenkins-ci.org/redhat-stable/jenkins-1.625.2-1.1.noarch.rpm";

From: "Indra Gunawan (ingunawa)" mailto:ingun...@cisco.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 17, 2016 at 12:35 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: Best Practices with LTS Updates

Then don't do yum, install the Jenkins as war on Tomcat, Jetty or the embedded 
Jetty that comes with Jenkins.

From: 
mailto:jenkinsci-users@googlegroups.com>> on 
behalf of Ashish Yadav 
mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 17, 2016 at 10:21 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: Best Practices with LTS Updates

I too am running jenkins v1.609.3.

However, I am concerned about upgrading to v1.642.2 due to the following which 
was 'introduced' in v1.625.3.
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09

How can I tell if this will impact me? How can I tell if this will be an issue 
if I upgrade to v1.625.3?

I am using the following plugins:

*   Maven Integration Plugin v2.7.1
*   Javadoc Plugin v1.1
*   HTML Publisher Plugin v1.3

Is there a way to upgrade to a specific version? If I do 'yum upgrade jenkins', 
I can only upgrade to v1.625.3


From: Brian Ray mailto:be_...@sbcglobal.net>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 17, 2016 at 11:01 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: Best Practices with LTS Updates

+1 to what Chris said.

Two more cents worth of advice: When I upgrade one of our Jenkins masters (on 
LTS) I first look at the changelogs to have some idea of the delta-- potential 
gotchas, new features to evangelize, etc. Aside from critical security releases 
I typically wait a day or two after the LTS release is available in the 
unlikely event that the LTS release is not S(table). That's never been the 
case, but my bias is very conservative for this particular Jenkins master.

On Wednesday, March 16, 2016 at 5:51:42 PM UTC-7, Christopher Orr wrote:
On 14/03/16 19:36, Mark Bidewell wrote:
> I am managing the Jenkins Server for my company.  Recently, we moved
> from 1.609.3 to 1.625.3.  I noticed however that the Required Core
> Dependencies for Pipe line skipped 1.625.x and went from 1.609.1 to 1.642.1.
>
> What are the best practices for selecting LTS versions to update?  Would
> an upgrade from say 1.609.3 to 1.642.2 be safe?

You're already on LTS, so there aren't many more "best practices", other
than update regularly :)

But there should generally be no problem with upgrading between releases
that are relatively close like those two are.

Regards,
Chris

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b62523a0-5e08-477d-baac-498a3722%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/b62523a0-5e08-477d-baac-498a3722%40googlegroups.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3104FD1.1DFE1%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D3104FD1.1DFE1%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr.

java.net.MalformedURLException: no protocol

2016-02-23 Thread Ashish Yadav

I am running Jenkins v1.609.3 on CentOS.

My jenkins log is filling up with these ‘errors’. What could be causing this?


Caught exception evaluating: browser.getFileLink(p)

Caught exception evaluating: browser.getDiffLink(p)



Feb 23, 2016 9:33:52 AM WARNING hudson.ExpressionFactory2$JexlExpression 
evaluate

Caught exception evaluating: browser.getDiffLink(p) in 
/view/1/job/tests/20/changes. Reason: java.net.MalformedURLException: no 
protocol:
java.net.MalformedURLException: no protocol:
at java.net.URL.(URL.java:586)
at java.net.URL.(URL.java:483)
at java.net.URL.(URL.java:432)
at 
hudson.plugins.git.browser.GitRepositoryBrowser.getUrl(GitRepositoryBrowser.java:47)
at hudson.plugins.git.browser.Stash.getDiffLink(Stash.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at 
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at 
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)  at 
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at 
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)  at 
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at 
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at 
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.

Re: git plugin, git client plugin and git

2016-02-08 Thread Ashish Yadav

Jenkins configuration:
[cid:CCBFDFBD-D0D7-4CBE-8F58-F56D6792A92C]


I ran ‘git - - version’ on my job and it looks like it is using the ‘default’ 
git installed on the slave node instead of the git plugin [v2.2.7].
Is that correct?

Job output

$ /bin/sh -xe /tmp/hudson1026664733309319541.sh
+ git --version
git version 1.7.1

Slave Node
Slave6$ git --version
git version 1.7.1

From: Mark Waite mailto:mark.earl.wa...@gmail.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Monday, February 8, 2016 at 3:01 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: git plugin, git client plugin and git

If you enabled JGit from the Jenkins global configuration, then there will be a 
pick list in each project configuration page which allows you to select either 
the default "Git executable" or JGit as the "Git executable".

I've attached two pictures that show the difference in my project configuration 
page.

Here's the default:

[Default-Git-executable.JPG]

Here's the JGit case:

[JGit-Git-executable.JPG]

Mark Waite

On Mon, Feb 8, 2016 at 1:38 PM Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
Thanks for the clarification. How/where do I see the option for the git client 
plugin to see if it is using the command line git or jgit?

From: Mark Waite mailto:mark.earl.wa...@gmail.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Monday, February 8, 2016 at 1:11 PM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: git plugin, git client plugin and git

The git plugin presents a user interface and implements most of the Jenkins git 
use cases, including things like choosing which branches to monitor, polling 
for changes, publishing changes and tags, ignoring commits based on message 
content or submitter, remembering reference repositories, remembering timeout 
values, etc.

The git client plugin provides a git SCM abstraction and allows the user to 
select one of two implementations, either command line git, or the pure Java 
JGit implementation.  It is called by the git plugin (and by other plugins 
which need git functionality).  The git client plugin was created as a result 
of the refactoring which created git plugin 2.x.  The git plugin 1.x code was 
hard to maintain, so Kohsuke Kawaguchi, Nicolas de Loof, and others created the 
git plugin 2.x implementation, with the git client plugin extracted as a git 
SCM API.

If the command line git implementation is chosen, then the command line git 
installed on the slave which executes the job is used to perform the git 
operations.  If the JGit implementation is chosen, then git operations are 
performed within the Jenkins process.

The command line git implementation is the "reference implementation".  It has 
the most features, and seems to be the most frequently used.  There are a 
number of limitations in the JGit implementation which don't exist in the 
command line git implementation.  Those use cases which it implements are 
generally as capable as the command line git implementation.  There is a little 
more information on command line git vs. JGit at 
https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-WhyNotJGit .

Mark Waite

On Mon, Feb 8, 2016 at 11:58 AM Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
I am running Jenkins LTS v1.609.3 on CentOS.

I have the following plugins installed.
git plugin v2.2.7
git client v1.11.0


However, I also have git installed on master and the slaves.

Master - - git version 1.7.12.4
Slave #1- git version 1.8.2.1
Slave #2 - git version 1.7.12.4
Slave #3 - git version 1.8.3.1
Slave #4 - git version 1.8.3.1
Slave #5 - git version 1.8.3.1
Slave #6  - git version 1.7.1
Slave# 7 - git version 1.8.3.1
Slave #8  - git version 1.8.2.1


When a job executes on the master or the slave, which ‘git’ is it using? Is it 
the version installed on the server or the git client plugin?
Also, why do I need both the git and git client plugin? Why not just the git 
client plugin?


--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D2DE416D.1595E%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D2DE416D.1595E%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
For more options, visit https

Re: git plugin, git client plugin and git

2016-02-08 Thread Ashish Yadav
Thanks for the clarification. How/where do I see the option for the git client 
plugin to see if it is using the command line git or jgit?

From: Mark Waite mailto:mark.earl.wa...@gmail.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Monday, February 8, 2016 at 1:11 PM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: git plugin, git client plugin and git

The git plugin presents a user interface and implements most of the Jenkins git 
use cases, including things like choosing which branches to monitor, polling 
for changes, publishing changes and tags, ignoring commits based on message 
content or submitter, remembering reference repositories, remembering timeout 
values, etc.

The git client plugin provides a git SCM abstraction and allows the user to 
select one of two implementations, either command line git, or the pure Java 
JGit implementation.  It is called by the git plugin (and by other plugins 
which need git functionality).  The git client plugin was created as a result 
of the refactoring which created git plugin 2.x.  The git plugin 1.x code was 
hard to maintain, so Kohsuke Kawaguchi, Nicolas de Loof, and others created the 
git plugin 2.x implementation, with the git client plugin extracted as a git 
SCM API.

If the command line git implementation is chosen, then the command line git 
installed on the slave which executes the job is used to perform the git 
operations.  If the JGit implementation is chosen, then git operations are 
performed within the Jenkins process.

The command line git implementation is the "reference implementation".  It has 
the most features, and seems to be the most frequently used.  There are a 
number of limitations in the JGit implementation which don't exist in the 
command line git implementation.  Those use cases which it implements are 
generally as capable as the command line git implementation.  There is a little 
more information on command line git vs. JGit at 
https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-WhyNotJGit .

Mark Waite

On Mon, Feb 8, 2016 at 11:58 AM Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
I am running Jenkins LTS v1.609.3 on CentOS.

I have the following plugins installed.
git plugin v2.2.7
git client v1.11.0


However, I also have git installed on master and the slaves.

Master - - git version 1.7.12.4
Slave #1- git version 1.8.2.1
Slave #2 - git version 1.7.12.4
Slave #3 - git version 1.8.3.1
Slave #4 - git version 1.8.3.1
Slave #5 - git version 1.8.3.1
Slave #6  - git version 1.7.1
Slave# 7 - git version 1.8.3.1
Slave #8  - git version 1.8.2.1


When a job executes on the master or the slave, which ‘git’ is it using? Is it 
the version installed on the server or the git client plugin?
Also, why do I need both the git and git client plugin? Why not just the git 
client plugin?


--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D2DE416D.1595E%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D2DE416D.1595E%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEAWtW1T%3D6%3DgQfXFCxwfVMGWsF%2BA_QRbqgaZ%2BNXBXSiqg%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEAWtW1T%3D6%3DgQfXFCxwfVMGWsF%2BA_QRbqgaZ%2BNXBXSiqg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/D2DE5894.15965%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


git plugin, git client plugin and git

2016-02-08 Thread Ashish Yadav
I am running Jenkins LTS v1.609.3 on CentOS.

I have the following plugins installed.
git plugin v2.2.7
git client v1.11.0


However, I also have git installed on master and the slaves.

Master - - git version 1.7.12.4
Slave #1- git version 1.8.2.1
Slave #2 - git version 1.7.12.4
Slave #3 - git version 1.8.3.1
Slave #4 - git version 1.8.3.1
Slave #5 - git version 1.8.3.1
Slave #6  - git version 1.7.1
Slave# 7 - git version 1.8.3.1
Slave #8  - git version 1.8.2.1


When a job executes on the master or the slave, which ‘git’ is it using? Is it 
the version installed on the server or the git client plugin?
Also, why do I need both the git and git client plugin? Why not just the git 
client plugin?

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


Re: slave log file

2016-01-29 Thread Ashish Yadav
Here is the startup log


Jan 28, 2016 10:02:55 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info

Started SelectChannelConnector@0.0.0.0:8080

Jan 28, 2016 10:02:55 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info

Started Ajp13SocketConnector@0.0.0.0:8009


Jan 28, 2016 10:02:55 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info

AJP13 is not a secure protocol. Please protect port 8009


Jan 28, 2016 10:02:55 PM INFO winstone.Logger logInternal

Winstone Servlet Engine v2.0 running: controlPort=disabled


Jan 28, 2016 10:02:55 PM INFO jenkins.InitReactorRunner$1 onAttained

Started initialization


Jan 28, 2016 10:03:00 PM INFO jenkins.InitReactorRunner$1 onAttained

Listed all plugins


Jan 28, 2016 10:03:00 PM INFO 
org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$DescriptorImpl

Using new style Permission with PermissionScope


Jan 28, 2016 10:03:00 PM INFO ruby.RubyRuntimePlugin start

Injecting JRuby into XStream


Jan 28, 2016 10:03:05 PM INFO 
com.youdevise.hudson.slavestatus.SlaveListenerInitiator init

Initialising slave-status plugin


Jan 28, 2016 10:03:05 PM INFO jenkins.InitReactorRunner$1 onAttained

Prepared all plugins


Jan 28, 2016 10:03:05 PM INFO jenkins.InitReactorRunner$1 onAttained

Started all plugins


Jan 28, 2016 10:03:05 PM INFO jenkins.InitReactorRunner$1 onAttained

Augmented all extensions


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave1


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave2


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave3


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave4


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave5


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave6


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave7


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave8


Jan 28, 2016 10:03:06 PM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect slave9



As you can see the startup hangs as this step (attempting to reconnect slave9). 
If I remove the /var/lib/jenkins/nodes/slave9/config.xml and restart jenkins, 
it then hangs on ‘attempting to reconnect’  to slave 8. Looks like whatever the 
very last slave it on the list causes the issue.


We have to do multiple reboots for this to eventually work.


  1.  Any ideas what could be causing this?
  2.  Any log files we can look at to troubleshoot further?
  3.  How can I make sure that the slave.jar file is up-to-date on the slave 
nodes before restarting jenkins? How often is the slave.jar file (version) 
updated?


Thanks,

Ashish.

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, January 28, 2016 at 10:53 PM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: slave log file

Our jenkins LTS v1.609.3 keeps hanging on a reboot when trying to connect to a 
slave. In order to troubleshoot this futher, where can we access the slave’s 
log file. The same log file that you see when you manage the node. However, in 
this case, jenkins isn’t up so we can’t navigate to the slave (ssh) log file.

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D2D04C6C.1525B%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D2D04C6C.1525B%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D2D0C1F1.15273%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: slave termination error

2016-01-29 Thread Ashish Yadav
Thanks Mathus. We were able to resolve the issue by restarting the master. 
Here’s what happened. A network outage caused the master to loose connectivity 
to the slaves. After some time, the master issues a termination request to the 
slaves. When the network issue was resolved, the slaves reconnected. However, 
the termination request was never cancelled by the master.

From: Baptiste Mathus mailto:m...@batmat.net>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Friday, January 29, 2016 at 1:45 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: slave termination error


As you can see in the stack trace, this error seems to come from the 
ResponseTimeMonitor. Are per chance your master node and the build agents not 
on the same network?
Could you try pinging nodes from the master and paste the result here so that a 
can judge if it appears normal or not?

My 2 cents

Le 28 janv. 2016 4:00 PM, "Ashish Yadav" 
mailto:ashish.ya...@firemon.com>> a écrit :
Any guidance is greatly appreciated…

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Date: Thursday, January 28, 2016 at 8:09 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: slave termination error

I restarted the slave node and am now getting this error even though the job 
finishes successfully.


Jan 28, 2016 8:04:30 AM WARNING hudson.model.Executor finish2

Executor #0 for NodeABC : executing dummy-job #49 termination trace
hudson.model.Computer$TerminationRequest: Termination requested at Wed Jan 27 
21:46:03 CST 2016 by Thread[Monitoring thread for Response Time started on Wed 
Jan 27 21:46:03 CST 2016,5,main] [id=278206]
at hudson.model.Computer.recordTermination(Computer.java:216)
at hudson.model.Computer.disconnect(Computer.java:466)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:601)
at 
hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:72)
at 
hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:302)



Jan 28, 2016 8:04:30 AM WARNING hudson.model.Executor finish2

Executor #0 for NodeABC : executing dummy-job #49 termination trace
hudson.model.Computer$TerminationRequest: Termination requested at Thu Jan 28 
07:10:51 CST 2016 by Thread[Handling POST /computer/NodeABC/doDisconnect from 
xxx.xxx.xxx.xxx : RequestHandlerThread[#47],5,main] [id=273178] from HTTP 
request for http://xxx/computer/NodeABC/doDisconnect
at hudson.model.Computer.recordTermination(Computer.java:207)
at hudson.model.Computer.disconnect(Computer.java:466)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:601)
at hudson.slaves.SlaveComputer.doDoDisconnect(SlaveComputer.java:594)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)  at 
org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
at 
org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHand

slave log file

2016-01-28 Thread Ashish Yadav
Our jenkins LTS v1.609.3 keeps hanging on a reboot when trying to connect to a 
slave. In order to troubleshoot this futher, where can we access the slave’s 
log file. The same log file that you see when you manage the node. However, in 
this case, jenkins isn’t up so we can’t navigate to the slave (ssh) log file.

-- 
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/D2D04C6C.1525B%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: slave termination error

2016-01-28 Thread Ashish Yadav
Any guidance is greatly appreciated…

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Date: Thursday, January 28, 2016 at 8:09 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: slave termination error

I restarted the slave node and am now getting this error even though the job 
finishes successfully.


Jan 28, 2016 8:04:30 AM WARNING hudson.model.Executor finish2

Executor #0 for NodeABC : executing dummy-job #49 termination trace
hudson.model.Computer$TerminationRequest: Termination requested at Wed Jan 27 
21:46:03 CST 2016 by Thread[Monitoring thread for Response Time started on Wed 
Jan 27 21:46:03 CST 2016,5,main] [id=278206]
at hudson.model.Computer.recordTermination(Computer.java:216)
at hudson.model.Computer.disconnect(Computer.java:466)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:601)
at 
hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:72)
at 
hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:302)



Jan 28, 2016 8:04:30 AM WARNING hudson.model.Executor finish2

Executor #0 for NodeABC : executing dummy-job #49 termination trace
hudson.model.Computer$TerminationRequest: Termination requested at Thu Jan 28 
07:10:51 CST 2016 by Thread[Handling POST /computer/NodeABC/doDisconnect from 
xxx.xxx.xxx.xxx : RequestHandlerThread[#47],5,main] [id=273178] from HTTP 
request for http://xxx/computer/NodeABC/doDisconnect
at hudson.model.Computer.recordTermination(Computer.java:207)
at hudson.model.Computer.disconnect(Computer.java:466)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:601)
at hudson.slaves.SlaveComputer.doDoDisconnect(SlaveComputer.java:594)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)  at 
org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
at 
org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
at 
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(Anonym

Re: slave termination error

2016-01-28 Thread Ashish Yadav
 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at 
org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
at 
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)



From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, January 28, 2016 at 7:03 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: slave termination error

I am running Jenkins v1.609.3

The jobs on my slave nodes are executing correctly. However, now I am getting 
the following error for every one of my nodes.


Executor #0 for NodeABC : executing job1 #104 termination trace
hudson.model.Computer$TerminationRequest: Termination requested at Wed Jan 27 
21:46:03 CST 2016 by Thread[Monitoring thread for Response Time started on Wed 
Jan 27 21:46:03 CST 2016,5,main] [id=278206]
at hudson.model.Computer.recordTermination(Computer.java:216)
at hudson.model.Computer.disconnect(Computer.java:466)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:601)
at 
hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:72)
at 
hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:302)



All my slaves are online and connected to master. Do I need to disconnect and 
re-connect them?


--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D2CF6DE0.151AD%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D2CF6DE0.151AD%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D2CF7C88.151B8%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


slave termination error

2016-01-28 Thread Ashish Yadav
I am running Jenkins v1.609.3

The jobs on my slave nodes are executing correctly. However, now I am getting 
the following error for every one of my nodes.


Executor #0 for NodeABC : executing job1 #104 termination trace
hudson.model.Computer$TerminationRequest: Termination requested at Wed Jan 27 
21:46:03 CST 2016 by Thread[Monitoring thread for Response Time started on Wed 
Jan 27 21:46:03 CST 2016,5,main] [id=278206]
at hudson.model.Computer.recordTermination(Computer.java:216)
at hudson.model.Computer.disconnect(Computer.java:466)
at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:601)
at 
hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:72)
at 
hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:302)



All my slaves are online and connected to master. Do I need to disconnect and 
re-connect them?

-- 
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/D2CF6DE0.151AD%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: LDAP Read Timeouts

2016-01-21 Thread Ashish Yadav
Any idea what could be causing these 3 different LDAP errors?

Error 1: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP 
response read timed out, timeout used:6ms.; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms.; remaining name ‘'
Error 2: org.acegisecurity.ldap.LdapDataAccessException: Failed to obtain 
InitialDirContext due to unexpected exception; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:3ms.
Error 3: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; 
nested exception is javax.naming.PartialResultException [Root exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms. [Root exception is com.sun.jndi.ldap.LdapReferralException: 
Continuation Reference; remaining name '']; remaining name ‘’]


From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Wednesday, January 20, 2016 at 3:45 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: LDAP Read Timeouts

Additional info…

Case 1: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP 
response read timed out, timeout used:6ms.; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms.; remaining name ‘'
Case 2: org.acegisecurity.ldap.LdapDataAccessException: Failed to obtain 
InitialDirContext due to unexpected exception; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:3ms.
Case 3: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; 
nested exception is javax.naming.PartialResultException [Root exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms. [Root exception is com.sun.jndi.ldap.LdapReferralException: 
Continuation Reference; remaining name '']; remaining name ‘']


Looks like 3 different errors/conditions.




Failed to search LDAP for username=ABCD
org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP response read 
timed out, timeout used:6ms.; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms.; remaining name ''
at 
org.acegisecurity.ldap.LdapTemplate$LdapExceptionTranslator.translate(LdapTemplate.java:295)
at org.acegisecurity.ldap.LdapTemplate.execute(LdapTemplate.java:128)
at 
org.acegisecurity.ldap.LdapTemplate.searchForSingleEntry(LdapTemplate.java:246)
at 
org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:119)
at 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:839)
at 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:790)
at 
jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32)
at 
org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308)
at 
org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218)
at 
hudson.security.TokenBasedRememberMeServices2.autoLogin(TokenBasedRememberMeServices2.java:128)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedCh

Re: LDAP Read Timeouts

2016-01-20 Thread Ashish Yadav
ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at 
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949)
at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at 
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.naming.NamingException: LDAP response read timed out, timeout 
used:3ms.
at com.sun.jndi.ldap.Connection.readReply(Connection.java:481)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:365)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2788)
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
at 
com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
at 
com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)
at 
com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)
at 
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at 
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at 
javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)
at 
org.acegisecurity.ldap.DefaultInitialDirContextFactory.connect(DefaultInitialDirContextFactory.java:180)
    ... 52 more





From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Wednesday, January 20, 2016 at 2:35 PM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: LDAP Read Timeouts

I am running Jenkins version 1.609.3 with LDAP plugin version 1.11

Lately, I have been seeing these errors in the logs.


Jan 20, 2016 1:57:27 PM WARNING 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService loadUserByUsername

Failed to search LDAP for username=ABCD
org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; nested 
exception is javax.naming.PartialResultException [Root exception is 
javax.n

LDAP Read Timeouts

2016-01-20 Thread Ashish Yadav
I am running Jenkins version 1.609.3 with LDAP plugin version 1.11

Lately, I have been seeing these errors in the logs.


Jan 20, 2016 1:57:27 PM WARNING 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService loadUserByUsername

Failed to search LDAP for username=ABCD
org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; nested 
exception is javax.naming.PartialResultException [Root exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms. [Root exception is com.sun.jndi.ldap.LdapReferralException: 
Continuation Reference; remaining name '']; remaining name '']
at 
org.acegisecurity.ldap.LdapTemplate$LdapExceptionTranslator.translate(LdapTemplate.java:295)
at org.acegisecurity.ldap.LdapTemplate.execute(LdapTemplate.java:128)
at 
org.acegisecurity.ldap.LdapTemplate.searchForSingleEntry(LdapTemplate.java:246)
at 
org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:119)
at 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:839)
at 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:790)
at 
jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32)
at 
org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308)
at 
org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218)
at 
hudson.security.TokenBasedRememberMeServices2.autoLogin(TokenBasedRememberMeServices2.java:128)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at 
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949)
at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at 
org.eclipse.jetty.

Re: Jenkins unable to restart. Requires multiple attempts.

2016-01-13 Thread Ashish Yadav
Where in jenkins server are the slave configs defined? I don’t see them 
anywhere in the config.xml on MASTER.

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Tuesday, January 12, 2016 at 11:57 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Jenkins unable to restart. Requires multiple attempts.

I am currently running Jenkins v1.609.3 on CentOS release 6.5 and have about 10 
slaves connected to it.

The issue that I have is that when I attempt a reboot, the jenkins log hangs on 
‘Attempting to connect to slave xyz’. After multiple reboot attempts, it 
finally makes it pass that ‘error’ and jenkins comes up. I have checked the 
slaves and I do see a slave.jar file on all of them.

What is weird is that I don’t have ANY ‘’ section in the master jenkins 
config.xml file so where is Jenkins finding the slaves to connect to? Is there 
a way to tell jenkins to ignore connecting to a slave if it has an issue and 
‘keep moving’ to bring up jenkins? Where in jenkins server are the slave 
configs defined? I don’t see them anywhere in the config.xml on MASTER. Could 
it be cached somewhere?



Thanks,

Ashish Yadav

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D2BA9AA5.13658%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D2BA9AA5.13658%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D2BBA20E.136B4%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins unable to restart. Requires multiple attempts.

2016-01-12 Thread Ashish Yadav
I am currently running Jenkins v1.609.3 on CentOS release 6.5 and have about 10 
slaves connected to it.

The issue that I have is that when I attempt a reboot, the jenkins log hangs on 
‘Attempting to connect to slave xyz’. After multiple reboot attempts, it 
finally makes it pass that ‘error’ and jenkins comes up. I have checked the 
slaves and I do see a slave.jar file on all of them.

What is weird is that I don’t have ANY ‘’ section in the master jenkins 
config.xml file so where is Jenkins finding the slaves to connect to? Is there 
a way to tell jenkins to ignore connecting to a slave if it has an issue and 
‘keep moving’ to bring up jenkins? Where in jenkins server are the slave 
configs defined? I don’t see them anywhere in the config.xml on MASTER. Could 
it be cached somewhere?



Thanks,

Ashish Yadav

-- 
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/D2BA9AA5.13658%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: v3.9

2015-12-18 Thread Ashish Yadav
Ok. The CentOS 3.9 VM is running JRE v1.6
Would Jenkins (LTS v1.609.3) be able to run on this vm?

From: Baptiste Mathus mailto:m...@batmat.net>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, December 17, 2015 at 11:52 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: v3.9


Jenkins runs on a JVM. Then it should mostly be dependant on which JRE version 
is installable on that version.

Le 18 déc. 2015 2:52 AM, "Ashish Yadav" 
mailto:ashish.ya...@firemon.com>> a écrit :
Can Jenkins be installed and run on CentOS release 3.9?

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D298C306.12E77%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D298C306.12E77%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6CrNpgb66Wxm50nk%3DGt7ZKO4wUZLgyzJN7MhjgdjP%3DXA%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6CrNpgb66Wxm50nk%3DGt7ZKO4wUZLgyzJN7MhjgdjP%3DXA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/D2996BE9.12EB1%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


v3.9

2015-12-17 Thread Ashish Yadav
Can Jenkins be installed and run on CentOS release 3.9?

-- 
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/D298C306.12E77%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


1.625.1 and Java 7

2015-12-17 Thread Ashish Yadav
Does Jenkins LTS  v1.625.1 require all slave nodes and master to run Java 7 or 
just the master to run Java 7?

-- 
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/D2983425.12E08%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Test email broken

2015-10-07 Thread Ashish Yadav
I am currently using Jenkins version 1.596.1 and Mailer plugin version 1.15. I 
am not able to send any email. This was working prior to the upgrade. Now I am 
getting javax.mail.AuthenticationFailedException: 535 5.7.8 Error: 
authentication failed

-- 
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/D23AD62C.117C4%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


stack trace

2015-09-18 Thread Ashish Yadav
Has anyone see this error before and what could be causing it? I am running 
Jenkins version 1.596.1

Stack trace

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.596.1.jar!/lib/hudson/failed-test.jelly:30:58:
  No page found '/lib/hudson/test/failed-test.jelly' for class 
hudson.tasks.junit.TestResult
at 
org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
at 
org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)  at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)  at 
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:4

Re: Annotating JIRA ticket is not working

2015-09-16 Thread Ashish Yadav
One other note…this works sporadically. Some JIRA tickets do get updated, while 
some do not. Any ideas what might be causing this or how to resolve it?

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Tuesday, September 15, 2015 at 3:57 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Annotating JIRA ticket is not working

I have a post build action to update the JIRA ticket after the build completes. 
I am even seeing this in the logs:


Sep 15, 2015 3:43:36 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:45:22 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:45:49 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:45:49 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:46:17 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:48:52 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465’


However, the JIRA ticket is NOT getting updated. What could be causing this and 
how can I resolve it?



--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D21DF06C.11025%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D21DF06C.11025%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D21ECE26.11043%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Annotating JIRA ticket is not working

2015-09-15 Thread Ashish Yadav
I have a post build action to update the JIRA ticket after the build completes. 
I am even seeing this in the logs:


Sep 15, 2015 3:43:36 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:45:22 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:45:49 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:45:49 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:46:17 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465'


Sep 15, 2015 3:48:52 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

Annotating JIRA id: ‘AB-465’


However, the JIRA ticket is NOT getting updated. What could be causing this and 
how can I resolve it?


-- 
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/D21DF06C.11025%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins job started via pull request

2015-08-03 Thread Ashish Yadav
I’d like to kick off some CI builds based on a STASH pull request. So basically 
have Jenkins and [Atlassian] STASH talk to each other so that we can do CI 
builds when a pull request is created. What’s the easiest way to do this?


-- 
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/D1E4CCB8.10069%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: multiple LDAP connections

2015-07-07 Thread Ashish Yadav
I do have the LDAP plugin installed. In the comments it states:

"Specify the name of the LDAP server host name(s) (like ldap.sun.com). If your 
LDAP server uses a port other than 389 (which is the standard for LDAP), you 
can also append a port number here, like ldap.acme.org:1389.
Where there are multiple redundant servers separate them by spaces, if the 
first named server is not available then requests will be attempted by each of 
the named servers in order. NOTE: This is to support LDAP server fail-over, 
once an any answer has been received from a server, that answer is taken as 
definitive"

Just confirming if this is accurate and what the syntax should be. Therefore, 
should I enter the LDAP as (with a space):

ldap://ldap1.company.com:389 ldap://ldap2.company.com:389


From: Kanstantsin Shautsou 
mailto:kanstantsin@gmail.com>>
Date: Tuesday, July 7, 2015 at 7:38 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Cc: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Subject: Re: multiple LDAP connections

Currently jenkins doesn't support failovers 
https://issues.jenkins-ci.org/browse/JENKINS-15063
Also note that current security library is outdated and implementing something 
using is maybe a waste of time.
There is existed issue for it https://issues.jenkins-ci.org/browse/JENKINS-5303 
and @ndeloof even created branch in jenkins repo 
https://github.com/jenkinsci/jenkins/commits/spring-security but didn't end it.

In case of ldap you can try implement failover in ldap-plugin.
On Monday, July 6, 2015 at 9:47:27 PM UTC+3, Ashish Yadav wrote:
How do I configure jenkins to connect to multiple ldaps?

Example:
ldap://ldap1.company.com:389
ldap://ldap2.company.com:389

In case there is an issue with ldap1. I want jenkins to use ldap2 automatically.

-- 
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/D1C134A2.F874%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


multiple LDAP connections

2015-07-06 Thread Ashish Yadav
How do I configure jenkins to connect to multiple ldaps?

Example:
ldap://ldap1.company.com:389
ldap://ldap2.company.com:389

In case there is an issue with ldap1. I want jenkins to use ldap2 automatically.

-- 
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/D1C03763.F82A%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: char not showing up properly

2015-06-15 Thread Ashish Yadav
On second look, it seems that the ‘tree’ is not showing.


[cid:A87A7B13-E5F0-47EB-85D5-0692970CA235]


[cid:F2EF421D-5843-4D9C-9569-DD313B544AA2]


Any ideas?
Has anyone come across this before?

From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Monday, June 15, 2015 at 10:15 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: char not showing up properly

I am using npm and jshint-stylish to display warning icons in the log file for 
my jenkins job.

I was showing the ‘triangle’ before
[cid:86BEDD43-4152-484B-9FA8-BA60156B959A]

but now it is showing back diamonds.
[cid:AAB56A1D-7625-4893-92D9-AADE2509FE10]

Any idea what could be causing this and how to correct it?

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D1A45632.F301%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D1A45632.F301%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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/D1A49737.F339%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


char not showing up properly

2015-06-15 Thread Ashish Yadav
I am using npm and jshint-stylish to display warning icons in the log file for 
my jenkins job.

I was showing the ‘triangle’ before
[cid:86BEDD43-4152-484B-9FA8-BA60156B959A]

but now it is showing back diamonds.
[cid:AAB56A1D-7625-4893-92D9-AADE2509FE10]

Any idea what could be causing this and how to correct it?

-- 
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/D1A45632.F301%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


update user.home variable on slave node

2015-06-12 Thread Ashish Yadav
The system properties for the slave node is showing user.home as /home/jenkins

Where is this defined and how do I force/change it to /var/lib/jenkins?

I already set the $HOME on the slave node to /var/lib/jenkins but the system 
properties file is not being updated to reflect that.

-- 
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/D1A0C38B.F01C%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


sh file permissions

2015-05-08 Thread Ashish Yadav
I am trying to run a job can executes a .sh file and am getting permission 
denied. The file is owned by the jenkins user but doesn’t have execute 
permissions. If I update the file in the job workspace to have execute 
permissions, the file perms get overlaid every time the job the runs. How can 
Jenkins call and execute a .sh file in the workspace?

-- 
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/D1724D53.D14A%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: unpin plugin

2015-04-17 Thread Ashish Yadav
Yes but why would the plugin be overwritten by a lower version? I would
expect it to at least stay the same version.

On 4/17/15, 9:47 AM, "Daniel Beck"  wrote:

>On 17.04.2015, at 16:23, Ashish Yadav  wrote:
>
>> Is this expected behavior?
>
>From https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins:
>
>> Pinned plugins will never be overwritten by bundled plugins during
>>Jenkins startup.
>
>By unpinning, you allowed it to be overwritten.
>
>-- 
>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/3374809F-D965-42A1-81E7-
>00F72DEFD7A6%40beckweb.net.
>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/D1568943.C0EB%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


unpin plugin

2015-04-17 Thread Ashish Yadav
Is this expected behavior?

Current version: LDAP Plugin v 2.11 [Pinned to Jenkins]
I clicked on un-pin
After reboot of Jenkins, LDAP Plugin changed to version 2.6

It did not stay at 2.11. When you unpin a plugin, doesn’t that mean that you 
can now manually upgrade it to any later version. It should not have ‘reverted’ 
it to an older version than the one currently installed.

-- 
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/D1568197.C0E6%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Migrate Jenkins Master and Slaves Nodes

2015-04-16 Thread Ashish Yadav
I need to migrate the Jenkins Master server and Slave servers to new 
infrastructure. What is the ‘best practice’ to perform this migration other 
than just copying the JENKINS_HOME directory? What other ‘critical’ files need 
to be migrated over?

-- 
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/D1552340.C0A0%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


missing the Job/ExtendedRead permission

2015-04-09 Thread Ashish Yadav
I implemented the Project Based Security Matrix plugin and am able to configure 
the jobs and grant permissions accordingly. I granted myself overall Admin 
access. However, there are select jobs that I can’t configure at all. I don’t 
even see the ‘configure’ link. When I try to configure or clone the job, I am 
getting ‘User missing the Job/ExtendedRead permission”

Please let me know how I can resolve this or what could be causing this. Only 
select jobs are impacted. A majority of the jobs have correct project based 
permissions.

-- 
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/D14BF97E.BED0%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: plugin usage

2015-03-31 Thread Ashish Yadav
Thanks.

What does this mean?

https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Usage+Plugin+%28Communit
y%29


Supported Extension pointsSupported types of plugins (extension points)
until now:

* Builder
* BuildWrapper
* JobProperty
* Publisher
* SCM
* Trigger

Also, does anyone know of any issues with this plugin against Jenkins LTS
version 1.596.1?



On 3/31/15, 1:15 PM, "Daniel Beck"  wrote:

>Plugin Usage Plugin may help you with that.
>
>On 31.03.2015, at 20:09, Ashish Yadav  wrote:
>
>> I have quite a few plugins that are installed and some that are marked
>>for an update. How can I tell if a plug-in is still in-use/valid and by
>>which job? I want to remove plugins that are no longer in-use or needed.
>> 
>> 
>> -- 
>> 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/D1404D00.9321%25ashish.
>>yadav%40firemon.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/C4D13464-94A1-4023-A90A-
>76551915F27A%40beckweb.net.
>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/D1404F2B.9325%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


plugin usage

2015-03-31 Thread Ashish Yadav
I have quite a few plugins that are installed and some that are marked for an 
update. How can I tell if a plug-in is still in-use/valid and by which job? I 
want to remove plugins that are no longer in-use or needed.

-- 
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/D1404D00.9321%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: server-based downloads

2015-03-19 Thread Ashish Yadav
How do I setup and configure the server side collection?

From: Richard Bywater mailto:rich...@byh2o.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 19, 2015 at 12:02 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: server-based downloads


That would be why you are getting the warning then as server side metadata 
collection is the preferred method :)

Richard

On 2:36AM, Fri, 20/03/2015 Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
It was enabled.

From: Richard Bywater mailto:rich...@byh2o.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 19, 2015 at 2:50 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: server-based downloads


On that screen was " Use browser for metadata download" enabled or disabled?

Richard

On 8:33AM, Thu, 19/03/2015 Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
Any idea why I am getting this warning message and if it is ‘valid’?

On 3/18/15, 9:23 AM, "Ashish Yadav" 
mailto:ashish.ya...@firemon.com>> wrote:

>I am not sure what option I should select on the configure security page?
>
>[] Prevent Cross Site Request Forgery exploits
>
> Crumbs   Crumbs Algorithm
> [] Default Crumb Issuer
>   [] Enable proxy compatibility
>
> [] Use browser for metadata download
>
>
>Why am I getting this warning anyway?
>
>
>On 3/18/15, 9:18 AM, "Daniel Beck" mailto:m...@beckweb.net>> 
>wrote:
>
>>Try clicking the link.
>>
>>On 18.03.2015, at 15:14, Ashish Yadav 
>>mailto:ashish.ya...@firemon.com>> wrote:
>>
>>> I am getting this warning on my Manage Jenkins screen "You currently
>>>are using browser-based download to retrieve metadata for Jenkins
>>>plugins and tools. This has reliability issues and is not considered
>>>fully secure. Considerswitching to server-based download.²
>>>
>>> Could you please let me know why I am getting this warning and how I
>>>can resolve it? I didn¹t see any Œarticles¹ about this online.

--
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<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D12F3D14.8C5B%25ashish.yadav%40firemon.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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui944do3ReXJjrbSpav%2BfLM%2BJB2F%3DfZOWSbY2T1Xd2X6w41w%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAMui944do3ReXJjrbSpav%2BfLM%2BJB2F%3DfZOWSbY2T1Xd2X6w41w%40mail.gmail.com?utm_medium=email&utm_source=footer>.

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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D1303AFE.8C9E%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D1303AFE.8C9E%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui946YDcSDJWue%3DggdGL0JtZYUuMx8rhZvMTHGhHxSWkgr%3Dg%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAMui946YDcSDJWue%3DggdGL0JtZYUuMx8rhZvMTHGhHxSWkgr%3D

plugin manager

2015-03-19 Thread Ashish Yadav
I just changed my Jenkins from v1.583 to LTS 1.596.1 and am getting a warning 
on the manage jenkins page.

This version of Jenkins comes with new versions of the following plugins that 
are currently pinned in the plugin manager. It is recommended to upgrade them 
to at least the version bundled with Jenkins.
Jenkins SSH Slaves plugin
External Monitor Job Type Plugin
JUnit Plugin
Matrix Project Plugin

I looked at the link below but don’t know what is recommended.
https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins

Can you please guide me on what the correct approach is? Should I unpin the 
plugin and update? Is there any risk or concern in unpinning and updating the 
plugins? Why/how were the plugins pinned in the first place?

-- 
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/D1304E7F.8D14%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: server-based downloads

2015-03-19 Thread Ashish Yadav
It was enabled.

From: Richard Bywater mailto:rich...@byh2o.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Thursday, March 19, 2015 at 2:50 AM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: server-based downloads


On that screen was " Use browser for metadata download" enabled or disabled?

Richard

On 8:33AM, Thu, 19/03/2015 Ashish Yadav 
mailto:ashish.ya...@firemon.com>> wrote:
Any idea why I am getting this warning message and if it is ‘valid’?

On 3/18/15, 9:23 AM, "Ashish Yadav" 
mailto:ashish.ya...@firemon.com>> wrote:

>I am not sure what option I should select on the configure security page?
>
>[] Prevent Cross Site Request Forgery exploits
>
> Crumbs   Crumbs Algorithm
> [] Default Crumb Issuer
>   [] Enable proxy compatibility
>
> [] Use browser for metadata download
>
>
>Why am I getting this warning anyway?
>
>
>On 3/18/15, 9:18 AM, "Daniel Beck" mailto:m...@beckweb.net>> 
>wrote:
>
>>Try clicking the link.
>>
>>On 18.03.2015, at 15:14, Ashish Yadav 
>>mailto:ashish.ya...@firemon.com>> wrote:
>>
>>> I am getting this warning on my Manage Jenkins screen "You currently
>>>are using browser-based download to retrieve metadata for Jenkins
>>>plugins and tools. This has reliability issues and is not considered
>>>fully secure. Considerswitching to server-based download.²
>>>
>>> Could you please let me know why I am getting this warning and how I
>>>can resolve it? I didn¹t see any Œarticles¹ about this online.

--
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<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D12F3D14.8C5B%25ashish.yadav%40firemon.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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui944do3ReXJjrbSpav%2BfLM%2BJB2F%3DfZOWSbY2T1Xd2X6w41w%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAMui944do3ReXJjrbSpav%2BfLM%2BJB2F%3DfZOWSbY2T1Xd2X6w41w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/D1303AFE.8C9E%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: server-based downloads

2015-03-18 Thread Ashish Yadav
Any idea why I am getting this warning message and if it is ‘valid’?

On 3/18/15, 9:23 AM, "Ashish Yadav"  wrote:

>I am not sure what option I should select on the configure security page?
>
>[] Prevent Cross Site Request Forgery exploits
>
> Crumbs   Crumbs Algorithm
> [] Default Crumb Issuer
>   [] Enable proxy compatibility
>
> [] Use browser for metadata download
>
>
>Why am I getting this warning anyway?
>
>
>On 3/18/15, 9:18 AM, "Daniel Beck"  wrote:
>
>>Try clicking the link.
>>
>>On 18.03.2015, at 15:14, Ashish Yadav  wrote:
>>
>>> I am getting this warning on my Manage Jenkins screen "You currently
>>>are using browser-based download to retrieve metadata for Jenkins
>>>plugins and tools. This has reliability issues and is not considered
>>>fully secure. Considerswitching to server-based download.²
>>> 
>>> Could you please let me know why I am getting this warning and how I
>>>can resolve it? I didn¹t see any Œarticles¹ about this online.

-- 
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/D12F3D14.8C5B%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: server-based downloads

2015-03-18 Thread Ashish Yadav
I am not sure what option I should select on the configure security page?

[] Prevent Cross Site Request Forgery exploits

 Crumbs   Crumbs Algorithm
 [] Default Crumb Issuer
   [] Enable proxy compatibility

 [] Use browser for metadata download


Why am I getting this warning anyway?


On 3/18/15, 9:18 AM, "Daniel Beck"  wrote:

>Try clicking the link.
>
>On 18.03.2015, at 15:14, Ashish Yadav  wrote:
>
>> I am getting this warning on my Manage Jenkins screen "You currently
>>are using browser-based download to retrieve metadata for Jenkins
>>plugins and tools. This has reliability issues and is not considered
>>fully secure. Considerswitching to server-based download.²
>> 
>> Could you please let me know why I am getting this warning and how I
>>can resolve it? I didn¹t see any Œarticles¹ about this online.
>> 
>> -- 
>> 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/D12EF268.8BBD%25ashish.
>>yadav%40firemon.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/205A0F81-2B4A-4064-A633-
>DBB2413435D1%40beckweb.net.
>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/D12EF3D3.8BC1%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


server-based downloads

2015-03-18 Thread Ashish Yadav
I am getting this warning on my Manage Jenkins screen "You currently are using 
browser-based download to retrieve metadata for Jenkins plugins and tools. This 
has reliability issues and is not considered fully secure. Considerswitching to 
server-based download.”

Could you please let me know why I am getting this warning and how I can 
resolve it? I didn’t see any ‘articles’ about this online.

-- 
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/D12EF268.8BBD%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Slave To Master Access Control config

2015-02-13 Thread Ashish Yadav
Dick,

Thanks for the prompt reply. Appreciate it. :)

From: , Dick 
mailto:dick.gi...@perkinelmer.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Friday, February 13, 2015 at 12:15 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: RE: Slave To Master Access Control config

Ashish, I think if your slaves are dedicated Jenkins build slaves and not used 
by anybody else, then you leave the subsystem off. This is the situation I have 
and I left it off.

How can I tell if a slave is executing anything on the master? I don't think it 
is currently doing so. How can I confirm this?

A job runs entirely ON the slave machine except for a small thread on the 
master that starts and sends commands to the slave. I guess you can look for a 
folder called Workspace in the Jobs/your-job/ area on the Master.

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ashish Yadav
Sent: Friday, February 13, 2015 11:28 AM
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Slave To Master Access Control config

Can someone please help me understand 
https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control ?

I have some jobs that are configured to run on a specific slave. These jobs are 
only dedicated to run on the specific slaves via the use of labels. Therefore, 
should i turn ON the access control or leave it OFF?
What is the definition of a 'Trusted Slave' in this context?

The slaves were built by me and I am the administrator for both the master and 
the slave nodes.

How can I tell if a slave is executing anything on the master? I don't think it 
is currently doing so. How can I confirm this?

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D1038235.8129%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D1038235.8129%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F8472%40AMERMBX02.PERKINELMER.NET<https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F8472%40AMERMBX02.PERKINELMER.NET?utm_medium=email&utm_source=footer>.
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/D1039C41.8151%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Slave To Master Access Control config

2015-02-13 Thread Ashish Yadav
Can someone please help me understand 
https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control ?

I have some jobs that are configured to run on a specific slave. These jobs are 
only dedicated to run on the specific slaves via the use of labels. Therefore, 
should i turn ON the access control or leave it OFF?
What is the definition of a 'Trusted Slave' in this context?

The slaves were built by me and I am the administrator for both the master and 
the slave nodes.

How can I tell if a slave is executing anything on the master? I don't think it 
is currently doing so. How can I confirm this?

-- 
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/D1038235.8129%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Re: Slave To Master Access Control

2015-02-11 Thread Ashish Yadav
Just a slight clarification. "These jobs are only dedicated to run on the 
specific slaves via labels.”

I am still not clear if this setting should be enabled or kept disabled.


From: Baptiste Mathus mailto:m...@batmat.net>>
Reply-To: 
"jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Wednesday, February 11, 2015 at 3:50 PM
To: "jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: Slave To Master Access Control


This article tasks about the Jenkins architecture for master/slaves 
relationship. This is totally unrelated to running/allowing jobs on some slaves.

(Btw, attaching jobs to node/slave instead of labels is considered a bad idea)

Cheers

Le 11 févr. 2015 16:41, "Ashish Yadav" 
mailto:ashish.ya...@firemon.com>> a écrit :
Can someone please help me understand 
https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control ?

I have some jobs that are configured to run on a specific slave. These jobs are 
only dedicated to run on the specific slaves. Therefore, should i turn ON the 
access control or leave it OFF?
What is the definition of a Trusted Slave in this context?

The slaves were built by me and I am the administrator for both the master and 
the slave nodes.

How can I tell if a slave is executing anything on the master? I don't think it 
is currently doing so. How can I confirm this?


--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D100D43D.802F%25ashish.yadav%40firemon.com<https://groups.google.com/d/msgid/jenkinsci-users/D100D43D.802F%25ashish.yadav%40firemon.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS55_FEaEuHcCAHVQN-7mCY9BiFujKCRk%2BCM6dqnyvp9OQ%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS55_FEaEuHcCAHVQN-7mCY9BiFujKCRk%2BCM6dqnyvp9OQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/D1012BA9.8059%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.


Slave To Master Access Control

2015-02-11 Thread Ashish Yadav
Can someone please help me understand 
https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control ?

I have some jobs that are configured to run on a specific slave. These jobs are 
only dedicated to run on the specific slaves. Therefore, should i turn ON the 
access control or leave it OFF?
What is the definition of a Trusted Slave in this context?

The slaves were built by me and I am the administrator for both the master and 
the slave nodes.

How can I tell if a slave is executing anything on the master? I don't think it 
is currently doing so. How can I confirm this?

-- 
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/D100D43D.802F%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.