Scripts not permitted to use staticMethod in Extensible Choice System Groovy

[Victoria Kozel]

Hello,

I am writing a simple groovy script to display role-based choices in the 
Extensible Choice. I get 

org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts 
not permitted to use staticMethod jenkins.model.Jenkins getInstance


when calling 


def authStrategy = Jenkins.instance.getAuthorizationStrategy()


I am not sure I understand the reason for this, but my question is - Is there a 
workaround for this error?


Thank you!!

Vicki

-- 
You received this message because you are subscribed to the Google 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/a7a4b4ab-a2fc-4e2b-8363-692b0f17ee67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: email-ext: "requester" option not available in Send to area

[Sébastien Hinderer]

Slide (2017/04/20 20:16 +):
> Did you expand the "Advanced" area of the plugin configuration?

I think I did that but perhaps I should retry with sighted assistance --
I am blind.

Will keep you posted at the beginning of next week.

Thanks,

Sébastien.

-- 
You received this message because you are subscribed to the Google 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/20170420205748.wa3qc2xtfafnv6gi%40pl-59055.rocqadm.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Re: email-ext: "requester" option not available in Send to area

[Slide]

Did you expand the "Advanced" area of the plugin configuration?

On Thu, Apr 20, 2017 at 6:22 AM Sébastien Hinderer <
sebastien.hinde...@inria.fr> wrote:

> Dear all,
>
> I just installed the latest version (2.57.2) of the email-ext plugin on
> a 2.32.3 LTS instance of Jenkins.
>
> I'd like the requester of a job to be notified of its result but can't
> achieve this, because the option to send the e-mail to the requester is
> not displayed. Neither is the possibility to include culprists, by the
> way.
>
> Can you think of any reason for this behaviour?
>
> Many thanks in advance for your help,
>
> Sébastien.
>
> --
> You received this message because you are subscribed to the Google 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/20170420132209.ujkpmtr7mh446lwi%40pl-59055.rocqadm.inria.fr
> .
> 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/CAPiUgVd%2BGs9HgxnT7Jh%2BHw%3DGKddmRzy%2BQG6394gJ7TzE-5kHXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publish Coverity plugin results via Email

[Victor Martinez]

You could potentially use the ext-email plugin:
- https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
and extend it to show those coverity details:
- 
https://github.com/jenkinsci/email-ext-plugin/tree/master/src/main/resources/hudson/plugins/emailext/templates

There is a closed ticket about that
- https://issues.jenkins-ci.org/browse/JENKINS-15336

Cheers


On Thursday, 20 April 2017 09:32:46 UTC+1, Nitzan Yemal wrote:
>
> Hi,
>
> I started to use Coverity plugin in our Jenkins and I wanted to know if I 
> can publish the scan results via mail? is there ant HTML file created in 
> that scan which I can send? 
> Is there a list pf Coverity environment variable I can use instead?
>
> Thanks,
> Nitzan
>

-- 
You received this message because you are subscribed to the Google 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/5a8fb1d2-e0a9-4dad-9e57-b6daee0894bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 500 error when saving a configuration or creating a job

[Ralph Goers]

Nevermind. Our nginx proxy was out of disk space.

Thanks
Ralph

On Thursday, April 20, 2017 at 9:33:21 AM UTC-7, Ralph Goers wrote:
>
> I just recently upgraded Jenkins from 2.7 to 2.55. After restarting 
> everything was fine.  Yesterday I went to the manage plugin page and 
> upgraded all the plugins except for those that said they use different 
> settings and will require jobs to be reconfigured.  Today when updating a 
> configuration and hitting save or trying to create a new job a 500 error is 
> shown on the screen. There are no errors in catalina.out.
>
> How can I determine what is causing the problem?
>
> Ralph
>

-- 
You received this message because you are subscribed to the Google 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/d99088b4-8227-4d05-8d5f-03fa2c0de34e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: getting error when trying to configure Jenkins with PTC Integrity

[Magnanao, Hector]

Is anyone able to help me with this ? I sent this out 10 days ago.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of hector.magna...@sap.com
Sent: Monday, April 10, 2017 3:02 PM
To: Jenkins Users 
Subject: getting error when trying to configure Jenkins with PTC Integrity

I'm having a problem trying to configure Jenkins with our PTC Server.  We get 
this error when we try to test the connection from our Jenkins client.  Below 
are the Jenkins settings:

Jenkins version:  1.631
JAVA version: JDK1.8.0_74
PTC Version:  10.6

Stack trace

javax.servlet.ServletException: java.lang.AbstractMethodError: 
com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket;

at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)

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:132)

at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:200)

at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178)

at 
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85)

at 
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99)

at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129)

at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)

at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129)

at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59)

at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129)

at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)

at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129)

at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)

at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)

at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)

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:171)

at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)

at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)

at 

500 error when saving a configuration or creating a job

[Ralph Goers]

I just recently upgraded Jenkins from 2.7 to 2.55. After restarting 
everything was fine.  Yesterday I went to the manage plugin page and 
upgraded all the plugins except for those that said they use different 
settings and will require jobs to be reconfigured.  Today when updating a 
configuration and hitting save or trying to create a new job a 500 error is 
shown on the screen. There are no errors in catalina.out.

How can I determine what is causing the problem?

Ralph

-- 
You received this message because you are subscribed to the Google 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/f1097076-398e-463b-a913-375d8d14f0a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Can't find global maven settings configuration ...

[Jeff]

We just spun up a new Jenkins server (Ubuntu 16.04/tomcat7/java8/Jenkins
v2.55) from scratch and am trying to configure both the user and global
Maven settings.xml.

I've gone into "Managed Files" and added the settings.xml files:

 [image: Inline image 3]

But nowhere in the "Maven Project Configuration" of the "Configure System"
page can I find the dialogs controlling the maven settings.xml.

All the documentation I can find shows what I can only assume are plugin
options from an older version of the plugin that look similar to:

 [image: Inline image 4]

The above options are not to be found.  Am I missing something?

-- 
You received this message because you are subscribed to the Google 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/CAPJK9%3DKC635O_xWYoUpAN_6YWLRp-Q9uTeYc_4kO%2BRE67Y%2BfMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

how to configure a custom parser for jenkins Warnings plugin

[Sylvain Plancoulaine]

Hi all,

I am trying to do a user defined parser using the gui for 
https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin 

According to documentation, it should be easy to understand, but It is not 
so straight forward to me to understand what should i do.
I am far to be familiar with that and don't know what is groovy


For *Name*, it is clear: I can do what I want: *my_personal_parser*

For *Link name* : I do not understand hyperlinks to what

*Trend report name* : An arbitrary name Compiler Warnings Trend

*Regular expression*   : something like this should be good 
*\*W,(\w+)\s+\(.*\)* but I don't exactly understand what should match

*Mapping script*: Do you have example of groovy script, or link to 
documentation? I also do not properly understand what log parser is waiting

an example of log message in my case is:
*xmelab: *W,DLCIML (../systemc/bin/plt/foo/cds.lib,1): cds.lib CDS.LIB file 
included multiple times 
'/sw/cadence/xcelium/16.11.002/lnx86/tools.lnx86/inca/files/cds.lib' 
(cds.lib command ignored).*
*TOOL: xmelab(64) 16.11-s002: Started on Apr 12, 2017 at 18:11:40 CEST*

Thank for your help,

Br,

Sylvain

-- 
You received this message because you are subscribed to the Google 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/2e4ef3f8-c009-4515-b349-b040e83f0b4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Call something to force "Please wait while Jenkins is getting ready to start" to show?

[Matthew Strickland]

We're running a lot of startup scripts for our jenkins box (user_data on 
our EC2 instance, mounting etc), is there a way to get the inbuilt start 
screen to show up (through a groovy script perhaps) and then to take it 
back down again so that anyone trying to use the box in this time is unable 
to?

Failing that, is there anyway to lock Jenkins from being used at all until 
we say it's ready? (No login screen even)

Thanks

Matt

-- 
You received this message because you are subscribed to the Google 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/74f15ce6-95b5-4dcb-8c5f-33ca04252dc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: How to specify svn credentialsId in pipeline job?

[David Aldrich]

The snippet generator has solved this for me:

additionalCredentials: [[credentialsId: '', realm: '']],

From: David Aldrich
Sent: 20 April 2017 16:29
To: 'thomas.lehm...@teamaol.com' ; Jenkins Users 

Subject: RE: How to specify svn credentialsId in pipeline job?

Hi Thomas

The credentialsId is now working fine for me, thanks for your help.

However, my svn checkout involves an external, which is not appearing in the 
workspace.  I guess I need to specify ‘additional credentials’.  I tried:

