Re: How to downgrade Jenkins from 2.x to 1.x version in windows

[Donald Morton]

I think you would want to restore the Jenkins home directory from a backup 
you made prior to the upgrade.


On Thursday, November 3, 2016 at 5:15:13 AM UTC-5, MI wrote:
>
> How could we downgrade to earlier version in case of something went wrong 
> after upgraded to newer version of Jenkins?
>

-- 
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/4421573d-3caa-4093-8157-03cb3b6c5cba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Global "disable triggers" options

[Donald Morton]

I've run a groovy script to disable all jobs before. Then, I just enable 
the jobs I want to run. The problem with that, though is that Pipeline jobs 
can't be disabled. So, I normally have to go into the test instance and 
manually remove the triggers on the Pipeline jobs to keep them from 
running. I'm sure a script could do this, too, but I haven't seen one.


On Monday, November 7, 2016 at 8:04:51 AM UTC-6, Michael Giroux wrote:
>
> We have a large jenkins configuration with 1700 jobs.  We have two use 
> cases in which the configuration is copied. We make a copy of the 
> configuration prior to any upgrade:
>
> 1. for purposes of testing new version and plugins prior to an upgrade
> 2. to have a running instance of the previous version to allow "emergency 
> builds" for projects that will not build in new version after an upgrade.
>
> In both of these use cases, we have two copies of Jenkins running at the 
> same time (on different ports of course), the old version, and the new 
> version.  In either case, we want to disable the build triggers for one of 
> the instances.  We do not want two copies of jenkins building the same 
> project based on polling, or due to upstream builds and/or snapshot changes.
>
> We can use "prepare to shutdown" to suspend one instance.  But if we 
> cancel shutdown to allow a specific build to be run, the flood gates open.
>
> It would be helpful  if there was an option to allow manual builds even 
> when "prepare to shutdown" is in effect.  Or, as the subject line suggests, 
> an option to disable triggers. Such an option should have an initial state 
> set by a system property allowing us to launch Jenkins with the option 
> initially on or off.
>
> Similar requests have been made previously:
> http://jenkins-ci.361315.n4.nabble.com/Suspend-Plugin-td1599530.html
>
> http://stackoverflow.com/questions/1299180/can-i-disable-hudsons-automatic-scheduled-builds-all-at-once
>
> I would be interested in hearing how other users handle this case, 
> especially case #2 in which we wish to have the old instance of Jenkins 
> available to run builds that might not execute in the new version.
>
> Michael
>
>
>

-- 
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/88fb59b0-ed81-47f2-8012-315f554d5f7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: publish-over-cifs in a pipeline build

[Donald Morton]

I think you can have the job run the "net use" command to tie credentials 
to a fileshare, and then just copy like it's a regular file. Not sure how 
you'd secure the credentials, though. Ansible, Puppet, or Windows DSC might 
be other options to pursue. 

On Tuesday, November 8, 2016 at 5:13:17 PM UTC-6, Tristan Bull wrote:
>
> Hi all,
>
> I'm looking at converting our Jenkins implementation over to pipeline 
> builds using the github-organization-folder plugin. Our current builds 
> publish build artifacts to a windows file share using the publish-over-cifs 
> plugin. What is the best way to accomplish this in a pipeline build? It 
> does not appear that the publish-over-cifs plugin is compatible. Thanks,
>
> -Tristan
>

-- 
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/7607bc55-d730-4585-804a-320afbc76146%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slave Jenkins on an RHEL box

[Donald Morton]

Sounds like the ssh command is failing. Maybe the password or private key 
is wrong? 


On Monday, November 14, 2016 at 10:28:20 AM UTC-6, Peter Berghold wrote:
>
> I have Jenkins running merrily on an Ubuntu box and want to set up a slave 
> on an RHEL box. 
>
> Created a script on the RHEL box that essentially launches a script that 
> in turn launches the slave.jar.  Trying to invoke it over SSH and there's 
> where things take a turn for the worse.
>
> I'm getting this:
>
> [11/14/16 16:22:37] Launching agent
> $ /usr/share/tomcat8/startSlave0
> Host key verification failed.
> ERROR: Unable to launch the agent for java.io.EOFException 
> : 
> unexpected stream termination
>   at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:365) 
> 
>   at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:310) 
> 
>   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:388) 
> 
>   at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:131) 
> 
>   at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261) 
> 
>   at 
> jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
>  
> 
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> 
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  
> 
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  
> 
>   at java.lang.Thread.run(Thread.java:745) 
> 
> ERROR: Process terminated with exit code 255
>
>
> That first line is a script on the master that does the SSH.What I'm not 
> sure about is exactly what is complaining about Host key verification.  Given 
> I can run that script by hand and it starts the jar file I'm a bit confused 
> about what's going on here. 
>
>
> Has anybody gotten this to work?
>
>
>

-- 
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/b9a359bf-eef0-4855-9178-515ee70acce6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: "more SCM polling activities scheduled than handled..."

[Donald Morton]

Maybe try setting it at 100 threads? That is the max it will do. Not sure 
if setting it blank does the same thing or not. 



