Re: crash plug-in warning - java heap space

[Ullrich Hafner]

Parsing is done on the master.

> Am 22.01.2016 um 14:45 schrieb iostrym :
> 
> Hi,
> 
> We did a crash with jenkins, using plug-in warnings with a logfile that is 70 
> Mo big :
> 
> [WARNINGS] Parsing warnings in console log with parser FPGA_Questa_UVM
> ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to 
> exception
> hudson.util.IOException2 
> : 
> remote file operation failed: /***/ at 
> hudson.remoting.Channel@**:serveur_linux_rdo 
> 
>   at hudson.FilePath.act(FilePath.java:861) 
> 
>   at hudson.FilePath.act(FilePath.java:838) 
> 
>   at 
> hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:447)
>  
> 
>   at 
> hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:411)
>  
> 
>   at 
> hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:320) 
> 
>   at 
> hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333)
>  
> 
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786)
>  
> 
>   at hudson.model.Build$BuildExecution.post2(Build.java:183) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733)
>  
> 
>   at hudson.model.Run.execute(Run.java:1592) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:88) 
> 
>   at hudson.model.Executor.run(Executor.java:237) 
> 
> Caused by: java.io.IOException 
> : Remote 
> call on serveur_linux_rdo failed
>   at hudson.remoting.Channel.call(Channel.java:681) 
> 
>   at hudson.FilePath.act(FilePath.java:854) 
> 
>   ... 14 more
> Caused by: java.lang.OutOfMemoryError 
> : 
> Java heap space
> 
> 
> We tried to re-run our slave with a bigger heap size but it doesn't help. So 
> we wonder if the HEAP error is regarding the master or the slave ? Which one 
> is executing the plug-in warning and do the parsing : master or slave ?
> 
> because of "Remote call on serveur_linux_rdo failed" we thought that the 
> parsing was done by the slave but as the upgrade of the heap size of  Java 
> Virtual Machine don't change anything and also because I succeed to crash the 
> master and shutdown all slaves connected to the master by testing it, I gives 
> me the feeling that the master may do something with the parsing.
> 
> Any idea ?
> 
> Best regards,
> 
> Armand
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> 

Re: [theme] New Jenkins Material Design Theme

[Baptiste Mathus]

+1. Nice!

Quick feedback: IMO, you should put bigger (or zoomable) screenshots on
your website. I just had a look and would have liked being able to see
things a bit more closely.

Thanks!

2016-01-21 18:23 GMT+01:00 Slide :

> I really like this theme, nice work!
>
> On Thu, Jan 21, 2016 at 10:17 AM Afonso F  wrote:
>
>> Hi guys,
>>
>> I created a Jenkins theme based on Google Material Design. It changes the
>> layout and icons using SVG ones. Take a look!
>>
>> http://afonsof.com/jenkins-material-theme/
>>
>>
>> 
>> 
>> 
>>
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/e1a3564b-cd21-4acc-b74b-645cddfd1902%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcCLNubvcptFsVXNaJp92ar9bWv_5%2BUCd_BWEbd3szk3A%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: How to configure Maven Installation via Groovy

[Baptiste Mathus]

https://github.com/batmat/jez/blob/master/jenkins-master/init_scripts/add_maven_auto_installer.groovy

auto-installs Maven 3.3.9 for example.

HTH

2016-01-21 17:43 GMT+01:00 Антон Юшков :

> Useful for me:
> import jenkins.model.*
>
> a=Jenkins.instance.getExtensionList(hudson.tasks.Maven.DescriptorImpl.
> class)[0];
> b=(a.installations as List);
> b.add(new hudson.tasks.Maven.MavenInstallation("MAVEN", "/usr/local/maven"
> , []));
> a.installations=b
> a.save()
>
>
>
> On Friday, January 9, 2015 at 2:08:17 AM UTC+4, Kenneth Baltrinic wrote:
>>
>> I am trying to build a chef recipe to deploy/manage our Jenkins
>> instances.  Things are going reasonably well but the ops-code Jenkin
>> cookbook only provides some basic configuration recipes. It does give you a
>> resource by which to run groovy scripts though and with that and the help
>> of a few blogs I have gotten some basic stuff set up.  However, now now I
>> am trying to do something quite simple in the UI but am stumped about how
>> to do this with a groovy script: Set up a Maven installation that installs
>> a specific version automatically.
>>
>> Here is what I think I have figured out so far:
>>
>>
>> *import jenkins.model.**
>>
>> *def inst = Jenkins.getInstance()*
>> *def desc = inst.getDescriptor('hudson.tasks.Maven')*
>> *def installs = desc.getInstallations()*
>>
>> installs in this case seems to have the list of existing installs, but I
>> cannot figure out how to programatically add an install to it, for instance
>> I would like to add an installation that is named 'mvn-3-0-5' that
>> automatically installs maven v 3.0.5.
>>
>> Any idea on how I can do this?  Any help will be much appreciated.
>> Thanks.
>>
>> --Ken
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6b4218ec-2008-490b-9b45-c1f283879219%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Jenkins Upgrade Installation Constraints and Risks