stage('Checkout') {
checkout([$class: 'SubversionSCM',
additionalCredentials: [credentialsId: 
'086c0d1a-15e7-4cea-9702-7528ac021fab'],
excludedCommitMessages: '',
excludedRegions: '',
excludedRevprop: '',
excludedUsers: 'buildbot',
filterChangelog: false,
ignoreDirPropChanges: false,
includedRegions: '',
locations: [[credentialsId: '086c0d1a-15e7-4cea-9702-7528ac021fab',
depthOption: 'infinity',
ignoreExternalsOption: true,
local: '.',
remote: "https://172.29.68.12/subversion/Leda/trunk/;]],
workspaceUpdater: [$class: 'UpdateUpdater']])
}

But that failed. I think my setting for additionalCredentials is wrong.  Can 
you help me correct the syntax please?

Best regards

David


From: thomas.lehm...@teamaol.com 
[mailto:thomas.lehm...@teamaol.com]
Sent: 20 April 2017 12:48
To: Jenkins Users 
>
Cc: thomas.lehm...@teamaol.com; David 
Aldrich >
Subject: Re: How to specify svn credentialsId in pipeline job?

You assing it to the parameter credentialsId.

On Thursday, April 20, 2017 at 1:13:20 PM UTC+2, David Aldrich wrote:
Thanks, I see it now. The credential does have a readable name.  Can I assign 
that name to credentialsId or should it be assigned to a different property?

From: thomas@teamaol.com 
[mailto:thomas@teamaol.com]
Sent: 20 April 2017 12:11
To: Jenkins Users 
Cc: thomas@teamaol.com; David Aldrich 

Subject: Re: How to specify svn credentialsId in pipeline job?

Click on the link an a table is shown and there is the columns ID ...
One note: if you forgot to provide a readable name you cannot change it. You 
have to re-create it then.

On Thursday, April 20, 2017 at 1:07:53 PM UTC+2, 
thomas@teamaol.com wrote:
When you click top/left on "Jenkins" (navigate to the mainpage) the link to the 
credentials
should appear on the left side (short before build queue).

On Thursday, April 20, 2017 at 12:59:31 PM UTC+2, David Aldrich wrote:
Thanks for your reply. I am an admin so I should be able to see everything.  
Where should I look for the credentials?

All our conventional jobs use the following credential seen on the job 
configuration page:

[https://lh5.googleusercontent.com/proxy/2i_Y0VgsbT3dDPnTx8xHlJoAJ_X4wU49L48fmjFQl1Fn6JpdOKhrhD0teLxJBFM-h17yECb8qRBvV3aQbAPzSIwIT5vm7Ak0yey-kZhQVShbsOe17M_qRCFv6oz4XJwVf23Pci55b2Vkj5i1xVVVGV48EKaXLdOi=w5000-h5000]

Where should I look for the corresponding credentialId?

Best regards

David

From: thomas@teamaol.com 
[mailto:thomas@teamaol.com]
Sent: 20 April 2017 11:39
To: Jenkins Users 
>
Cc: David Aldrich >
Subject: Re: How to specify svn credentialsId in pipeline job?

Usually the adminstrator of a Jenkins is reponsible to register credentials
with a useful (readable) name. If those admin forget to give a name Jenkins
does it for your which results usually in something like this: 
"b86bc2b6-994b-4811-ac98-0f35e9a9b114'

Of course you don't wanna have such ID's in your coded pipeline. Consider
you might have running your pipeline on different Jenkins providing the same
credentials (names) your project should be able to build without code changes.

It might be a permission thing that you cannot see the credentials.


On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
Hi

I have created a simple pipeline job that is intended just to check out a 
working copy from svn initially.

Here's the script:

node {
   echo 'Hello World'

   stage('Checkout') {
  checkout([$class: 'SubversionSCM',
  additionalCredentials: [],
  excludedCommitMessages: '',
  excludedRegions: '',
  excludedRevprop: '',
  excludedUsers: 'buildbot',
  filterChangelog: false,
  ignoreDirPropChanges: false,
  includedRegions: '',
  locations: [[credentialsId: 'b86bc2b6-994b-4811-ac98-0f35e9a9b114',
   depthOption: 'infinity',
  

Git Parameter Plug-in does not list Git commit Ids

[Sukumar Reddy]

Hello All,

we are using jenkins 2.7.22.0.3 (cloudbees version)
Configured build parameterized job and i am able to view the git commit ids 
in git parameter box

Attached images for better understanding. Please suggest me if any one has 
come across similar issue

-- 
You received this message because you are subscribed to the Google 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/b20eef6a-fc35-4a74-b966-c33cd3d789f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't capture command results in Kubernetes Pipeline Jenkinsfile

[Mark Nuttall]

In case anyone else finds this topic, the key link 
is https://jenkins.io/doc/book/pipeline/jenkinsfile/

"Only the [double quoted form] will support the dollar-sign ($) based 
string interpolation"

-- 
You received this message because you are subscribed to the Google 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/c6de5e7b-e504-41de-93c9-e96ae4499687%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to restore to previous state after automatic update

[Mark Waite]

That's good.  You have the system running again.

You'll probably have the exact same problem the next time you (or someone
else) updates plugins.  This is a good time to switch to Java 8, and
confirm that you have successfully switched to Java 8.

You'll need to install Java 8 on the machine, confirm that Java 8 is the
default Java, then find the Jenkins configuration which starts your Jenkins
server, confirm it is using Java 8, then verify Java 8 is used from the
"System Information" page for the master agent.

Mark Waite

On Thu, Apr 20, 2017 at 8:26 AM CNemo  wrote:

> I got it up and running doing following:
>
> 1. Renamed Plugins directory. Did not helped.
> 2. Installed 1.8 on a box. Did not helped
> 3. Renamed local copy of JRE and copied one from fresh installation.
> Reverted back plugins. Started just fine.
>
> Thought I do not know if this set of actions OK and there is better way of
> fixing 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/8ac8f636-b1c9-49a3-bca2-f17679caf35f%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/CAO49JtEwZRahcg2q%2B9SA-3_EjM8GKn7Mj6Q2pCTVZy4xpPoFMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to restore to previous state after automatic update

[CNemo]

I got it up and running doing following:

1. Renamed Plugins directory. Did not helped.
2. Installed 1.8 on a box. Did not helped
3. Renamed local copy of JRE and copied one from fresh installation. 
Reverted back plugins. Started just fine.

Thought I do not know if this set of actions OK and there is better way of 
fixing 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/8ac8f636-b1c9-49a3-bca2-f17679caf35f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to restore to previous state after automatic update

[CNemo]

Mark,

thank you for your reply! That's what I've suspected too. Problem is that 
I'm absolutely not sure what I really need to do.
I understand that It should be simple to install additional JDKs from 
Jenkins Configuration UI, but I'm not able to start Jenkins. Would be 
installing JDK 1.8 on the box enough to fix my problem? Looking at command 
line in log, I tend to believe that Jenkins windows service is pulling 
configuration from somewhere and falling back to local JRE, that is located 
in subdirectory.
Where I can point Jenkins core to a specific JDK?

Also how I can disable plugins without using UI? I attempted rename plugins 
directory to no avail.

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

email-ext: "requester" option not available in Send to area

[Sébastien Hinderer]

Dear all,

I just installed the latest version (2.57.2) of the email-ext plugin on
a 2.32.3 LTS instance of Jenkins.

I'd like the requester of a job to be notified of its result but can't
achieve this, because the option to send the e-mail to the requester is
not displayed. Neither is the possibility to include culprists, by the
way.

Can you think of any reason for this behaviour?

Many thanks in advance for your help,

Sébastien.

-- 
You received this message because you are subscribed to the Google 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/20170420132209.ujkpmtr7mh446lwi%40pl-59055.rocqadm.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Slave JVM randomly dies on large machines

[Steffen Schröter]

Hi,

i have a little problem with the slave JVM randomly dying on our larger
build machines. When these machines are under heavy load the following
error tends to pop up somewhat randomly on the slave connection:

https://pastebin.com/raw/BaY2rJ7G

The likeliness of these errors increases with the amount of builds running
on the slave. If i allow only 20 executors it occurs very rarely or never
while with 100 executors its quite likely for the slave to disconnect from
this once all executors have a job running on them.

The affected machines are dual socket systems with two 18 Core Xeon CPUs
making for 36 cores and 72 threads (HT). 384GB RAM (or more) are installed
of which 200GB are assigned to a ramdisk (tmpfs). This ramdisk is used for
the jenkins workspace.

As OS we use Debian 8 (Jessie) with the 4.9 kernel from backports. The
Jenkins version is 2.55 and the installed Java version is OpenJDK
1.8.0_121.

The running builds are mostly larger C projects being compiled with gcc
and some latex documentation.

Since it occurs only with many parallel builds running this somewhat
suggests that we might be hitting some kind of limit that causes the slave
process to be terminated. However there is nothing in the logs
(journalctl, dmesg) hinting at that and as far i know neither the oom
killer nor ulimit use SIGTERM for that purpose.

The following limits are reported by `ulimit -a`:
https://pastebin.com/raw/RXXWnc49

Anyone happen to have an idea what might be the cause or what else i could
look at?

-- 
You received this message because you are subscribed to the Google 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/236d182d6e7e9aaff19b2fb0e642adc5.squirrel%40user.vexar.de.
For more options, visit https://groups.google.com/d/optout.

Declarative Pipeline - Agent wonderment

[Danny Rehelis]

Help me understand this please, in case my Pipeline looks like this -

pipeline {
agent none
stages {
stage ('Stage #1') {
agent { label 'builder' }
steps {
echo "Hello World"
}
}
stage ('Stage #2') {
agent { label 'builder' }
steps {
echo "Hello World"
}
}
}
}

Will the second stage run on the same builder labeled server instance (same
one from first stage) or will pick any other possibly idle labeled server
available at the time?
Is it possible to force "stickiness" for explicitly configured agents?

-- 
You received this message because you are subscribed to the Google 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/CAObRFCUJrs_BrOqrDXH62E_27JpL3bBQDJf%3DWsWkdEO%3D8CmKdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't capture command results in Kubernetes Pipeline Jenkinsfile

[Mark Nuttall]

Having asked the question I've now stumbled onto the answer: I'm just not 
printing the result correctly. The correct syntax to print variables is, 

echo "c = ${c}"


It needs to be double quotes and not single quotes in order for the 
variable substitution 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b9dcfe8d-e311-4664-b4b0-e18dd194c270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Basic pipeline questions (using svn)

[David Aldrich]

Hi

Sorry for asking basic questions, but I need some help with my first pipeline. 
Here's what I have so far:

node {
stage('Checkout') {
checkout([$class: 'SubversionSCM',
additionalCredentials: [],
excludedCommitMessages: '',
excludedRegions: '',
excludedRevprop: '',
excludedUsers: 'buildbot',
filterChangelog: false,
ignoreDirPropChanges: false,
includedRegions: '',
locations: [[credentialsId: '086c0d1a-15e7-4cea-9702-7528ac021fab',
depthOption: 'infinity',
ignoreExternalsOption: true,
local: '.',
remote: "https://172.29.68.12/subversion/Leda/trunk/;]],
workspaceUpdater: [$class: 'UpdateUpdater']])
}
}


1)  How do I specify a specific node?

2)  How do I emulate the conventional job's checkout strategy 'Use 'svn 
update' as much as possible' so that a checkout is done if the workspace is 
empty or an update is done if a previous checkout exists?


Best regards

David

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

Re: Can't capture command results in Kubernetes Pipeline Jenkinsfile

[thomas . lehmann]

Easy thing ;)
The variable "c" is not know by the shell script

withEnv(["c=$c"]){
   sh 'c=${c}'
}




On Thursday, April 20, 2017 at 1:55:34 PM UTC+2, Mark Nuttall wrote:
>
> Hello, 
> I'm porting an existing Jenkinsfile to use the kubernetes plugin and its 
> syntax. I've hit a problem in which I need to get the result of a shell 
> command, but get only empty strings. This code worked correctly until being 
> ported to the kubernetes plugin syntax. 
>
> Here's my Jenkinsfile, showing a simple command just to help explain the 
> problem:
>
> #!groovy
>
> podTemplate(
>   label: 'mypod',
>   containers: [containerTemplate(name: 'maven', image: 'maven:3.5.0-jdk-8'
> , ttyEnabled: true, command: 'cat')],
> ){
>   node('mypod') {
> stage ('build') {
>   container ('maven') {
> sh 'ls > out.txt'
> sh 'cat out.txt'
>
> def c = sh(script: 'cat out.txt', returnStdout: true).trim();
> sh 'echo c = ${c}'
>
>
> def c2 = readFile('out.txt').trim()
> sh 'echo c2 = ${c2}'
>   }
> }
>   }
> }
>
> The relevant output, below, is very long but it shows that the 'ls' 
> command runs successfully, and that I can cat the result of that file: but 
> I am completely unable to read the file into a variable, or to execute the 
> command and store the result as a variable, which is what I really want to 
> do. I've highlighted the relevant sections in yellow. Please help me, I'm 
> getting desperate :-(
>
> Many thanks,
>
> -- Mark
>
> # # + ls
>
> [Pipeline] sh[sample.microservicebuilder.test] Running shell script
> Executing shell script inside container [maven] of pod 
> [kubernetes-991f3f512a3e4c13aa5c7960410311bb-25c6ad58b93c]
> Executing command: sh -c echo $$ > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/pid';
>  jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/script.sh'
>  > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-log.txt'
>  2>&1; echo $? > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-result.txt'
>  
> # cd "/home/jenkins/workspace/sample.microservicebuilder.test"
> sh -c echo $$ > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/pid';
>  jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/script.sh'
>  > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-log.txt'
>  2>&1; echo $? > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-result.txt'
>  
> exit*# # + cat out.txt
> Dockerfile
> Jenkinsfile
> README.md
> manifests
> out.txt
> pom.xml
> server.xml
> src*[Pipeline] sh[sample.microservicebuilder.test] Running shell script
> Executing shell script inside container [maven] of pod 
> [kubernetes-991f3f512a3e4c13aa5c7960410311bb-25c6ad58b93c]
> Executing command: sh -c echo $$ > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/pid';
>  jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/script.sh'
>  > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/output.txt'
>  2> 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-log.txt';
>  echo $? > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-result.txt'
>  
>
> # cd "/home/jenkins/workspace/sample.microservicebuilder.test"
> sh -c echo $$ > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/pid';
>  jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/script.sh'
>  > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/output.txt'
>  2> 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-log.txt';
>  echo $? > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-result.txt'
>  
> exit
> # # + cat out.txt[Pipeline] sh[sample.microservicebuilder.test] Running shell 
> script
> Executing shell script inside container [maven] of pod 
> [kubernetes-991f3f512a3e4c13aa5c7960410311bb-25c6ad58b93c]
> Executing command: sh -c echo $$ > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/pid';
>  jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/script.sh'
>  > 
> '/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/jenkins-log.txt'
>  2>&1; echo $? > 
> 

Re: Even after having 'wipe out repository & force clone' option, my workspace is not fresh

[Mark Waite]

I'm surprised that doesn't work in a pipeline context.  I thought I had
integration tests which were checking that.  I'll need to double check.
Please submit a bug report with steps to duplicate the problem.

Pipeline has the deleteDir() step which will delete the contents of the
current directory, or, when wrapped in a dir() step, it will delete the
contents of that directory.  Refer to
https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#deletedir-recursively-delete-the-current-directory-from-the-workspace
for
the documentation.  That will give you explicit control to delete the
contents of the directory from within the pipeline step, without adding the
WipeWorkspace extension to your checkout() step.

In your pipeline, are you using the git() step or the more general purpose
checkout() step?  If you're using the git() step, you may need to switch to
the checkout() step.

Mark Waite

On Thu, Apr 20, 2017 at 3:45 AM ishan jain  wrote:

> I am selecting below option in my build pipeline, where internally i would
> checkout a repo and work on it. But the worspace with the repository clone
> is still there in every job execution and this is creating problems for me.
> I have to manually delete the worspace on the server everytime to make it
> work and this is so annoying.
> Also, i think this cleaning option is not applicable for the workspaces
> created on slave nodes, but i am not sure. How can i make sure that the
> workspace is wiped-out everytime with a job, on master and on every slave
> node it will use.
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google 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/b5a50c25-ed64-42b6-a106-c473260cb5cb%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/CAO49JtFkzrWkYbTjPG_kDF4aXhQ%2BX4w6OzEeM%2BnavWBw6i3cSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Can't capture command results in Kubernetes Pipeline Jenkinsfile

[Mark Nuttall]

Hello, 
I'm porting an existing Jenkinsfile to use the kubernetes plugin and its 
syntax. I've hit a problem in which I need to get the result of a shell 
command, but get only empty strings. This code worked correctly until being 
ported to the kubernetes plugin syntax. 

Here's my Jenkinsfile, showing a simple command just to help explain the 
problem:

#!groovy

podTemplate(
  label: 'mypod',
  containers: [containerTemplate(name: 'maven', image: 'maven:3.5.0-jdk-8', 
ttyEnabled: true, command: 'cat')],
){
  node('mypod') {
stage ('build') {
  container ('maven') {
sh 'ls > out.txt'
sh 'cat out.txt'

def c = sh(script: 'cat out.txt', returnStdout: true).trim();
sh 'echo c = ${c}'


def c2 = readFile('out.txt').trim()
sh 'echo c2 = ${c2}'
  }
}
  }
}

The relevant output, below, is very long but it shows that the 'ls' command 
runs successfully, and that I can cat the result of that file: but I am 
completely unable to read the file into a variable, or to execute the 
command and store the result as a variable, which is what I really want to 
do. I've highlighted the relevant sections in yellow. Please help me, I'm 
getting desperate :-(

Many thanks,

-- Mark

# # + ls

[Pipeline] sh[sample.microservicebuilder.test] Running shell script
Executing shell script inside container [maven] of pod 
[kubernetes-991f3f512a3e4c13aa5c7960410311bb-25c6ad58b93c]
Executing command: sh -c echo $$ > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/pid';
 jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/script.sh'
 > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-log.txt'
 2>&1; echo $? > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-result.txt'
 
# cd "/home/jenkins/workspace/sample.microservicebuilder.test"
sh -c echo $$ > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/pid';
 jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/script.sh'
 > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-log.txt'
 2>&1; echo $? > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-e505a1a7/jenkins-result.txt'
 
exit*# # + cat out.txt
Dockerfile
Jenkinsfile
README.md
manifests
out.txt
pom.xml
server.xml
src*[Pipeline] sh[sample.microservicebuilder.test] Running shell script
Executing shell script inside container [maven] of pod 
[kubernetes-991f3f512a3e4c13aa5c7960410311bb-25c6ad58b93c]
Executing command: sh -c echo $$ > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/pid';
 jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/script.sh'
 > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/output.txt'
 2> 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-log.txt';
 echo $? > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-result.txt'
 

# cd "/home/jenkins/workspace/sample.microservicebuilder.test"
sh -c echo $$ > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/pid';
 jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/script.sh'
 > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/output.txt'
 2> 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-log.txt';
 echo $? > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-9af67ea2/jenkins-result.txt'
 
exit
# # + cat out.txt[Pipeline] sh[sample.microservicebuilder.test] Running shell 
script
Executing shell script inside container [maven] of pod 
[kubernetes-991f3f512a3e4c13aa5c7960410311bb-25c6ad58b93c]
Executing command: sh -c echo $$ > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/pid';
 jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/script.sh'
 > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/jenkins-log.txt'
 2>&1; echo $? > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/jenkins-result.txt'
 
# cd "/home/jenkins/workspace/sample.microservicebuilder.test"
sh -c echo $$ > 
'/home/jenkins/workspace/sample.microservicebuilder.test@tmp/durable-3fd54a06/pid';
 jsc=durable-85fd500743f4a1b75ec1fa7e5bc276e5; JENKINS_SERVER_COOKIE=$jsc 

Re: How to specify svn credentialsId in pipeline job?

[thomas . lehmann]

You assing it to the parameter *credentialsId*.

On Thursday, April 20, 2017 at 1:13:20 PM UTC+2, David Aldrich wrote:
>
> Thanks, I see it now. The credential does have a readable name.  Can I 
> assign that name to credentialsId or should it be assigned to a different 
> property?
>
>  
>
> *From:* thomas@teamaol.com  [mailto:
> thomas@teamaol.com ] 
> *Sent:* 20 April 2017 12:11
> *To:* Jenkins Users 
> *Cc:* thomas@teamaol.com ; David Aldrich <
> david@emea.nec.com >
> *Subject:* Re: How to specify svn credentialsId in pipeline job?
>
>  
>
> Click on the link an a table is shown and there is the columns ID ...
> One note: if you forgot to provide a readable name you cannot change it. 
> You have to re-create it then.
>
> On Thursday, April 20, 2017 at 1:07:53 PM UTC+2, thomas@teamaol.com 
> wrote:
>
> When you click top/left on "Jenkins" (navigate to the mainpage) the link 
> to the credentials
>
> should appear on the left side (short before build queue).
>
> On Thursday, April 20, 2017 at 12:59:31 PM UTC+2, David Aldrich wrote:
>
> Thanks for your reply. I am an admin so I should be able to see 
> everything.  Where should I look for the credentials?
>
>  
>
> All our conventional jobs use the following credential seen on the job 
> configuration page:
>
>  
>
>  
>
> Where should I look for the corresponding credentialId?
>
>  
>
> Best regards
>
>  
>
> David
>
>  
>
> *From:* thomas@teamaol.com [mailto:thomas@teamaol.com] 
> *Sent:* 20 April 2017 11:39
> *To:* Jenkins Users 
> *Cc:* David Aldrich 
> *Subject:* Re: How to specify svn credentialsId in pipeline job?
>
>  
>
> Usually the adminstrator of a Jenkins is reponsible to register credentials
>
> with a useful (readable) name. If those admin forget to give a name Jenkins
> does it for your which results usually in something like this: 
> "b86bc2b6-994b-4811-ac98-0f35e9a9b114'
>
>
> Of course you don't wanna have such ID's in your coded pipeline. Consider
>
> you might have running your pipeline on different Jenkins providing the 
> same
>
> credentials (names) your project should be able to build without code 
> changes.
>
>  
>
> It might be a permission thing that you cannot see the credentials.
>
>  
>
>
> On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
>
> Hi 
>
> I have created a simple pipeline job that is intended just to check out a 
> working copy from svn initially. 
>
> Here's the script: 
>
> node { 
>echo 'Hello World' 
> 
>stage('Checkout') { 
>   checkout([$class: 'SubversionSCM', 
>   additionalCredentials: [], 
>   excludedCommitMessages: '', 
>   excludedRegions: '', 
>   excludedRevprop: '', 
>   excludedUsers: 'buildbot', 
>   filterChangelog: false, 
>   ignoreDirPropChanges: false, 
>   includedRegions: '', 
>   locations: [[credentialsId: 
> 'b86bc2b6-994b-4811-ac98-0f35e9a9b114', 
>depthOption: 'infinity', 
>ignoreExternalsOption: true, 
>local: '.', 
>remote: ""]], 
>   workspaceUpdater: [$class: 'UpdateUpdater']]) 
>   } 
> } 
>
> Is the script valid? 
>
> How do I determine the 'credentialsId' ?   (I have credentials set up in 
> non-pipeline jobs already). 
>
> Best regards 
>
> David 
>
>  
>
> Click here 
> 
>  
> to report this email as spam.
>
>

-- 
You received this message because you are subscribed to the Google 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/c3ec1ffd-4020-435f-98d9-013ca8440518%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How/when does Jenkins refresh job configuration (params, etc.) from pipeline script?

[thomas . lehmann]

Basically the pipeline script is code and as long the code is not executed 
it does nothing.
If you decide to adjust job configuration via script like "poll scm", 
"interval", enable/disable concurrent build
and how many history entries to keep then it will affect next build only.

You have following options  ...

 a) Pipeline job: you specify all fix parameters and then load the 
Jenkinsfile from your repository. The process is coded the parameters are 
manual.
 b) Multibranch pipeline job: you don't have any parameters and each remote 
branch can build in parallel. The pipeline code need to decide
 when to do what ... (example: you could eval the git branch and 
decided by where to deploy or where to deploy anyway). So basicall all is 
coded.

If you have same job running in multiple Jenkins instances (like cloud: AWS 
regions) then you might wanna also investigate
into Job DSL which is an extension the whole process. It allows to write a 
seed job that could run on each of your Jenkins instances creating
the required Jenkins jobs for you automatically.

A final word of warning related coded parameters ...
The pipeline DSL is - unfortunately - not designed to implement a behavior 
for such job parameters
which reflect the often seen Language feature "+=" (append) which means 
when you change one option only all other parameters you might have set 
manually
in the job configuration are overwritten. As an example ... if you do 
following ... look at the pipeline syntax for the properties and adjust 
those two entries same way and
then you see which options are additional changed ...

properties([
// Max # of builds to keep: 10
buildDiscarder(logRotator(artifactDaysToKeepStr: '', 
artifactNumToKeepStr: '', daysToKeepStr: '', numToKeepStr: '10')),
// Do not allow concurrent builds
disableConcurrentBuilds()
])


Kind Regards,
Thomas

On Monday, April 17, 2017 at 6:55:24 PM UTC+2, Pavel Strashkin wrote:
>
> Hi there,
>
> I wonder if anyone has details about how/when jenkins refreshes job 
> configuration from pipeline script (Jenkinsfile)? Is it when build is 
> triggered or some background job? What if I just want to adjust 
> configuration (add optional params) w/o running stages, how would I achieve 
> so?
>
> Thanks!
>

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

RE: How to specify svn credentialsId in pipeline job?

[David Aldrich]

Thanks, I see it now. The credential does have a readable name.  Can I assign 
that name to credentialsId or should it be assigned to a different property?

From: thomas.lehm...@teamaol.com [mailto:thomas.lehm...@teamaol.com]
Sent: 20 April 2017 12:11
To: Jenkins Users 
Cc: thomas.lehm...@teamaol.com; David Aldrich 
Subject: Re: How to specify svn credentialsId in pipeline job?

Click on the link an a table is shown and there is the columns ID ...
One note: if you forgot to provide a readable name you cannot change it. You 
have to re-create it then.

On Thursday, April 20, 2017 at 1:07:53 PM UTC+2, 
thomas@teamaol.com wrote:
When you click top/left on "Jenkins" (navigate to the mainpage) the link to the 
credentials
should appear on the left side (short before build queue).

On Thursday, April 20, 2017 at 12:59:31 PM UTC+2, David Aldrich wrote:
Thanks for your reply. I am an admin so I should be able to see everything.  
Where should I look for the credentials?

All our conventional jobs use the following credential seen on the job 
configuration page:

[https://lh5.googleusercontent.com/proxy/2i_Y0VgsbT3dDPnTx8xHlJoAJ_X4wU49L48fmjFQl1Fn6JpdOKhrhD0teLxJBFM-h17yECb8qRBvV3aQbAPzSIwIT5vm7Ak0yey-kZhQVShbsOe17M_qRCFv6oz4XJwVf23Pci55b2Vkj5i1xVVVGV48EKaXLdOi=w5000-h5000]

Where should I look for the corresponding credentialId?

Best regards

David

From: thomas@teamaol.com 
[mailto:thomas@teamaol.com]
Sent: 20 April 2017 11:39
To: Jenkins Users 
>
Cc: David Aldrich >
Subject: Re: How to specify svn credentialsId in pipeline job?

Usually the adminstrator of a Jenkins is reponsible to register credentials
with a useful (readable) name. If those admin forget to give a name Jenkins
does it for your which results usually in something like this: 
"b86bc2b6-994b-4811-ac98-0f35e9a9b114'

Of course you don't wanna have such ID's in your coded pipeline. Consider
you might have running your pipeline on different Jenkins providing the same
credentials (names) your project should be able to build without code changes.

It might be a permission thing that you cannot see the credentials.


On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
Hi

I have created a simple pipeline job that is intended just to check out a 
working copy from svn initially.

Here's the script:

node {
   echo 'Hello World'

   stage('Checkout') {
  checkout([$class: 'SubversionSCM',
  additionalCredentials: [],
  excludedCommitMessages: '',
  excludedRegions: '',
  excludedRevprop: '',
  excludedUsers: 'buildbot',
  filterChangelog: false,
  ignoreDirPropChanges: false,
  includedRegions: '',
  locations: [[credentialsId: 'b86bc2b6-994b-4811-ac98-0f35e9a9b114',
   depthOption: 'infinity',
   ignoreExternalsOption: true,
   local: '.',
   remote: ""]],
  workspaceUpdater: [$class: 'UpdateUpdater']])
  }
}

Is the script valid?

How do I determine the 'credentialsId' ?   (I have credentials set up in 
non-pipeline jobs already).

Best regards

David


Click 
here
 to report this email as spam.

-- 
You received this message because you are subscribed to the Google 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/2610488400a54eaf9c7cb2eb3c0025ae%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Re: How to specify svn credentialsId in pipeline job?

[thomas . lehmann]

Click on the link an a table is shown and there is the columns ID ...
One note: if you forgot to provide a readable name you cannot change it. 
You have to re-create it then.

On Thursday, April 20, 2017 at 1:07:53 PM UTC+2, thomas@teamaol.com 
wrote:
>
> When you click top/left on "Jenkins" (navigate to the mainpage) the link 
> to the credentials
> should appear on the left side (short before build queue).
>
> On Thursday, April 20, 2017 at 12:59:31 PM UTC+2, David Aldrich wrote:
>>
>> Thanks for your reply. I am an admin so I should be able to see 
>> everything.  Where should I look for the credentials?
>>
>>  
>>
>> All our conventional jobs use the following credential seen on the job 
>> configuration page:
>>
>>  
>>
>>  
>>
>> Where should I look for the corresponding credentialId?
>>
>>  
>>
>> Best regards
>>
>>  
>>
>> David
>>
>>  
>>
>> *From:* thomas@teamaol.com [mailto:thomas@teamaol.com] 
>> *Sent:* 20 April 2017 11:39
>> *To:* Jenkins Users 
>> *Cc:* David Aldrich 
>> *Subject:* Re: How to specify svn credentialsId in pipeline job?
>>
>>  
>>
>> Usually the adminstrator of a Jenkins is reponsible to register 
>> credentials
>>
>> with a useful (readable) name. If those admin forget to give a name 
>> Jenkins
>> does it for your which results usually in something like this: 
>> "b86bc2b6-994b-4811-ac98-0f35e9a9b114'
>>
>>
>> Of course you don't wanna have such ID's in your coded pipeline. Consider
>>
>> you might have running your pipeline on different Jenkins providing the 
>> same
>>
>> credentials (names) your project should be able to build without code 
>> changes.
>>
>>  
>>
>> It might be a permission thing that you cannot see the credentials.
>>
>>  
>>
>>
>> On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
>>
>> Hi 
>>
>> I have created a simple pipeline job that is intended just to check out a 
>> working copy from svn initially. 
>>
>> Here's the script: 
>>
>> node { 
>>echo 'Hello World' 
>> 
>>stage('Checkout') { 
>>   checkout([$class: 'SubversionSCM', 
>>   additionalCredentials: [], 
>>   excludedCommitMessages: '', 
>>   excludedRegions: '', 
>>   excludedRevprop: '', 
>>   excludedUsers: 'buildbot', 
>>   filterChangelog: false, 
>>   ignoreDirPropChanges: false, 
>>   includedRegions: '', 
>>   locations: [[credentialsId: 
>> 'b86bc2b6-994b-4811-ac98-0f35e9a9b114', 
>>depthOption: 'infinity', 
>>ignoreExternalsOption: true, 
>>local: '.', 
>>remote: ""]], 
>>   workspaceUpdater: [$class: 'UpdateUpdater']]) 
>>   } 
>> } 
>>
>> Is the script valid? 
>>
>> How do I determine the 'credentialsId' ?   (I have credentials set up in 
>> non-pipeline jobs already). 
>>
>> Best regards 
>>
>> David 
>>
>>  
>>
>> Click here 
>> 
>>  
>> to report this email as spam.
>>
>

-- 
You received this message because you are subscribed to the Google 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/05550dc0-0343-46cd-8666-bb0fb19828b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to specify svn credentialsId in pipeline job?

[thomas . lehmann]

When you click top/left on "Jenkins" (navigate to the mainpage) the link to 
the credentials
should appear on the left side (short before build queue).

On Thursday, April 20, 2017 at 12:59:31 PM UTC+2, David Aldrich wrote:
>
> Thanks for your reply. I am an admin so I should be able to see 
> everything.  Where should I look for the credentials?
>
>  
>
> All our conventional jobs use the following credential seen on the job 
> configuration page:
>
>  
>
>  
>
> Where should I look for the corresponding credentialId?
>
>  
>
> Best regards
>
>  
>
> David
>
>  
>
> *From:* thomas@teamaol.com  [mailto:
> thomas@teamaol.com ] 
> *Sent:* 20 April 2017 11:39
> *To:* Jenkins Users 
> *Cc:* David Aldrich 
> *Subject:* Re: How to specify svn credentialsId in pipeline job?
>
>  
>
> Usually the adminstrator of a Jenkins is reponsible to register credentials
>
> with a useful (readable) name. If those admin forget to give a name Jenkins
> does it for your which results usually in something like this: 
> "b86bc2b6-994b-4811-ac98-0f35e9a9b114'
>
>
> Of course you don't wanna have such ID's in your coded pipeline. Consider
>
> you might have running your pipeline on different Jenkins providing the 
> same
>
> credentials (names) your project should be able to build without code 
> changes.
>
>  
>
> It might be a permission thing that you cannot see the credentials.
>
>  
>
>
> On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
>
> Hi 
>
> I have created a simple pipeline job that is intended just to check out a 
> working copy from svn initially. 
>
> Here's the script: 
>
> node { 
>echo 'Hello World' 
> 
>stage('Checkout') { 
>   checkout([$class: 'SubversionSCM', 
>   additionalCredentials: [], 
>   excludedCommitMessages: '', 
>   excludedRegions: '', 
>   excludedRevprop: '', 
>   excludedUsers: 'buildbot', 
>   filterChangelog: false, 
>   ignoreDirPropChanges: false, 
>   includedRegions: '', 
>   locations: [[credentialsId: 
> 'b86bc2b6-994b-4811-ac98-0f35e9a9b114', 
>depthOption: 'infinity', 
>ignoreExternalsOption: true, 
>local: '.', 
>remote: ""]], 
>   workspaceUpdater: [$class: 'UpdateUpdater']]) 
>   } 
> } 
>
> Is the script valid? 
>
> How do I determine the 'credentialsId' ?   (I have credentials set up in 
> non-pipeline jobs already). 
>
> Best regards 
>
> David 
>
>  
>
> Click here 
> 
>  
> to report this email as spam.
>

-- 
You received this message because you are subscribed to the Google 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/81d2a0e0-3a50-416d-8baa-f9f04c5102a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: How to specify svn credentialsId in pipeline job?

[David Aldrich]

Thanks for your reply. I am an admin so I should be able to see everything.  
Where should I look for the credentials?

All our conventional jobs use the following credential seen on the job 
configuration page:

[cid:image001.png@01D2B9CD.84833030]

Where should I look for the corresponding credentialId?

Best regards

David

From: thomas.lehm...@teamaol.com [mailto:thomas.lehm...@teamaol.com]
Sent: 20 April 2017 11:39
To: Jenkins Users 
Cc: David Aldrich 
Subject: Re: How to specify svn credentialsId in pipeline job?

Usually the adminstrator of a Jenkins is reponsible to register credentials
with a useful (readable) name. If those admin forget to give a name Jenkins
does it for your which results usually in something like this: 
"b86bc2b6-994b-4811-ac98-0f35e9a9b114'

Of course you don't wanna have such ID's in your coded pipeline. Consider
you might have running your pipeline on different Jenkins providing the same
credentials (names) your project should be able to build without code changes.

It might be a permission thing that you cannot see the credentials.


On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
Hi

I have created a simple pipeline job that is intended just to check out a 
working copy from svn initially.

Here's the script:

node {
   echo 'Hello World'

   stage('Checkout') {
  checkout([$class: 'SubversionSCM',
  additionalCredentials: [],
  excludedCommitMessages: '',
  excludedRegions: '',
  excludedRevprop: '',
  excludedUsers: 'buildbot',
  filterChangelog: false,
  ignoreDirPropChanges: false,
  includedRegions: '',
  locations: [[credentialsId: 'b86bc2b6-994b-4811-ac98-0f35e9a9b114',
   depthOption: 'infinity',
   ignoreExternalsOption: true,
   local: '.',
   remote: ""]],
  workspaceUpdater: [$class: 'UpdateUpdater']])
  }
}

Is the script valid?

How do I determine the 'credentialsId' ?   (I have credentials set up in 
non-pipeline jobs already).

Best regards

David


Click 
here
 to report this email as spam.

-- 
You received this message because you are subscribed to the Google 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/64c1cd58411e4404a271df89484b788d%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins BuildHistory | MBs of space is consumed

[thomas . lehmann]

I would assume that is the size (sum) of your build artifacts.
When you click in one history entry you should see the build artifacts (and 
its size)

On Wednesday, April 19, 2017 at 12:17:35 PM UTC+2, LnT wrote:
>
> Hi,
>
> one of my job's history show like below.
> What are these statistics under trend ?
>
> why such MBs of space is consumed ?
> Any cluse
>
>
> Regards,
> LnT
>

-- 
You received this message because you are subscribed to the Google 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/8045633c-6c1a-4dbf-a6f9-e3a45aaeb9a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to specify svn credentialsId in pipeline job?

[thomas . lehmann]

Usually the adminstrator of a Jenkins is reponsible to register credentials
with a useful (readable) name. If those admin forget to give a name Jenkins
does it for your which results usually in something like this: 
"b86bc2b6-994b-4811-ac98-0f35e9a9b114'

Of course you don't wanna have such ID's in your coded pipeline. Consider
you might have running your pipeline on different Jenkins providing the same
credentials (names) your project should be able to build without code 
changes.

It might be a permission thing that you cannot see the credentials.


On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
>
> Hi 
>
> I have created a simple pipeline job that is intended just to check out a 
> working copy from svn initially. 
>
> Here's the script: 
>
> node { 
>echo 'Hello World' 
> 
>stage('Checkout') { 
>   checkout([$class: 'SubversionSCM', 
>   additionalCredentials: [], 
>   excludedCommitMessages: '', 
>   excludedRegions: '', 
>   excludedRevprop: '', 
>   excludedUsers: 'buildbot', 
>   filterChangelog: false, 
>   ignoreDirPropChanges: false, 
>   includedRegions: '', 
>   locations: [[credentialsId: 
> 'b86bc2b6-994b-4811-ac98-0f35e9a9b114', 
>depthOption: 'infinity', 
>ignoreExternalsOption: true, 
>local: '.', 
>remote: ""]], 
>   workspaceUpdater: [$class: 'UpdateUpdater']]) 
>   } 
> } 
>
> Is the script valid? 
>
> How do I determine the 'credentialsId' ?   (I have credentials set up in 
> non-pipeline jobs already). 
>
> Best regards 
>
> David 
>
>

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

Re: Jenkins Okta auth

[Ivan Fernandez Calvo]

Hi,

To configure Okta as SAML service you have to follow this 
documentation 
http://developer.okta.com/standards/SAML/setting_up_a_saml_application_in_okta, 
It seems like you did that and have the IdP up and running, you have to set 
these setting in order to make it works

*Single Sign on Url *: 
http://myhostaddress.com:8080/securityRealm/finishLogin
*Use this for Recipient URL and Destination URL*: Checked
*Audience URI (SP Entity ID)*: 
http://myhostaddress.com:8080/securityRealm/finishLogin
*Name ID Fornat* : EmailAdress
*Application username*: Okta username
*Attribute Statements* - I did not specify any here
*Group Attribute Statements*: Name=Group Nameformat=Basic Filtertype=regex 
Filter=.*


Jenkins:
*Security Realm*: SAML 2.0
*IdP Metadata* : Copied from Okta
*Display Name Attribute*: The default of (
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name)
*Group Attribute*: Group
*Username Attribute*: left blank

reviewing you configuration you set Request Binding to HTTP POST, this kind 
of binding it is not yet suppported by SAML Plugin you have to use HTTP 
Redirect Binding



El jueves, 20 de abril de 2017, 10:20:01 (UTC+2), st...@flugel.it escribió:
>
> I'm trying to configure okta with saml jenkins plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/SAML+Plugin
> But getting error Cannot find entity 
> https://www.okta.com/saml2/service-provider/spibofbfpairxsdsimgc or role 
> {urn:oasis:names:tc:SAML:2.0:metadata}
>
> there is my metadata
>  xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="
> https://www.okta.com/saml2/service-provider/spibofbfpairxsdsimgc;>  
> AuthnRequestsSigned="true" WantAssertionsSigned="true" 
> protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">  
> use="encryption">http://www.w3.org/2000/09/xmldsig#
> ">MIIDpDCCAoygAwIBAgIGAVuJmnDlMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG
>
> A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU
>
> MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi03ODQxMTkxHDAaBgkqhkiG9w0BCQEW
>
> DWluZm9Ab2t0YS5jb20wHhcNMTcwNDIwMDQyMzExWhcNMjcwNDIwMDQyNDExWjCBkjELMAkGA1UE
>
> BhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNV
>
> BAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtNzg0MTE5MRwwGgYJ
>
> KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
>
> lfVL/XL9lEftDwzL8oSWGzJq8jAWFdZgRRP0ufz7BcNhIQsUXGKnl5cf29Q7FZ5/nqybu5Pg0M3V
>
> Y3tBgDk8L6wDvsujyCxsZLwmek8jgrAb2Kk3HZY5y0yHkQSKQ2ASUBmvvx10MpYF1hsrPaZ2ZXqk
>
> IbWbI/XmzCsdPnWxRcPZ3AtLl1b0dB5G+vJ3TG2hlcoSHH2+MV3Zv/wRSTskBhsrpDwpHtz5BC7l
>
> gsSvtcd4FC5lCspD1SarZ9jguXCPcUgi7JkKWSYZOHRFFLYraG21CQwlNdb6MgulCTNyfM17i9sq
>
> IXbfIrO8YdGi0YCAoFX04p0tHP0lJbcf6KbNiQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQAONbGS
>
> R/E99tsSARjOJQC2RO03jeyamRrUnNZVqL4S9zw49s7P0n9HakJ4Vb8H0aiOvVqNPwrkXmMuwjP7
>
> 9KCHbMDTGogo8CGxSl3bMJ3DNo+A/ecVaI4IgM6y4bCAst6f8EBopj39a7+r69HPU1fzqaPz2Cti
>
> CdZ07QiCt51B52eCU9TzdAdJLB1cCby3GfyAbszyTVS6ZFPoC814XF0K38u6pVz5Ab6dTQ5L1Jho
>
> iD4JTIJFN317io/0UsPwdLak325HjT7ufNxV+cR/zTedIvj8V6GEorfIYtGGUaq8M1xSqmwiJg0o
> YUEZhwOmNNHrRoqSWXGjEDzJKgtP1Fzn  
> Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/> Algorithm="http://www.w3.org/2001/04/xmlenc#aes192-cbc"/> Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>  
> use="signing">http://www.w3.org/2000/09/xmldsig#
> ">MIIDpDCCAoygAwIBAgIGAVuJmnDlMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG
>
> A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU
>
> MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi03ODQxMTkxHDAaBgkqhkiG9w0BCQEW
>
> DWluZm9Ab2t0YS5jb20wHhcNMTcwNDIwMDQyMzExWhcNMjcwNDIwMDQyNDExWjCBkjELMAkGA1UE
>
> BhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNV
>
> BAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtNzg0MTE5MRwwGgYJ
>
> KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
>
> lfVL/XL9lEftDwzL8oSWGzJq8jAWFdZgRRP0ufz7BcNhIQsUXGKnl5cf29Q7FZ5/nqybu5Pg0M3V
>
> Y3tBgDk8L6wDvsujyCxsZLwmek8jgrAb2Kk3HZY5y0yHkQSKQ2ASUBmvvx10MpYF1hsrPaZ2ZXqk
>
> IbWbI/XmzCsdPnWxRcPZ3AtLl1b0dB5G+vJ3TG2hlcoSHH2+MV3Zv/wRSTskBhsrpDwpHtz5BC7l
>
> gsSvtcd4FC5lCspD1SarZ9jguXCPcUgi7JkKWSYZOHRFFLYraG21CQwlNdb6MgulCTNyfM17i9sq
>
> IXbfIrO8YdGi0YCAoFX04p0tHP0lJbcf6KbNiQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQAONbGS
>
> R/E99tsSARjOJQC2RO03jeyamRrUnNZVqL4S9zw49s7P0n9HakJ4Vb8H0aiOvVqNPwrkXmMuwjP7
>
> 9KCHbMDTGogo8CGxSl3bMJ3DNo+A/ecVaI4IgM6y4bCAst6f8EBopj39a7+r69HPU1fzqaPz2Cti
>
> CdZ07QiCt51B52eCU9TzdAdJLB1cCby3GfyAbszyTVS6ZFPoC814XF0K38u6pVz5Ab6dTQ5L1Jho
>
> iD4JTIJFN317io/0UsPwdLak325HjT7ufNxV+cR/zTedIvj8V6GEorfIYtGGUaq8M1xSqmwiJg0o
> YUEZhwOmNNHrRoqSWXGjEDzJKgtP1Fznurn:oasis:names:tc:SAML:1.1:nameid-format:unspecifiedurn:oasis:names:tc:SAML:1.1:nameid-format:emailAddressurn:oasis:names:tc:SAML:2.0:nameid-format:persistenturn:oasis:names:tc:SAML:2.0:nameid-format:transient  
> 

Even after having 'wipe out repository & force clone' option, my workspace is not fresh

[ishan jain]

I am selecting below option in my build pipeline, where internally i would 
checkout a repo and work on it. But the worspace with the repository clone 
is still there in every job execution and this is creating problems for me. 
I have to manually delete the worspace on the server everytime to make it 
work and this is so annoying.
Also, i think this cleaning option is not applicable for the workspaces 
created on slave nodes, but i am not sure. How can i make sure that the 
workspace is wiped-out everytime with a job, on master and on every slave 
node it will use.
 
















































-- 
You received this message because you are subscribed to the Google 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/b5a50c25-ed64-42b6-a106-c473260cb5cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

java.io.IOException: Unexpected EOF in jenkins

[venkatesh guttal]

Hi 
I was running the jobs, after running 16 hours i got below error message.

java.io.IOException 
: Unexpected 
EOF
at 
hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99) 

at 
hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
 

at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
 

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
 

Caused: java.io.IOException: Backing channel 'inblrmrbld15' is disconnected.
at 
hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:192)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257)
at com.sun.proxy.$Proxy58.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1730)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:405)
Build step 'Execute shell' marked build as failure


Regards,

Venkatesh

-- 
You received this message because you are subscribed to the Google 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/f0b00ab9-6abb-4083-8405-faccca28c5d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0x7fefb8931a32, pid=15332, tid=0x7fef9b1f1700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libzip.so+0x11a32]  newEntry+0x62
#
# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---  T H R E A D  ---

Current thread (0x7fefb435d800):  JavaThread "Channel reader thread: 
channel" [_thread_in_native, id=15354, 
stack(0x7fef9b0f1000,0x7fef9b1f2000)]

siginfo: si_signo: 7 (SIGBUS), si_code: 2 (BUS_ADRERR), si_addr: 
0x7fefba6cc730

Registers:
RAX=0x7fef28026f50, RBX=0x7fefb422b690, RCX=0x0101, 
RDX=0x0100
RSP=0x7fef9b1eda00, RBP=0x7fef9b1eda50, RSI=0x0048, 
RDI=0x7fef2820
R8 =0x7fef2888, R9 =0x0001, R10=0x0048, 
R11=0x0014
R12=0x7fefba6cc713, R13=0x7fef28026f50, R14=0x5bbd78a2, 
R15=0x7fefb42312c0
RIP=0x7fefb8931a32, EFLAGS=0x00010202, CSGSFS=0x0033, 
ERR=0x0004
  TRAPNO=0x000e

Top of Stack: (sp=0x7fef9b1eda00)
0x7fef9b1eda00:   7fefa1f90c18 7fef
0x7fef9b1eda10:   7fefb4231390 7fefb9d9284e
0x7fef9b1eda20:   7fef28026f50 7fefb422b690
0x7fef9b1eda30:   7fef28026ec0 7fefb42312c0
0x7fef9b1eda40:   5bbd78a2 0014
0x7fef9b1eda50:   7fef9b1edab0 7fefb893218f
0x7fef9b1eda60:   7fefb435d800 7fef9b1efe8c
0x7fef9b1eda70:   

How to approve pending signatures?

[Maciej Gawinecki]

Hi,

I have pipeline that downloads Groovy script from Git, but Groovy script 
fails with

  org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts 
not permitted to use method java.net.URL openStream

I found /var/lib/jenkins/scriptApproval.xml file with the following excerpt:



  
  ...
  

  
  method java.net.URL openStream
  true

  
...



I have editted the script into

  
  method java.net.URL openStream
  
...


but after Jenkins restart and re-running the pipeline it get overwritten.

How do I approve pending signatures?

Regards,
Maciej

-- 
You received this message because you are subscribed to the Google 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/96cf8845-3fca-4651-a392-28299c357fb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Publish Coverity plugin results via Email

[Nitzan Yemal]

Hi,

I started to use Coverity plugin in our Jenkins and I wanted to know if I 
can publish the scan results via mail? is there ant HTML file created in 
that scan which I can send? 
Is there a list pf Coverity environment variable I can use instead?

Thanks,
Nitzan

-- 
You received this message because you are subscribed to the Google 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/c7aba20b-54ce-41ec-a860-3413691cfe43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Okta auth

[stas]

I'm trying to configure okta with saml jenkins plugin 
https://wiki.jenkins-ci.org/display/JENKINS/SAML+Plugin
But getting error Cannot find entity 
https://www.okta.com/saml2/service-provider/spibofbfpairxsdsimgc or role 
{urn:oasis:names:tc:SAML:2.0:metadata}

there is my metadata
https://www.okta.com/saml2/service-provider/spibofbfpairxsdsimgc;>http://www.w3.org/2000/09/xmldsig#;>MIIDpDCCAoygAwIBAgIGAVuJmnDlMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG
A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU
MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi03ODQxMTkxHDAaBgkqhkiG9w0BCQEW
DWluZm9Ab2t0YS5jb20wHhcNMTcwNDIwMDQyMzExWhcNMjcwNDIwMDQyNDExWjCBkjELMAkGA1UE
BhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNV
BAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtNzg0MTE5MRwwGgYJ
KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
lfVL/XL9lEftDwzL8oSWGzJq8jAWFdZgRRP0ufz7BcNhIQsUXGKnl5cf29Q7FZ5/nqybu5Pg0M3V
Y3tBgDk8L6wDvsujyCxsZLwmek8jgrAb2Kk3HZY5y0yHkQSKQ2ASUBmvvx10MpYF1hsrPaZ2ZXqk
IbWbI/XmzCsdPnWxRcPZ3AtLl1b0dB5G+vJ3TG2hlcoSHH2+MV3Zv/wRSTskBhsrpDwpHtz5BC7l
gsSvtcd4FC5lCspD1SarZ9jguXCPcUgi7JkKWSYZOHRFFLYraG21CQwlNdb6MgulCTNyfM17i9sq
IXbfIrO8YdGi0YCAoFX04p0tHP0lJbcf6KbNiQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQAONbGS
R/E99tsSARjOJQC2RO03jeyamRrUnNZVqL4S9zw49s7P0n9HakJ4Vb8H0aiOvVqNPwrkXmMuwjP7
9KCHbMDTGogo8CGxSl3bMJ3DNo+A/ecVaI4IgM6y4bCAst6f8EBopj39a7+r69HPU1fzqaPz2Cti
CdZ07QiCt51B52eCU9TzdAdJLB1cCby3GfyAbszyTVS6ZFPoC814XF0K38u6pVz5Ab6dTQ5L1Jho
iD4JTIJFN317io/0UsPwdLak325HjT7ufNxV+cR/zTedIvj8V6GEorfIYtGGUaq8M1xSqmwiJg0o
YUEZhwOmNNHrRoqSWXGjEDzJKgtP1Fznhttp://www.w3.org/2001/04/xmlenc#aes128-cbc"/>http://www.w3.org/2001/04/xmlenc#aes192-cbc"/>http://www.w3.org/2001/04/xmlenc#aes256-cbc"/>http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>http://www.w3.org/2000/09/xmldsig#;>MIIDpDCCAoygAwIBAgIGAVuJmnDlMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG
A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU
MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi03ODQxMTkxHDAaBgkqhkiG9w0BCQEW
DWluZm9Ab2t0YS5jb20wHhcNMTcwNDIwMDQyMzExWhcNMjcwNDIwMDQyNDExWjCBkjELMAkGA1UE
BhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNV
BAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtNzg0MTE5MRwwGgYJ
KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
lfVL/XL9lEftDwzL8oSWGzJq8jAWFdZgRRP0ufz7BcNhIQsUXGKnl5cf29Q7FZ5/nqybu5Pg0M3V
Y3tBgDk8L6wDvsujyCxsZLwmek8jgrAb2Kk3HZY5y0yHkQSKQ2ASUBmvvx10MpYF1hsrPaZ2ZXqk
IbWbI/XmzCsdPnWxRcPZ3AtLl1b0dB5G+vJ3TG2hlcoSHH2+MV3Zv/wRSTskBhsrpDwpHtz5BC7l
gsSvtcd4FC5lCspD1SarZ9jguXCPcUgi7JkKWSYZOHRFFLYraG21CQwlNdb6MgulCTNyfM17i9sq
IXbfIrO8YdGi0YCAoFX04p0tHP0lJbcf6KbNiQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQAONbGS
R/E99tsSARjOJQC2RO03jeyamRrUnNZVqL4S9zw49s7P0n9HakJ4Vb8H0aiOvVqNPwrkXmMuwjP7
9KCHbMDTGogo8CGxSl3bMJ3DNo+A/ecVaI4IgM6y4bCAst6f8EBopj39a7+r69HPU1fzqaPz2Cti
CdZ07QiCt51B52eCU9TzdAdJLB1cCby3GfyAbszyTVS6ZFPoC814XF0K38u6pVz5Ab6dTQ5L1Jho
iD4JTIJFN317io/0UsPwdLak325HjT7ufNxV+cR/zTedIvj8V6GEorfIYtGGUaq8M1xSqmwiJg0o
YUEZhwOmNNHrRoqSWXGjEDzJKgtP1Fznurn:oasis:names:tc:SAML:1.1:nameid-format:unspecifiedurn:oasis:names:tc:SAML:1.1:nameid-format:emailAddressurn:oasis:names:tc:SAML:2.0:nameid-format:persistenturn:oasis:names:tc:SAML:2.0:nameid-format:transienthttps://dev-784119.oktapreview.com/sso/saml2/0oaa7zvi6k6kK4Rm00h7; 
index="0" isDefault="true"/>http://www.w3.org/XML/1998/namespace; 
xml:lang="en">dev-784119http://www.w3.org/XML/1998/namespace; 
xml:lang="en">Flugel.it-dev-784119http://www.w3.org/XML/1998/namespace; 
xml:lang="en">https://flugel.it

in Okta:
SAML PROTOCOL SETTINGS

IdP Issuer URI 
https://ip:8080/securityRealm/finishLogin

IdP Single Sign-On URL 
https://ip:8080/securityRealm/finishLogin

IdP Signature Certificate 
Pub cer for SSL

Request Binding 
HTTP POST

Request Signature

Sign SAML Authentication Requests
Request Signature Algorithm 
SHA-256

Response Signature Verification 
Response or Assertion

Response Signature Algorithm 
SHA-256

Destination 
https://ip:8080/securityRealm/finishLogin
Okta Assertion Consumer Service URL

Trust-specific

Organization (shared)
Max Clock Skew 
2
Minutes

Jenkins running from official docker image with options:
--httpPort=-1 --httpsPort=8080 
--httpsCertificate=/var/lib/jenkins/jenkins.crt 
--httpsPrivateKey=/var/lib/jenkins/jenkins.key

-- 
You received this message because you are subscribed to the Google 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/76f577db-634b-4b2b-8c49-6f37cba3bb51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

java.util.zip.ZipException: error reading zip file by clicking on "Build Now" in jenkins

[venkatesh guttal]

Hi 
The below error will come whenever i start the build.
When i restart the jenkin's this error will go off, After some time again 
it will come.

Please help me to sort this issue, Please find the attached log files.

java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)

