Frequent ClosedChannelExceptions
Since a few days we are getting tons of messages like the below in the controller log. Does anyone have an idea what the problem could be? Even though there are only INFO messages they clutter the log and something seems to have changed. 2022-07-21 11:54:55.413+ [id=1515042] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-1515042 for ECS-workflow-tests-ubuntu20.04-java17-jx2fn terminated: java.nio.channels.ClosedChannelException 2022-07-21 11:54:55.671+ [id=1519507] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-1519507 for ECS-workflow-tests-ubuntu20.04-java17-jx2fn terminated: java.nio.channels.ClosedChannelException 2022-07-21 11:54:55.947+ [id=1523846] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-1523846 for ECS-workflow-tests-ubuntu20.04-java17-jx2fn terminated: java.nio.channels.ClosedChannelException 2022-07-21 11:54:56.204+ [id=1518008] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-1518008 for ECS-workflow-tests-ubuntu20.04-java17-jx2fn terminated: java.nio.channels.ClosedChannelException Thanks, Thorsten -- 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/132db439-6b7a-4584-86a6-6284f1ae1b10n%40googlegroups.com.
Re: getting variables from a downstream job
Write files with the desired parameters in the "build" job, archive the files, and unarchive them in the downstream job. Then you can read the parameters stored in the file. Here's a sketch how we do it: In the upstream job: def downstreamParams = [:] downstreamParams.foo = 'bar' downstreamParams.bar = 'foo' writeFile file: 'my.params', text: downstreamParams.inspect() archiveArtifacts artifacts: "*.params" And in the downstream job: step([$class: 'CopyArtifact', filter: '*.params', projectName: 'upstream-project', selector: [$class: 'TriggeredBuildSelector', fallbackToLastSuccessful: true], target: '']) def upstreamParams = Eval.me(readFile(file: 'my.params')) -- 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/dda635c1-7e0d-485d-8d1d-064d90cf7c37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Shared files in pipeline library?
Most of our jobs use a bunch of common shell functions which are sourced at the beginning of the job. Currently these shell functions are in a separate repository. Since it's a pain to check out more than one repository per job, I though about moving the shell function into a global shared pipeline library which is loaded via @Library in the Jenkinsfile (we already have such a library). However, afaik the library is only checked out on the master and is not available on the slaves, i.e. I cannot source any include files in shell script commands. Is there any other convenient way to use a set of common files across many jobs and slaves? -- 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/2629c793-8d18-4599-897f-fd3b46394585%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sending mail from pipeline not working
Afaik I have to configure the contents of "mail" myself. However, I just
want the same mail sent by pipeline jobs as by freesytle jobs, i.e.
depending on the job's status with different subjects, etc. I checked the
mail server's log files and no sign of any mails sent from pipelines.
This whole pipeline stuff seems very buggy to me, not being able to send
mails is just one of many issues...
On Wednesday, March 1, 2017 at 9:53:42 AM UTC+1, Baptiste Mathus wrote:
>
> Out of curiosity, why are you using the "step" step, instead of plain
> "mail" or "email" one. I can confirm mail is working for us, and email too
> for sure. So I would look into the server logs, maybe your email is getting
> refused out for some reason due to the content or so.
>
> Did you try using the snippet generator to get the right syntax?
>
> 2017-02-27 12:48 GMT+01:00 Thorsten Meinl >:
>
>>
>> Anything interesting in the build log?
>>>
>>> Nope, only
>>
>> [Pipeline] stage[Pipeline] { (Send mail)[Pipeline] step[Pipeline]
>> }[Pipeline] // stage
>>
>>
>>
>> --
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/ff777064-1eaf-43a6-9079-fdc67df074bf%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/ff777064-1eaf-43a6-9079-fdc67df074bf%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> 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/190bf5c8-98b3-4461-b73b-0944e237df4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Remote call on Channel failed with pipeline jobs
Hi, I have several slaves running on multiple OS and executing pipeline jobs. When a (part of a ) job runs any of the Windows slaves I get tons of messages such as Cannot contact WindowsServer2012: java.io.IOException: Remote call on Channel to /172.17.xx.xx failed It seems this message is issued every time when there is a system out message from slave while it's executing a shell script. Yet, the job continues to run and finishes successfully. I couldn't find any log file where there are more details on the message and also the system out of the process on the slave doesn't show anything. Does anyone have an idea what's going on? Thanks, Thorsten -- 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/c31f06e1-e3a3-4b0e-ae00-050a2b601a47%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sending mail from pipeline not working
> Anything interesting in the build log?
>
> Nope, only
[Pipeline] stage[Pipeline] { (Send mail)[Pipeline] step[Pipeline] }[Pipeline]
// stage
--
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/ff777064-1eaf-43a6-9079-fdc67df074bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sending mail from pipeline not working
Hi, I am unable to send any mail from pipeline jobs using step([$class: 'Mailer', notifyEveryUnstableBuild: true, recipients: 'me@mail']) The mail just isn't sent. Sending mails works perfectly in freestyle jobs. Is this a bug or am I missing something? Thanks, Thorsten -- 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/d6165d02-66a7-4f42-98a4-24051afacbe4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Pipeline, parallel, and junit = broken
I've read on several places that matrix jobs in pipeline are replaced by the "parallel" step. However, this doesn't work at all with junit tests. We have a bunch of JUnit tests that are tested on different OS. They are exactly the same tests for all OS, hence also the output file names are identical. This wasn't a problem with matrix jobs because every axis was treated as an independent job and you could easily browser the tests for every configuration. With a parallel pipeline this isn't possible because all result files collect by "junit" are thrown together which makes it impossible to distinguish and also sometimes the display is just wrong (depending on which parallel branch is collected the last). In short, parallel is totally useless in such cases. Now I'm wondering if there are any plans to address this issue (I guess many users have the same problem) or if there is another approach to run the same tests on several OS with a pipeline job. -- 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/4defdd37-cb02-4969-af28-f9d99f4ff7c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Semaphore system for matrix jobs
Am 21.01.2014 17:20, schrieb Magnus Sandberg: > I was just trying to see if there's a true use case for this or not, I > have thought about this along the same lines as in "Throttle Concurrent > Builds Plugin" but for Job Groups as defined in Priority Sorter. Definitely there is a use case. The link to the commercial extensions in one of the other replies states exactly our problem. I just didn't find where to get this extension independently of the whole "Enterprise Jenkins" they want to sell. Thanks for looking into this! Thorsten -- Dr.-Ing. Thorsten Meinl KNIME.com AG Technoparkstr. 1 8005 Zurich, Switzerland signature.asc Description: OpenPGP digital signature
Re: Semaphore system for matrix jobs
Hi Magnus, The description is a bit "high-level" but it looks like this could be a fit to our problem. I'm happy to give it a try! Thorsten Am 21.01.2014 14:34, schrieb Magnus Sandberg: > Hi, > > I'm thinking about adding something like this to the Priority Sorter > (JENKINS-21214 <https://issues.jenkins-ci.org/browse/JENKINS-21214>) do > you think that would be something for you? > > /Magnus > > > 2014/1/20 Benjamin Lau <mailto:benjamin.a@gmail.com>> > > I've always managed this by limiting the executors on the host where I > run the tests... but I'm suspecting you have a set up where each of > the VMs has its own computer/node entry in Jenkins so you have one > executor for each. > > You might be able to work around this by setting up one of your > systems as the access point for the VMs and manage all the testing > from there. That way you can still host all the tests on your single > physical machine, but you can limit the number of concurrent jobs > using the existing executor feature. > > Good luck, > > Ben > > On Mon, Jan 20, 2014 at 12:31 PM, <mailto:thorsten.me...@knime.com>> wrote: > > Hi all, > > > > We have a product that we are currently testing on six different > operating > > systems. Our test jobs is a matrix job that runs on six different > slaves > > (one for each OS). However, the slaves are virtual machines on a > single host > > computer. It has enough RAM and disk space for even more VMs, but > "only" six > > cores. I.e. if all matrix subjobs run at the same time, the system > will be > > overloaded. On the other hand, sequential execution just takes too > long. We > > need a mechanism to control the maximum number of concurrent > matrix subjobs > > that are allowed to run at the same time. I haven't found any > plug-in that > > can achieve this. Ideally each slave can be assigned a semaphore (the > > physical host for the VM) that has a maximum value (the number of > jobs that > > can run at the same time). Does anybody know a way to achieve this > with > > available plug-ins? How difficult would it be to create such an > extension? > > > > Cheers, > > > > Thorsten > > > > -- > > 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 > <mailto:jenkinsci-users%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 Users" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to jenkinsci-users+unsubscr...@googlegroups.com > <mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > 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/nnZXDun4ZFE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- Dr.-Ing. Thorsten Meinl KNIME.com AG Technoparkstr. 1 8005 Zurich, Switzerland signature.asc Description: OpenPGP digital signature
Semaphore system for matrix jobs
Hi all, We have a product that we are currently testing on six different operating systems. Our test jobs is a matrix job that runs on six different slaves (one for each OS). However, the slaves are virtual machines on a single host computer. It has enough RAM and disk space for even more VMs, but "only" six cores. I.e. if all matrix subjobs run at the same time, the system will be overloaded. On the other hand, sequential execution just takes too long. We need a mechanism to control the maximum number of concurrent matrix subjobs that are allowed to run at the same time. I haven't found any plug-in that can achieve this. Ideally each slave can be assigned a semaphore (the physical host for the VM) that has a maximum value (the number of jobs that can run at the same time). Does anybody know a way to achieve this with available plug-ins? How difficult would it be to create such an extension? Cheers, Thorsten -- 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.