[Baptiste Mathus]

Hi,

Basically, yes, there are obviously many risks doing a fast-forward of
almost 5 years, maybe even more with a project as active as Jenkins :).

BUT, depending on your environment (how many jobs, nodes, exotic configs,
unmaintained/custom plugins...), this may not be a so big issue in the end.
The upgrade should still be pretty automatic if you're a bit lucky.
No specific patch or something should be required off the top of my head.

What you want to do is to replicate your whole current install the new
target server, and just try upgrading. You'll see how it goes. Crawl the
archive here about how to move a server onto another machine about that
(basically, rsync should almost always be sufficient from my experience).

When you have done that, and have found specific issues, don't hesitate to
come back here to ask for help/advice.

HTH

-- Cheers

2016-01-21 17:40 GMT+01:00 Nia Hunter :

> Good morning, I have two basic questions. I am not sure if this is the
> correct group for these questions, if not please let me know where to pose
> these questions.
>
> We are using Jenkins as a stand-alone application on our UNIX server.
>
> 1. Other than Java 7 and above, are there any System Requirements or
> Environmental constraints associated with upgrading from a much older
> version of Jenkins to the latest? For example, we are using Version 1.423
> and would like to go to at least Version 1.638, but preferably the latest.
> Is there a patch required when doing an upgrade from such an old version?
>
> 2. Are there any general risks associated with upgrading from an older
> version to a newer version?
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/8afcd1af-840f-4d05-b72e-afcc8a57600f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: "somecommand".execute()

[Baptiste Mathus]

What are you trying to do actually? I don't understand why you use a
synchronized block. Also, wouldn't you be using proc.wait() instead of
waitFor()?

2016-01-21 13:48 GMT+01:00 Niksan :

> When running a process on a slave using execute system groovy, what's the
> correct way to syncronise so a wait() can be performed on the process?
>
> def proc = "dir".execute()
> synchronized (proc) {
>proc.consumeProcessOutput(out, out)
>proc.wait();
> }
>
> this just waits forever and not synchronising causes and exception.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/64e99f96-a409-42db-940d-5bca578378a6%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Exception when I try to trigger buildflow job from workflow job

[EK]

An example to reproduce :

this is my workflow script , it takes param1 (string) from user when 
running, and executes buildflowjob : 
#
println(param1);
build job: 'buildflowjob', parameters: [[$class: 'StringParameterValue', 
name: 'param1', value:param1]]
#

this is my buildflowjob script, it takes param1 (string) from user when 
running

println(params['param1']));



On Thursday, January 21, 2016 at 3:45:12 PM UTC+2, EK wrote:

> Hi , 
>
>
> I am facing the following error , we recently moved to workflow and when 
> we try to run\trigger old build flow jobs from workflow jobs we get exception:
>
> Stacktrace of exception is as below , appreciate if anyone can help\advice on 
> this and how we can overcome the issue ? 
>
>
> Best Regards
>
> EK
>
>
> FATAL: Cannot cast object 'MyWorkFlowJobName #3' with class 
> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
> 'hudson.model.AbstractBuild'org.codehaus.groovy.runtime.typehandling.GroovyCastException
>  
> :
>  Cannot cast object 'MyWorkFlowJobName #3' with class 
> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
> 'hudson.model.AbstractBuild'
>   at 
> org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
>  
> 
>   at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:599)
>  
> 
>   at 
> com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall(FlowDSL.groovy:55)
>  
> 
>   at sun.reflect.GeneratedMethodAccessor1187.invoke(Unknown Source)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>   at java.lang.reflect.Method.invoke(Unknown Source)
>   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:428)
>   at 
> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
>   at 
> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
>   at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
> Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>   at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
> Source)
>   at 
> com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods.groovy:26)
>   at sun.reflect.GeneratedMethodAccessor941.invoke(Unknown Source)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>   at java.lang.reflect.Method.invoke(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:51)
>   at 
> org.codehaus.groovy.runtime.metaclass.NewInstanceMetaMethod.invoke(NewInstanceMetaMethod.java:54)
>   at 
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
>   at 
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
>   at 
> com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:52)
>   at 
> com.cloudbees.plugins.flow.FlowRun$FlyweightTaskRunnerImpl.run(FlowRun.java:219)
>   at hudson.model.Run.execute(Run.java:1738)
>   at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155)
>   at hudson.model.ResourceController.execute(ResourceController.java:98)
>   at hudson.model.Executor.run(Executor.java:410)
>
>

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

