LDAP src code
Hello, I was wondering where can I find ldap plugin src code? Thanks
Re: LDAP src code
https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin There is a GitHub link in the plug-in section.. Am 07.01.2013 um 09:24 schrieb Levin, Ilya ilya.le...@hp.com: Hello, I was wondering where can I find ldap plugin src code? Thanks
Re: Jenkins svn ssh / host key verification problems
Anyone that has an idea? It is getting pretty anoying so far . Would love to get this working because it seems very promosing On Friday, January 4, 2013 3:19:31 PM UTC+1, Bjørn Water wrote: So i am trying to use the M2-release plugin to release my project and push it to my nexus. I can do svn checkout and i can even tag my build and see it in my repo but when i try to do mvn release:prepare after a succesfull build i get an error [ERROR] BUILD FAILURE[INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:153) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:287) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:237) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 28 more Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH
Base-URL Confusion
Dear all, our jenkins is reachable via different URLs / domains. Most of the time this is not an issue, because most links in the web interface are generated relatively to the current URL (our desired behavior). However, sometimes links are generated using a wrong domain, which results in the fact that suddenly the login cookies aren't valid anymore. This mostly happens for graphs drawn by some plugins. From our experience these plugins seems to build their links in an absolute fashion starting from the Jenkins URL provided in the general settings of jenkins. What is the idea behind having a fixed URL in the configuration, if it isn't actually used most of the time? From our point of view we would like to continue providing the jenkins instance under several URLs in parallel, which is complicated by this fact. Kind regards, Johannes signature.asc Description: OpenPGP digital signature
RE: Master + slave + job JVM memory tuning...
Have enough RAM on the slave that you can run your jobs plus Jenkins + some for overhead. (e.g. 1GB of Jenkins slave, + #executors * ( 2GB for Maven +2GB for unit tests in forked VM) + OS overhead) Although this amount is mostly an overkill setting it too close to the threshold will slow your jobs down due to paging at best, or mean you get intermittent failures due to OOM at worst – (memory is generally cheaper that human time taken to investigate issues!) (our maven jobs can be very memory hungry so your figures will vary) (Note I recommend a single executor per slave) The master depends more on how many jobs / reports per jobs / job history you have etc – we use 10GB (but not tomcat). If you’re in the UK and there is any spaces left I will cover some things like this next week at the Jenkins User Event. /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jeff Sent: 04 January 2013 21:56 To: jenkinsci-users@googlegroups.com Subject: Master + slave + job JVM memory tuning... I'm trying to optimize how much memory I allocate to the master application (aka - tomcat), slave processes, maven tasks, etc. and going crazy. I've been unsuccessful in finding a guideline to determine how much memory I ought to allocate or if I should just let the defaults work. All machines are single processor, dual core with 4 GB ram. I've typically set tomcat to use 2048MB + 512MB permgen space and set my maven process to use 384MB max. Is this reasonable? My slaves are set to run 4 executors. Jobs use either svn or git to check out code and Maven to build with a SONAR post-build analysis. We also do Maven releases at times. How much does the core slave process need? Is there a rule-of-thumb based on the number of executors? Any perspective/considerations/resources/links/pointers are much appreciated. -- Jeff Vincent predato...@gmail.commailto:predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBoxhttp://db.tt/9O6LfBX !! ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
How can I do something after jenkins checkout code but before package
I have a maven web project,and it quote another maven web project. Then,when I use jenkins build the project from SVN,it will only package this one project,but I want package the two. so,I want checkout another project's code using svn commands after jenkins checkout code but before package, but I don't know where to write the svn commands in the config page of jenkins. who can help me?
Re: significance of .jenkins diectory tree
On 28/12/12 21:26, Kamal Ahmed wrote: Hi, Does anyone know the significance of /home/user/.jenkins and the files/Directories under it? That's where Jenkins stores *all* of its data by default, if you start Jenkins as your user. See https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins Can i remove them without having any impact on my jenkins Instance ? No. If you delete it, you will lose all of your existing configuration, jobs and build information. Chris
debuging existing plugins
Hi, I'm trying to debug a plugin using: LOGGER.log(Level.INFO,Something ), Where can I see this log after starting Jenkins (http://server:port/jenkins/log/allhttp://%3cserver%3e:port/jenkins/log/all doesn't help)? Thanks.
trigger re-keying manually
Hi everyone! I've updated our LTS version to 1.480.2 just now and accidentially clicked on Dismiss for the re-keying message (not knowing I wouldn't be able to bring it up again). How do I trigger the re-keying manually now? Thanks in advance! Steffen
LTS upgrade notifications
I just switched one of my Jenkins servers to the LTS release. I downloaded the war file and replaced my current war file. I then updated the update site for the plugins and restarted. Everything is running fine, except when I goto Manage Jenkins I'm still prompted to upgrade to the latest bleeding edge release. Did I miss something here or do the LTS releases not check a separate update site? In the bottom right I see 1.480.1. -- http://mtu.net/~jpschewe
RE: Problem while migrating from Hudson 2.1.2
If you look at the wiki page for migrating from Hudson, you'll notice in bold red text that you can only upgrade from =1.398 reliably. Hudson changed the format of their XML after that and so the formats are no longer compatible. Sent from my Windows Phone -- From: bthiebault Sent: 1/7/2013 3:37 AM To: jenkinsci-users@googlegroups.com Subject: Problem while migrating from Hudson 2.1.2 Hi everyone, I am running Hudson 2.1.2 on a computer that is going to be upgraded (hardware + OS upgrade to Debian 6). As I need to reinstall everything, I thought it might be a good idea to switch from Hudson to Jenkins. So I installed Jenkins on the new machine (using apt-get) and moved the home directory from /var/lib to /home/jenkins following instructions here: http://robertbasic.com/blog/changing-jenkins-home-directory-on-ubuntu Then I archived my former /home/hudson folder and transfered it to the new machine. I tried to unzip it piece by piece. Copying the plugins and users worked very smoothly. However, copying the jobs folder is more problematic and I now have a stacktrace on jenkins home page. Can anyone help? Kind regards, Ben Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.497.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.497.jar!/lib/hudson/projectView.jelly:64:22: d:invokeBody java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.497.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.497.jar!/lib/hudson/projectView.jelly:64:22: d:invokeBody java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:624) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) 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:135) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
Re: LTS upgrade notifications
Don't use the link on the webpage. Use the link provided by Jenkins itself instead.
Re: Problem while migrating from Hudson 2.1.2
Thanks for your answer. I indeed had seen this bold red text notice but was wondering if it was only not supported or completely impossible. I guess I have my answer... I will thus go back to Hudson. Kind regards, Ben On Monday, 7 January 2013 15:01:44 UTC+1, slide wrote: If you look at the wiki page for migrating from Hudson, you'll notice in bold red text that you can only upgrade from =1.398 reliably. Hudson changed the format of their XML after that and so the formats are no longer compatible. Sent from my Windows Phone --
Re: Problem while migrating from Hudson 2.1.2
On Mon, Jan 7, 2013 at 8:38 AM, bthiebault benoit.thieba...@gmail.com wrote: Thanks for your answer. I indeed had seen this bold red text notice but was wondering if it was only not supported or completely impossible. I guess I have my answer... I will thus go back to Hudson. Can you re-create the jobs under jenkins? -- Les Mikesell lesmikes...@gmail.com
Re: Problem while migrating from Hudson 2.1.2
I've been contemplating writing a conversion plugin, but I don't know enough about the new Hudson format yet to do it. On Mon, Jan 7, 2013 at 8:42 AM, Les Mikesell lesmikes...@gmail.com wrote: On Mon, Jan 7, 2013 at 8:38 AM, bthiebault benoit.thieba...@gmail.com wrote: Thanks for your answer. I indeed had seen this bold red text notice but was wondering if it was only not supported or completely impossible. I guess I have my answer... I will thus go back to Hudson. Can you re-create the jobs under jenkins? -- Les Mikesell lesmikes...@gmail.com -- Website: http://earl-of-code.com
Re: Problem while migrating from Hudson 2.1.2
I could, but this is long and tedious... and I would lose the history... On Mon, Jan 7, 2013 at 4:42 PM, Les Mikesell lesmikes...@gmail.com wrote: On Mon, Jan 7, 2013 at 8:38 AM, bthiebault benoit.thieba...@gmail.com wrote: Thanks for your answer. I indeed had seen this bold red text notice but was wondering if it was only not supported or completely impossible. I guess I have my answer... I will thus go back to Hudson. Can you re-create the jobs under jenkins? -- Les Mikesell lesmikes...@gmail.com
Re: Changing dashboard column header names
Hey Jeff, if you really want to change Configure you could change the files (coloumnHeader.properties) from the Configure Job Column Plugin. They contain the value for the Column. There is no way to change it in Jenkins. Your second point, console, is not directly connected to this plugin. Am Samstag, 5. Januar 2013 00:19:35 UTC+1 schrieb Jeff Vincent: Is changing the column names possible? I just added the Configure Job Column Plugin that gives me a direct link to the job configuration. However the column name is called Configure which is about 8 characters wider than the icon: [image: Inline image 1] which is a wasted space. I have the same issue with the Console column that has a little icon for the console output: [image: Inline image 2] Is there a way to change these names? -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
Re: EnvInject plugin not passing environment variable to post build action
Hi, im not sure if i get you correctly, but have you tried a parametrized build to set a variable with your server and use this later ? Because the help description includes : The Build requires user input (this would be your server) which will be available during the build process. If i create such a paramter, i can echo him later at build step, did not try to work with him in a post build step. Only other reason i used this, was to trigger a different job and transmit this parameter. (Parameterized trigger Plugin) But again, im not sure if this is helpfull for a post Build step. Sry if im wasting your time.
How set java.io.tmpdir=/tmp for Jenkins slave?
Is there a way to set system property: java.io.tmpdir=/tmp for a slave? I am launching the slave via SSH. I assume if I can map java.io.tmpdir=/volume1/tmp my problem is solved. My problem is I am running out of /tmp space with a Jenkins slave running on a Synology ARM based NAS which uses tmpfs or RAM as the /tmp resource. Thanks in advance, -Ed
Null pointer exceptions after upgrade from 1.480.1 to 1.480.2
I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the Debian package manager. The machine was running with authentication enabled and was using Debian, CentOS, Red Hat, and Windows slave agents. The Linux slave agents are launched with ssh. The Windows slave agents are launched with JNLP from a batch file on the Windows machines. The upgrade seems to have blocked all connections from the Windows (JNLP) slaves. I assume that is intentional since I had authentication enabled and 1.480.2 attempts to disallow unauthenticated slave agent connections. I resolved that by disabling authentication on the master server. After the upgrade, I see some Dead entries in the list of slaves on the left side of the Jenkins opening page. When I click the red Dead entry, it shows the following stack trace: java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:218) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:64) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1197) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:136) at hudson.model.Executor.run(Executor.java:211) Once I click through that Dead thread one or two times, the slave agent seems to remain running without interruption. Are those expected results that are part of the transition from 1.480.1 to 1.480.2? Thanks, Mark Waite
RE: Master + slave + job JVM memory tuning...
Thanks...I unfortunately can't be in the UK for the event. So if the amount of RAM is fixed (4GB), what is a good rule of thumb for determining what to allocate to the slave process, how many executors it can reasonably support, etc? I realize there are a lot of other variables but any starting point and things to consider or factor in that may not be obvious could help. Or is it just a matter or monitoring and tuning? On Jan 7, 2013 2:31 AM, Nord, James jn...@nds.com wrote: Have enough RAM on the slave that you can run your jobs plus Jenkins + some for overhead. (e.g. 1GB of Jenkins slave, + #executors * ( 2GB for Maven +2GB for unit tests in forked VM) + OS overhead) Although this amount is mostly an overkill setting it too close to the threshold will slow your jobs down due to paging at best, or mean you get intermittent failures due to OOM at worst – (memory is generally cheaper that human time taken to investigate issues!) (our maven jobs can be very memory hungry so your figures will vary) (Note I recommend a single executor per slave) The master depends more on how many jobs / reports per jobs / job history you have etc – we use 10GB (but not tomcat). If you’re in the UK and there is any spaces left I will cover some things like this next week at the Jenkins User Event. /James *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Jeff *Sent:* 04 January 2013 21:56 *To:* jenkinsci-users@googlegroups.com *Subject:* Master + slave + job JVM memory tuning... I'm trying to optimize how much memory I allocate to the master application (aka - tomcat), slave processes, maven tasks, etc. and going crazy. I've been unsuccessful in finding a guideline to determine how much memory I ought to allocate or if I should just let the defaults work. All machines are single processor, dual core with 4 GB ram. I've typically set tomcat to use 2048MB + 512MB permgen space and set my maven process to use 384MB max. Is this reasonable? My slaves are set to run 4 executors. Jobs use either svn or git to check out code and Maven to build with a SONAR post-build analysis. We also do Maven releases at times. How much does the core slave process need? Is there a rule-of-thumb based on the number of executors? Any perspective/considerations/resources/links/pointers are much appreciated. -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
Email-ext plugin for Jenkins 1.464
I am using Jenkins 1.464 at my workplace. I need to send an email on each notification so I installed email-ext from my organisation's repository(sorry don't know the version). When I click on Editable Email Notifications in Post-Build Actions, it shows Javascript error 'emailExtInit' is undefined' I tried to rectify the problem as mentioned in Jenkins-13737 http://jenkins-ci.org/commit/email-ext-plugin/ee715fbd1bd81e83cb9501c311fd04f309431a2c But it shows null error now. What is the possible solution to above problem? I would really appreciate the help.. If possible which Email-ext plugins should I use with Jenkins 1.464 to solve the problem of success build trigger?
Re: Email-ext plugin for Jenkins 1.464
Probably 2.24.1 On Mon, Jan 7, 2013 at 11:43 AM, Sanket sanket.narag...@gmail.com wrote: I am using Jenkins 1.464 at my workplace. I need to send an email on each notification so I installed email-ext from my organisation's repository(sorry don't know the version). When I click on Editable Email Notifications in Post-Build Actions, it shows Javascript error 'emailExtInit' is undefined' I tried to rectify the problem as mentioned in Jenkins-13737 http://jenkins-ci.org/commit/email-ext-plugin/ee715fbd1bd81e83cb9501c311fd04f309431a2c But it shows null error now. What is the possible solution to above problem? I would really appreciate the help.. If possible which Email-ext plugins should I use with Jenkins 1.464 to solve the problem of success build trigger? -- Website: http://earl-of-code.com
Re: Null pointer exceptions after upgrade from 1.480.1 to 1.480.2
Hi Mark, On 07/01/2013 18:21, Mark Waite wrote: I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the Debian package manager. The machine was running with authentication enabled and was using Debian, CentOS, Red Hat, and Windows slave agents. The Linux slave agents are launched with ssh. The Windows slave agents are launched with JNLP from a batch file on the Windows machines. The upgrade seems to have blocked all connections from the Windows (JNLP) slaves. I assume that is intentional since I had authentication enabled and 1.480.2 attempts to disallow unauthenticated slave agent connections. I resolved that by disabling authentication on the master server. I believe that is a consequence of the changes made in 1.480.2. I haven't upgraded my Jenkins instance yet to see this but I read the following advisory earlier today and believe the change is related to that. https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 Regards Richard After the upgrade, I see some Dead entries in the list of slaves on the left side of the Jenkins opening page. When I click the red Dead entry, it shows the following stack trace: java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:218) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:64) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1197) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:136) at hudson.model.Executor.run(Executor.java:211) Once I click through that Dead thread one or two times, the slave agent seems to remain running without interruption. Are those expected results that are part of the transition from 1.480.1 to 1.480.2? Thanks, Mark Waite
Re: Master + slave + job JVM memory tuning...
I would never advise more than one executor per slave :-o At some point there will be unit test failures in a project as it has badly written unit tests that blindly assume they can use port 12345 (and it will be in use for a different job - and then fight each other). And it will be the CI systems fault and come at a time that the most awkward for you (the project is trying to release, and you are about to leave for the weekend!) The exception to this would be where the jenkins job is acting more as a controller and the work is being performed on some other system. /James On Monday, 7 January 2013 18:36:58 UTC, Jeff Vincent wrote: Thanks...I unfortunately can't be in the UK for the event. So if the amount of RAM is fixed (4GB), what is a good rule of thumb for determining what to allocate to the slave process, how many executors it can reasonably support, etc? I realize there are a lot of other variables but any starting point and things to consider or factor in that may not be obvious could help. Or is it just a matter or monitoring and tuning? On Jan 7, 2013 2:31 AM, Nord, James jn...@nds.com javascript: wrote: Have enough RAM on the slave that you can run your jobs plus Jenkins + some for overhead. (e.g. 1GB of Jenkins slave, + #executors * ( 2GB for Maven +2GB for unit tests in forked VM) + OS overhead) Although this amount is mostly an overkill setting it too close to the threshold will slow your jobs down due to paging at best, or mean you get intermittent failures due to OOM at worst – (memory is generally cheaper that human time taken to investigate issues!) (our maven jobs can be very memory hungry so your figures will vary) (Note I recommend a single executor per slave) The master depends more on how many jobs / reports per jobs / job history you have etc – we use 10GB (but not tomcat). If you’re in the UK and there is any spaces left I will cover some things like this next week at the Jenkins User Event. /James *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Jeff *Sent:* 04 January 2013 21:56 *To:* jenkins...@googlegroups.com javascript: *Subject:* Master + slave + job JVM memory tuning... I'm trying to optimize how much memory I allocate to the master application (aka - tomcat), slave processes, maven tasks, etc. and going crazy. I've been unsuccessful in finding a guideline to determine how much memory I ought to allocate or if I should just let the defaults work. All machines are single processor, dual core with 4 GB ram. I've typically set tomcat to use 2048MB + 512MB permgen space and set my maven process to use 384MB max. Is this reasonable? My slaves are set to run 4 executors. Jobs use either svn or git to check out code and Maven to build with a SONAR post-build analysis. We also do Maven releases at times. How much does the core slave process need? Is there a rule-of-thumb based on the number of executors? Any perspective/considerations/resources/links/pointers are much appreciated. -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.com javascript: and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
Re: LTS upgrade notifications
you may waat to remove the contents of jenkins_dir/data/updates /James On Monday, 7 January 2013 13:53:18 UTC, Jon Schewe wrote: I just switched one of my Jenkins servers to the LTS release. I downloaded the war file and replaced my current war file. I then updated the update site for the plugins and restarted. Everything is running fine, except when I goto Manage Jenkins I'm still prompted to upgrade to the latest bleeding edge release. Did I miss something here or do the LTS releases not check a separate update site? In the bottom right I see 1.480.1. -- http://mtu.net/~jpschewe
Problem running tests in jenkins-test-harness from Eclipse
Hi, I've got a little problem recently. I'm no longer able to run the tests in the jenkins-test-harness from within Eclipse. It was running successfully for a while but now I get the following stacktrace in the JUnit-view: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:898) at jenkins.model.Jenkins.init(Jenkins.java:795) at hudson.model.Hudson.init(Hudson.java:81) at org.jvnet.hudson.test.HudsonTestCase.newHudson(HudsonTestCase.java:479) at org.jvnet.hudson.test.HudsonTestCase.setUp(HudsonTestCase.java:316) at junit.framework.TestCase.runBare(TestCase.java:132) at org.jvnet.hudson.test.HudsonTestCase.runBare(HudsonTestCase.java:294) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:882) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at hudson.ExtensionList.get(ExtensionList.java:153) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1066) at hudson.maven.PluginImpl.init(PluginImpl.java:54) ... 13 more It might have started after I ran the server with mvn hudson-dev:run but I'm not sure. What might be the problem? All tests run successfully from the terminal. Regards, Joakim
Re: Run junkins jobs as different user
Hi, This means the only way I can do that is to use a slave. As a developer I never needed to do that before even if I am familiar with the terms master/slave. Do you suggest any link for beginners? if it is in the context of jenkins would be awesome? Thank you On Fri, Jan 4, 2013 at 6:01 PM, Les Mikesell lesmikes...@gmail.com wrote: On Fri, Jan 4, 2013 at 3:35 PM, Adam Tong adam.to...@gmail.com wrote: We are using Linux. So maybe there is a way to that on Linux? But this supposes Jenkins offers that possibility. If you use ssh to start the slave, you should be able to log in as any user - as long as you have the password or set up keys. I think you should even be able to run multiple instances on the same host as different users if you wanted. -- Les Mikesell lesmikes...@gmail.com
Re: How set java.io.tmpdir=/tmp for Jenkins slave?
Hi, Try to add the following inside the JVM options: -Djava.io.tmpdir=/foo (click on Advanced under Launch method to see show this field). Then disconnect and reconnect the slave to take this parameter into account. Cheers, Reynald On Monday, January 7, 2013 at 18:51 , Ed of the Mountain wrote: Is there a way to set system property: java.io.tmpdir=/tmp for a slave? I am launching the slave via SSH. I assume if I can map java.io.tmpdir=/volume1/tmp my problem is solved. My problem is I am running out of /tmp space with a Jenkins slave running on a Synology ARM based NAS which uses tmpfs or RAM as the /tmp resource. Thanks in advance, -Ed
Setting the context root on Jenkins 1.498 on debian 6 (latest) has broken
Hi all, I have been running jenkins on Debian for quite a while now, and the documented way to set the context root to /jenkins was to add a --prefix=/jenkins to the JENKINS_OPTS variable in the /etc/init.d/jenkins script. When I did an apt-get update; apt-get dist-upgrade it told me the latest version has removed that. I went ahead and installed the latest script assuming there was another way of doing it but I cannot figure out where I should add it now. /etc/init.d/jenkins no longer has the environment variable, and ~/config.xml doesn't include any likely looking suspects. Any ideas? The wiki didn't turn up much either (it suggested adding the --prefix). Thanks. Col
Is it possible to fail build if test time increases by X%
Hi all, Does anyone know how to do this? Can I fail a build if a test time increases by a certain percentage? For example, if a test takes 100 ms today, but tomorrow it takes 5 seconds...can I have Jenkins fail the build?
Re: Setting the context root on Jenkins 1.498 on debian 6 (latest) has broken
Simpler than I thought: - add a new line containing JENKINS_ARGS=--prefix=/jenkins to /etc/init.d/jenkins - add to the DAEMONS_ARGS --env=JENKINS_ARGS=$JENKINGS_ARGS Restart jenkins. So the relevant fragment now reads: [code] JENKINS_ARGS=--prefix=/jenkins #DAEMON=$JENKINS_SH DAEMON=/usr/bin/daemon DAEMON_ARGS=--name=$NAME --inherit --env=JENKINS_HOME=$JENKINS_HOME --env=JENKINS_ARGS=$JENKINS_ARGS --output=$JENKINS_LOG --pidfile=$PIDFILE --env=prefix=/jenkins [/code] On Monday, 7 January 2013 21:52:35 UTC, Colin Yates wrote: Hi all, I have been running jenkins on Debian for quite a while now, and the documented way to set the context root to /jenkins was to add a --prefix=/jenkins to the JENKINS_OPTS variable in the /etc/init.d/jenkins script. When I did an apt-get update; apt-get dist-upgrade it told me the latest version has removed that. I went ahead and installed the latest script assuming there was another way of doing it but I cannot figure out where I should add it now. /etc/init.d/jenkins no longer has the environment variable, and ~/config.xml doesn't include any likely looking suspects. Any ideas? The wiki didn't turn up much either (it suggested adding the --prefix). Thanks. Col
Re: LTS upgrade notifications
Can you explain more? What link provided by Jenkins? On Mon, Jan 7, 2013 at 8:09 AM, SBreitbach steffen.breitb...@1und1.dewrote: Don't use the link on the webpage. Use the link provided by Jenkins itself instead. -- http://mtu.net/~jpschewe
Re: How set java.io.tmpdir=/tmp for Jenkins slave?
Thank you Reynald! That solved my problem. Somehow I was blind to seeing the Advanced button on the slave node configuration page. Thanks again for your help! -Ed On Jan 7, 2013, at 3:31 PM, Reynald Borer wrote: Hi, Try to add the following inside the JVM options: -Djava.io.tmpdir=/foo (click on Advanced under Launch method to see show this field). Then disconnect and reconnect the slave to take this parameter into account. Cheers, Reynald On Monday, January 7, 2013 at 18:51 , Ed of the Mountain wrote: Is there a way to set system property: java.io.tmpdir=/tmp for a slave? I am launching the slave via SSH. I assume if I can map java.io.tmpdir=/volume1/tmp my problem is solved. My problem is I am running out of /tmp space with a Jenkins slave running on a Synology ARM based NAS which uses tmpfs or RAM as the /tmp resource. Thanks in advance, -Ed
Re: LTS upgrade notifications
Deleting the contents of the updates directory fixed it. Now I see the option to get 1.480.2 instead of 1.496. On Mon, Jan 7, 2013 at 1:29 PM, teilo teilo+goo...@teilo.net wrote: you may waat to remove the contents of jenkins_dir/data/updates /James On Monday, 7 January 2013 13:53:18 UTC, Jon Schewe wrote: I just switched one of my Jenkins servers to the LTS release. I downloaded the war file and replaced my current war file. I then updated the update site for the plugins and restarted. Everything is running fine, except when I goto Manage Jenkins I'm still prompted to upgrade to the latest bleeding edge release. Did I miss something here or do the LTS releases not check a separate update site? In the bottom right I see 1.480.1. -- http://mtu.net/~jpschewe -- http://mtu.net/~jpschewe
Re: Null pointer exceptions after upgrade from 1.480.1 to 1.480.2
I have the same issue after upgrading from 1.480.1 to 1.480.2 on Ubuntu 12.04. I am able to launch the windows slaves manually, but unable to have them run as a windows service from the gui. I am able to install it as a service from the command line, but the master never connects to the slave. The only hint I have is if I try to run the command for a headless slave, then I get java.io.IOException: Failed to load http://jenkins/computer/server-bld-pc1/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:238) at hudson.remoting.Launcher.run(Launcher.java:200) at hudson.remoting.Launcher.main(Launcher.java:173) I'm obviously missing something here so any pointers greatly appreciated. I have removed all the jar, exe and xml files from the slaves several times, completely deleted the service from the slave, but no change in the behavior. thanks, chanda On Mon, Jan 7, 2013 at 11:17 AM, Richard Mortimer ri...@oldelvet.org.ukwrote: Hi Mark, On 07/01/2013 18:21, Mark Waite wrote: I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the Debian package manager. The machine was running with authentication enabled and was using Debian, CentOS, Red Hat, and Windows slave agents. The Linux slave agents are launched with ssh. The Windows slave agents are launched with JNLP from a batch file on the Windows machines. The upgrade seems to have blocked all connections from the Windows (JNLP) slaves. I assume that is intentional since I had authentication enabled and 1.480.2 attempts to disallow unauthenticated slave agent connections. I resolved that by disabling authentication on the master server. I believe that is a consequence of the changes made in 1.480.2. I haven't upgraded my Jenkins instance yet to see this but I read the following advisory earlier today and believe the change is related to that. https://wiki.jenkins-ci.org/**display/SECURITY/Jenkins+** Security+Advisory+2013-01-04https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 Regards Richard After the upgrade, I see some Dead entries in the list of slaves on the left side of the Jenkins opening page. When I click the red Dead entry, it shows the following stack trace: java.lang.NullPointerException at hudson.matrix.**MatrixConfiguration.newBuild(** MatrixConfiguration.java:218) at hudson.matrix.**MatrixConfiguration.newBuild(** MatrixConfiguration.java:64) at hudson.model.AbstractProject.**createExecutable(** AbstractProject.java:1197) at hudson.model.AbstractProject.**createExecutable(** AbstractProject.java:136) at hudson.model.Executor.run(**Executor.java:211) Once I click through that Dead thread one or two times, the slave agent seems to remain running without interruption. Are those expected results that are part of the transition from 1.480.1 to 1.480.2? Thanks, Mark Waite -- *Confidentiality Notice*: This e-mail, including all attachments, is confidential information of Lytro, Inc. If the reader of this e-mail is not the intended recipient or its authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: Setting the context root on Jenkins 1.498 on debian 6 (latest) has broken
/etc/default/jenkins should be your friend on debian. /James On Monday, 7 January 2013 21:52:35 UTC, Colin Yates wrote: Hi all, I have been running jenkins on Debian for quite a while now, and the documented way to set the context root to /jenkins was to add a --prefix=/jenkins to the JENKINS_OPTS variable in the /etc/init.d/jenkins script. When I did an apt-get update; apt-get dist-upgrade it told me the latest version has removed that. I went ahead and installed the latest script assuming there was another way of doing it but I cannot figure out where I should add it now. /etc/init.d/jenkins no longer has the environment variable, and ~/config.xml doesn't include any likely looking suspects. Any ideas? The wiki didn't turn up much either (it suggested adding the --prefix). Thanks. Col
Re: Is it possible to fail build if test time increases by X%
There is no way that I currently know of, and the company I work for have have a need for performance regression tests jobs (so I have looked). I have not yet had time to open an IDE to look at this. (we want to look at a rolling average rather than the last successful job, and also match this to individual tests - so when a new test is introduced it doesn't immediately mark the build as unstable!) On Monday, 7 January 2013 21:57:29 UTC, Keith B. Perry wrote: Hi all, Does anyone know how to do this? Can I fail a build if a test time increases by a certain percentage? For example, if a test takes 100 ms today, but tomorrow it takes 5 seconds...can I have Jenkins fail the build?
Re: Is it possible to fail build if test time increases by X%
@teilo - That is pretty much exactly what I am looking for. This could be a fun project, but I am not sure I have time right now. This would be an awesome feature. On Monday, January 7, 2013 4:49:16 PM UTC-6, teilo wrote: There is no way that I currently know of, and the company I work for have have a need for performance regression tests jobs (so I have looked). I have not yet had time to open an IDE to look at this. (we want to look at a rolling average rather than the last successful job, and also match this to individual tests - so when a new test is introduced it doesn't immediately mark the build as unstable!) On Monday, 7 January 2013 21:57:29 UTC, Keith B. Perry wrote: Hi all, Does anyone know how to do this? Can I fail a build if a test time increases by a certain percentage? For example, if a test takes 100 ms today, but tomorrow it takes 5 seconds...can I have Jenkins fail the build?
Re: Run junkins jobs as different user
SSH is not the only way to run something as a different user. On any Unix-like system, you should be familiar with the sudo command which can be configured to allow any user to run any command as some other user, optionally restricting the command and optionally requiring a password. URL:http://linux.die.net/man/8/sudo However, if you ever want to use multiple slaves, using SSH may turn out to be a simpler configuration even if running a slave as a different user on the same system. Adam Tong wrote: Hi, This means the only way I can do that is to use a slave. As a developer I never needed to do that before even if I am familiar with the terms master/slave. Do you suggest any link for beginners? if it is in the context of jenkins would be awesome? Thank you On Fri, Jan 4, 2013 at 6:01 PM, Les Mikesell lesmikes...@gmail.com wrote: On Fri, Jan 4, 2013 at 3:35 PM, Adam Tong adam.to...@gmail.com wrote: We are using Linux. So maybe there is a way to that on Linux? But this supposes Jenkins offers that possibility. If you use ssh to start the slave, you should be able to log in as any user - as long as you have the password or set up keys. I think you should even be able to run multiple instances on the same host as different users if you wanted. -- Jonathan Rogers
Re: Job Generator Plugin jobs get stuck when deleting generated jobs
I have a top-level generator project trigger_builds_generator with one generator parameter MANUAL_GIT_BRANCH which triggers two parameterized build entries for a second level project build_generator with two different values for a second generator parameter VIRTUALENV_NAME. The build_generator project in turn triggers two different projects to run tests. Running the hierarchy generates seven projects overall. If you need it, I can probably provide the configuration itself. After running the hierarchy in the default create mode, I see the seven new projects. Then, I run the hierarchy exactly the same way except checking the Delete jobs and confirmation check boxes. The top-level trigger_builds_generator job succeeds immediately, removing the project it had created. However, three jobs remain executing, one for each lower level generator project. They cannot be killed by any means I'm aware of. Once I restart Jenkins, the invincible jobs are gone of course and some of the projects they were intended to delete have gone away. As I said, I only see this problem when using the delete mode. Creating brand new or replacing existing jobs works fine. It looks like there's some locking problem that only exhibits in delete mode. syl20bnr wrote: Can you give me more details on your hierarchy so I can try to reproduce this bug ? Thank you. Le jeudi 3 janvier 2013 23:02:15 UTC-5, JonathanRRogers a écrit : Whenever I run a job generator job to delete an existing hierarchy of generated jobs, the generator jobs themselves get stuck. They never complete and if I attempt to kill them manually, the entire Jenkins web interface gets stuck and I can never load another page. The only way to get rid of the stuck jobs I've found so far is to restart Jenkins. Generating new jobs doesn't seem to have the same problem, even if replacing existing ones. -- Jonathan Rogers
JNLP slave no longer works
I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer connect. I get an error: JNLPException[category: Download Error : Exception: java.io.IOException: Server returned HTTP response code: 403 for URL: https://server:8010/computer/slave-jnlp/slave-agent.jnlp : LaunchDesc: null ] at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) I have security turned on, although anonymous has overall read. What other permissions do I need to change? What are my options? -- http://mtu.net/~jpschewe
Re: JNLP slave no longer works
This is unfortunately a necessary measure. See the Fix section in https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 2013/1/7 Jon Schewe jpsch...@mtu.net I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer connect. I get an error: JNLPException[category: Download Error : Exception: java.io.IOException: Server returned HTTP response code: 403 for URL: https://server:8010/computer/slave-jnlp/slave-agent.jnlp : LaunchDesc: null ] at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) I have security turned on, although anonymous has overall read. What other permissions do I need to change? What are my options? -- http://mtu.net/~jpschewe -- Kohsuke Kawaguchi
Re: JNLP slave no longer works
OK, so if I just keep the jnlp local now instead of always requesting it on
startup, thing will continue to work, correct?
On Monday, January 7, 2013, Kohsuke Kawaguchi wrote:
This is unfortunately a necessary measure.
See the Fix section in
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04
2013/1/7 Jon Schewe jpsch...@mtu.net javascript:_e({}, 'cvml',
'jpsch...@mtu.net');
I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer
connect. I get an error:
JNLPException[category: Download Error : Exception: java.io.IOException:
Server returned HTTP response code: 403 for URL:
https://server:8010/computer/slave-jnlp/slave-agent.jnlp : LaunchDesc:
null ]
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I have security turned on, although anonymous has overall read. What
other permissions do I need to change? What are my options?
--
http://mtu.net/~jpschewe
--
Kohsuke Kawaguchi
--
On my mobile device - please excuse typos