java.util.zip.ZipException: error reading zip file

at java.util.zip.ZipFile.read(Native Method)

at java.util.zip.ZipFile.access$1400(ZipFile.java:60)

at 
java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)

at 
java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)

at 
java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)

at 
java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:478)

at sun.misc.Resource.getBytes(Resource.java:124)

at 
java.net.URLClassLoader.defineClass(URLClassLoader.java:462)

at 
java.net.URLClassLoader.access$100(URLClassLoader.java:73)

at java.net.URLClassLoader$1.run(URLClassLoader.java:368)

Caused: java.lang.ClassNotFoundException: hudson.remoting.ProxyOutputStream

 

Regards,

Venkatesh

-- 
You received this message because you are subscribed to the Google 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/1c23265b-9e2e-496f-a9a4-6fc19316ad5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
build no:15
[EnvInject] - Loading node environment variables.
Building remotely on inblrmrbld15 in workspace 
/homes/bldmgr/workspace/MR27_BUILD
[INFO] computeChangeLogBeforeCheckout = false
[INFO] computeChangeLogAfterCheckout  = true
java.util.zip.ZipException: error reading zip file
at java.util.zip.ZipFile.read(Native Method)
at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
at 
java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
at java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:478)
at sun.misc.Resource.getBytes(Resource.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:462)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
Caused: java.lang.ClassNotFoundException: hudson.remoting.ProxyOutputStream
at java.net.URLClassLoader$1.run(URLClassLoader.java:370)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2583)
at java.lang.Class.getDeclaredField(Class.java:2068)
at 
java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1703)
at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:484)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:472)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.(ObjectStreamClass.java:472)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:369)
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:598)
at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1630)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1521)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1781)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373)
at 
hudson.util.StreamTaskListener.readObject(StreamTaskListener.java:190)
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:498)
at 
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058)
at 