Re: Version Number Plugin does not work when job is running more then once

[Baptiste Mathus]

Looking at the code [1], IMO this is a likely a bug. This is indeed gonna
blow up each time the previous build will still be building, as
build.getResult() will by contract return null if currently building.

So, I think you should file an issue in the tracker about that. And if
possible the associated PR to higher your chances to get an official
release with that fix.

Cheers

[1]
https://github.com/jenkinsci/versionnumber-plugin/blob/master/src/main/java/org/jvnet/hudson/tools/versionnumber/VersionNumberBuilder.java#L262

2016-01-21 17:19 GMT+01:00 Andrew Novinger :

> I have a Jenkins job that is using the Version Number Plugin to change the
> build label in Jenkins to show the environment name and job number.
>
> This job is not throttle so it can run many times concurrently for
> different environments.
>
> The issue I am having is the first environment that is run, the label gets
> update and is correct, the next job that is running while the first job is
> running.  We get a null pointer exception thrown (see below), and the
> Jenkins label does not change.
>
> ERROR: java.lang.NullPointerExceptionjava.lang.NullPointerException 
> 
> at 
> org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.incBuild(VersionNumberBuilder.java:262)
>  
> 
>   at 
> org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.setUp(VersionNumberBuilder.java:540)
>  
> 
>   at hudson.model.Build$BuildExecution.doRun(Build.java:156) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 
> 
>   at hudson.model.Run.execute(Run.java:1738) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>   at hudson.model.Executor.run(Executor.java:410) 
> 
>
> Any ideas on how to make this plugin work on a job that can run concurrently?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/41c4eebd-8df9-4af9-8ca3-67e042db0f7a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [theme] New Jenkins Material Design Theme

[Mohan PAKALAPATI]

Looks great
+1
On 21 Jan 2016 22:46, "Afonso F"  wrote:

> Hi guys,
>
> I created a Jenkins theme based on Google Material Design. It changes the
> layout and icons using SVG ones. Take a look!
>
> http://afonsof.com/jenkins-material-theme/
>
>
> 
> 
> 
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e1a3564b-cd21-4acc-b74b-645cddfd1902%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAHCF%2BH4%2BUiLbJKHNFb1dCQi%3D6htiBuNLY-jfheNJ%3DDR01c8TLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Upgrade Installation Constraints and Risks

[Mark Waite]

Since you spent a long time on a single version, you should probably
upgrade to a long term support version (currently 1.642.1) rather than to a
weekly version.  LTS versions have additional testing and tend to be
supported longer (though none of them are supported for 5 years).

Mark Waite

On Sat, Jan 23, 2016 at 8:50 AM Nia Hunter  wrote:

> Thank you this has been most helpful and I will be sure to come back with
> any questions if I encounter any issues!
>
> Sent from my iPhone
>
> On Jan 23, 2016, at 8:35 AM, Baptiste Mathus  wrote:
>
> Hi,
>
> Basically, yes, there are obviously many risks doing a fast-forward of
> almost 5 years, maybe even more with a project as active as Jenkins :).
>
> BUT, depending on your environment (how many jobs, nodes, exotic configs,
> unmaintained/custom plugins...), this may not be a so big issue in the end.
> The upgrade should still be pretty automatic if you're a bit lucky.
> No specific patch or something should be required off the top of my head.
>
> What you want to do is to replicate your whole current install the new
> target server, and just try upgrading. You'll see how it goes. Crawl the
> archive here about how to move a server onto another machine about that
> (basically, rsync should almost always be sufficient from my experience).
>
> When you have done that, and have found specific issues, don't hesitate to
> come back here to ask for help/advice.
>
> HTH
>
> -- Cheers
>
> 2016-01-21 17:40 GMT+01:00 Nia Hunter :
>
>> Good morning, I have two basic questions. I am not sure if this is the
>> correct group for these questions, if not please let me know where to pose
>> these questions.
>>
>> We are using Jenkins as a stand-alone application on our UNIX server.
>>
>> 1. Other than Java 7 and above, are there any System Requirements or
>> Environmental constraints associated with upgrading from a much older
>> version of Jenkins to the latest? For example, we are using Version 1.423
>> and would like to go to at least Version 1.638, but preferably the latest.
>> Is there a patch required when doing an upgrade from such an old version?
>>
>> 2. Are there any general risks associated with upgrading from an older
>> version to a newer version?
>>
>> Thanks!
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/8afcd1af-840f-4d05-b72e-afcc8a57600f%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
>
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/55-9UlaD44A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6_D7COajvP0XadaY7dn71_nTLyExuFkS72aRxL%2B%3DqY8Q%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/E2DE1AE0-27CF-4288-A86F-9A31B4935CD3%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: downloads from archives.jenkins-ci.org never finish...