On Monday, November 14, 2016 at 3:11:27 PM UTC-6, Josh Santangelo wrote:
>
> I’d love to stop polling, but with Jenkins behind our firewall and git 
> outside of it, the conversation is only one way.
>
> Here’s what I’m seeing in the git polling log on those processes. I would 
> accept that if it timed out it would just try again later, but once it gets 
> in this state, the project never automatically builds again. I can even 
> manually do a build which will be successful, but polling never sorts 
> itself out.
>
> poll] Last Built Revision: Revision 
> e5779a7ee33a8c58a4e13c9930f02b67a07c964a (refs/remotes/origin/multitaction)
>  > C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h g...@bitbucket.org 
> :stimulant/DWD.git # timeout=10
> ERROR: Timeout after 10 minutes
>
> ERROR
> : Failed to join a process
>
> org.jvnet.winp.WinpException
> : Failed to read environment variable table error=299 at 
> .\envvar-cmdline.cpp:201
> at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method)
> at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:126)
> at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:102)
> at hudson.util.ProcessTree$Windows$1.getArguments(ProcessTree.java:444)
> at 
> hudson.plugins.msbuild.MsBuildKillingVeto.vetoProcessKilling(MsBuildKillingVeto.java:55)
> at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:242)
> at hudson.util.ProcessTree$Windows$1.killRecursively(ProcessTree.java:425)
> at hudson.util.ProcessTree.killAll(ProcessTree.java:145)
> at hudson.Proc$LocalProc.destroy(Proc.java:378)
> at hudson.Proc$LocalProc.kill(Proc.java:370)
> at hudson.Proc$1.run(Proc.java:157)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
> -- 
> S T I M U L Λ N T
> Josh Santangelo, Technical Director
> P 415 363 0336 / HQ 415 255 7081 / T @stimulant
>
> On Nov 13, 2016, at 6:30 AM, Baptiste Mathus  > wrote:
>
> Hi,
>
> The ideal target you should actually strive for is to "kill polling", and 
> use push instead, as explained in 
> http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
>
> If you really really cannot consider that, then in your place I would 
> maybe try and mimic what Jenkins is supposedly doing: on your machine, 
> write a script that clones repo, or updates it every minute (or something 
> similar with what you put in Jenkins), during say an hour, or a day. Goal 
> being to have data about connectivity.
>
> Maybe it's just bitbucket.org that's inconsistent, and sometimes never 
> answers. Or maybe not. IMO that's the first thing you want to look at. 
>
> For example, looking at https://status.bitbucket.org/ I see issues around 
> the date of your message, was your issue that day or something that's been 
> consistently problematic across weeks?
>
> -- Baptiste
>
> 2016-11-10 22:30 GMT+01:00 Josh Santangelo  >:
>
>> Hi all -- I'm seeing the "There are more SCM polling activities scheduled 
>> than handled, so the threads are not keeping up with the demands" error 
>> consistently on my Jenkins setup (2.3, running as a Windows service).
>>
>> Going to my http://jenkins/descriptor/hudson.triggers.SCMTrigger/ page 
>> does show jobs hanging for hours at a time, but always different jobs.
>>
>> I currently have 14 jobs enabled which are polling git repos on 
>> BitBucket.org (I had more, but I disabled a bunch trying to troubleshoot 
>> this issue).
>>
>> On the "Manage Jenkins" page I set "Max # of concurrent polling" to 
>> empty, which seems to mean an unlimited number of threads, but the issue 
>> remains.
>>
>> Is there anything else I should look at?
>>
>> thanks,
>> -josh
>>
>> -- 
>> 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/03919522-cec0-43e7-8c9f-ed102234a3a6%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 
> 

Re: Getting "java.io.NotSerializableException" exception in Jenkins pipeline, groovy.

[Donald Morton]

Here are some references for you:

https://support.cloudbees.com/hc/en-us/articles/230612967-Pipeline-The-pipeline-even-if-successful-ends-with-java-io-NotSerializableException

https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#serializing-local-variables

https://issues.jenkins-ci.org/browse/JENKINS-35140




On Sunday, November 13, 2016 at 11:13:35 PM UTC-6, Ganesh Kumbhar wrote:
>
> Hello All,
>
> I am new to Jenkins pipeline and recently started to use it for my project 
> build.
>
> So, from Jenkins file I am calling a method from other .groovy file which 
> is simple script having some functions defined and in those functions I am 
> creating antbuilder object -> "@Field AntBuilder antBuilder = new 
> AntBuilder()"
> But the problem is, I am not able to call any ant targets using antbuilder 
> object, simply calling echo using this object like -> " antBuilder.echo 
> 'print 
> statement' "  gives *"NotSerializableException"*exception.
>
> java.io.NotSerializableException: org.apache.tools.ant.taskdefs.Echo
>
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>
>
> So please guide me to resolve this problem if anyone had faced this issue 
> or have any idea about it.
> Any help is appreciated!
> Thank you very much!
> Ganesh K.
>

-- 
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/2b760da3-e4d8-4da4-a554-dbfca8576d86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.