Crash after update to 1.468
Hi, Jenkins 1.468 crashes at startup: Running from: /usr/share/jenkins/jenkins.war 12.06.2012 08:09:45 winstone.Logger logInternal INFO: Beginning extraction from war file Jenkins home directory: /srv/jenkins/jenkins found at: EnvVars.masterEnvVars.get(JENKINS_HOME) 12.06.2012 08:09:46 winstone.Logger logInternal INFO: AJP13 Listener started: port=8009 12.06.2012 08:09:46 winstone.Logger logInternal INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled 12.06.2012 08:09:46 jenkins.InitReactorRunner$1 onAttained INFO: Started initialization 12.06.2012 08:09:46 jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins 12.06.2012 08:09:46 hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run INFO: Trying to connect 12.06.2012 08:09:46 hudson.plugins.im.HudsonIsBusyListener init INFO: Executor busy listener created 12.06.2012 08:09:46 jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins 12.06.2012 08:09:49 jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins 12.06.2012 08:09:49 jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions 12.06.2012 08:09:58 jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs 12.06.2012 08:09:58 org.apache.sshd.common.util.SecurityUtils$BouncyCastleRegistration run INFO: Trying to register BouncyCastle as a JCE provider 12.06.2012 08:09:58 org.apache.sshd.common.util.SecurityUtils$BouncyCastleRegistration run INFO: Registration succeeded 12.06.2012 08:09:58 org.jenkinsci.main.modules.sshd.SSHD start INFO: Started SSHD at port 50408 12.06.2012 08:09:58 jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization 12.06.2012 08:09:59 org.springframework.context.support.AbstractApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@2a163765: display name [Root WebApplicationContext]; startup date [Tue Jun 12 08:09:59 CEST 2012]; root of context hierarchy 12.06.2012 08:09:59 org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@2a163765]: org.springframework.beans.factory.support.DefaultListableBeanFactory@37eaab 12.06.2012 08:09:59 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@37eaab: defining beans [initialDirContextFactory,bindAuthenticator,ldapUserSearch,authenticationManager,authoritiesPopulator]; root of factory hierarchy 12.06.2012 08:09:59 org.acegisecurity.ldap.DefaultInitialDirContextFactory setProviderUrl INFO: URL 'ldaps://URL/dc=cut,dc=cut', root DN is 'dc=cut,dc=cut' 12.06.2012 08:09:59 jenkins.InitReactorRunner$1 onTaskFailed SCHWERWIEGEND: Failed Finalizing set up java.lang.IllegalAccessError: tried to access method hudson.security.SecurityRealm.findBean(Ljava/lang/Class;Lorg/springframework/context/ApplicationContext;)Ljava/lang/Object; from class hudson.security.LDAPSecurityRealm$LDAPUserDetailsService at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.init(LDAPSecurityRealm.java:419) at hudson.security.LDAPSecurityRealm.createSecurityComponents(LDAPSecurityRealm.java:369) at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:398) at hudson.security.HudsonFilter.reset(HudsonFilter.java:134) at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:1960) at jenkins.model.Jenkins$17.run(Jenkins.java:2524) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:874) 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.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) 12.06.2012 08:09:59 hudson.WebAppMain$2 run SCHWERWIEGEND: Failed to initialize Jenkins org.jvnet.hudson.reactor.ReactorException: java.lang.IllegalAccessError: tried to access method hudson.security.SecurityRealm.findBean(Ljava/lang/Class;Lorg/springframework/context/ApplicationContext;)Ljava/lang/Object; from class hudson.security.LDAPSecurityRealm$LDAPUserDetailsService at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:885) at jenkins.model.Jenkins.init(Jenkins.java:790) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at
Re: Create a pre-production environment for Jenkins
Hi, It seems that 'push' automatically updates of Jenkins and its plugins from pre-production to production is difficult. However, it would be interesting to know how to create a sort of continuous integration of the continuous integration environment :) Thank you for your answer. Le lundi 11 juin 2012 23:09:29 UTC+2, LesMikesell a écrit : On Mon, Jun 11, 2012 at 2:54 PM, mpapo - Michael Pailloncy michael.paillo...@gmail.com wrote: nobody ever had this problematic ? I think most people do it the other way around. That is they build and test their test environment first, then after seeing that it works, duplicate it into production. But, I think you have a point that there is no easy way to keep them loosely coordinated so you can test changes in an ongoing way and be sure that they won't break jobs that have evolved differently in production. -- Les Mikesell lesmikes...@gmail.com
Re: jenkins_1.469_all.deb missing!
I'm trying again today to upgrade jenkins without any success :-( $ sudo apt-get update ... $ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: jenkins 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 48.7 MB of archives. After this operation, 1077 kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://pkg.jenkins-ci.org/debian/ binary/ jenkins 1.469 [48.7 MB] Fetched 48.7 MB in 5s (8792 kB/s) Failed to fetch http://pkg.jenkins-ci.org/debian/binary/jenkins_1.469_all.deb Size mismatch It seems there is a mismatch between the package and its reference into the package table (Packages.gz or Packages.bz2) in the server. Regards, Le 11/06/2012 18:15, Kohsuke Kawaguchi a écrit : My apologies, I've done incorrect merge this Sunday, and so 1.469 bits are bogus. I'm fixing them now and releasing 1.468, which should have been what's released. 2012/6/10 mokimiguel.moquil...@gmail.com: Hi, I tried unsuccessfully upgrading of jenkins on our GNU/Linux Debian machine. It seems the package jenkins 1.469 is missing: Err http://pkg.jenkins-ci.org/debian/ binary/ jenkins 1.469 404 Not Found And in the web site, the link jenkins_1.469_all.deb at http://pkg.jenkins-ci.org/debian/ has sent back a 404 web page. -- Large corporations have no human feelings. They are psychopaths by design. RMS
AW: Jenkins CLI user gets locked in Active Directory
So, I tried again with the new Active Directory plugin. When using our Service_Build user, there is no authentication request coming into Active Directory, which is how it should be. So the problem was the old, buggy Active Directory plugin. Thanks for the help best regards, Eric -Ursprüngliche Nachricht- Von: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] Im Auftrag von Lewis, Eric Gesendet: Montag, 11. Juni 2012 17:08 An: jenkinsci-users@googlegroups.com Betreff: AW: Jenkins CLI user gets locked in Active Directory Ok, upgrading to the latest Active Directory plugin solves at least the problem in the Jenkins configuration page. I'll check tomorrow about the rest of the problem. Best regards, Eric -Ursprüngliche Nachricht- Von: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] Im Auftrag von Lewis, Eric Gesendet: Montag, 11. Juni 2012 14:14 An: jenkinsci-users@googlegroups.com Betreff: AW: Jenkins CLI user gets locked in Active Directory Ok, I checked with our sysadmin, but there's not more information in the logs. However, another problem, which I postponed, may be the cause. As I mentioned, we're using Active Directory for authentification. In the Jenkins config, I'm using the Matrix-based security. Since we installed the new version, I always see errors in the GUI and in the log. For instance, for the mentioned Service_Build user, I see: Failed to test the validity of the user name Service_Build org.acegisecurity.BadCredentialsException: Failed to retrieve user information for Service_Build; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 04DC: LdapErr: DSID-0C0906E8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v1db1]; remaining name 'DC=ipie,DC=ch' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:130) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:95) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:27) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:551) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:304) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:288) at sun.reflect.GeneratedMethodAccessor3018.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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
Can you run a downstream project only if the upstream has changed?
Dear all, I have a Maven project with two jobs: 1) Test - runs all tests (with surefire), and runs on every SCM commit 2) Deploy - deploys the new version on a server, and runs once at midnight Everything is running great. However, we're now on a phase where changes don't happen very often. Still, every night the deploy job redeploys the project. Ideally, if no commits were performed that day, there is no need for the deploy job to run. Is there a way to run project only if there were changes in the upstream since the previous run ? Cheers, Miguel Almeida
A question about the upcoming change: Added a new hook to enable matrix project axes to change its values per build.
Hello,
I saw this in the change log:
Added a new hook to enable matrix project axes to change its values per
build.
Does this mean that we will be able to use environment variables and/or
parameters (i.e.${MY_VAR}) to change the axes before launching the build?
This would be awesome in situations where you want to launch the same
configuration on different sets of machines.
Thank you,
_
Costin Caraivan
Re: jenkins_1.469_all.deb missing!
Strange: not even a forced install proceeds for me ;( best Jan
Re: jenkins_1.469_all.deb missing!
Same here on yum repo, following these instructions https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions is throwing Error Downloading Packages: jenkins-1.469-1.1.noarch: failure: jenkins-1.469-1.1.noarch.rpm from jenkins: [Errno 256] No more mirrors to try. J. On Tuesday, June 12, 2012 4:24:20 PM UTC+2, Jan Ptacek wrote: Strange: not even a forced install proceeds for me ;( best Jan
Ability to hide the New Job link without revoking create job permissions?
We recently upgraded from Hudson 1.385 to Jenkins 1.467. On Hudson, we had a plugin that we used to create jobs, which had a predetermined set of criteria for how a job was set up. The create permission was revoked across almost every ACL, and people that did not have create permission could still create jobs with this plugin. Since the upgrade to Jenkins, this is not the case. Using this plugin fails claiming that the user does not have permission. Ultimately, we want all of the users in our company to only have the option to use this plugin to create jobs, since it sets them up to our company's standard. That said, is there any way to: 1) Hide the new job link, or 2) Temporarily escalate permissions within the context of one plugin Currently the plugin is still using the 1.385 apis. I'll be updating them to use the Jenkins apis soon, but given that this is a bug fix we need to try and push it would be prudent to keep the scope of changes as small as possible. However, if the only way to fix this is to use the Jenkins apis, I can perform that update. Any help is appreciated.
RE: M2 Release plugin disapper
Hi Tim, The following page should give detailed information about this: https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup Specifically Within the Job”permission group there will be a permission called“Release” /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of ?? Sent: 12 June 2012 14:52 To: jenkinsci-users@googlegroups.com Subject: Re: M2 Release plugin disapper Upgrade to the latest version whatever for jenkins or m2 release plugin, collabet net plugin, problem still happens. Does anyone know how to auth the M2 release plugin? Br, Tim 2012/6/12 吴亭 wutingb...@gmail.commailto:wutingb...@gmail.com Does any one met this problem before? Br, Tim 2012/6/12 吴亭 wutingb...@gmail.commailto:wutingb...@gmail.com Hi Nord, Thanks for your reply, could you see more detail about this, I search a lot from my jenkins config tab and do not find this configuration. Thanks in advance. Br, Tim 2012/6/11 Nord, James jn...@nds.commailto:jn...@nds.com There is a separate permission for the m2release that you can configure in the Jenkins config. From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com] On Behalf Of Tim Sent: 11 June 2012 14:57 To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: M2 Release plugin disapper Hi there, I am using the M2 Release plugin for us to release the project, and recently, for the security issue, we use team forge to auth the project. However, I found, only admin can do the maven release, other team member can not see Perform maven release Button. Do you have any experience for this? Br, Tim ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.commailto: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 **
Send over ftp only changed scm files
There are some way to do that? I'm trying to do find some plugin or solution since yesterday. Can someone help me?
Re: Send over ftp only changed scm files
On 12-06-12 02:10 PM, Roy wrote: There are some way to do that? I'm trying to do find some plugin or solution since yesterday. Can someone help me? I don't know about anyone else but I don't think I really understand what it is you want. b. signature.asc Description: OpenPGP digital signature
Re: Crash after update to 1.468
see https://issues.jenkins-ci.org/browse/JENKINS-14080 my shortterm-solution : complete disable security and LDAP ( in config.xml ). On Tuesday, June 12, 2012 9:09:42 AM UTC+2, MR wrote: I've got the same problem - currently testing with different jenkins-versions -- but still the same error. Am Dienstag, 12. Juni 2012 08:17:51 UTC+2 schrieb fxp: Hi, Jenkins 1.468 crashes at startup: Running from: /usr/share/jenkins/jenkins.war 12.06.2012 08:09:45 winstone.Logger logInternal INFO: Beginning extraction from war file Jenkins home directory: /srv/jenkins/jenkins found at: EnvVars.masterEnvVars.get(JENKINS_HOME) 12.06.2012 08:09:46 winstone.Logger logInternal INFO: AJP13 Listener started: port=8009 12.06.2012 08:09:46 winstone.Logger logInternal INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled 12.06.2012 08:09:46 jenkins.InitReactorRunner$1 onAttained INFO: Started initialization 12.06.2012 08:09:46 jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins 12.06.2012 08:09:46 hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run INFO: Trying to connect 12.06.2012 08:09:46 hudson.plugins.im.HudsonIsBusyListener init INFO: Executor busy listener created 12.06.2012 08:09:46 jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins 12.06.2012 08:09:49 jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins 12.06.2012 08:09:49 jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions 12.06.2012 08:09:58 jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs 12.06.2012 08:09:58 org.apache.sshd.common.util.SecurityUtils$BouncyCastleRegistration run INFO: Trying to register BouncyCastle as a JCE provider 12.06.2012 08:09:58 org.apache.sshd.common.util.SecurityUtils$BouncyCastleRegistration run INFO: Registration succeeded 12.06.2012 08:09:58 org.jenkinsci.main.modules.sshd.SSHD start INFO: Started SSHD at port 50408 12.06.2012 08:09:58 jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization 12.06.2012 08:09:59 org.springframework.context.support.AbstractApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@2a163765: display name [Root WebApplicationContext]; startup date [Tue Jun 12 08:09:59 CEST 2012]; root of context hierarchy 12.06.2012 08:09:59 org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@2a163765]: org.springframework.beans.factory.support.DefaultListableBeanFactory@37eaab 12.06.2012 08:09:59 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@37eaab: defining beans [initialDirContextFactory,bindAuthenticator,ldapUserSearch,authenticationManager,authoritiesPopulator]; root of factory hierarchy 12.06.2012 08:09:59 org.acegisecurity.ldap.DefaultInitialDirContextFactory setProviderUrl INFO: URL 'ldaps://URL/dc=cut,dc=cut', root DN is 'dc=cut,dc=cut' 12.06.2012 08:09:59 jenkins.InitReactorRunner$1 onTaskFailed SCHWERWIEGEND: Failed Finalizing set up java.lang.IllegalAccessError: tried to access method hudson.security.SecurityRealm.findBean(Ljava/lang/Class;Lorg/springframework/context/ApplicationContext;)Ljava/lang/Object; from class hudson.security.LDAPSecurityRealm$LDAPUserDetailsService at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.init(LDAPSecurityRealm.java:419) at hudson.security.LDAPSecurityRealm.createSecurityComponents(LDAPSecurityRealm.java:369) at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:398) at hudson.security.HudsonFilter.reset(HudsonFilter.java:134) at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:1960) at jenkins.model.Jenkins$17.run(Jenkins.java:2524) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:874) 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.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) 12.06.2012 08:09:59 hudson.WebAppMain$2 run SCHWERWIEGEND: Failed to initialize Jenkins org.jvnet.hudson.reactor.ReactorException: java.lang.IllegalAccessError: tried to access method
Push Git tags options doesn't exist for us
The docs make reference to a Push GIT tags back to origin repository option but we're on 1.1.19 version of the plugin and I'm looking at the Post Build options that appear when you add a Post-build Action for Git Publisher: Git Publisher Push Only If Build Succeeds Merge Results Tags[ Add Tag ] Tags to push to remote repositories Branches[ Add Branch ] Branches to push to remote repositories That's it. That's all there is. Is there some reason I don't have the Push GIT tags back to origin repository option because we're running it on Windows or something else?
Re: Offline and revert slave after build?
I've found a partial solution, at least. I installed the Groovy Post-build plugin and for every job add a Groovy script: manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true) -- Sami Sami Tikka kirjoitti 11.6.2012 kello 21.24: Can I pick your brains for a moment? I have suddenly developed a need to make sure my slaves (libvirt vms) are clean when running test jobs. My initial idea was to use jenkins cli to take a node offline during a test run to prevent it from accepting more work (my slaves all have just 1 executor) and then using parameterized trigger to run a job on the master that would recreate the slave vm. Unfortunately these test slaves run in a network with limited access due to company security policies. The slaves are not able to e.g. connect to the master. I believe this prevents me from using the jenkins cli in the slave. Is there another way I can make a slave take only 1 build, execute it and not pick up more work? I saw the Offline node on failure plugin, which seemed promising, but it seems to take a node offline only when a build fails. The libvirt cloud plugin sets up a new libvirt slave type, but as far as I can see it does not provide a way to recreate the slave after every build or revert to a clean snapshot. Any ideas? -- Sami
BMC BladeLogic Jenkins
Did you come up with a good solution to this? I am on a tram in the same situation. Thanks, James
Re: Jenkins gets killed / crashes unexpectedly
Try 1.469. -- Sami Ove Ranheim kirjoitti 12.6.2012 kello 15.44: Hi, I experience this strange problem with Jenkins (build: #1468). It's running under its own non-privileged user on Centos 6. During execution of Maven 3 tests, all of a sudden the Jenkins process gets killed. I'm clueless to what's causing this. The console log is really not too informative either: INFO: Started SSHD at port 56903 Jun 12, 2012 10:37:40 AM jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization Jun 12, 2012 10:37:43 AM org.springframework.context.support.AbstractApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@140c7272: display name [Root WebApplicationContext]; startup date [Tue Jun 12 10:37:43 CEST 2012]; root of context hierarchy Jun 12, 2012 10:37:43 AM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@140c7272]: org.springframework.beans.factory.support.DefaultListableBeanFactory@3b896429 Jun 12, 2012 10:37:43 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@3b896429: defining beans [filter,legacy]; root of factory hierarchy Jun 12, 2012 10:37:43 AM hudson.TcpSlaveAgentListener init INFO: JNLP slave agent listener started on TCP port 44944 Jun 12, 2012 10:37:56 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running Jun 12, 2012 10:41:02 AM hudson.model.Run run INFO: PoC Build #10 main build action completed: SUCCESS Jun 12, 2012 11:06:03 AM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in PoC Build. Triggering #11 ./j.sh: line 5: 25446 Killed java -jar jenkins.war --httpPort=8082 --prefix=/jenkins Any idea to what's causing this? -Ove
Re: Can you run a downstream project only if the upstream has changed?
Configure the Deploy job to also check out source code from SCM (even though it would not use it) and make it poll only at midnight. Alternatively, make the Test job trigger a job which waits until next midnight and then triggers Deploy. -- Sami Miguel Almeida kirjoitti 12.6.2012 kello 14.30: Dear all, I have a Maven project with two jobs: 1) Test - runs all tests (with surefire), and runs on every SCM commit 2) Deploy - deploys the new version on a server, and runs once at midnight Everything is running great. However, we're now on a phase where changes don't happen very often. Still, every night the deploy job redeploys the project. Ideally, if no commits were performed that day, there is no need for the deploy job to run. Is there a way to run project only if there were changes in the upstream since the previous run ? Cheers, Miguel Almeida
Re: Jenkins gets killed / crashes unexpectedly
It could be the kernel running out of virtual memory and the OOM (out of memory) killer is killing jenkins. Run the dmesg command in a terminal window on your jenkins server and see if the OOM kill has been active. Also see. https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError Regards Richard On 12/06/2012 13:44, Ove Ranheim wrote: Hi, I experience this strange problem with Jenkins (build: #1468). It's running under its own non-privileged user on Centos 6. During execution of Maven 3 tests, all of a sudden the Jenkins process gets killed. I'm clueless to what's causing this. The console log is really not too informative either: INFO: Started SSHD at port 56903 Jun 12, 2012 10:37:40 AM jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization Jun 12, 2012 10:37:43 AM org.springframework.context.support.AbstractApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@140c7272: display name [Root WebApplicationContext]; startup date [Tue Jun 12 10:37:43 CEST 2012]; root of context hierarchy Jun 12, 2012 10:37:43 AM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@140c7272]: org.springframework.beans.factory.support.DefaultListableBeanFactory@3b896429 Jun 12, 2012 10:37:43 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@3b896429: defining beans [filter,legacy]; root of factory hierarchy Jun 12, 2012 10:37:43 AM hudson.TcpSlaveAgentListener init INFO: JNLP slave agent listener started on TCP port 44944 Jun 12, 2012 10:37:56 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running Jun 12, 2012 10:41:02 AM hudson.model.Run run INFO: PoC Build #10 main build action completed: SUCCESS Jun 12, 2012 11:06:03 AM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in PoC Build. Triggering #11 ./j.sh: line 5: *25446 Killed java -jar jenkins.war --httpPort=8082 --prefix=/jenkins* Any idea to what's causing this? -Ove