[Alex Domoradov]

I do really need exactly jenkins_1.565.2_all.deb (debian 7). Could anyone 
share with me?

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

Re: AWS ECS Plugin

[nicolas de loof]

You could use docker-custom-build-environment-plugin for this exact
scenario, with bind mounted /var/run/docker.sock so you can run containers
side by side (vs "in-docker"). Would need some tests on my side to ensure
this scenario is supported, I have this on my TOD for a while but never
took time to setup a test environment for it...

2016-01-22 21:01 GMT+01:00 Brandon Wagner :

> I would like to run Docker containers for all of my software projects and
> dynamically allocate build slaves via ECS (so that I can have a core
> cluster that can do builds quickly; in contrast to spinning up an EC2
> instance).
>
>  For example, I have a Java application which is completely contained in a
> Docker container (I can build it, run tests, and run the actual application
> with Tomcat all within the container). I want to use this for a variety of
> different purposes (dev, testing, qa, and production). In order to make it
> reusable like that, I don't want to include Jenkins Slave packages and
> expose ports. I'd rather deploy out a Jenkins-Slave container to my ECS
> cluster, and then have that slave handle running my application's docker
> container which also performs tests.
>
> I also support other team applications which are already running docker
> container builds in Jenkins (locally on the Jenkins Master). I want it to
> be transparent to them that I'm "outsourcing" build slaves to ECS. It
> shouldn't matter to them that I'm changing the way Jenkins is performing
> builds.
>
> Let me know if you (or anyone else) have suggestions based on my goals.
>
> -Brandon Wagner
>
>
> On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof  > wrote:
>
>> privileged flag has been added to development build (
>> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
>> anyway, DinD is probably not a good idea (there's really few docker
>> usages to actually require it). What's your actual need ?
>>
>> 2016-01-22 20:46 GMT+01:00 Brandon Wagner :
>>
>>> So I ended up figuring my issue out. I think there were a couple of
>>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>>> Docker Container I was using was mapping to the host port 5000. And my Load
>>> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
>>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>>> ECS.
>>>
>>> My next problem: I want to use docker-in-docker to run docker builds on
>>> my docker jenkins slaves. I'm trying to use
>>> https://github.com/tehranian/dind-jenkins-slave which looks good, but I
>>> don't see an option on the Jenkins ECS plugin to run the slave as
>>> privileged which is necessary for docker-in-docker.
>>>
>>>
>>> -Brandon Wagner
>>>
>>> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>
 First look into jenkins logs.
 Also check on ECS a task definition has been created for
 jenkins-slaves.
 Also double check ECS nodes can ping your jenkins master URL.

 2016-01-21 22:13 GMT+01:00 Brandon Wagner :

> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin
> to deploy Jenkins Slave Containers for builds. I have an ECS cluster 
> setup,
> and I have it configured in my Jenkins Configuration. Everything appears 
> to
> be good until I try to build a job, restricting to the ecs cloud label I
> setup, and it just comes back with "(pending—
> Jenkins-Container-Cloud-456...164
> is
> offline)" .
>
> Does anyone know how to fix this, or have suggestions on debugging
> steps?
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

 --
 You received this message because you are subscribed to a topic in the
 Google Groups "Jenkins Users" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-users/kSBWy3gBQbg/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 

Re: Jenkins Upgrade Installation Constraints and Risks

[Nia Hunter]

Noted! Thanks!!! 

Sent from my iPhone

