repo down - can't build/release
Hi all, I can't release (or build) as repo.jenkins-ci.org seems dead. https://jenkins.ci.cloudbees.com/job/plugins/job/cucumber-testresult-plugin/23/console Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:1.509 from/to repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/): Failed to transfer file: http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/plugin/1.509/plugin-1.509.pom. Return code is: 500 , ReasonPhrase:Internal Server Error. Failed to transfer Could not find artifact org.jenkins-ci.plugins:plugin:pom:1.509 in central (http://repo.cloudbees.com/content/repositories/central) ERROR: Failed to parse POMs Can someone take a look at artifactory please. /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Best way to back up Jenkins?
Hi Christopher, CloudBees have a commercial backup plugin – and there is a couple of open source equiv (thin backup). I use the CB version – it can scp or write it to the file system – but you could easily have another job that pulled the file in and ran some git commands to push it off site. I would guess the open source equiv would be able to do something similar. http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/backup.html# https://wiki.jenkins-ci.org/display/JENKINS/Backup+Plugin https://wiki.jenkins-ci.org/display/JENKINS/thinBackup /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Christopher Ambler Sent: 10 September 2014 03:47 To: jenkinsci-dev@googlegroups.com Subject: Best way to back up Jenkins? What's the best practice way of backing up a full Jenkins install and config suitable for restoring most easily if a machine is fed to a dragon or our data center were to be hit by a meteor? Is there a plugin that will do a backup, say weekly, to Github? The best developers are lazy. I'm lazy and would like to automate this... -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: workflow issue with dir
Yes - that fixed it.
Thanks Daniel.
-Original Message-
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
d...@googlegroups.com] On Behalf Of Daniel Beck
Sent: 15 August 2014 18:33
To: jenkinsci-dev@googlegroups.com
Subject: Re: workflow issue with dir
From the error message, it seems dir requires a block containing the
commands to run in the specified directory. Try something like
dir ('foobar') {
sh 'pwd'
}
On 15.08.2014, at 19:02, James Nord (jnord) jn...@cisco.com wrote:
Hi all,
There seems to be an issue with the workflow Change Directory step (or
me...)
With the following workflow
node() {
sh 'rm -fr -- *'
sh 'mkdir foobar'
echo 'about to change dir'
dir 'foobar'
echo 'changed dir'
}
I get the following output
Running: Allocate node : Start
Running on master in /opt/jenkins/data/jobs/changedir/workspace
Running: Allocate node : Body : Start
Running: Shell Script
[workspace] $ nohup sh -c
'/opt/jenkins/data/jobs/changedir/workspace/.8e7bf62b/script.sh'
'/opt/jenkins/data/jobs/changedir/workspace/.8e7bf62b/jenkins-log.txt'
21; echo $?
'/opt/jenkins/data/jobs/changedir/workspace/.8e7bf62b/jenkins-result.txt'
+ rm -fr -- '*'
Running: Shell Script
[workspace] $ nohup sh -c
'/opt/jenkins/data/jobs/changedir/workspace/.22ea1fbb/script.sh'
'/opt/jenkins/data/jobs/changedir/workspace/.22ea1fbb/jenkins-log.txt'
21; echo $?
'/opt/jenkins/data/jobs/changedir/workspace/.22ea1fbb/jenkins-result.txt'
+ mkdir foobar
Running: Print Message
about to change dir
Running: Change Directory
Running in /opt/jenkins/data/jobs/changedir/workspace/foobar
Running: Allocate node : Body : End
Running: Allocate node : End
Running: End of Workflow
java.lang.IllegalStateException: There's no body to invoke
at
org.jenkinsci.plugins.workflow.cps.CpsStepContext.invokeBodyLater(CpsSte
pContext.java:226)
at
org.jenkinsci.plugins.workflow.cps.CpsStepContext.invokeBodyLater(CpsSte
pContext.java:217)
at
org.jenkinsci.plugins.workflow.steps.PushdStep$Execution.start(PushdStep.
java:77)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:131)
at
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:7
9)
at
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClass
Site.java:45)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.j
ava:42)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.ja
va:108)
at
com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvo
ker.java:15)
at Script1.run(Script1.groovy:5)
at Unknown.Unknown(Unknown)
at ___cps.transform___(Native Method)
at
com.cloudbees.groovy.cps.impl.ContinuationGroup$1.call(ContinuationGrou
p.java:66)
at
com.cloudbees.groovy.cps.impl.ContinuationGroup$1.call(ContinuationGrou
p.java:62)
at sun.reflect.GeneratedMethodAccessor366.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:
90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1079)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at
org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClass
Site.java:44)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.ja
va:112)
at
com.cloudbees.groovy.cps.CategorySupport$_use_closure1.doCall(Category
Support.groovy:15)
at sun.reflect.GeneratedMethodAccessor365.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:
90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(Cl
osureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoM
etaClassSite.java:66)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCal
lSite.java:141)
at
com.cloudbees.groovy.cps.CategorySupport$_use_closure1.doCall(Category
Support.groovy)
at sun.reflect.GeneratedMethodAccessor364.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:
90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233
workflow issue with dir
Hi all,
There seems to be an issue with the workflow Change Directory step (or me...)
With the following workflow
node() {
sh 'rm -fr -- *'
sh 'mkdir foobar'
echo 'about to change dir'
dir 'foobar'
echo 'changed dir'
}
I get the following output
Running: Allocate node : Start
Running on master in /opt/jenkins/data/jobs/changedir/workspace
Running: Allocate node : Body : Start
Running: Shell Script
[workspace] $ nohup sh -c
'/opt/jenkins/data/jobs/changedir/workspace/.8e7bf62b/script.sh'
'/opt/jenkins/data/jobs/changedir/workspace/.8e7bf62b/jenkins-log.txt' 21;
echo $?
'/opt/jenkins/data/jobs/changedir/workspace/.8e7bf62b/jenkins-result.txt'
+ rm -fr -- '*'
Running: Shell Script
[workspace] $ nohup sh -c
'/opt/jenkins/data/jobs/changedir/workspace/.22ea1fbb/script.sh'
'/opt/jenkins/data/jobs/changedir/workspace/.22ea1fbb/jenkins-log.txt' 21;
echo $?
'/opt/jenkins/data/jobs/changedir/workspace/.22ea1fbb/jenkins-result.txt'
+ mkdir foobar
Running: Print Message
about to change dir
Running: Change Directory
Running in /opt/jenkins/data/jobs/changedir/workspace/foobar
Running: Allocate node : Body : End
Running: Allocate node : End
Running: End of Workflow
java.lang.IllegalStateException: There's no body to invoke
at
org.jenkinsci.plugins.workflow.cps.CpsStepContext.invokeBodyLater(CpsStepContext.java:226)
at
org.jenkinsci.plugins.workflow.cps.CpsStepContext.invokeBodyLater(CpsStepContext.java:217)
at
org.jenkinsci.plugins.workflow.steps.PushdStep$Execution.start(PushdStep.java:77)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:131)
at
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:79)
at
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at
com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15)
at Script1.run(Script1.groovy:5)
at Unknown.Unknown(Unknown)
at ___cps.transform___(Native Method)
at
com.cloudbees.groovy.cps.impl.ContinuationGroup$1.call(ContinuationGroup.java:66)
at
com.cloudbees.groovy.cps.impl.ContinuationGroup$1.call(ContinuationGroup.java:62)
at sun.reflect.GeneratedMethodAccessor366.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1079)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at
org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:44)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at
com.cloudbees.groovy.cps.CategorySupport$_use_closure1.doCall(CategorySupport.groovy:15)
at sun.reflect.GeneratedMethodAccessor365.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at
com.cloudbees.groovy.cps.CategorySupport$_use_closure1.doCall(CategorySupport.groovy)
at sun.reflect.GeneratedMethodAccessor364.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.Closure.call(Closure.java:415)
at groovy.lang.Closure.call(Closure.java:409)
at
org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:106)
at
org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.access$400(GroovyCategorySupport.java:64)
at
org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:246)
at org.codehaus.groovy.runtime.GroovyCategorySupport$use.call(Unknown Source)
at
RE: Require JDK 7 to build?
I blame Stephen for starting us down that path to which others said “me too” I have no problem using JDK7 as the minimum JDK to compile with (I do this already as source and target are set to 1.6 and animal sniffer normally catches my oopses). /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Kohsuke Kawaguchi Sent: 08 August 2014 23:08 To: jenkinsci-dev@googlegroups.com Subject: Re: Require JDK 7 to build? I think you misunderstood the question. We aren't talking about changing what Jenkins users have to run Jenkins with. We are still going to produce class file format 50.0, that runs with Java6 and onward. 2014-08-01 5:44 GMT-07:00 James Nord (jnord) jn...@cisco.commailto:jn...@cisco.com: -1 due to things like the lovely maven integration that would require builds use jdk8 also. (I will pre-empt the toolchains answer as Jenkins does not have a suitable[1] toolchains implementation to run maven with X and compile code with Y). /James [1] which will auto install the JDKs (and or other tools) required for compiling/testing etc, and create a nicely formed toolchains.xml with the actual installed tools location. From: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com] On Behalf Of Nigel Magnay Sent: 01 August 2014 10:16 To: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com Subject: Re: Require JDK 7 to build? (roll on JDK 8 as min runtime) +1 Yes, please. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Require JDK 7 to build?
-1 due to things like the lovely maven integration that would require builds use jdk8 also. (I will pre-empt the toolchains answer as Jenkins does not have a suitable[1] toolchains implementation to run maven with X and compile code with Y). /James [1] which will auto install the JDKs (and or other tools) required for compiling/testing etc, and create a nicely formed toolchains.xml with the actual installed tools location. From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Nigel Magnay Sent: 01 August 2014 10:16 To: jenkinsci-dev@googlegroups.com Subject: Re: Require JDK 7 to build? (roll on JDK 8 as min runtime) +1 Yes, please. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Jenkins Workflow Summit to go with JUC Bay Area?
Hi Kohsuke et al. I'm defiantly interested in the workflow brainstorming/hacking/discussing etc. assuming I get travel approval. Having something focused is easier to get approved rather than a generic unconference. /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi Sent: 30 July 2014 22:31 To: Jenkins Dev; eve...@lists.jenkins-ci.org Subject: Jenkins Workflow Summit to go with JUC Bay Area? Some of you were in the Jenkins Scalability Summit last year [1,2,3]. I'm trying to see if we can do a similar one this year back to back with JUC Bay Area. To recap, the idea of the scalability summit was to have a small number of serious active users/developers in the room, to deep dive into Jenkins. The last year the event was themed around scalability and was run in part like an unconference, where the attendees have collectively decided on the agenda for the day. We could keep the same theme this year, but someone suggested to me that since workflow is a big focus this year, maybe that could be the theme. I can easily picture Jesse and I presenting technical details of various parts of the workflow plugin, people sharing and collecting real-world use cases, brainstorming around enhancements / roadmap, maybe even a workshop of getting extensions implemented. Is something like this interesting for you? Is it worth doing? (Another suggestion was to just turn it into a full-blown unconference. Namely, don't have any particular theme, and allow anyone who wants to come to come. We'll just let attendees dictate the topics. The only problem I have with this is that we need a lot bigger venue, which is hard to come by, so unless somebody local in the bay area shows up and sponsors a suitable venue, I don't think this is happening.) [1] https://wiki.jenkins- ci.org/display/JENKINS/Jenkins+Scalability+Summit+2013 [2] http://jenkins-ci.org/content/jenkins-scalability-summit-recap [3] https://docs.google.com/document/d/1GqkWPnp- bvuObGlSe7t3k76ZOD2a8Z2M1avggWoYKEs/edit -- Kohsuke Kawaguchi http://kohsuke.org/ -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: 1.565.1 LTS RC testing started
I have observed a slower startup time in this when compared to 1.532.3 There's more churn in the GC and indeed the full gc time is up from .2s to 2s from startup to display the jenkinsURL/ page with all jobs/folders/health reported. -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of oliver gondža Sent: 14 July 2014 13:07 To: jenkinsci-dev@googlegroups.com Subject: Fwd: 1.565.1 LTS RC testing started --- Forwarded message --- From: oliver gondža ogon...@gmail.com To: jenkinsci-us...@googlegroups.com jenkinsci- us...@googlegroups.com Cc: Subject: 1.565.1 LTS RC testing started Date: Mon, 14 Jul 2014 13:14:10 +0200 Hello everyone, Latest RC was made public last Wednesday. Join us testing what will become next LTS release! We have 10 days to make sure that all the fixes[1] are in place and no new regressions was introduced. Report your findings in this thread or in the test plan wiki. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war Check community maintained LTS test plan https://wiki.jenkins- ci.org/display/JENKINS/LTS+1.565.x+RC+Testing [1] https://issues.jenkins- ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+1017 2+AND+labels+%3D+%221.565.1-fixed%22 Thank you -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: 1.565.1 LTS RC testing started
when upgrading plugins if I deselect Restart Jenkins when installation is complete and no jobs are running then it automatically reselects itself. /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of James Nord (jnord) Sent: 15 July 2014 19:01 To: jenkinsci-dev@googlegroups.com Subject: RE: 1.565.1 LTS RC testing started I have observed a slower startup time in this when compared to 1.532.3 There's more churn in the GC and indeed the full gc time is up from .2s to 2s from startup to display the jenkinsURL/ page with all jobs/folders/health reported. -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of oliver gondža Sent: 14 July 2014 13:07 To: jenkinsci-dev@googlegroups.com Subject: Fwd: 1.565.1 LTS RC testing started --- Forwarded message --- From: oliver gondža ogon...@gmail.com To: jenkinsci-us...@googlegroups.com jenkinsci- us...@googlegroups.com Cc: Subject: 1.565.1 LTS RC testing started Date: Mon, 14 Jul 2014 13:14:10 +0200 Hello everyone, Latest RC was made public last Wednesday. Join us testing what will become next LTS release! We have 10 days to make sure that all the fixes[1] are in place and no new regressions was introduced. Report your findings in this thread or in the test plan wiki. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war Check community maintained LTS test plan https://wiki.jenkins- ci.org/display/JENKINS/LTS+1.565.x+RC+Testing [1] https://issues.jenkins- ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+1017 2+AND+labels+%3D+%221.565.1-fixed%22 Thank you -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: 1.565.1 LTS RC testing started
Cancelling a shutdown via the ui results in this requires a post try posting Hitting the post results in Problem accessing /cancelQuietDown. Reason: No valid crumb was included in the request -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of James Nord (jnord) Sent: 15 July 2014 19:15 To: jenkinsci-dev@googlegroups.com Subject: RE: 1.565.1 LTS RC testing started when upgrading plugins if I deselect Restart Jenkins when installation is complete and no jobs are running then it automatically reselects itself. /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of James Nord (jnord) Sent: 15 July 2014 19:01 To: jenkinsci-dev@googlegroups.com Subject: RE: 1.565.1 LTS RC testing started I have observed a slower startup time in this when compared to 1.532.3 There's more churn in the GC and indeed the full gc time is up from .2s to 2s from startup to display the jenkinsURL/ page with all jobs/folders/health reported. -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of oliver gondža Sent: 14 July 2014 13:07 To: jenkinsci-dev@googlegroups.com Subject: Fwd: 1.565.1 LTS RC testing started --- Forwarded message --- From: oliver gondža ogon...@gmail.com To: jenkinsci-us...@googlegroups.com jenkinsci- us...@googlegroups.com Cc: Subject: 1.565.1 LTS RC testing started Date: Mon, 14 Jul 2014 13:14:10 +0200 Hello everyone, Latest RC was made public last Wednesday. Join us testing what will become next LTS release! We have 10 days to make sure that all the fixes[1] are in place and no new regressions was introduced. Report your findings in this thread or in the test plan wiki. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war Check community maintained LTS test plan https://wiki.jenkins- ci.org/display/JENKINS/LTS+1.565.x+RC+Testing [1] https://issues.jenkins- ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+1017 2+AND+labels+%3D+%221.565.1-fixed%22 Thank you -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: 1.565.1 LTS RC testing started
On 15.07.2014, at 20:14, James Nord (jnord) jn...@cisco.com wrote: when upgrading plugins if I deselect Restart Jenkins when installation is complete and no jobs are running then it automatically reselects itself. If Jenkins is already in Quiet Down mode (red banner) when you were visiting that page, then this is an old issue (since 1.532 or earlier). JENKINS- 21383 is a bit different but I think they are related. Fair enough if it's an existing issue - had never seen it before on 1.532.3 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
dynamically registering listeneners.
Hi all, How do you *dynamically* register and unregister a listener in a non-deprecated way? e.g. I want to attach a run listener only if some configuration has been set on a plugin (and obviously it needs removing as well as adding if the options changes!) RunListener.register() seems the obvious candidate but this is deprecated with no viable alternative listed when you want to add a listener at runtime. Is the answer it's not deprecated for this use case - or have I missed some other API? (bizarrely enough unregister() is not deprecated) Regards, /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
jenkins-ci.org down
503 Service Unavailable No server is available to handle this request. :( -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: [ANN] Open-sourcing workflow plugin
The James Nord operator :-) /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi Sent: 13 May 2014 23:08 To: jenkinsci-dev@googlegroups.com Subject: [ANN] Open-sourcing workflow plugin Jesse and I have been working on the workflow plugin, and we think it got the point that we can open-source it. We've talked about the workflow plugin several occasions mainly offline. Put simply, it's a new job type where we aim to solve a number of pain points --- such as job sprawl, long-running tasks, jobs that span multiple computers, etc. Slide deck [4] talks a bit more about the motivation and what it aims to solve. And we've talked some more about this in the last Scalability Summit [5]. But we've been spending more time coding than documenting, so if you are interested in this, you'd have to come to Jenkins User Conference [6] where we plan to spend some quality time talking about this plugin. The code is at [1], the issue tracker component is at [2], and if you want to help us hack on this, Jesse and I track our TODOs in [3]. Trello tracks short- term tasks while JIRA should be used for bug reports and nice to have backlogs. This series of plugins are still very much a work in progress, and we don't recommend you to deploy this in your production Jenkins instance just yet. But we've been seeing great interest from users about this feature, and we think this is a nice moment in that we have enough meat to show you what we are trying to do, at the same time things are in flux enough that we can make significant breaking changes based on feedback. To play with this, see readme of [1]. [1] https://github.com/jenkinsci/workflow-plugin [2] https://issues.jenkins-ci.org/browse/JENKINS/component/18820 [3] https://trello.com/b/u2fJQnDX/workflow [4] https://docs.google.com/a/cloudbees.com/presentation/d/1wwqp2x4kwZk etpoLzrn85IUOULmj9zFtcm1o1XepgbE/edit#slide=id.g2c4c22109_028 [5] https://docs.google.com/document/d/1GqkWPnp- bvuObGlSe7t3k76ZOD2a8Z2M1avggWoYKEs/edit#heading=h.593939myiof9 [6] http://www.cloudbees.com/jenkins/juc-2014 -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: [ANN] Open-sourcing workflow plugin
if you are interested in this, you'd have to come to Jenkins User Conference [6] where we plan to spend some quality time talking about this plugin. According to the agendas this looks like it is only the Boston JUG? Workflow in Jenkins Jesse Glick, CloudBees, Inc. Is there anything planned for berlin that I've missed / has not been announced? /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
buildflow release?
Is it time for another release of buildflow plugin? There have been numerous fixes/improvements/changes since the last release over a year ago[1] The only issue I see is that it has broken backwards compatability due to the removal of the workspace - but if this is the accepted route it would be better to get that out now before too many more people start relying on it... @Nicolas - I'm happy to cut the release if you don't have time. /James [1] https://github.com/jenkinsci/build-flow-plugin/compare/build-flow-plugin-0.10...master -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Increase logging level to debug 2 hour startup
Hi Artur, 100MB/s sustained transfers means very little in the context of Jenkins startup (and depending on your workload on running performance). You need to look at random read io performance (aka read IOPs). I went from 3 hours for a cold startup with 16 * 300GB 10k SAS drives on an internal RAID with 1GB flash cache memory to 3 minutes with a single Samsung 840 SSDs (which is now a RAID 1 pair of these drives) . (Warm startup - service jenkins restart - went from 2 hours to 2 minutes...) The sustained transfer of both setups is in a similar ballpark- the random IO reads puts the SSDs in a different league. There's still however an issue in that Jenkins may be loading too much data for these job types and plugins. I would suggest a quick benchmark when jenkins is shutdown of finding all config.xml files under job directories in jenkins_inst_dir/data and then loading them into memory (cat filename null) and timing that to see how long it takes (jenkins may well load some more depending on what plugins you have installed). /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Artur Szostak Sent: 25 March 2014 14:34 To: jenkinsci-dev@googlegroups.com Subject: RE: Increase logging level to debug 2 hour startup About 600 matrix jobs and 50 free-style jobs. The matrix jobs typically have about 60 sub jobs. Most jobs are triggered with the Build after other projects are built option to form a dependency tree. I keep only the last 50 builds for most jobs and only the last 10 successful artifacts, simply to save disk space. I would imagine all this is a rather straight forward use case. In case this is asked: The machine my instance is running on has 24 cores, 64GB or RAM and 2TB or RAID disk space that can sustain ~100MB/s transfers. So how does your setup compare that you get a 2 minute start time? At some point I thought it might be coming from a plugin so I even tried to wipe all the plugins and just have the core jenkins 1.532.2 start. Still got about 2 hours. Cheers Artur From: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com [jenkinsci-dev@googlegroups.com] on behalf of Baptiste Mathus [bmat...@batmat.net] Sent: 25 March 2014 13:45 To: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com Subject: RE: Increase logging level to debug 2 hour startup How many jobs do you have? You may have a specific typology which triggers that show startup time. There are many installations out there with many thousands jobs and it doesn't seen this takes that much time,I guess it would have been reported if so. For example, we for one have a 600+ jobs installation, and it takes about 2 minutes to start. Cheers Le 25 mars 2014 13:24, Artur Szostak aszos...@partner.eso.orgmailto:aszos...@partner.eso.org a écrit : filter project type I meant, matrix project type, which apparently allows a custom filter to be specified. So much for lazy loading then. I guess I have no choice but to suffer my 2 hour start up times. This means Jenkins does not scale properly beyond a few hundred jobs. All quite disappointing :-( -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: overriding Project.upstreamProjects
there is no workspace and hence no upstream projects. Not sure what you mean. Upstream/downstream project relationships have nothing to do with workspaces. No workspace -- no artifacts -- no fingerprints. it (and many other things) seem to be based around the assumption of fingerprints Rightly so. Why do you need to fake anything? Just make sure that whatever information is passed from build to build is properly fingerprinted, and the causal relationship will fall out of that automatically. But when you don't directly consume artifacts there is nothing to fingerprint. For example commit build --(triggers)- flow build flow build is // pseudo code // get the latest stable build of project X, project Y and project Z // add them to RunParamters Build(testA, parameters) Parallel( build(testB, parameters), build(testC,parameters)) SO the flow runs multiple tests - and should aggregate these results so you only need to look at the Flow to see the test results - not have to drill into each project. On top of that - there is no point showing all the combined test results if you can't tell in the flow what changed from Run X to Run Y without having to drill into logs, and then search up and around in Jenkins. That is I want to be able to look at the flow build job and see all tests and dependency changes by just looking at the job/flow_build page. Hope that clarifies what I am attempting to achieve. /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
overriding Project.upstreamProjects
Hi all, For the buildflow plugin upstream projects are not recorded - as in reality there is no workspace and hence no upstream projects. But this is not really the case - the flow could be retrieving a run and passing that as a parameter to many sub jobs - so I would like to be able to see the upstream changes (and aggregated results of the tests in the flow) in a single place. Whilst overriding getUpstreamProjects() would be possible - it (and many other things) seem to be based around the assumption of fingerprints, and I'm wondering if there is some fundamental reason why just overriding getUpstream wouldnlt work and if I really need to start faking fingerprint useage so that the main jenkins depenedency graph is in sync. Regards /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Probable class loading issue / conflict between plugins
Anyone? I didn’t expect to have to require a plugin-first classloader unless the conflicting library was in core? Is my use pf persisting 3rd party classes via xStream broken by design (can we only persist internal to the plugin classes?) Is this just a case of requiring shading of the cucumber classes (in which case anyideas how to do this so that old builds don’t break?) /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Peter Hayes Sent: 21 January 2014 16:02 To: jenkinsci-dev@googlegroups.com Subject: Probable class loading issue / conflict between plugins Hi, I am writing a custom plugin to publish cucumber test results to a quality center database for internal reporting needs. To do so, I am using the cucumber-jvm gherkin library to process the test result file as was done in the cucumber-testresult-plugin. My code is working fine and processing the results but when I also installed the cucumber-testresult-plugin on my Jenkins instance and used that, I am seeing this error message when trying to display the test results: Status Code: 500 Exception: Stacktrace: java.lang.ClassCastException: gherkin.formatter.model.Tag cannot be cast to gherkin.formatter.model.Tag at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResult.tally(CucumberTestResult.java:273) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultAction.load(CucumberTestResultAction.java:119) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultAction.getResult(CucumberTestResultAction.java:147) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultAction.getTarget(CucumberTestResultAction.java:174) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:610) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:683) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776) I believe this can happen when there are classloader consistency issues. I looked at the code for the cucumber-testresult-plugin and it is using the XStream2[1] class to load the serialized test results from the disk (in the load method above)[2] and then when it goes to process those results in the tally method[3], it blows up. Is there a potential issue in the way the XStream2 class is handling the classloading? I am running this on Jenkins 1.520 Thanks, Peter [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/XStream2.java [2] https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultAction.java#L111 [3] https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResult.java#L221 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
JIRA down?
Is this expected (I may have missed an announcement or two)? 503: The server is temporarily unable to service your request due to maintenance downtime or capacity problems -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Probable class loading issue / conflict between plugins
Hi Peter, OffTopic Interestingly enough we are planning on pushing results back from the cucumber plugin to another system – so I wonder if there is some commonality that the plugin should expose rather than requiring many plugins parsing the same files. /OffTopic /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Peter Hayes Sent: 21 January 2014 16:02 To: jenkinsci-dev@googlegroups.com Subject: Probable class loading issue / conflict between plugins Hi, I am writing a custom plugin to publish cucumber test results to a quality center database for internal reporting needs. To do so, I am using the cucumber-jvm gherkin library to process the test result file as was done in the cucumber-testresult-plugin. My code is working fine and processing the results but when I also installed the cucumber-testresult-plugin on my Jenkins instance and used that, I am seeing this error message when trying to display the test results: Status Code: 500 Exception: Stacktrace: java.lang.ClassCastException: gherkin.formatter.model.Tag cannot be cast to gherkin.formatter.model.Tag at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResult.tally(CucumberTestResult.java:273) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultAction.load(CucumberTestResultAction.java:119) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultAction.getResult(CucumberTestResultAction.java:147) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultAction.getTarget(CucumberTestResultAction.java:174) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:610) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:683) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776) I believe this can happen when there are classloader consistency issues. I looked at the code for the cucumber-testresult-plugin and it is using the XStream2[1] class to load the serialized test results from the disk (in the load method above)[2] and then when it goes to process those results in the tally method[3], it blows up. Is there a potential issue in the way the XStream2 class is handling the classloading? I am running this on Jenkins 1.520 Thanks, Peter [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/XStream2.java [2] https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultAction.java#L111 [3] https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResult.java#L221 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
WIKI plugin info?
Hi all, For some reason 2 of my plugins have no plugin info in the WIKI? https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Test+Result+Plugin Is this something I've done wrong or is the backed template a little iffy? Regards, /james -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
sorcerer.j-ci.org up2date?
Hi all, Can someone look at http://sorcerer.jenkins-ci.org/ it appears as though the source is out of date wrt the javadocs at http://javadoc.jenkins-ci.orghttp://javadoc.jenkins-ci.org/ e.g. jenkins.model.RunAction2 is not found in sorcerer. /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Job profiler plugin
Obviously such a thing would probably only work for freestyle type builds. Maven2 builds the time is eaten in between every mojo execution so Sum(mojo time) (maven start time - maven end time). There can be a lot of overhead in here... /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Steven Deal Sent: 18 December 2013 19:17 To: jenkinsci-dev@googlegroups.com Subject: Re: Job profiler plugin I did see that... I should try it before I suggest what it can/cannot do. I was hoping for something that could understand the various phases of the build, even at a high level... like post-build or publishing and then calculate the time spent in each phase. I have a build that can run from 26 minutes to just under two hours due to some network issues we are facing. No one really wants to drill into the logs; but, if on the job page there was a graph showing where the time was spent, it might raise the issue. On Wed, Dec 18, 2013 at 2:00 PM, Jesse Glick jgl...@cloudbees.commailto:jgl...@cloudbees.com wrote: On Wed, Dec 18, 2013 at 1:54 PM, Steven Deal stevend...@gmail.commailto:stevend...@gmail.com wrote: I'm wondering if there exist a plugin that might capture the amount of time a job spends in each phase of the build? https://wiki.jenkins-ci.org/display/JENKINS/Timestamper (More of a question for the users' list I guess.) -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/8M4PmFeQVDU/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Beta release of Gerrit Trigger plugin 2.11.0
So I've hand removed those lines from beta2 and the templates are happy. What's not so happy is the Use Rest API - all I get when I enter a username password and try to test is Connection error : peer not authenticated I even tried a user in the Gerrit Administrators group but I still get the same response. The https cert is signed by our internal certificate - but that won't be in the Jenkins java trustsore. Is that a problem - or is it something else? I've tried both the users ldap password and the Gerrit http password. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Mathieu Wang Sent: 12 December 2013 15:19 To: jenkinsci-dev@googlegroups.com Cc: 'Mathieu Wang' Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0 Yes, this variable is not used anywhere, so we can remove the tag safely. On Thursday, December 12, 2013 4:41:15 AM UTC-5, Robert Sandell wrote: Actually the GerritTrigger class is quite explicit in its declaration to Jenkins that it asserts AbstractProject to be the item it is added to. Whatever kind of trickery the template plugin does after that is somewhat beyond its control. On the other hand I did a quick usage search for the trigger variable that is being declared on the line where it blows up and couldn't find any. @Mathew do you think it's safe to remove the j:invokeStatic var=trigger... tag on line 5 in config.jelly? Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications From: jenkin...@googlegroups.comjavascript: [mailto:jenkin...@googlegroups.comjavascript:] On Behalf Of teilo Sent: den 11 december 2013 17:45 To: jenkin...@googlegroups.comjavascript: Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0 sorry trigger happy that should read from an earlier post 2.10.1 release (aka 2.10.2-snapshot) On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote: Not sure this is still the case (as its from an early post but the plugins assumptions about project types appears incorrect and results in the following error javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68: j:arg Can't convert com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4javascript: to class hudson.model.AbstractProject I don't think this is a regression in the Cloudbees templates (although they may have been upgraded at similar times). On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote: Did some fixes in this area and released 2.11-beta-2 Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications From: jenkin...@googlegroups.commailto:jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] On Behalf Of Sandell, Robert Sent: den 9 december 2013 16:48 To: jenkin...@googlegroups.commailto:jenkin...@googlegroups.com Subject: RE: Beta release of Gerrit Trigger plugin 2.11.0 Ah, It's because the server config is retrieved via the serverName field of the trigger and not from the provider of the event. I noticed some other places where I've missed that particular issue. I'll start a 2.11-beta branch to work on these. Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications From: jenkin...@googlegroups.commailto:jenkin...@googlegroups.com [mailto:jen...@googlegroups.com] On Behalf Of Jyrki Puttonen Sent: den 7 december 2013 18:00 To: jenkin...@googlegroups.commailto:jenkin...@googlegroups.com Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0 I found out one problem, using Any Server prevents Jenkins from reporting result to Gerrit. This happens from retriggering, pushing and from the search and trigger -page. Log has following line in every case: Caused by: java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531) At that line, there's PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly() I would guess that getServer return null when Any Server is selected. I'm not sure what should be done when the returned server is null, so I couldn't fix this myself :) On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen jyrk...@gmail.commailto:jyrk...@gmail.com wrote: Hi, I just installed the beta version, and had few problems. 1. Gerrit configuration was lost, and I had to add a new server. 2. Manual triggering from search didn't work. After following steps and testing after everyone it started to work - I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH - Changed server from Any Server to specific one - Touched every field in Project configuration (pattern, branch) Then
RE: [ANN] Buildflow extensions plugin
Hi Domi, Thanks for letting me know, I've update the wiki. 'build-flow-concurrent-extensions' is _currently_ correct. I was going to remove the build-flow prefix as it's pretty obvious that you want a build flow extension but haven't yet done so :) /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Dominik Bartholdi Sent: 04 December 2013 17:38 To: Jenkins Developers Cc: jenkinsci-us...@googlegroups.com Subject: Re: [ANN] Buildflow extensions plugin Hi James, the documentation is already inconstant: there arte two different names mention to register the extension, which one is correct? - extension.'build-flow-concurrent-extensions' or - extension.'concurrent-extensions' regards Domi On 03.12.2013, at 15:02, James Nord (jnord) jn...@cisco.commailto:jn...@cisco.com wrote: Hi all, As per the Jenkins user conference in Palo Alto - I can now officially announce the open sourcing of the build flow extensions pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Extensions+Plugin. This plugin adds an extension to aid in the co-ordinating of the jobs within in a single when the flow is run concurrently and is at different stages. (for more details see these slides or recordinghttp://www.cloudbees.com/jenkins/juc2013/juc2013-palo-alto-abstracts.cb#JamesNord) Currently you will have to build this from source and it requires an unreleased version of thebuildflowhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin. Regards /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Has anyone written a jenkins plugin using groovy?
A large portion of build flow is groovy. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Kyle Boon Sent: 25 October 2013 06:35 To: jenkinsci-dev@googlegroups.com Subject: Has anyone written a jenkins plugin using groovy? Has anyone written a jenkins plugin using groovy? I've seen some very old discussions around it from 2009 or so but nothing newer. Kyle -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
new repos
Hello, Could someone create me two new repositories and JIRA components please https://https://github.com/jenkinsci/buildflow-extensions-plugingithub.com/jenkinsci/buildflow-extensions-pluginhttps://github.com/jenkinsci/buildflow-extensions-plugin https://https://github.com/jenkinsci/cucumber-testresult-plugingithub.com/jenkinsci/cucumber-testresult-pluginhttps://github.com/jenkinsci/cucumber-testresult-plugin Thanks, /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: sortable tables with footers?
Thanks Johsuke, sortbottom did the job.
As for handling tfoot there are a couple of options (I'm not a DOM cross
browser expert so I only have looked at this in Chrome - others may vary - but
thead/tfoot/tbody where introduced in HTML4!)
Option1 - don't use table.rows - just use table.tBodies (which itself can have
multiple tbody - so you would need to aggregate table.tBodies[0..n].rows[0..m]
(may loose backwards compatability here - but could always fall back?)
Option2 - table.tFoot.rows (similar can then be done for table.tHead.rows if
you want more than 1 row as a header...) then remove any of the rows present
when looking at table.rows
/James
-Original Message-
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi
Sent: 08 October 2013 19:56
To: jenkinsci-dev@googlegroups.com
Subject: Re: sortable tables with footers?
This should be in UI samples, but if the row has the class name sortbottom,
it'll always stick to the bottom. Similar effect for sorttop.
Handling tfoot is a great idea. How does one check if a row is in tfoot? We
can then change the refresh function accordingly.
On 10/08/2013 10:22 AM, teilo wrote:
HI all,
Is it possible to generate a sortable table that has a footer as well as a
header?
I had a quick look at the source and it appears the sorter code treats all
rows
apart from the first as sortable but wondered if there was any tricks to get
this working?
I've tried putting the footer in a tfoot but that doesnkt work in IE or
chrome :-(
example of what I am trying to do
table class=pane sortable id=mytable
thead
tr
td class=pane-headerHeader1/td
td class=pane-header style=width:5emHeader1/td
/tr
/thead
tbody
!-- only entries in here should be sortable. --
j:forEach var=p items=${it.someList}
tr
td class=pane data=${p.desc}${p.desc}/td
td class=pane data=${p.value}${p.value}/td
/tr
/j:forEach
/tbody
tfoot
!-- these entries also get sorted but should always be the last
rows
:-( --
tr
td class=pane-headerTotal/td
td class=pane-header${it.totalString}/td
/tr
/tfoot
/table
Thanks in advance.
/James
--
You received this message because you are subscribed to the Google
Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: Build flow plugin: How to copy results from downstream jobs
The problem with a flow is that the flow can be dynamic - so having to specify
the jobs may lead to incorrect jobs being aggregated - or maintinaing duplicate
information.
It also appears to rely upon getDownStreamRelationship that relies on
fingerprints to work unless overridden.
Perhaps this should be moved to the dev list...
/James
From: jenkinsci-us...@googlegroups.com
[mailto:jenkinsci-us...@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 15:52
To: jenkinsci-us...@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs
I don't want to follow this direction, as I know people won't consider the
warning on documentation.
AggregatedTestResultPublisher can be configured with a set of jobs, maybe this
require some tweaks on UI, not sure (sorry, don't have much time to investigate
on this topic today)
2013/8/30 John Russell jjruss...@gmail.commailto:jjruss...@gmail.com
I see the class javadoc for that class but how would I use that to actually
aggregate the junit tests to report in the build-flow plugin?
Is it also possible to discourage people in the documentation and yet leave the
workspace there so its possible?
On Fri, Aug 30, 2013 at 9:22 AM, nicolas de loof
nicolas.del...@gmail.commailto:nicolas.del...@gmail.com wrote:
I indeed removed workspace support especially to discourage such a write some
custom jenkins code using DSL approach.
build-flow is about orchestrating jobs, not creating custom plugins
junit aggregator is using the original location for junit results, and
dynamically aggregating. It doesn't copy to local project.
2013/8/30 John Russell jjruss...@gmail.commailto:jjruss...@gmail.com
Teilo, When did build flow stop having a workspace? I finally got this to work
by archiving all of the junit files from the downstream jobs onto the master,
running build-flow on the master, and directly copying the files from the
archive of the downstream build to build flow and running the junit results
post build step.
So this won't work anymore? If there is no workspace how would any junit result
post build step work?
On Friday, August 30, 2013 4:14:04 AM UTC-4, teilo wrote:
The BuildFlow doesn't use a workspace anymore[1] - so your workaround most
likely won't work as you expect.
I'm not convinced that this is a good thing as like you I would like to show
test results in the main flow job - not have another job that is just aggregate
report.
On Monday, 12 August 2013 20:17:54 UTC+1, John Russell wrote:
Do you guys have any idea how to pull files, specifically test results, from
the jobs started in a build flow up to the build flow job itself so it can be
the one that presents all of the test results?
I presume that if I can copy them from the slaves up to the workspace of the
build flow build that the post build step of processing the test results will
get them all. Any thoughts on how to get those files back to the master?
On Thursday, January 3, 2013 2:30:31 AM UTC-5, Nicolas De loof wrote:
sure, rescue handle whatever happens in gard block, that has no restriction on
nested content
2013/1/3 Patrick van der Velde
petrikva...@gmail.commailto:petrikva...@gmail.com
Thanks for that suggestion. One question about the guard statement. Can it
handle multiple statements? i.e. is the following allowed?
guard {
build(job1)
build(job2)
} rescue {
build(finaljob)
}
or even this
guard {
parallel(
{ build(job1a) },
{ build(job2a) },
)
parallel(
{ build(job1b) },
{ build(job2b) },
)
} rescue {
build(finaljob)
}
My script looks a bit like that last one but when I tried putting a guard
clause around it I got the following error:
ERROR: Failed to run DSL Script
groovy.lang.MissingMethodExceptionhttp://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException:
No signature of method: com.cloudbees.plugins.flow.FlowDelegate.rescue() is
applicable for argument types: (Script1$_run_closure1_closure3) values:
Removing the guard clause made it work. So I'm guessing guard can only handle 1
item?
Thanks
Petrik
On Wed, Jan 2, 2013 at 10:16 PM, nicolas de loof
nicolas...@gmail.commailto:nicolas...@gmail.com wrote:
use gard+rescue so you can execute a post-job even when some jobs are unstable
2013/1/2 Patrick petrikva...@gmail.commailto:petrikva...@gmail.com
Ok I'm going to have to amend this answer. My idea of having a separate job at
the end to gather the results would work if it wasn't for the fact that the
build flow plugin kills the build as soon as one of the jobs fails. That means
I only can get the results if the build works which is not what I want. I want
the results gathering to always take place, even if the all the build jobs
fail. Any way to achieve this?
Thanks
Petrik
On Wednesday, 2 January 2013 11:46:54 UTC+13, Patrick wrote:
Hi
Mmm ok, I guess I could create a separate job to gather all the test
RE: 1.509.3 RC1 posted
Hi Arnaud. I actually agree here - perhaps because we are both using for the majority Maven2/3 job types - a lot of our jobs have tens of modules (some have 100+) and we use nested Folders heavily. I had load times of 2-3 hours - moving from 16*SAS HDD to SSD reduced that to 2-3 minutes - if you have that option (and haven't already taken it) I suggest you take a look. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Arnaud Héritier Sent: 28 August 2013 08:48 To: Jenkinsci-dev@googlegroups.com Subject: Re: 1.509.3 RC1 posted For your info, even with the lazy loading my server takes ~20 min to start. I thing the improvement is really little compared to 1.480 On Wed, Aug 28, 2013 at 9:39 AM, Arnaud Héritier aherit...@gmail.commailto:aherit...@gmail.com wrote: Jesse, here is a first Threads Dump while having a white screen : https://gist.github.com/aheritier/6363143 I think Jenkins is loading various things to display in the UI because I can see in logs that it is doing it's jobs and I have jobs running correctly. On Wed, Aug 28, 2013 at 9:08 AM, Arnaud Héritier aherit...@gmail.commailto:aherit...@gmail.com wrote: Yes I will try to submit thread dumps if I can generate one while the problem occurs. At least it really usable compared to previous 1.509 LTS I have also this error when jenkins is starting : https://gist.github.com/aheritier/6362959 But I see no error while running (all plugins are up-to-date) Cheers On Wed, Aug 28, 2013 at 12:01 AM, Jesse Glick jgl...@cloudbees.commailto:jgl...@cloudbees.com wrote: On Tue, Aug 27, 2013 at 5:50 PM, Arnaud Héritier aherit...@gmail.commailto:aherit...@gmail.com wrote: It seems that sometimes the dashboard takes some time to load Investigate with thread dumps and file as needed; could be lts-candidate for a future LTS release. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Plugin Installation trend not updated on the Jenkins wiki
You are finally writing your Maven+ plugin :-P (I'm probably going to have to drop into stealth mode as well to get the *exciting new stuff* done enough to push out a new set of OSS plugins for Jenkins... Deadlines! ) -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: BuildFlow Plugin licence - Afferro GPL / GPL?
Short term I am working on limiting concurrent execution of jobs in a flow to
prevent exhaustion (there is no point pulling myjob#2 from the queue when
myjob#3 is in the queue as well - think parameterised jobs and build(myjob,
upstream:build; other:fred) ).
Not sure to understand, can you describe with more details ?
Sure, hopefully I can explain this better with an example.
Take an example flow that is triggered by a commit job.
build(level1_smoke, run: upstream)
build(level2_tests, run: upstream)
build(level3_indepthtests, run: upstream)
assuming
a commit build take 10 minutes
level1_smoke build takes 5 minutes
level2_tests build take 20 minutes
level3_indepth build takes 1 hour
(you want to manage the flow with the flow plugin - why wouldn't you)
Given any commit you want to know quickly if the level1_smoke tests fail (or
pass).
As such you need to enable concurrent executions of flow_job
As commits can be hitting the SCM for commit constantly we will have a run of
commit every 10 minutes, without any restrictions (given that the jobs are
parameterised) we will very quickly have lots of entries for the subsequent
jobs.
As we want some quick turnaround (we want to know as soon as possible when a
commit doesn't pass all these tests) we need to enable concurrent exectution of
these level_* jobs.
This will very quicky exhaust a large number of executors.
In reality - you don't care about knowing if every build of commit passes all
the tests.
What you care about is knowing that when level3_indepth tests have run against
a particular commit build that all the preceding jobs in the flow have also
passed and run against the exact same commit run and that any invocation of the
level3_indepth tests will run against the most recent commit that has also
passed the preceding level2_tests.
The non-flow way could be for level3_indepth to get the latest run of commit
as it started and to be triggered by a successful level2_test. This has a
drawback as you could get a run for which there is no successful level2 tests.
Alternatively you can use promoted builds - but that punts logic up to the
commit build which may be undesirable for various reasons.
Or you could get the run from the leve2_test that caused the level3_indepth to
run - this way makes it harder to use some Jenkins plugins, and moves a lot of
the intelligence to the Job (which should just be concentrating on the test
task at hand).
So back to the BuildFlow - We have multiple FlowRuns running concurrently and
say level3_indepth is running we don't want to start another one. However as
soon as level3_indepth has finished we want the most recent attempt to start a
new level3_indepth to succeed (and any that are not the most recent to abort
the flow run)
Doing this in the Flow DSL makes sense as there you can take advantage of
things extra flow features like parallel / guard rescue etc, showing the
build graph etc...
So the aboce leads to something like the following:
build(level1_smoke, run: upstream)
block (level2) {
build(level2_tests, run: upstream)
}
block (level3) {
build(level3_indepthtests, run: upstream)
}
Now this makes even more sense when you have realise that all the tests are
cucumber tests just with different tags - and these can actually be the same
job - (thus reducing job maintainance) and can be parameterised further...
Which leads to something like the following..
build(acceptance_tests, run: upstream, level:1)
block (level2) {
build(acceptance_tests, run: upstream, level:2)
}
block (level3) {
parallel {
build(acceptance_tests, run: upstream, level:3a)
build(acceptance_tests, run: upstream, level:3b)
}
}
This will run acceptance_tests with level:1 for every invocation of the
BuildFlow. However it will only run acceptance_tests for the latest level:2
if a level:2 job is not already running.
If it is not running the the flowrun will wait. If multiple FlowRuns are
waiting for the level2 block then when the block is released only the most
recent FlowRun will be able to enter it - and all others will have the FlowRun
Aborted.The block can also run across multiple jobs for example the
level3 block will prevent any new starts of 3a or 3b tests.
Or in a time line (at is the acceptance_tests job)
t=0flow#1 - at level=1
t=5flow#1 - at level=2
t=10 flow#2 - at level=1
t=20 flow#3 - at level=1
t=25 flow#1 - [ at level=3a, at level=3b ]
t=25 flow#2 (aborted as flow#3 is waiting to enter the same block)
t=25 flow#3 - at level=2
t=65 flow#3 - [ at level=3a, at level=3b ]
Hopefully that clears things up a bit. If something is not clear let me know
(as I will eventually need to put something like this on the Wiki)
/James
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
jelly help.
Hi all,
I need to show some specific help for some extensions - but I can't figure out
how get from the extension to the extension specific help (the url of the
plugin implementing the extension + fixed string). Anyone any ideas.
I currently have the following in help-foo.jelly:
j:jelly xmlns:j=jelly:core xmlns:st=jelly:stapler xmlns:d=jelly:define
xmlns:l=/lib/layout xmlns:t=/lib/hudson xmlns:f=/lib/form
xmlns:i=jelly:fmt xmlns:p=/lib/hudson/project
div
div
This is some global help.
/div
j:forEach
items=${app.getExtensionList('com.cisco.wibble.BazExtension')} var=ext
!-- need to get the extension specific help here - which may come
from a different plugin --
!--it should be something like a
href=/plugin/PLUGIN_ARTIFACT_ID/extensionclass/help- extension.html --
st:include page=/help-extension.html from=${ext}/
/j:forEach
/div
/j:jelly
Which gives me st:include No page found '/help-extension.html' for class
com.cisco.wible.ext.SuperBazExtension
I feel I'm close - just missing the final piece - anyone any pointers?
/James
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: Jelly variable for Project Display Name
project.displayName
This is just an expansion using javaBeans getters from
http://javadoc.jenkins-ci.org/hudson/model/Item.html#getDisplayName()
/James
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On
Behalf Of Ken
Sent: 19 August 2013 18:04
To: jenkinsci-dev@googlegroups.com
Subject: Jelly variable for Project Display Name
Anyone know the Jelly variable I could use to access the nicer looking Project
Display Name? (Found in Jenkins under Advanced Project Options.)
The Jelly variable for the Project Name is ${project.name} but I can't quite
figure out what the variable/macro for Project Display Name is.
-Ken
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: Persistent slave
Hi Nickolay, For virtual you can somewhat accomplish this with the Cloudbees auto scaling plugin. You create a pool of virtual machines, and then assign one to your build which you can access via SSH. You can do whatever you want to to this VM as this VM is not the slave VM - although there are no additional states available. If you feel like coding then you could probably do something similar with the vSphere cloud plugin, or the labmanager plugin. I have a plan to do something similar for physical machines - have a pool - be able to obtain one (or more), control the OS to revert to a snapshot etc.. but have some other things I need to accomplish first, and the extra snapshots will require UCS hardware and some SAN - yet to be determined. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Jason Swager Sent: 07 August 2013 15:34 To: jenkinsci-dev@googlegroups.com Subject: Re: Persistent slave As far as I know, this isn't possible. The basic slave architecture requires a constant, unbroken connection to the slave. If the connection is broken, the build is considered a failure. There might be ways to handle this in the slave classes, but if there is, I'm not aware of them. See this Stackoverflow Questionhttp://stackoverflow.com/questions/5543413/reconfigure-and-reboot-a-hudson-jenkins-slave-as-part-of-a-build that deals with the same issue. There are workarounds, but none quite as elegant as a rebootable slave. On Wednesday, August 7, 2013 7:18:17 AM UTC-7, Nickolay Rumyantsev wrote: Hi! I am looking for a way to create a new kind of a slave (or a channel or smth) for defining a set of testing machines (virtual and real) in my jenkins. It must meet the following requirements: 1. It should provide additional states like: rebooting, broken, available (and probably some others). The logic of selecting the current state exists already and is related to tha testing process. 2. The job that is being executed on such kind of the slave should be tolerant to slave reboot (until the specified timeout is exceeded) so the build will proceed after reboot normally. I had a look a the exiting plugins and it looks for me that there is no similar plugin for now. Can you please tell me if is it possible and if it is so suggest what plugin can I take as a base or which extension points should I look at to start development? Thanks, Nickolay -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: cucumber-reports-plugin
I've created a pull request[1] for the jenkinsci repo so that others can comment on this rather than just pulling the trigger. /James [1] https://github.com/jenkinsci/cucumber-reports-plugin/pull/1 From: Kingsley Hendrickse [mailto:kings...@masterthought.net] Sent: 31 July 2013 13:44 To: James Nord (jnord) Cc: jenkinsci-dev@googlegroups.com; Alex Thomson (alethoms) Subject: Re: cucumber-reports-plugin Hi The maintained code is https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java and this is where all releases come from. I didn't create the jenkinsci repo or the wiki page - but I will update it to point at the masterthought repo. The cucumber-reports plugin is in the update centre or you can download it from http://www.masterthought.net/section/cucumber-reporting Thanks --Kingsley On 31 Jul 2013, at 15:24, James Nord (jnord) jn...@cisco.commailto:jn...@cisco.com wrote: Hi Kingsley, Just wondering why the cucumber reports plugin is being developed and released from the masterthought repo[1] rather than the Jenkins repo[2] - which is listed as the official[3] repo in the wiki? Is there any plans to move back to the Jenkins repo - or should all the source in the Jenkins repo be replaced by a notice saying where the source is and the wiki be updated? Regards /James [1] https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java [2] https://github.com/jenkinsci/cucumber-reports-plugin [3] https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Reports+Plugin -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: building core
On Wed, Jul 24, 2013 at 4:16 PM, teilo teilo+goo...@teilo.net wrote: Is buildhive for core working at the moment? I guess you mean https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/ rather than BuildHive per se. Probably - its whatever takes the pull requests for core from github and builds them and adds comments. Pull requests for the last day seem to have no comments on them and the ci server appears to have no executors There was a problem on this server (excessive disk usage) but I fixed that yesterday. Existing pull requests don't seem to have triggered anything? e.g. https://github.com/jenkinsci/jenkins/pull/881 https://github.com/jenkinsci/jenkins/pull/880 /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: plugin jars contain maven?
Thanks Jesse. /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Jesse Glick Sent: 24 July 2013 23:07 To: jenkinsci-dev@googlegroups.com Subject: Re: plugin jars contain maven? On Wed, Jul 24, 2013 at 5:08 PM, Jesse Glick jgl...@cloudbees.com wrote: Bug in HudsonTestCase (and JenkinsRule). https://issues.jenkins-ci.org/browse/JENKINS-18918 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
plugin jars contain maven?
Hi all, Just noticed that the m2release 0.11 plugin _jar_ contains both apache-maven-2.2.1 and apache-maven-3.0.1 It's not confined to the m2release plugin - the copyartifact (1.27) plugin jar contains apache-maven-2.2.1 (but not 3!). Anyone else notices similar shinanigans - as it drastically increases the size of the jar and also the resulting hpi/jpi. /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: how to retrieve schedule job build number ?
Can you not get this from the future that is returned from the call to schedule build? http://javadoc.jenkins-ci.org/hudson/model/queue/QueueTaskFuture.html#getStartCondition() http://javadoc.jenkins-ci.org/hudson/model/queue/QueueTaskFuture.html#waitForStart() /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of nicolas de loof Sent: 10 July 2013 11:07 To: jenkinsci-dev@googlegroups.com Subject: how to retrieve schedule job build number ? I'm triggering a job (build flow plugin) using project.scheduleBuild2 I'd like to get the build number as the build start, not waiting for completion (just like queue widget does). Seems I need the Queue Item ID for this purpose, but scheduleBuild2 don't expose this one. Any suggestion ? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Backports to 1.509.2 done, please post RC
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Jesse Glick Sent: 08 July 2013 23:36 To: jenkinsci-dev@googlegroups.com Subject: Re: Backports to 1.509.2 done, please post RC On 06/28/2013 08:56 AM, James Nord (jnord) wrote: Issues I have found: Are these regressions from 1.509.1, or broken also in 1.509.1? And are they filed in JIRA? Issues specific to folders would be better sent to CloudBees support (though the bug might ultimately be determined to be in Jenkins core). Hi Jesse, As you are aware I had some major issues with 1.509.1 so the issues mentioned may have already been present in the prior LTS but I may not have noticed as I was pre-occupied with the OMG it doesn't work and is in production issues that were not apparent on my test system :-( I will raise a CB support ticket about the folder + weather. After a period of inactivity (overnight) when navigating to a page with lots of jobs I see a high page load time (minutes) (also have the latest dashboard plugin installed). So the above was very likely in 1.509.1 but not prior LTS and there are numerous reports / JIRAs about it - however I thought they had been traced back to dashboard plugin (and some others) and had been fixed - so I did not expect to see this anymore. I haven't yet raised a JIRA for this as it may well be down to my m2Release plugin - where the lastRelease permalink is not using the new symlink support in 1.509 to avoid having to walk the build history. However this functionality is only exposed on the job page - or a dashboard - so I did not expect to see any wait until one of those pages was actually displayed (can anyone confirm if my expectations are correct in this regard - if they are I will raise a JIRA and point CB support at it :-) ) /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Buildhive is not showing the latest artifact of a successful build
Agreed - it would be nice if the top level project listed all artifacts for all modules :-) /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Ulli Hafner Sent: 05 July 2013 10:29 To: jenkinsci-dev@googlegroups.com Subject: Re: Buildhive is not showing the latest artifact of a successful build Ah, I see. Seems that we should improve the usability of the maven project type;-) At least for single module builds it is quite cumbersome to have some information shown only on submodule level and not on the top level. Shouldn't every UI part on the submodule level show the aggregation on the top-level? (As this is done for test or code analysis results?) Ulli Am 04.07.2013 um 16:37 schrieb James Nord (jnord) jn...@cisco.com: Hi Ulli, It already does - e.g. https://jenkins.ci.cloudbees.com/job/plugins/job/m2release-plugin/last StableBuild/org.jvnet.hudson.plugins.m2release$m2release/ /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Ulli Hafner Sent: 03 July 2013 14:03 To: jenkinsci-dev@googlegroups.com Subject: Buildhive is not showing the latest artifact of a successful build Would it be possible to archive the latest artifact (*.hpi file) in our plug-in jobs in Buildhive? Then I can point reporters of a bug to the latest snapshot release for a test... Ulli -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Buildhive is not showing the latest artifact of a successful build
Hi Ulli, It already does - e.g. https://jenkins.ci.cloudbees.com/job/plugins/job/m2release-plugin/lastStableBuild/org.jvnet.hudson.plugins.m2release$m2release/ /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Ulli Hafner Sent: 03 July 2013 14:03 To: jenkinsci-dev@googlegroups.com Subject: Buildhive is not showing the latest artifact of a successful build Would it be possible to archive the latest artifact (*.hpi file) in our plug-in jobs in Buildhive? Then I can point reporters of a bug to the latest snapshot release for a test... Ulli -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Re: Backports to 1.509.2 done, please post RC
Issues I have found: Weather Icons. Icons on folders are randomly missing (pointing to empty.png) going into the folder (and its child shows enabled jobs have status). e.g [cid:image001.png@01CE7404.75236C30] On a folder if you click on a weather link you get taken to jobname/lastbuild - but folders don't get built and this results in a 404. After a period of inactivity (overnight) when navigating to a page with lots of jobs I see a high page load time (minutes) (also have the latest dashboard plugin installed). So could be a fault in m2release, but would only expect the delay if I was viewing the dashboard. Otherwise seems to be holding up much better than 1.509.1 /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Jerome Lacoste Sent: 23 June 2013 15:32 To: jenkinsci-dev@googlegroups.com Cc: Kohsuke Kawaguchi Subject: Re: Re: Backports to 1.509.2 done, please post RC On Saturday, June 22, 2013 5:26:49 AM UTC-5, vjuranek wrote: I didn't spot any issues [1] (*). I'll be completely offline for one week since now, so from my PoV, I'm fine to release it After many users of only using latest, I have now started using LTS versions :) Is it expected that http://jenkins-ci.org/changelog-stable doesn't reflect the contents of the branch ? The upcoming changes is empty. Thanks! Jerome (*) I had some issue with updated Jira plugin and hadn't enough time to investigate it, but seems to me like a configuration bug in my environment [1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.509.x+RC+Testing On Thursday 20 June 2013 20:51:04 Kohsuke Kawaguchi wrote: Posted On Wednesday, June 19, 2013, Kohsuke Kawaguchi wrote: All right, then I'll incorporate these changes into this evening 1.509.2 RC. On 06/19/2013 12:49 PM, Vojtech Juranek wrote: On Wednesday 19 June 2013 11:51:58 Kohsuke Kawaguchi wrote: I backported two more bugs and pushed 'stable-1.509.3'. sounds good to me. I'll be completely offline for once week since Saturaday or so, so there could be some delay with testing (but given we have already good amount of selenium tests, I'll maybe finished it this by Friday) I've also expanded backend-commit-history-parser to assist the backporting process. See https://wiki.jenkins-ci.org/**display/JENKINS/Backporting+** toolkit+for+LTShttps://wiki.jenkins-ci.org/display/JENKINS/Backporting+ toolkit+for+LTS for more details. great, thanks for that! -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. inline: image001.png
plugin maven groupId
Hi all, I am biting the bullet and dropping support for Hudson from my plugin (the Hudson community have forked it anyway). The plugin is still using the old org.jvnet.hudson.plugins Maven groupId - so I was considering changing this at the same time. However I wasn't sure if this is required to stay the same for plugin updates (or any other reason). So before I make the change to the groupId is there any reason not to? /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Jenkins Viewed by Google Chrome Loses Styling Randomly
Yes I see this (thought it was our setup), I haven’t updated from 1.480 LTS in a while so I think this is more a recent Chrome update issue than a Jenkins issue. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Chris Wozny Sent: 21 May 2013 14:56 To: jenkinsci-dev@googlegroups.com Subject: Jenkins Viewed by Google Chrome Loses Styling Randomly All, I'm not sure if this has happened with anyone else, but I find that sometimes when I'm viewing our Jenkins server (1.515 but this has been happening for at least the last 10 releases), the page will refresh and lose all of its stylesheet formatting. Unfortunately, I can't attach or upload an image to this post. Here is the console output which causes this lack of formatting: ←[33mMay 21, 2013 9:49:44 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception winstone.ClientSocketException: Failed to write to client at winstone.ClientOutputStream.write(ClientOutputStream.java:41) at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:182) at winstone.WinstoneOutputStream.flush(WinstoneOutputStream.java:218) at winstone.WinstoneOutputStream.close(WinstoneOutputStream.java:228) at java.util.zip.DeflaterOutputStream.close(Unknown Source) at org.kohsuke.stapler.compression.FilterServletOutputStream.close(FilterServletOutputStream.java:36) at java.io.FilterOutputStream.close(Unknown Source) at sun.nio.cs.StreamEncoder.implClose(Unknown Source) at sun.nio.cs.StreamEncoder.close(Unknown Source) at java.io.OutputStreamWriter.close(Unknown Source) at java.io.BufferedWriter.close(Unknown Source) at org.dom4j.io.XMLWriter.close(XMLWriter.java:286) at org.kohsuke.stapler.jelly.HTMLWriterOutput.close(HTMLWriterOutput.java:70) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:56) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) 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:48) 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:124) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
RE: Plugin can't find its own descriptor?
We only run jobs on slaves and the master has no executors, so would this code not reliably hit this issue if it was a master/slave issue? /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Christoph Kutzinski Sent: 30 January 2013 11:55 To: jenkinsci-dev@googlegroups.com Subject: Aw: Plugin can't find its own descriptor? I'm not sure but maybe the code part where you are is running in the forked Java VM for the Maven build where the descriptors would be null - AFAIK. You need to do your work in a callable which executes the code on the master. Gesendet: Mittwoch, 30. Januar 2013 um 12:49 Uhr Von: James Nord (jnord) jn...@cisco.commailto:jn...@cisco.com An: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com Betreff: Plugin can't find its own descriptor? Hi all, I got a really bizarre stacktrace from my plugin overnight (m2release 0.9.1, Jenkins 1.466.2+JENKINS-15382). ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.commailto:jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.model.AbstractDescribableImpl.getDescriptor(AbstractDescribableImpl.java:35) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.getDescriptor(M2ReleaseBuildWrapper.java:395) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:234) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:817) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) But this occurs at the end of the job during the plugin environments teardown But what I don't understand is how the plugin can be used in a job if its main descriptor can't be found, and this was a once off as subsequent releases are fine... Anyone any clues - is there any know issues in core around this area? /James -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.commailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Plugin can't find its own descriptor?
java.lang.NullPointerException at hudson.model.AbstractDescribableImpl.getDescriptor(AbstractDescribable Impl.java:35) Jenkins.getInstance() is null. Perhaps Jenkins is shutting down? Hmmm I did update a couple of plugins and hit restart when no jobs are running but this job was running then so it shouldn't have shutdown until after the job finished. However looking that the rest of the build logs the build seems to have abruptly terminated part way though so you may well be correct - and the restart when no jobs are running may be restart when I feel like it and I will probably go back to plugin updated by hand (copy hpi, restart service) is there any known issue in core around this area? Generally there are occasional race conditions involving app==null, frequently seen during shutdown. It is probably impossible to improve null safety here since this API uses the singleton pattern rather than dependency injection. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
