Jenkins slave with java.io.EOFException
Hi experts, I want to achieve a simple master-slave configuration with Jenkins. On my local machine, everything worked like a charm and now I wanted to set it up on my client's machine. But there, I get an End of File Exception in catalina.out after 60 seconds. This is the full stack trace: java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:180) at java.io.DataInputStream.readUTF(DataInputStream.java:592) at java.io.DataInputStream.readUTF(DataInputStream.java:547) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:148) Has anyone got this before, or can someone please give me a hint what I'm doing wrong here? What could be the reason? Many thanks! Cheers Stefan -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Resource Counting/Management
Just an FYI but concurrent builds plugin supports what you want out of the box. Brett Sent from my mobile so please forgive any auto correct errors Kind regards, Brett On 1 Nov 2013 15:18, "AndyB" wrote: > > Thanks for pointers. I'll check both the core's concepts of resources and > their use in the locks/latches plugin. > > Thanks again, > Andy > > > > On Thursday, 31 October 2013 15:53:27 UTC, Ricardo Silva wrote: >> >> I've never used it myself, and maybe it uses the same concept Stephen >> mentioned (so it could be broken), but the Throttle Concurrent Build >> plugin [1] has a "Multi-Project Throttle Categories" which I think fits >> with what you want to do. >> >> Declare in the global configuration a licenses category and the maximum >> number, and tag all jobs that use a license with that category. (It just >> doesn't fit well with jobs that use multiple licenses of a single >> product.) >> >> [1] >> https://wiki.jenkins-ci.org/display/JENKINS/Throttle+ >> Concurrent+Builds+Plugin >> >> >> On 10/31/2013 04:42 PM, Stephen Connolly wrote: >> > There is a concept of a Resource within Jenkins and jobs can be marked >> as >> > using N of that number of the Resource instances, and you can declare >> how >> > many total instances of the resource exist. >> > >> > Jenkins will stall builds until they can get the required number of >> those >> > resources. >> > >> > The locks and latches plugin uses this with resources of size 1 to >> > implement locks... Beware there are bugs in the Resource model that to >> my >> > knowledge have never been fixed (these are mostly seen as "bugs in >> locks >> > and latches" but actually are issues in core) have a look at the issues >> in >> > the locks and latches plugin to see if they are things you can live >> with >> > before you start down that road though >> > >> >> > >> >> -- >>Ricardo >> > -- > 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. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: build flow, early exit from parallel construct?
Take a look at src/test/groovy/com/cloudbees/plugins/flow/AbortTest.groovy
- this should say that it is possible to do what you want :-)
On Tuesday, 29 October 2013 02:43:19 UTC-4, asmundo wrote:
>
> On Tue, Oct 29, 2013 at 4:16 AM, James Nord (jnord)
>
> > wrote:
>
>> The changes I have put in to support this are not in a release version
>> of the buildflow – so you will need to download source and compile, or grab
>> it from the Jenkins ci instance.
>>
>
> I forgot to state that I am did this. Sorry about that. I am running:
>
>* 305af7f Merge pull request #37 from mattiasbpersson/master
>* build-flow-plugin:0.11-SNAPSHOT
>
> I did very much like the groovy shell evaluation!
>
> Asmund
>
>
>
>
>
>>
>
>>
>> ** **
>>
>> /James
>>
>> ** **
>>
>> *From:* jenkins...@googlegroups.com [mailto:
>> jenkins...@googlegroups.com ] *On Behalf Of *Åsmund Østvold
>> *Sent:* 28 October 2013 17:34
>>
>> *To:* jenkins...@googlegroups.com
>> *Subject:* Re: build flow, early exit from parallel construct?
>>
>> ** **
>>
>> Thank you James,
>>
>> ** **
>>
>> I finally freed up some time and was able do a new stab at this. I have
>> inlined some questions and feedback.
>>
>> ** **
>>
>> On Fri, Oct 25, 2013 at 6:33 AM, James Nord (jnord)
>> >
>> wrote:
>>
>> KillRunningjobs is called internally if the flow is aborted (or one of
>> the jobs is aborted).
>>
>> Internallyt this is handled by catching either (IIRC) a
>> JobAborteException (or also an IOException).
>>
>> ** **
>>
>> I did search for 10 minutes for "JobAborteException" or something close
>> to this. But my Jenkins/Java knowledge is limite...
>>
>>
>>
>> The IOException will show a stack trace in your console output – wheres
>> the jobAbortEx will just show “Aborted” (and the cause if you set one),**
>> **
>>
>> ** **
>>
>> I did try the blow but was not able to abort flow job. Job 'pass' takes
>> 20s and job 'fail' taks only 5s:
>>
>> ** **
>>
>> parallel(
>>
>> { b = build("pass");
>>
>> if (b.getResult() == Result.FAILURE) {
>>
>> throw new java.io.IOException("foo")
>>
>> } },
>>
>> { b = build( "fail" );
>>
>> if (b.getResult() == Result.FAILURE) {
>>
>> throw new java.io.IOException("foo")
>>
>> }}
>>
>> )
>>
>> ** **
>>
>> Console output:
>>
>> ** **
>>
>> ** **
>>
>> parallel {
>>
>> Schedule job fail
Mailer plugin
Hi, I already have the mailer plugin installed. I'm trying to configure the hudson.tasks.Mailer.xml via groovy. meaning, using the setters on the hudson.tasks.Mailer inner class, DescriptorImpl. The problem is that I don't know how to retrieve a reference to it from the list of pluginWrappers I get from: Jenkins.instance.pluginManager.plugins. Or maybe I should approach the matter in another way. Thanks, Noam -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Dynamic Axis plugin sometimes inserts "default"
This issue was fixed in the latest version (1.02)! On Thursday, February 14, 2013 2:53:28 AM UTC+2, JonathanRRogers wrote: > > I've been using the Dynamic Axis plugin for several weeks to run a set > of test suites the names of which are set in the source code repository. > Normally this works great but once in a while, the word "default" is > inserted into the list of test suite names. Of course, this causes > failures since there is no test suite by that name. > > I understand that "default" is the value Dynamic Axis will use when no > variable has been defined for the axis. However, there clearly is a > value set and "default" is added to it, which is definitely the wrong > behavior. Since this only happens in a small minority of job executions, > perhaps there is a race condition. > -- > Jonathan Ross Rogers > > -- > Jonathan Rogers > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