> On Jan 23, 2016, at 12:37 PM, Mark Waite  wrote:
> 
> Since you spent a long time on a single version, you should probably upgrade 
> to a long term support version (currently 1.642.1) rather than to a weekly 
> version.  LTS versions have additional testing and tend to be supported 
> longer (though none of them are supported for 5 years).
> 
> Mark Waite
> 
>> On Sat, Jan 23, 2016 at 8:50 AM Nia Hunter  wrote:
>> Thank you this has been most helpful and I will be sure to come back with 
>> any questions if I encounter any issues! 
>> 
>> Sent from my iPhone
>> 
>>> On Jan 23, 2016, at 8:35 AM, Baptiste Mathus  wrote:
>>> 
>> 
>>> Hi,
>>> 
>>> Basically, yes, there are obviously many risks doing a fast-forward of 
>>> almost 5 years, maybe even more with a project as active as Jenkins :).
>>> 
>>> BUT, depending on your environment (how many jobs, nodes, exotic configs, 
>>> unmaintained/custom plugins...), this may not be a so big issue in the end. 
>>> The upgrade should still be pretty automatic if you're a bit lucky. 
>>> No specific patch or something should be required off the top of my head.
>>> 
>>> What you want to do is to replicate your whole current install the new 
>>> target server, and just try upgrading. You'll see how it goes. Crawl the 
>>> archive here about how to move a server onto another machine about that 
>>> (basically, rsync should almost always be sufficient from my experience).
>>> 
>>> When you have done that, and have found specific issues, don't hesitate to 
>>> come back here to ask for help/advice.
>>> 
>>> HTH
>>> 
>>> -- Cheers
>>> 
>>> 2016-01-21 17:40 GMT+01:00 Nia Hunter :
 Good morning, I have two basic questions. I am not sure if this is the 
 correct group for these questions, if not please let me know where to pose 
 these questions.
 
 We are using Jenkins as a stand-alone application on our UNIX server.
 
 1. Other than Java 7 and above, are there any System Requirements or 
 Environmental constraints associated with upgrading from a much older 
 version of Jenkins to the latest? For example, we are using Version 1.423 
 and would like to go to at least Version 1.638, but preferably the latest. 
 Is there a patch required when doing an upgrade from such an old version?
 
 2. Are there any general risks associated with upgrading from an older 
 version to a newer version?
 
 Thanks!
 -- 
 You received this message because you are subscribed to the Google Groups 
 "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/8afcd1af-840f-4d05-b72e-afcc8a57600f%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>> 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-users/55-9UlaD44A/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-users+unsubscr...@googlegroups.com.
>> 
>>> 
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6_D7COajvP0XadaY7dn71_nTLyExuFkS72aRxL%2B%3DqY8Q%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/E2DE1AE0-27CF-4288-A86F-9A31B4935CD3%40gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/55-9UlaD44A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFoUYwG1DHJHAr9vpSobUwQ7JDTZfkwVOVxkarXsNpTSQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: Jenkins Upgrade Installation Constraints and Risks

[Nia Hunter]

Thank you this has been most helpful and I will be sure to come back with any 
questions if I encounter any issues! 

Sent from my iPhone

> On Jan 23, 2016, at 8:35 AM, Baptiste Mathus  wrote:
> 
> Hi,
> 
> Basically, yes, there are obviously many risks doing a fast-forward of almost 
> 5 years, maybe even more with a project as active as Jenkins :).
> 
> BUT, depending on your environment (how many jobs, nodes, exotic configs, 
> unmaintained/custom plugins...), this may not be a so big issue in the end. 
> The upgrade should still be pretty automatic if you're a bit lucky. 
> No specific patch or something should be required off the top of my head.
> 
> What you want to do is to replicate your whole current install the new target 
> server, and just try upgrading. You'll see how it goes. Crawl the archive 
> here about how to move a server onto another machine about that (basically, 
> rsync should almost always be sufficient from my experience).
> 
> When you have done that, and have found specific issues, don't hesitate to 
> come back here to ask for help/advice.
> 
> HTH
> 
> -- Cheers
> 
> 2016-01-21 17:40 GMT+01:00 Nia Hunter :
>> Good morning, I have two basic questions. I am not sure if this is the 
>> correct group for these questions, if not please let me know where to pose 
>> these questions.
>> 
>> We are using Jenkins as a stand-alone application on our UNIX server.
>> 
>> 1. Other than Java 7 and above, are there any System Requirements or 
>> Environmental constraints associated with upgrading from a much older 
>> version of Jenkins to the latest? For example, we are using Version 1.423 
>> and would like to go to at least Version 1.638, but preferably the latest. 
>> Is there a patch required when doing an upgrade from such an old version?
>> 
>> 2. Are there any general risks associated with upgrading from an older 
>> version to a newer version?
>> 
>> Thanks!
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/8afcd1af-840f-4d05-b72e-afcc8a57600f%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/55-9UlaD44A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6_D7COajvP0XadaY7dn71_nTLyExuFkS72aRxL%2B%3DqY8Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: downloads from archives.jenkins-ci.org never finish...

