REST API update job boken?
Hi,
I have installed Jenkins LTS 1.596.2 and I came across to the fact that
updating the job configuration via de REST API doesn't seem to work anymore.
I tried something like:
curl -v -X POST --data-binary @req.xml -u myuser:mypass \
-H 'Content-Type: application/xml' \
-w '\nStatus: %{http_code}\n' \
http://myjenkins.host.com/job/myjob/config.xml;
And I get a 500 response.
The same happens if I use the Python API.
Looks like somehow it is failing to obtain the SAX parser.
Has anyone noticed this too?
This is the stack trace:
java.io.IOException: Failed to persist config.xml
at hudson.model.AbstractItem.updateByXml(AbstractItem.java:648)
at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:614)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
jenkins.security.BasicHeaderProcessor.success(BasicHeaderProcessor.java:140)
at
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:82)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at
Re: REST API update job boken?
Thanks
On Tue, Mar 31, 2015 at 4:18 PM, Daniel Beck m...@beckweb.net wrote:
This may have been caused by a security fix in Jenkins 1.596.1 / Jenkins
1.600.
This issue is tracked as
https://issues.jenkins-ci.org/browse/JENKINS-27548 -- please provide more
information as requested there.
On 31.03.2015, at 20:49, Nicky Ramone nixe...@gmail.com wrote:
Hi,
I have installed Jenkins LTS 1.596.2 and I came across to the fact that
updating the job configuration via de REST API doesn't seem to work anymore.
I tried something like:
curl -v -X POST --data-binary @req.xml -u myuser:mypass \
-H 'Content-Type: application/xml' \
-w '\nStatus: %{http_code}\n' \
http://myjenkins.host.com/job/myjob/config.xml;
And I get a 500 response.
The same happens if I use the Python API.
Looks like somehow it is failing to obtain the SAX parser.
Has anyone noticed this too?
This is the stack trace:
java.io.IOException: Failed to persist config.xml
at hudson.model.AbstractItem.updateByXml(AbstractItem.java:648)
at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:614)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
jenkins.security.BasicHeaderProcessor.success(BasicHeaderProcessor.java:140)
at
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:82)
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
Re: Archived Artifacts
Domi, I think this is the solution to my problem. I will try this. Thanks! On Tue, Dec 18, 2012 at 1:04 PM, domi d...@fortysix.ch wrote: In the advanced section of your maven build, you can Disable automatic artifact archiving With the Create Job Advanced Plugin you can disable this setting per default for new jobs: https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin /Domi On 18.12.2012, at 16:26, Kanstantsin Shautsou gentoo.inte...@gmail.com wrote: You use maven style project, it saves build artifacts. If you have problems with space, decrease history. On 10.12.2012, at 20:41, Nicky Ramone nixe...@gmail.com wrote: Hello. I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds. Example: $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz Is this due to fingerprinting? is there any way to avoid this? Thanks Regards
Re: Archived Artifacts
Did anyone notice the same behavior? On Mon, Dec 10, 2012 at 2:41 PM, Nicky Ramone nixe...@gmail.com wrote: Hello. I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds. Example: $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz Is this due to fingerprinting? is there any way to avoid this? Thanks Regards
Archived Artifacts
Hello. I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds. Example: $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz Is this due to fingerprinting? is there any way to avoid this? Thanks Regards
Promoted Build Plugin: trigger a promotion remotely
Hi
Is it possible/straightforward to execute a promotion remotely with a
client such as 'curl'?
My promotions are manually triggered and they require for a particular user
to approve it.
I noticed that the URLs used has this format:
http://
jenkins_host/job/job_name/build_number/promotion/promotionProcess/promotion_name/promotionCondition/hudson.plugins.promoted_builds.conditions.ManualCondition/approve
I also noticed that the form data sent is:
json:{: johndoe}
where johndoe is the username that approves it.
So, I have tried this:
curl --user johndoe:johndoepass -X POST -d 'json:{: johndoe}'
http://jenkins_host/job/dummy/30/promotion/promotionProcess/mypromotion/promotionCondition/hudson.plugins.promoted_builds.conditions.ManualCondition/approve
but I get an Error 400: Exception: This page expects a form submission
Has anyone done this before?
Thanks.
Regards.
Re: promotion config.xml url
It doesn't. Last time I checked (a few weeks ago) there was still no way of getting this info. There's a feature request open for this and for more complete remote handling of promotions. On Fri, Aug 24, 2012 at 1:39 PM, AnthonyJ anthony.jeff...@cox.net wrote: we need help figuring out the url to the promotion config.xml This works for a job: http://SERVER/job/JOBNAME/config.xmlhttp://bcg-jenkins/job/FLO-fork-bronze-init/config.xml But this does not work for a promotion config? http://http://bcg-jenkins/job/FLO-fork-bronze-init/promotion/CompareApproved/config.xml SERVER http://bcg-jenkins/job/FLO-fork-bronze-init/config.xml/job/http://bcg-jenkins/job/FLO-fork-bronze-init/promotion/CompareApproved/config.xml JOBNAME http://bcg-jenkins/job/FLO-fork-bronze-init/config.xml /promotion/PROMOTIONNAME/config.xmlhttp://bcg-jenkins/job/FLO-fork-bronze-init/promotion/CompareApproved/config.xml
Envinject Plugin: Resolve environment variables on properties file path
Hi It would be useful if we could use environment variables when specifying the Properties File Path. When doing a promotion, I am currently trying to load a properties file that exists in the archived artifacts of that build. So, I used: ../builds/$BUILD_NUMBER/archive/my.properties Unfortunately, the Envinject plugin does not seem to be resolving the BUILD_NUMBER variable. Is this correct? Any ideas? Thanks. Regards
Re: Envinject Plugin: Resolve environment variables on properties file path
Looks like it does pick environment variables, but the BUILD_NUMBER being picked is the one that corresponds to the promotion #. Is there a way of obtaining the number of the build being promoted? On Wed, Jun 27, 2012 at 2:32 PM, Nicky Ramone nixe...@gmail.com wrote: Hi It would be useful if we could use environment variables when specifying the Properties File Path. When doing a promotion, I am currently trying to load a properties file that exists in the archived artifacts of that build. So, I used: ../builds/$BUILD_NUMBER/archive/my.properties Unfortunately, the Envinject plugin does not seem to be resolving the BUILD_NUMBER variable. Is this correct? Any ideas? Thanks. Regards
Re: Envinject Plugin: Resolve environment variables on properties file path
Thank you, Chris. PROMOTED_NUMBER is the variable I'm looking for, but the Envinject plugin is not resolving it. On Wed, Jun 27, 2012 at 3:32 PM, cjo cjo.john...@gmail.com wrote: The behaviour is correct the default env variables that the promotion job sees are the one for its own runs (as it a job/project in itself). However it provides a different set of env variables, so that you can get at job being promoted, these are PROMOTED_URL - URL of the job being promoted ex: http://jenkins/job/job_name_being_promoted/77/ PROMOTED_JOB_NAME - Promoted job name ex: job_name_being_promoted PROMOTED_NUMBER - Build number of the promoted job ex: 77 PROMOTED_ID - ID of the build being promoted ex: 2012-04-12_17-13-03 As copied from the wiki page https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin Chris On Wednesday, June 27, 2012 7:08:43 PM UTC+1, Nicky Ramone wrote: It still behaves strangely. It doesn't seem to resolve variables. On Wed, Jun 27, 2012 at 2:45 PM, Nicky Ramone nixe...@gmail.com wrote: Looks like it does pick environment variables, but the BUILD_NUMBER being picked is the one that corresponds to the promotion #. Is there a way of obtaining the number of the build being promoted? On Wed, Jun 27, 2012 at 2:32 PM, Nicky Ramone nixe...@gmail.com wrote: Hi It would be useful if we could use environment variables when specifying the Properties File Path. When doing a promotion, I am currently trying to load a properties file that exists in the archived artifacts of that build. So, I used: ../builds/$BUILD_NUMBER/**archive/my.properties Unfortunately, the Envinject plugin does not seem to be resolving the BUILD_NUMBER variable. Is this correct? Any ideas? Thanks. Regards
Which container to use for Jenkins on production?
Hi We have been using Tomcat for some time now to deploy Jenkins. We will probably put this behind an Apache Httpd so that we can redirect from a URL with no port. Example: We would forward http://jenkins.ourinstance.com/ to http://jenkins.ourinstance.com:8080/jenkins I was wondering if there are other suggestions for the deployment. The instructions seems to use the embedded Winstone that comes with Jenkins. What other deployment schemes do you have/suggest, especially for port redirect? Thanks. Regards.
Re: Which container to use for Jenkins on production?
Thank you, Les. On Mon, Jun 18, 2012 at 2:00 PM, Les Mikesell lesmikes...@gmail.com wrote: On Mon, Jun 18, 2012 at 8:34 AM, Nicky Ramone nixe...@gmail.com wrote: We have been using Tomcat for some time now to deploy Jenkins. We will probably put this behind an Apache Httpd so that we can redirect from a URL with no port. Example: We would forward http://jenkins.ourinstance.com/ to http://jenkins.ourinstance.com:8080/jenkins I was wondering if there are other suggestions for the deployment. The instructions seems to use the embedded Winstone that comes with Jenkins. What other deployment schemes do you have/suggest, especially for port redirect? I think it works nicely with winstone and the apache ajp proxy. I have other things being proxied by the same apache front end so I set both the jenkins url path and the ajp port for jenkins. With the RHEL/Centos rpm package you can do this in /etc/sysconfig/jenkins with a line like: JENKINS_ARGS=--prefix=/jenkins --ajp13Port=8010 and then add this to /etc/httpd/conf.d/proxy_ajp.conf: ProxyPass /jenkins/ ajp://localhost:8010/jenkins/ Other distos may put the config changes in different places. Also, I made an empty directory /var/www/html/jenkins as a quick fix so the default apache settings would send a redirect if you omit the trailing slash on /jenkins/. There is probably a cleaner way to accomplish that... -- Les Mikesell lesmikes...@gmail.com
Promoted Builds Plugin: Manual approval throws exception
Hi I'm trying a very basic configuration where I want to promote the build manually and trigger a downstream job. When I go to Promotion Status and click on Approve I get an IllegalArgumentException with not much detail. Status Code: 500Exception: java.lang.IllegalArgumentException: dummy-project Stacktrace: javax.servlet.ServletException: java.lang.IllegalArgumentException: webmail-control-panel at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) 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) ... ... Does this happen to anyone else? I'm using the latest version of the plugin as well as the latest version of Jenkins (1.470), but the same happens with previous versions of Jenkins. Thanks.
Memory dump at startup
Hi I just upgraded to Jenkins 1.470 and since then I haven't been able to start it up. I tried downgrading again but now I get the same errors with the previous version that worked. I don't know if somehow my data could have got corrupted. This is where the error starts on the log: ... ... INFO: Started all plugins Jun 14, 2012 4:44:59 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions *** glibc detected *** /opt/jdk/1.6.0_16/bin/java: free(): invalid pointer: 0x09b9b070 *** === Backtrace: = /lib/libc.so.6[0xc7c0f1] /lib/libc.so.6(cfree+0x90)[0xc7fbc0] /lib/libglib-2.0.so.0(g_free+0x31)[0x82a481] /usr/lib/libgconf-2.so.4(gconf_activate_server+0xce)[0x9f018a4e] /usr/lib/libgconf-2.so.4[0x9f024e82] /usr/lib/libgconf-2.so.4[0x9f025c0b] /usr/lib/libgconf-2.so.4[0x9f025e5e] /usr/lib/libgconf-2.so.4(gconf_engine_get_fuller+0x1b9)[0x9f0280f9] /usr/lib/libgconf-2.so.4(gconf_engine_get_entry+0x7e)[0x9f0283ce] /usr/lib/libgconf-2.so.4[0x9f02c617] /usr/lib/libgconf-2.so.4[0x9f02c89e] /usr/lib/libgconf-2.so.4(gconf_client_get_bool+0x4f)[0x9f02d21f] /opt/jdk/1.6.0_16/jre/lib/i386/libnet.so(Java_sun_net_spi_DefaultProxySelector_getSystemProxy+0x6db)[0xa28ab8db] [0xf432e4aa] [0xf4326f27] [0xf4326f27] [0xf432434c] /opt/jdk/1.6.0_16/jre/lib/i386/server/libjvm.so[0xf7749a20] /opt/jdk/1.6.0_16/jre/lib/i386/server/libjvm.so[0xf790d828] /opt/jdk/1.6.0_16/jre/lib/i386/server/libjvm.so[0xf774987f] /opt/jdk/1.6.0_16/jre/lib/i386/server/libjvm.so(JVM_DoPrivileged+0x396)[0xf77aa6c6] /opt/jdk/1.6.0_16/jre/lib/i386/libjava.so(Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2+0x3d)[0xf737196d] [0xf43b72d5] [0xf4326f27] [0xf4326f27] [0xf4326f27] [0xf4327403] [0xf4326f27] ... ... Has anyone come across such errors? Thanks in advance.
Re: Promoted Builds Plugin: Does not automatically promote despite qualifications being met
It looks like a weird bug. It happens on one set of jobs but not on another one I have. Another problem I'm having is that when you manually promote a build that triggers a downstream build, the triggered downstream build does not include information from the upstream project, which is a big problem. On Thu, Apr 12, 2012 at 4:05 AM, Taubert, Helge t...@zuehlke.com wrote: Hi! ** ** We have a similar issue for some versions back now. We get the following warning: ** ** ** ** WARNING: Job_A appears to use this job as a promotion criteria, but no fingerprint is recorded. Fingerprint needs to be enabled on both this job and Job_A ** ** If you check the fingerprints manually, everything is fine, but the promotion does not work. It worked one and a half year ago. Then there were some race condition which made it fail sometimes. These were fixed and it worked for a while. Then it stopped working at all. ** ** It would be nice to have this feature working again. ** ** Greetings, ** ** Helge ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Nicky Ramone *Sent:* Mittwoch, 11. April 2012 18:31 *To:* jenkinsci-users@googlegroups.com *Subject:* Promoted Builds Plugin: Does not automatically promote despite qualifications being met ** ** Hello. ** ** I have the following build sequence with Maven jobs: A -- B -- C and I want to promote A when C has finished successfully. I am tracking fingerprints of the same artifact in all 3 jobs, and I verify that they are correct. ** ** When C finishes, the Promotion Status looks fine with met qualifications: ** ** Promotions my_promotion [Force promotion] This promotion has not happened. Met Qualification *Downstream builds succeeded* C #8 http://localhost:8080/job/C/8/ Unmet Qualification ** ** Despite that, the promotion never occurs (you can see the label This promotion has not happened). I found a couple of threads/issues that seem to be pointing to the same problem, but no solution available: http://jenkins.361315.n4.nabble.com/Promotion-is-not-working-td3643188.html https://issues.jenkins-ci.org/browse/JENKINS-10199 ** ** I'm using Jenkins 1.455 and Promoted Builds Plugin 2.4 Has anyone else come across this issue? ** ** Thanks Cheers. ** **
Promoted Builds Plugin: Does not automatically promote despite qualifications being met
Hello. I have the following build sequence with Maven jobs: A -- B -- C and I want to promote A when C has finished successfully. I am tracking fingerprints of the same artifact in all 3 jobs, and I verify that they are correct. When C finishes, the Promotion Status looks fine with met qualifications: Promotions my_promotion This promotion has not happened. Met Qualification Downstream builds succeededC #8http://localhost:8080/job/C/8/Unmet Qualification Despite that, the promotion never occurs (you can see the label This promotion has not happened). I found a couple of threads/issues that seem to be pointing to the same problem, but no solution available: http://jenkins.361315.n4.nabble.com/Promotion-is-not-working-td3643188.html https://issues.jenkins-ci.org/browse/JENKINS-10199 I'm using Jenkins 1.455 and Promoted Builds Plugin 2.4 Has anyone else come across this issue? Thanks Cheers.
Re: Build Pipeline view issues
Chris, you are right. The integration between the Build Pipeline plugin and the Promoted Builds plugin does not exist. Somewhere I read that this is a desired feature and it may come in the future. On Wed, Feb 8, 2012 at 6:18 AM, Chris Withers ch...@simplistix.co.ukwrote: Hi All, I'm having trouble with this build pipeline: http://jenkins.simplistix.co.**uk/view/testfixtures/http://jenkins.simplistix.co.uk/view/testfixtures/ So, what I want is: - testfixtures-buildout (the initial job) - testfixtures-tox and testfixtures-docs are downstream jobs that run if -buildout succeeds (this bit is working) - If all the above succeeds, testfixtures-release needs to be manually triggered (this works), preferably from the pipeline view (this doesn't) So, firstly, I use the build promotion plugin, with a manual approve step in testfixtures-buildout to trigger testfixtures-release. This is actually working; I thought it wasn't, but it's just the build promotion UI isn't that intuitive... However, it doesn't seem like the pipeline view plugin looks at the promotion plugin's config at all. Have I got that right? If so, it would be great if it could look at the promotion plugin config, see there's a manual step, and add a button where appropriate. Don't suppose the Centrum guys are working on that? So, in the absence of that, I configured a Build Pipeline Plugin - Manually Execute Downstream Project of testfixtures-release on testfixtures buildout. I think this has worked, but produces a weird layout on http://jenkins.simplistix.co.**uk/view/testfixtures/http://jenkins.simplistix.co.uk/view/testfixtures/ How can I get testfixtures-release to show up in a 4th column to the right of testfixures-docs rather than in the 3rd column below testfixtures-docs? cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk
Re: copy artifacts - pick from two upstream jobs
Nevermind, I found it. On Thu, Mar 22, 2012 at 11:17 AM, Nicky Ramone nixe...@gmail.com wrote: Where is that Upstream build that triggered this job-functionality of the Copy-Artifacts-Plugin ? On Tue, Feb 21, 2012 at 12:23 PM, Fred G fred.g...@googlemail.com wrote: Hi Chris, You can use the Upstream build that triggered this job-functionality of the Copy-Artifacts-Plugin. Unfortunately you still need to specify the name of the triggering job. I will try to fix this in an upcoming version. Until then you need to specify two Copy artifacts from another project build steps (one for each triggering project) and mark them as optional. Hth, Fred
Build Pipeline Plugin: Not possible to rebuild?
Hi It looks like that plugin does not allow you to rebuild a specific stage of the pipeline after it has succeeded. The downside of this is that if, for example, you had a stage for deploying, you wouldn't be able to redeploy if needed. Has anyone else found this to be an inconvenient? Cheers.
Re: Groovy Plugin: Obtain upstream builds?
Yeah, this is how I'm doing it right now (don't know if there's a better way to do it): build = Thread.currentThread().executable upstreamBuilds = build.getUpstreamBuilds() The problem is that it's not easy to determine which upstream build triggered the current build. On Tue, Mar 20, 2012 at 5:51 PM, Andrew Bayer andrew.ba...@gmail.comwrote: I think you'd have to use the system groovy build step to do this, but it should be possible there. A. On Tue, Mar 20, 2012 at 10:08 AM, Nicky Ramone nixe...@gmail.com wrote: Hi. Is it possible to obtain the upstream build objects in a groovy script executed by the Groovy Plugin? You can do this in the Groovy Post Build Plugin with: manager.build.getUpstreamBuilds() Is there a similar way of doing it? Thanks Regards.
Re: Build Pipeline Plugin: does not correctly define the upstream build?
To be more clear, here you can see the build page. Notice how the text Start by upstream project... differs from the Upstream Builds ? Build #92 (Mar 21, 2012 11:40:57 AM) add descriptionhttp://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/91/editDescription Revision: 38 No changes. Started by upstream project foo-1.0 http://localhost:8080/job/foo-1.0/ build number 11 http://localhost:8080/job/foo-1.0/11/ Upstream Builds - foo-1.0 http://localhost:8080/job/foo-1.0/[image: Success]#14http://localhost:8080/job/foo-1.0/14/ On Wed, Mar 21, 2012 at 11:58 AM, Nicky Ramone nixe...@gmail.com wrote: Hello. I created a simple pipeline. I noticed that it seems to be doing something wrong for a build that is not the last one. Take this pipeline view, for instance: foo-1.0 http://localhost:8080/view/foo_pipeline/job/foo-1.0/ foo-deploy-qahttp://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/ Svn: 37 http://localhost:8080/view/foo_pipeline/# foo-1.0 #14 http://localhost:8080/view/foo_pipeline/job/foo-1.0/14/ Mar 20, 2012 4:50:51 PM ART Duration: 35 sec foo-deploy-qa #47 http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/47/ Mar 20, 2012 4:51:32 PM ART Duration: 5.8 sec Svn: 37 http://localhost:8080/view/foo_pipeline/# foo-1.0 #13 http://localhost:8080/view/foo_pipeline/job/foo-1.0/13/ Mar 20, 2012 12:30:41 PM ART Duration: 25 sec foo-deploy-qa #90 http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/90/ Mar 21, 2012 11:38:26 AM ART Duration: 4.5 sec Svn: 35 http://localhost:8080/view/foo_pipeline/# foo-1.0 #12 http://localhost:8080/view/foo_pipeline/job/foo-1.0/12/ Mar 20, 2012 12:02:30 PM ART Duration: 35 sec foo-deploy-qa #91 http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/91/ Mar 21, 2012 11:40:57 AM ART Duration: 4.6 sec Svn: 35 http://localhost:8080/view/foo_pipeline/# foo-1.0 #11 http://localhost:8080/view/foo_pipeline/job/foo-1.0/11/ Mar 20, 2012 12:01:08 PM ART Duration: 22 sec Pending build of project: foo-deploy-qa Trigger If I decide to trigger the foo-deploy-qa build on the bottom (the one that's pending), I would expect the upstream build for it to be foo-1.0#11. However, this doesn't seem to happen. I created a simple system script with the Groovy Plugin to show the upstream build: build = Thread.currentThread().executable upstreamBuilds = build.getUpstreamBuilds() println upstream builds: + upstreamBuilds So, after the build is run, I can see this in the console: upstream builds: [hudson.maven.MavenModuleSet@680525[foo-1.0]:14] As you can see, it always returns the last upstream build (foo-1.0#14 in this case), not the one that corresponds to that pipeline (foo-1.0#11 in this case). Has anyone come across this problem too? Thanks. Cheers.
Groovy Plugin: Obtain upstream builds?
Hi. Is it possible to obtain the upstream build objects in a groovy script executed by the Groovy Plugin? You can do this in the Groovy Post Build Plugin with: manager.build.getUpstreamBuilds() Is there a similar way of doing it? Thanks Regards.
Re: Pipeline Plugin: Use compiled artifact from previous stage
Thanks both. I think that could work. There a few other problems with pipelines and Maven. I will probably open another thread for this. Regards. On Wed, Mar 14, 2012 at 10:25 PM, Pete peteha...@gmail.com wrote: We do this but do not rely on the repository manager to pull down the artifact. We configure the Maven Jenkins build job to archive the artifact and then in the downstream job we configure a run parameter and execute a shell using the passed run url to download the artifact. On Wed, Mar 14, 2012 at 4:33 PM, Nigel Magnay nigel.mag...@gmail.com wrote: Hard to tell without some more detail -- wouldn't the jar name be the same each time anyway? You can probably craft something with a combination of copy-artifacts plugin, maven repository server plugin and possibly a groovy script.. On Wed, Mar 14, 2012 at 7:05 PM, Nicky Ramone nixe...@gmail.com wrote: Did anyone get a chance to read this? On Tue, Mar 13, 2012 at 2:44 PM, Nicky Ramone nixe...@gmail.com wrote: Hi Suppose I build a Java project with Maven and a two-stage pipeline: Stage 1: Packaging and unit-testing (here the jar is built and deployed into the repository manager) Stage 2: Deploy to QA (here the jar is grabbed from the repository manager and placed in the QA server) How can I know which artifact name and version to grab at Stage 2? Thank you. Cheers.
Re: Pipeline Plugin: Use compiled artifact from previous stage
Actually, even though grabbing the artifact from the Maven repository seems like a good idea, I think it's more coherent that you use the artifact from the upstream job in order to guarantee that the artifact is the one being processed at the current pipeline. Another build might be run in the middle, or someone could deploy to the repository the artifact in the middle of the process, and then you would be picking an artifact not produced by the pipeline. So, for consistency it's best to always use data and artifacts produced by the pipeline itself. On Thu, Mar 15, 2012 at 10:12 PM, Jeff predato...@gmail.com wrote: If archiving allows referencing an artifact with a url, why not use the Maven repository URL for the artifact? And as to JAR naming (reponding to a previous post ), maven builds jars with the version and optional SNAPSHOT tag, which is the way it should be in my opinion...because I really dislike dredging through a whole pile of jars trying to figure out what version is being used because every version is named the same. On Mar 15, 2012 11:53 AM, Nicky Ramone nixe...@gmail.com wrote: Thanks both. I think that could work. There a few other problems with pipelines and Maven. I will probably open another thread for this. Regards. On Wed, Mar 14, 2012 at 10:25 PM, Pete peteha...@gmail.com wrote: We do this but do not rely on the repository manager to pull down the artifact. We configure the Maven Jenkins build job to archive the artifact and then in the downstream job we configure a run parameter and execute a shell using the passed run url to download the artifact. On Wed, Mar 14, 2012 at 4:33 PM, Nigel Magnay nigel.mag...@gmail.com wrote: Hard to tell without some more detail -- wouldn't the jar name be the same each time anyway? You can probably craft something with a combination of copy-artifacts plugin, maven repository server plugin and possibly a groovy script.. On Wed, Mar 14, 2012 at 7:05 PM, Nicky Ramone nixe...@gmail.com wrote: Did anyone get a chance to read this? On Tue, Mar 13, 2012 at 2:44 PM, Nicky Ramone nixe...@gmail.com wrote: Hi Suppose I build a Java project with Maven and a two-stage pipeline: Stage 1: Packaging and unit-testing (here the jar is built and deployed into the repository manager) Stage 2: Deploy to QA (here the jar is grabbed from the repository manager and placed in the QA server) How can I know which artifact name and version to grab at Stage 2? Thank you. Cheers.
Re: View - make available to all users
Try the following: Log in with admin privileges. The last tab available in the view will be named +. Click on that tab to create a new shared view. Cheers. On Tue, Mar 13, 2012 at 12:58 PM, MartinD martin.dick...@snapon.com wrote: I've been trying to create some views that will be available to all users, including anonymous visitors. But I can't find any way to make a view public.Can anyone tell me what I'm missing? We're using version 1.455, with Matrix-based security, using Jenkins's own user database. I'm logged in as a user with full permission to do anything. I can create a view, but the Edit View page doesn't have any option to make it public, and I haven't found anything under Manage Jenkins | Configure System either.
Pipeline Plugin: Use compiled artifact from previous stage
Hi Suppose I build a Java project with Maven and a two-stage pipeline: Stage 1: Packaging and unit-testing (here the jar is built and deployed into the repository manager) Stage 2: Deploy to QA (here the jar is grabbed from the repository manager and placed in the QA server) How can I know which artifact name and version to grab at Stage 2? Thank you. Cheers.
Re: Cannot build any jobs: Pending - Waiting for next available executor
That seems to be a different problem. I haven't defined any quiet periods, and I'm only trying to run one single build right now. The job never starts. On Wed, Mar 7, 2012 at 10:41 AM, matthew.web...@diamond.ac.uk wrote: This is probably https://issues.jenkins-ci.org/browse/JENKINS-12994 - vote for that ticket if it is a problem for you (and/or add a note to the ticket indicating that you are also experiencing it) ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Nicky Ramone *Sent:* 07 March 2012 13:34 *To:* jenkinsci-users@googlegroups.com *Subject:* Cannot build any jobs: Pending - Waiting for next available executor ** ** Hi ** ** Since several days I'm unable to build anything and I can't understand what's wrong. Jenkins keeps waiting for an available executor but never starts: ** ** The server has enough free space and memory. I tried restarting Jenkins, upgrading to the latest version (now I'm on 1.454), restarting the job, but still nothing. I also looked at the catalina.out logs but found nothing related to that.* *** ** ** Maybe someone can give me a hint, please? Thanks in advance. -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Re: Cannot build any jobs: Pending - Waiting for next available executor
This is an install that has been there for a long time. The # of executors is 0. Does that mean it's unlimited? On Wed, Mar 7, 2012 at 10:53 AM, Slide slide.o@gmail.com wrote: Is this a new install of Jenkins? Or one that's been up for a while? How many executors do you have defined in the global config? On Mar 7, 2012 6:49 AM, Nicky Ramone nixe...@gmail.com wrote: That seems to be a different problem. I haven't defined any quiet periods, and I'm only trying to run one single build right now. The job never starts. On Wed, Mar 7, 2012 at 10:41 AM, matthew.web...@diamond.ac.uk wrote: This is probably https://issues.jenkins-ci.org/browse/JENKINS-12994 - vote for that ticket if it is a problem for you (and/or add a note to the ticket indicating that you are also experiencing it) ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Nicky Ramone *Sent:* 07 March 2012 13:34 *To:* jenkinsci-users@googlegroups.com *Subject:* Cannot build any jobs: Pending - Waiting for next available executor ** ** Hi ** ** Since several days I'm unable to build anything and I can't understand what's wrong. Jenkins keeps waiting for an available executor but never starts: ** ** The server has enough free space and memory. I tried restarting Jenkins, upgrading to the latest version (now I'm on 1.454), restarting the job, but still nothing. I also looked at the catalina.out logs but found nothing related to that. ** ** Maybe someone can give me a hint, please? Thanks in advance. -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Re: Cannot build any jobs: Pending - Waiting for next available executor
Thanks! that worked. It's building now. I don't know how it got to the value 0. Do you have any tips for how to choose that number? I don't have any slaves right now. On Wed, Mar 7, 2012 at 11:00 AM, Slide slide.o@gmail.com wrote: Try changing to 1. On Mar 7, 2012 6:57 AM, Nicky Ramone nixe...@gmail.com wrote: This is an install that has been there for a long time. The # of executors is 0. Does that mean it's unlimited? On Wed, Mar 7, 2012 at 10:53 AM, Slide slide.o@gmail.com wrote: Is this a new install of Jenkins? Or one that's been up for a while? How many executors do you have defined in the global config? On Mar 7, 2012 6:49 AM, Nicky Ramone nixe...@gmail.com wrote: That seems to be a different problem. I haven't defined any quiet periods, and I'm only trying to run one single build right now. The job never starts. On Wed, Mar 7, 2012 at 10:41 AM, matthew.web...@diamond.ac.uk wrote: This is probably https://issues.jenkins-ci.org/browse/JENKINS-12994 - vote for that ticket if it is a problem for you (and/or add a note to the ticket indicating that you are also experiencing it) ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Nicky Ramone *Sent:* 07 March 2012 13:34 *To:* jenkinsci-users@googlegroups.com *Subject:* Cannot build any jobs: Pending - Waiting for next available executor ** ** Hi ** ** Since several days I'm unable to build anything and I can't understand what's wrong. Jenkins keeps waiting for an available executor but never starts: ** ** The server has enough free space and memory. I tried restarting Jenkins, upgrading to the latest version (now I'm on 1.454), restarting the job, but still nothing. I also looked at the catalina.out logs but found nothing related to that. ** ** Maybe someone can give me a hint, please? Thanks in advance. -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Re: Cannot build any jobs: Pending - Waiting for next available executor
Thanks very much for helping. Cheers. On Wed, Mar 7, 2012 at 11:19 AM, Didier Durand durand.did...@gmail.comwrote: Hi, You may want to relate the number of executors to the number of cores on your jenkins server if it is more or less dedicated to Jenkins Soon you will also realize that you need to define priorities to sort out jobs in the queue: then this plugin gets useful: http://wiki.hudson-ci.org/display/HUDSON/Priority+Sorter+Plugin regards didier On Mar 7, 3:06 pm, Nicky Ramone nixe...@gmail.com wrote: Thanks! that worked. It's building now. I don't know how it got to the value 0. Do you have any tips for how to choose that number? I don't have any slaves right now. On Wed, Mar 7, 2012 at 11:00 AM, Slide slide.o@gmail.com wrote: Try changing to 1. On Mar 7, 2012 6:57 AM, Nicky Ramone nixe...@gmail.com wrote: This is an install that has been there for a long time. The # of executors is 0. Does that mean it's unlimited? On Wed, Mar 7, 2012 at 10:53 AM, Slide slide.o@gmail.com wrote: Is this a new install of Jenkins? Or one that's been up for a while? How many executors do you have defined in the global config? On Mar 7, 2012 6:49 AM, Nicky Ramone nixe...@gmail.com wrote: That seems to be a different problem. I haven't defined any quiet periods, and I'm only trying to run one single build right now. The job never starts. On Wed, Mar 7, 2012 at 10:41 AM, matthew.web...@diamond.ac.uk wrote: This is probablyhttps:// issues.jenkins-ci.org/browse/JENKINS-12994- vote for that ticket if it is a problem for you (and/or add a note to the ticket indicating that you are also experiencing it) ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Nicky Ramone *Sent:* 07 March 2012 13:34 *To:* jenkinsci-users@googlegroups.com *Subject:* Cannot build any jobs: Pending - Waiting for next available executor ** ** Hi ** ** Since several days I'm unable to build anything and I can't understand what's wrong. Jenkins keeps waiting for an available executor but never starts: ** ** The server has enough free space and memory. I tried restarting Jenkins, upgrading to the latest version (now I'm on 1.454), restarting the job, but still nothing. I also looked at the catalina.out logs but found nothing related to that. ** ** Maybe someone can give me a hint, please? Thanks in advance. -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