Re: Jenkins 2.7 vs 2.4

[Filippo]

Hi James,
yes, I'm using the 2.46.1 version.
But I can use Blue Ocean only for browsing activity, because our projects 
are stored under SVN while Blue Ocean seems to support only GIT projects, 
so I must switch to "classic UI" every time I have to change some build 
configuration.

Bye

Filippo

Il giorno giovedì 20 aprile 2017 07:57:20 UTC+2, James Dumay ha scritto:
>
> Hi Filippo,
>
> Great to hear that you are upgrading to use Blue Ocean :)
>
> While Blue Ocean is compatible with 2.7.1 and above I do strongly advise 
> using the latest LTS, 2.46.1, as there have been several nasty security 
> vulnerabilities.
>
> All the best,
>
> James
>
> On Tuesday, April 18, 2017 at 8:52:14 PM UTC+10, Filippo wrote:
>>
>> Hello,
>> I've installed Jenkins 2.4 on a CentOS server via yum. I would like to 
>> try Blue Ocean, that runs only with Jenkins v 2.7.
>> So I opened the RedHat repository (https://pkg.jenkins.io/redhat/) and 
>> noticed that the 2.7 rpm is dated 2016/05/29, while the 2.4 is dated 
>> 2017/02/13.
>> The question is: why is the 2.7 so older than 2.4?
>> And are the other packages (2.8 and 2.9) also compatible with blue ocean?
>>
>> Thanks.
>>
>>

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