[Alex Domoradov]

Any updates?

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

Re: Exception when I try to trigger buildflow job from workflow job

[Craig Rodrigues]

Hi,

I have a patch to address this issue.
Would you be willing to build the build-flow-plugin from my branch and
provide feedback?
You can build it with:

git clone https://github.com/jenkinsci/build-flow-plugin
cd build-flow-plugin
git fetch origin pull/70/head:70
git checkout 70
mvn install

--
Craig

On Sat, Jan 23, 2016 at 12:49 PM, Craig Rodrigues 
wrote:

> Hi,
>
> Thanks for posting your sample scripts.
> I was able to reproduce your problem.
>
> It looks like the Build Flow plugin needs to change to use the Run class,
> instead of AbstractBuild
> in order to be compatible with workflow/pipeline plugin.
>
> --
> Craig
>

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

Re: Exception when I try to trigger buildflow job from workflow job

[Craig Rodrigues]

Hi,

Thanks for posting your sample scripts.
I was able to reproduce your problem.

It looks like the Build Flow plugin needs to change to use the Run class,
instead of AbstractBuild
in order to be compatible with workflow/pipeline plugin.

--
Craig


On Sat, Jan 23, 2016 at 12:22 AM, EK  wrote:

> An example to reproduce :
>
> this is my workflow script , it takes param1 (string) from user when
> running, and executes buildflowjob :
> #
> println(param1);
> build job: 'buildflowjob', parameters: [[$class: 'StringParameterValue',
> name: 'param1', value:param1]]
> #
>
> this is my buildflowjob script, it takes param1 (string) from user when
> running
> 
> println(params['param1']));
> 
>
>
> On Thursday, January 21, 2016 at 3:45:12 PM UTC+2, EK wrote:
>
>> Hi ,
>>
>>
>> I am facing the following error , we recently moved to workflow and when 
>> we try to run\trigger old build flow jobs from workflow jobs we get 
>> exception:
>>
>> Stacktrace of exception is as below , appreciate if anyone can help\advice 
>> on this and how we can overcome the issue ?
>>
>>
>> Best Regards
>>
>> EK
>>
>>
>> FATAL: Cannot cast object 'MyWorkFlowJobName #3' with class 
>> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
>> 'hudson.model.AbstractBuild'org.codehaus.groovy.runtime.typehandling.GroovyCastException
>>  
>> :
>>  Cannot cast object 'MyWorkFlowJobName #3' with class 
>> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
>> 'hudson.model.AbstractBuild'
>>  at 
>> org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
>>  
>> 
>>  at 
>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:599)
>>  
>> 
>>  at 
>> com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall(FlowDSL.groovy:55)
>>  
>> 
>>  at sun.reflect.GeneratedMethodAccessor1187.invoke(Unknown Source)
>>  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>  at java.lang.reflect.Method.invoke(Unknown Source)
>>  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:428)
>>  at 
>> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
>>  at 
>> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
>>  at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
>> Source)
>>  at 
>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>>  at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
>> Source)
>>  at 
>> com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods.groovy:26)
>>  at sun.reflect.GeneratedMethodAccessor941.invoke(Unknown Source)
>>  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>  at java.lang.reflect.Method.invoke(Unknown Source)
>>  at 
>> org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:51)
>>  at 
>> org.codehaus.groovy.runtime.metaclass.NewInstanceMetaMethod.invoke(NewInstanceMetaMethod.java:54)
>>  at 
>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
>>  at 
>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
>>  at 
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
>>  at 
>> com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:52)
>>  at 
>> com.cloudbees.plugins.flow.FlowRun$FlyweightTaskRunnerImpl.run(FlowRun.java:219)
>>  at hudson.model.Run.execute(Run.java:1738)
>>  at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155)
>>  at hudson.model.ResourceController.execute(ResourceController.java:98)
>>  at hudson.model.Executor.run(Executor.java:410)
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group