[JIRA] (JENKINS-32944) if only one hypervisor, there are no virtual machines selectable
Title: Message Title Treussart Matthieu updated an issue Jenkins / JENKINS-32944 if only one hypervisor, there are no virtual machines selectable Change By: Treussart Matthieu Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32944) if only one hypervisor, there are no virtual machines selectable
Title: Message Title Treussart Matthieu commented on JENKINS-32944 Re: if only one hypervisor, there are no virtual machines selectable Still an issue, config : Jenkins 2.138.2 + Libvirt Slaves plugin 1.8.5 + org.libvirt:libvirt:0.4.7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54170) Kubernetes agent does not connect on first several attempts
Title: Message Title John Jeffers created an issue Jenkins / JENKINS-54170 Kubernetes agent does not connect on first several attempts Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-10-20 05:15 Environment: Jenkins 2.138.2 running in Kubernetes using jenkins/jenkins:2.138.2 image Kubernetes plugin 1.13.0 Priority: Minor Reporter: John Jeffers I'm seeing long wait times for kubernetes build slaves to run jobs. What appears to be happening is the Jenkins master is refusing connection, but eventually accepts, at which time the build slave registers and start running the job. Here's a representative example of logs from the JNLP container when this is happening. You will see several failed attempts to connect, then it accepts the connection. This is easily reproducible. Sometimes it connects relatively quickly, other times it takes 5 minutes or so before it finally accepts the connection. Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Oct 20, 2018 4:57:41 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: jenkins-slave-w5dwq-sdx28 Oct 20, 2018 4:57:41 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Oct 20, 2018 4:57:41 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.23 Oct 20, 2018 4:57:41 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Oct 20, 2018 4:57:41 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among https://jenkins.mycompany.com/ Oct 20, 2018 4:57:42 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect,
[JIRA] (JENKINS-23265) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Title: Message Title Bruno P. Kinoshita commented on JENKINS-23265 Re: TestLink plugin indicates test case as "not run" and TestLink is not updated with build status Sobhit Sharma not updates from my, sorry. I am not using the plug-in, nor is my current employer, and at spare time I am working on other open source projects right now, so not much time left to volunteer on this plug-in. But if anyone suggests a fix through a pull request, I'd be happy to have a look, review, merge, and release a new version. I put this plug-in up for adoption, so anybody willing to contribute for a longer time and would like to be the maintainer, just get in touch. If anybody's environment is broken, and a fix is desperately needed, CloudBees offers paid services to manage plug-ins. Cheers Bruno Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52292) Support Multiple Vault IDs
Title: Message Title joel damata commented on JENKINS-52292 Re: Support Multiple Vault IDs +1 for this feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title
Christoph Loesch commented on JENKINS-54120
Re: Output directory or source file null.
ok, added to Source-Code-Management: Additional Behaviours: Check out to a sub-directory: source to be sure i checked the wiki and noticed i did it exactly as described in Project Setup(Traditional) now it stops here:
...
Fetching upstream changes from https://salsa.debian.org/debian/olsrd.git
> git fetch --tags --progress https://salsa.debian.org/debian/olsrd.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision aa2a47024230b443052c5b07163ec2f76361c7e0 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f aa2a47024230b443052c5b07163ec2f76361c7e0
Commit message: "d/control: Remove trailing whitespaces"
> git rev-list --no-walk aa2a47024230b443052c5b07163ec2f76361c7e0 # timeout=10
$ dpkg-parsechangelog --version
[olsrd] $ dpkg-parsechangelog --count 1
We do not appear to have an actual package
Build step 'Debian Pbuilder' marked build as failure
Finished: FAILURE
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Hit this again today. This has become an annoyance for us, since when we push a change to a Job DSL job, we frequently see this behavior on any running instances of that job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31448) NPE in update center on restart
Title: Message Title AnneTheAgile commented on JENKINS-31448 Re: NPE in update center on restart Oleg Nenashev do you mean that this ticket was resolved 'fixed' by you since it should be deleted/cancelled and you re-made it elsewhere? (So the 'fix' is that ticket should not be here/open.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title
AnneTheAgile edited a comment on JENKINS-54031
Re: GitHub OAuth plugin fails with Jenkins 2.146
[~jkmatt] fyi, the upgrade guide referenced in above PR against this ticket adds;{code:java}As a workaround, it is possible to temporarily disable part of the security hardening by setting the https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties[Java system properties] `hudson.model.AbstractItem.skipPermissionCheck` and `hudson.model.Run.skipPermissionCheck` to `true`. {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title AnneTheAgile commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Matt Friedman fyi, the upgrade guide referenced above adds; As a workaround, it is possible to temporarily disable part of the security hardening by setting the https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties[Java system properties] `hudson.model.AbstractItem.skipPermissionCheck` and `hudson.model.Run.skipPermissionCheck` to `true`. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-53750
Re: Shell scripts keep the working directory locked on Windows
> {quote} I think the issue was introduced in this commit: [https://github.com/jenkinsci/durable-task-plugin/commit/8c3504398e5c9292512410077da0e67eaae1c4c4], which is the one that added the timestamp-updating background job. {quote} Ah, you're right, it probably was introduced in that commit.Either way, I'd recommend moving the directory manipulation into your shell scripts and then combining them so that your script can be run and tested independently from Jenkins and so it is not as susceptible to changes in the implementation of the {{sh}}/{{bat}} steps.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48106) java.io.EOFException continue occur when using health check with aws network load balancer
Title: Message Title Jeff Thompson commented on JENKINS-48106 Re: java.io.EOFException continue occur when using health check with aws network load balancer Are you still seeing this issue? Can you provide further information about what is happening? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title Devin Nusbaum commented on JENKINS-53750 Re: Shell scripts keep the working directory locked on Windows > I think the issue was introduced in this commit: https://github.com/jenkinsci/durable-task-plugin/commit/8c3504398e5c9292512410077da0e67eaae1c4c4, which is the one that added the timestamp-updating background job. Ah, you're right, it probably was introduced in that commit. Either way, I'd recommend moving the directory manipulation into your shell scripts and then combining them so that your script can be run and tested independently from Jenkins and so it is not as susceptible to changes in the implementation of the sh/bat steps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-47834 Add the support for Remoting work dir configuration of JNLP Launcher Change By: Jeff Thompson Component/s: libvirt-slave-plugin Component/s: slave-setup-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-47834 Add the support for Remoting work dir configuration of JNLP Launcher Change By: Jeff Thompson Labels: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Devin Nusbaum commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Sam Van Oort I was about to write a similar comment with the same suspicions, (but thankfully refreshed the page before doing so!), and I agree that decreasing the check frequency here as you suggest seems like it would help. I think the ideal solution would be to buffer the logs on the remote end and send them across the wire at line boundaries where possible, but as you said, that seems significantly more complicated to get right. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Devin Nusbaum edited a comment on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps [~svanoort] I was about to write a similar comment with the same suspicions, (but thankfully refreshed the page before doing so!), and I agree that decreasing the check frequency [here|https://github.com/jenkinsci/durable-task-plugin/blob/d12aa576cb5400907b215662f051b99f83995fc9/src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java#L497] as you suggest seems like it would help. I think the ideal solution would be to buffer the logs on the remote end in durable-task and send them across the wire at line boundaries where possible, but as you said, that seems significantly more complicated to get right. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50703) Jenkins slave jar retained context when Jenkins master was offline
Title: Message Title Jeff Thompson commented on JENKINS-50703 Re: Jenkins slave jar retained context when Jenkins master was offline Can you provide additional information on reproducing this? Anything relevant about configuration, plugins, environment, or how this is observed. Logs would certainly be useful. My initial, simple attempts at reproduction were unsuccessful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50703) Jenkins slave jar retained context when Jenkins master was offline
Title: Message Title Jeff Thompson assigned an issue to Jeff Thompson Jenkins / JENKINS-50703 Jenkins slave jar retained context when Jenkins master was offline Change By: Jeff Thompson Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Thanks Lars Bilke – digging in, it seems this has pointed to the problem: we have a bug here with the log indexing, which for parallel steps it is showing parallels running shell steps is switching from one branch to another with just a few bytes of log at a time. My suspicion for Jesse Glick is that we have a combination of the Controller.watch API (which sends logs from a shell step in 100 ms slices) plus the indexing which is trying to index with each of these mini-slices of log. The crude solution would be to set up so we're sending logs from the Shell/Batch/Powershell steps less frequently (say, every 5s or so). This would greatly reduce the interleaving. For controller.watch without the log handling rewrite, this probably wasn't as much of an issue because the log data came in larger batches. We could also consider trying to buffer and consolidate those writes (at either end) but I suspect that will be considerably more complex to do correctly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Hide Evergreen Jenkins plugin for non-evergreen installs
Title: Message Title Baptiste Mathus updated JENKINS-54167 Jenkins / JENKINS-54167 Hide Evergreen Jenkins plugin for non-evergreen installs Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Hide Evergreen Jenkins plugin for non-evergreen installs
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54167 Hide Evergreen Jenkins plugin for non-evergreen installs Change By: Baptiste Mathus Summary: Fix Hide Evergreen Jenkins plugin description in the update center for non-evergreen installs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus commented on JENKINS-54167 Re: Fix plugin description in the update center Note: again thanks to Daniel I finally chose an even better path: PR has been filed against the UC generation repo to hide evergreen Jenkins plugin. As we're using anyway only incrementals releases on evergreen distribution, this is fine. This Jenkins plugin becomes invisible to standard installs, which if what we want. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus updated JENKINS-54167 Jenkins / JENKINS-54167 Fix plugin description in the update center Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54169) Download of newer version does not use proxy configuration
Title: Message Title James Richard assigned an issue to Richard Otte Jenkins / JENKINS-54169 Download of newer version does not use proxy configuration Change By: James Richard Assignee: Gavin Killough Richard Otte Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54169) Download of newer version does not use proxy configuration
Title: Message Title Patrick Ruckstuhl created an issue Jenkins / JENKINS-54169 Download of newer version does not use proxy configuration Issue Type: Bug Assignee: Gavin Killough Components: blackduck-detect-plugin Created: 2018-10-19 19:18 Priority: Major Reporter: Patrick Ruckstuhl As far as I can tell, the fetching of a newer version of blackduck detect (e.g. when configured as latest). It doesn't use the proxy settings (and therefore fails to download). For the scanning it does use it. Add Comment
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus commented on JENKINS-54167 Re: Fix plugin description in the update center Daniel just told me that now pom.xml is mostly ignored, so this is extracted from index.jelly. Fixing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus started work on JENKINS-54167 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53467) task Mailer misses getSmtpHost()
Title: Message Title Joseph Petersen edited a comment on JENKINS-53467 Re: task Mailer misses getSmtpHost() [~mwyraz] it is now released in mailer plugin as 1.22 (y) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53467) task Mailer misses getSmtpHost()
Title: Message Title Joseph Petersen commented on JENKINS-53467 Re: task Mailer misses getSmtpHost() Michael mich...@wyraz.de it is now released as 1.22 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Lars Bilke edited a comment on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I uploaded a build directory of an affected build run: [ https://d.pr/f/vz7Gjk +|https://d.pr/f/vz7Gjk] Maybe I can provide some more info next week .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Lars Bilke edited a comment on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I uploaded a build directory of an affected build run: http https :// drops d . bilke.co pr / f/ vz7GjkMaybe I can provide some more info next week .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Lars Bilke edited a comment on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I attached uploaded a build directory of an affected build run :http://drops . bilke.co/vz7Gjk Maybe I can provide some more info next week .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Mark Waite edited a comment on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) I'm seeing this as well in the Jenkins log. It seems to be an [intentional message|https://github.com/jenkinsci/workflow-job-plugin/blob/0f39d7cd0b70ab2505191e0090c034a64f517d7a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java#L1064] from workflow-job-plugin.Now I'll need to reconsider how I test specific bugs with Pipeline jobs. I've used the groovy post build plugin to read the logfile from the manager object, but that is apparently no longer a preferred action. Any hints of the preferred replacement for getLogFile()? That message was [added to workflow-job-plugin 2 years ago|https://github.com/jenkinsci/workflow-job-plugin/commit/e6a58e8e2d30f7faa6941694ff58770cc14f50e7]. I'm a little ashamed I didn't detect the message sooner , though looking at the tags which include that commit, it seems to have first appeared in workflow-job-plugin 2 . 26, not in any of the preceding plugin releases . Maybe I'm not as inattentive as I thought . .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Mark Waite edited a comment on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) I'm seeing this as well in the Jenkins log. It seems to be an [intentional message|https://github.com/jenkinsci/workflow-job-plugin/blob/0f39d7cd0b70ab2505191e0090c034a64f517d7a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java#L1064] from workflow-job-plugin.Now I'll need to reconsider how I test specific bugs with Pipeline jobs. I've used the groovy post build plugin to read the logfile from the manager object, but that is apparently no longer a preferred action. Any hints of the preferred replacement for getLogFile()? That message was [added to workflow-job-plugin 2 years ago|https://github.com/jenkinsci/workflow-job-plugin/commit/e6a58e8e2d30f7faa6941694ff58770cc14f50e7]. I'm a little ashamed I didn't detect the message sooner... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Mark Waite commented on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) I'm seeing this as well in the Jenkins log. It seems to be an intentional message from workflow-job-plugin. Now I'll need to reconsider how I test specific bugs with Pipeline jobs. I've used the groovy post build plugin to read the logfile from the manager object, but that is apparently no longer a preferred action. Any hints of the preferred replacement for getLogFile()? That message was added to workflow-job-plugin 2 years ago. I'm a little ashamed I didn't detect the message sooner... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54128 Timestamper causes lots of WARNING messages in the log (getLogFile call) Change By: Mark Waite Component/s: timestamper-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45469) Missing Pipeline DSL step exception is not caught by try-catch
Title: Message Title Taras Postument commented on JENKINS-45469 Re: Missing Pipeline DSL step exception is not caught by try-catch And there is nothing to be done? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Lars Bilke commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I attached a build directory of an affected build run. Maybe I can provide some more next week .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps By the way if you are able to create a support bundle using the support-core plugin, which includes thread dumps as well as many other things (as you choose), it attempts to anonymize any strings appearing in text files that look like job names etc. But yes, feel free to send any files privately. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Beck commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Amending upgrade guide in https://github.com/jenkins-infra/jenkins.io/pull/1843 – would appreciate if someone could try the amended instructions so we know these are a complete workaround. Can also be done while Jenkins is running (until the next restart) by running the following script console script: hudson.model.AbstractItem.SKIP_PERMISSION_CHECK = true hudson.model.Run.SKIP_PERMISSION_CHECK = true Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title
Prem Gangana edited a comment on JENKINS-50975
Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root
- > Having - is for uniformity sake since you were having jenkins-lib - ${NODE_NAME}-${JOB_ NAME}. -> Deleting the client is actually what i was going to ask you about. Cleaning up the client is needed here, otherwise the clients are going to get stacked up.-> How about using BUILD_NUMBER ?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title
Prem Gangana commented on JENKINS-50975
Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root
> Having - is for uniformity sake since you were having jenkins-lib${NODE_NAME}-${JOB_ NAME}. -> Deleting the client is actually what i was going to ask you about. Cleaning up the client is needed here, otherwise the clients are going to get stacked up. -> How about using BUILD_NUMBER ?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Beck commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Oh, right. That makes sense. That's controlled by a different system property: hudson.model.Run.skipPermissionCheck. You'll need to set both to true. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48500) Jenkins List view missing some jobs when using regex filter
Title: Message Title Sven Schoenung updated an issue Jenkins / JENKINS-48500 Jenkins List view missing some jobs when using regex filter Change By: Sven Schoenung Component/s: core Component/s: view-job-filters-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48500) Jenkins List view missing some jobs when using regex filter
Title: Message Title Sven Schoenung edited a comment on JENKINS-48500 Re: Jenkins List view missing some jobs when using regex filter 1. This isn't an issues issue with the view-job-filters plugin since you're using the stock Jenkins regex filter.2. Try selecting "Recurse in subfolders". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48500) Jenkins List view missing some jobs when using regex filter
Title: Message Title Sven Schoenung commented on JENKINS-48500 Re: Jenkins List view missing some jobs when using regex filter 1. This isn't an issues with the view-job-filters plugin since you're using the stock Jenkins regex filter. 2. Try selecting "Recurse in subfolders". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32496) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard
Title: Message Title Sven Schoenung resolved as Fixed Fixed in view-job-filters 2.0.4. Jenkins / JENKINS-32496 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard Change By: Sven Schoenung Status: Open Resolved Assignee: Sven Schoenung Resolution: Fixed Released As: https://github.com/jenkinsci/view-job-filters-plugin/releases/tag/view-job-filters-2.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-14916) Stackoverflow in annonymous mode
Title: Message Title Sven Schoenung resolved as Fixed Fixed in view-job-filters 2.0.4. Jenkins / JENKINS-14916 Stackoverflow in annonymous mode Change By: Sven Schoenung Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/view-job-filters-plugin/releases/tag/view-job-filters-2.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Matt Friedman commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Daniel Beck Setting the property only partially fixed the issue for us. We downgraded to get back full functionality. IIRC, it allowed access to the summary page for a build, but not to things like console log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
Title: Message Title Sven Schoenung resolved as Fixed Jenkins / JENKINS-13464 Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459 Change By: Sven Schoenung Status: Open Resolved Assignee: Jacob Robertson Sven Schoenung Resolution: Fixed Released As: https://github.com/jenkinsci/view-job-filters-plugin/releases/tag/view-job-filters-2.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
Title: Message Title Sven Schoenung commented on JENKINS-13464 Re: Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459 Fixed in view-job-filters 2.0.4. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54168) Jacoco: "RuntimeException: While reading class directory"
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-54168 Jacoco: "RuntimeException: While reading class directory" Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-10-19 16:30 Priority: Minor Reporter: Cyrille Le Clerc multibranch pipeline Jenkinsversion 2.144. java.lang.RuntimeException: While reading class directory: /var/lib/jenkins/jobs/myproject/branches/main/builds/561/jacoco/classes at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:131) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:110) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:339) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:326) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:657) at org.jenkinsci.plugins.pipeline.maven.publishers.JacocoReportPublisher.process(JacocoReportPublisher.java:213) at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118) at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1053) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:368) at
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Jon B Yes, we can understand the potential security concerns (though they're less than with overall build). With those concerns in mind, you can email the thread dump in private to Jesse and I (svano...@cloudbees.com and jgl...@cloudbees.com). We'd appreciate any other information you can supply (the workflow subfolder of the build above, Pipeline scripts, etc). Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23265) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Title: Message Title Sobhit Sharma commented on JENKINS-23265 Re: TestLink plugin indicates test case as "not run" and TestLink is not updated with build status I am also facing this issue. Any update on this ? Bruno P. Kinoshita Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54114) Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins?
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54114 Re: Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins? This message comes from the OS, so maybe ssh-agent is not in the path. Cannot run program "ssh-agent": CreateProcess error=2, The system cannot find the file specified Also, keep in mind that ssh-agent should run per user session, so should be started when Jenkins do login on the agent (~/.bashrc usually) see https://unix.stackexchange.com/questions/72552/whats-the-purpose-of-ssh-agent I'm using latest jenkins server on windows, I tried all the solutions available for similar kind of problems but none of them worked out, How can I fix this ? ssh-agent is running in back ground if ps -p $SSH_AGENT_PID > /dev/null > then > echo "ssh-agent is already running" > # Do something knowing the pid exists, i.e. the process with $PID is running > else > eval ssh-agent -s > fi ssh-agent is already running Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54156) Fails to run when non "Default" version is used
Title: Message Title James Richard assigned an issue to Richard Otte Jenkins / JENKINS-54156 Fails to run when non "Default" version is used Change By: James Richard Assignee: Gavin Killough Richard Otte Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54005) Trying to unexport an object that's already unexported (is back)
Title: Message Title Jeff Thompson commented on JENKINS-54005 Re: Trying to unexport an object that's already unexported (is back) PR is merged. I'll get it out in the next release when I can. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54114) Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins?
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54114 Re: Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins? Yep, you need it https://issues.jenkins-ci.org/browse/JENKINS-36997 https://github.com/jenkinsci/ssh-agent-plugin/pull/17 https://github.com/janvrany/ssh-agent-plugin/blob/9b7c44a95f88dd284f90eb49c7420baa54f46895/src/main/java/com/cloudbees/jenkins/plugins/sshagent/exec/ExecRemoteAgentFactory.java#L58-L76 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jon B edited a comment on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps [~svanoort] Someone on our security team advised me to take caution with respect to posting a thread dump from our Jenkins. Is there some way for me to share this privately without such that the thread dump is not viewable to the public internet? I would try to open the dump files and scrape out anything that looks scary by hand but I'd much prefer to not post it publicly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54114) Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins?
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54114 Re: Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins? IIRC ssh-agent plugin uses the ssh-agent local native implementation since some versions ago, you must install the ssh-agent package in the OS. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54167 Fix plugin description in the update center Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Beck commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Could I get confirmation that setting the system property I mentioned in a previous comment works in fact for nobody who's affected? Because that would be a related core bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54167
Fix plugin description in the update center
Change By:
Baptiste Mathus
h3. Problem statementIt should be clear that the Evergreen Jenkins plugin is not designed to be installed on a non-evergreen Jenkins instance.But currently for some reason, [ despite the fact I wrote |https://github.com/jenkinsci/evergreen-plugin/blob/evergreen-0.9/pom.xml] {{Jenkins Evergreen Plugin - Note: you should generally never install this plugin yourself.}}In the plugin manager, it looks like: !screenshot-1.png! h4. Expected behaviorThe end of that message should be visible. I suppose there's a tokenization that cuts after the hyphen or something. Probably we just remove it and that's enough.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jon B commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Sam Van Oort Someone on our security team advised me to take caution with respect to posting a thread dump from our Jenkins. Is there some way for me to share this privately without such that the thread dump is not viewable to the public internet? I would try to open the dump files and scrape out anything that looks scary by hand but I'd much prefer to not post it publicly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54167
Fix plugin description in the update center
Change By:
Baptiste Mathus
h3. Problem statementIt should be clear that the Evergreen Jenkins plugin is not designed to be install installed on a non-evergreen Jenkins instance.But currently for some reason, despite the fact I wrote {{Jenkins Evergreen Plugin - Note: you should generally never install this plugin yourself.}} In the plugin manager, it looks like: !screenshot-1.png! h4. Expected behavior The end of that message should be visible. I suppose there's a tokenization that cuts after the hyphen or something. Probably we just remove it and that's enough.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54167 Fix plugin description in the update center Change By: Baptiste Mathus Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Jon B Lars Bilke kutzi We've pulled this from the update center, but still would badly like to solve this bug. In order to try to resolve this, we're asking if you could supply as much information as you feel comfortable about the builds that were running at the time the problem manifested. Specifically, if there's any way you could be persuaded to upload a ZIP / tar.gz of the build folder for those builds (appropriately censored), it would be extremely helpful. Especially helpful: the Pipeline and Shared Library code run, the 'workflow' subdirectory (contains XML files describing the build's step structure), the log file for the builds, and the log-index file for the build (both inside the build directory). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54167) Fix plugin description in the update center
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54167 Fix plugin description in the update center Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen, evergreen-plugin Created: 2018-10-19 15:42 Priority: Major Reporter: Baptiste Mathus Problem statement It should be clear that the Evergreen Jenkins plugin is not designed to be install on a non-evergreen Jenkins instance. But currently for some reason, despite the fact I wrote Expected behavior Add Comment
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jon B updated an issue Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Jon B The graph here in this description more clearly depicts whats going on. I'm the only one using this jenkins server today... you can !image-2018-10-14-17-35-11-037.png|width=657,height=137!Around 5pm, i kicked off a pipeine. The pipeline builds a container and then uses that container to run some pytests...!image-2018-10-14-17-36-52-958.png|width=329,height=367!It is during that last "postbuild" phase, the CPU runs real hot. While the pytest shards are running, they are just doing a pytest run and then i capture the junit.xml file.The reason why this is a problem is that with too many of these running at the same time, Jenkins blips out and we cannot contact the web interface because when the CPU is pegged.. it basically crashes the master.Here are details about my jenkins:My jenkins is 100% current: * Jenkins ver. 2.147 * Please note I did today accept the plugin updates described on [https://github.com/jenkinsci/jep/blob/master/jep/210/README.adoc#abstract] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Jesse Glick commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies I do not know exactly what -Dscope=compile is supposed to do, but without that option the artifact does appear in compile scope, and if you either exclude the transitive dependency chain via the jsch plugin or update the plugin to a version without a dependency on that library, it appears in test scope. When I look at the help for the option you gave, I see Note that this feature does not currently work due to MSHARED-4 whether or not that message is still accurate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53862) Blue Ocean spinner animation uses 25-50% CPU
Title: Message Title Vivek Pandey assigned an issue to Nicolae Pascu Jenkins / JENKINS-53862 Blue Ocean spinner animation uses 25-50% CPU Change By: Vivek Pandey Assignee: Nicolae Pascu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title David Matejcek edited a comment on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 Same problem, it seems the problem is the old GIT 1.7.10.4 installed on Debian 7.11. Workaround: delete the repository and don't use shallow clone with this version of GIT. I got no problem with git 2.17.1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title
James Nord edited a comment on JENKINS-53957
Re: hpi bundles transitive dependencies of test scope dependencies
is there a [ link to the fix for above case|https://github.com/jenkinsci/maven-plugin/pull/121] ? I do not think closing this as WONT_FIX is correct. when \ {{mvn -Dverbose org.apache.maven.plugins:maven-dependency-plugin:3.1.1:tree -Dscope=compile }}does not list an artifact yet it is included in the hpi this says something is very wrong.developers are used to the standard tools provided by Maven, if you are saying they are wrong then that is one thing but please report issues upstream about why they are wrong as well.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps CC Daniel Beck – the PR to pull this from the update center is https://github.com/jenkins-infra/update-center2/pull/247 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title David Matejcek commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 Same problem, it seems the problem is the old GIT 1.7.10.4 installed on Debian 7.11. Workaround: delete the repository and don't use shallow clone with this version of GIT. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title
James Nord commented on JENKINS-53957
Re: hpi bundles transitive dependencies of test scope dependencies
is there a link to the fix? I do not think closing this as WONT_FIX is correct. when {{mvn -Dverbose org.apache.maven.plugins:maven-dependency-plugin:3.1.1:tree -Dscope=compile }}does not list an artifact yet it is included in the hpi this says something is very wrong. developers are used to the standard tools provided by Maven, if you are saying they are wrong then that is one thing but please report issues upstream about why they are wrong as well.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Decided to pull this from the update center pending better diagnostics. If we could pinpoint the root cause of the CPU usage, I suspect I could offer a fix the same day, but so far we have not gotten enough data. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Jesse Glick resolved as Won't Fix maven-hpi-plugin was behaving correctly in this case; it was the maven-plugin POM which was wrong (indirectly, via another POM). I offered a fix. Jenkins / JENKINS-53957 hpi bundles transitive dependencies of test scope dependencies Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title James Nord commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies I have no doubt that the maven-plugin has a hairy pom (which is why I was using it as an internal test case for some tooling - hence why I found this error ). Just flagging as another case I found for prosperity. Now if I can work out why the optional handling in my Maven / my tool is wrong I may just go an try and complete maven-hpi-plugin#23 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50960) Pipeline jobs hangs after restart with build trigger step
Title: Message Title Sam Van Oort commented on JENKINS-50960 Re: Pipeline jobs hangs after restart with build trigger step Lucie Votypkova Is this still reproducible? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Jesse Glick commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies maven-plugin has a quite complex POM. I suspect you will find there is some more “interesting” explanation for this JAR’s presence, which is not normally present in plugin archives despite all having the same jenkins-test-harness test dep. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz updated JENKINS-54166 Jenkins / JENKINS-54166 Date parameter is lost upon restart Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title
Jesse Glick edited a comment on JENKINS-54073
Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
It would also be interesting to know whether setting the JVM option {{\-Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=false}} has any apparent effect. If so, this would mean that there is a performance issue with watch mode, perhaps caused by more frequent transmission of stdout packets from {{sh}} steps, which could presumably be tweaked in various ways: decreasing the log check frequency (currently hard-coded at 100ms); collecting all output into a memory buffer on the agent side and changing {{DurableTaskStep.HandlerImpl}} to do a single {{ProxyOutputStream.write}} call, letting it choose a potentially larger window size ({{Channel.PIPE_WINDOW_SIZE}} 1Mb?) than the 4k used by {{IOUtils.copy}}.On the other hand, this update has been released for weeks and is active even without the rest of JEP-210 (it just means the stdout would get directed a little differently on the master side, after receiving the packets); and the streaming mode used by the now-default watch system is much closer to how freestyle builds have always sent stdout.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Michael DeGuzis commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin Hmm ok, I will check into that. I was hoping to restrict this at the node level. I'm not entirely sure how to achieve this with that plugin, but maybe I missed something. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz started work on JENKINS-54166 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-54166 Date parameter is lost upon restart Issue Type: Bug Assignee: Pierre Beitz Components: date-parameter-plugin Created: 2018-10-19 14:31 Priority: Major Reporter: Pierre Beitz Upon restart, the date parameter plugin is losing the date value. Reproduction Scenario 1. Create a job with a date parameter and use it (for instance in a shell script). 2. Put Jenkins in quiet mode 3. Trigger a build of the job 4. Restart 5. After restart, the job will fail with: ERROR: Build step failed with exception java.lang.IllegalArgumentException: Null value not allowed as an environment variable: DATE at hudson.EnvVars.put(EnvVars.java:356) at hudson.model.StringParameterValue.buildEnvironment(StringParameterValue.java:56) at me.leejay.jenkins.dateparameter.DateParameterValue.buildEnvironment(DateParameterValue.java:81) at hudson.model.ParametersAction.buildEnvVars(ParametersAction.java:89) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:90) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title James Nord reopened an issue Jenkins / JENKINS-53957 hpi bundles transitive dependencies of test scope dependencies Change By: James Nord Resolution: Won't Fix Status: Resolved Reopened Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title James Nord commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies There is another occurrence of this that I have found. maven-plugin 3.1.2 includes findbugs-annotations which is from a test scope dependency. org.jenkins-ci.main:maven-plugin:hpi:3.1.2 +- org.jenkins-ci.plugins:javadoc:jar:1.0:compile +- org.jenkins-ci.plugins:mailer:jar:1.7:compile +- org.jenkins-ci.plugins:junit:jar:1.6:compile +- org.jenkins-ci.main.maven:maven-agent:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven-interceptor:jar:1.12-alpha-1:compile +- org.jvnet.hudson:maven2.1-interceptor:jar:1.2:compile +- org.jenkins-ci.main.maven:maven3-agent:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven31-agent:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven32-agent:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven33-agent:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven35-agent:jar:1.12-alpha-1:compile | - org.apache.maven:maven-repository-metadata:jar:3.5.0:compile +- org.jenkins-ci.main.maven:maven3-interceptor:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven31-interceptor:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven32-interceptor:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven33-interceptor:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven35-interceptor:jar:1.12-alpha-1:compile +- org.jenkins-ci.main.maven:maven3-interceptor-commons:jar:1.12-alpha-1:compile +- org.apache.maven:maven-core:jar:3.1.0:compile | +- org.apache.maven:maven-model:jar:3.1.0:compile | +- org.apache.maven:maven-settings:jar:3.1.0:compile | +- org.apache.maven:maven-settings-builder:jar:3.1.0:compile | +- org.apache.maven:maven-artifact:jar:3.1.0:compile | +- org.apache.maven:maven-plugin-api:jar:3.1.0:compile | +- org.apache.maven:maven-model-builder:jar:3.1.0:compile | +- org.codehaus.plexus:plexus-interpolation:jar:1.16:compile | - org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile +- org.apache.maven:maven-compat:jar:3.1.0:compile +- org.apache.maven:maven-aether-provider:jar:3.1.0:compile +- org.apache.maven:maven-embedder:jar:3.1.0:compile | +- org.sonatype.plexus:plexus-cipher:jar:1.7:compile | - commons-cli:commons-cli:jar:1.2:compile +- org.eclipse.aether:aether-api:jar:1.1.0:compile +- org.eclipse.aether:aether-impl:jar:1.1.0:compile +- org.eclipse.aether:aether-spi:jar:1.1.0:compile +- org.eclipse.aether:aether-util:jar:1.1.0:compile +- org.eclipse.aether:aether-transport-wagon:jar:1.1.0:compile +- org.eclipse.aether:aether-connector-basic:jar:1.1.0:compile +- org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.3:compile | +- javax.enterprise:cdi-api:jar:1.0:compile | | +- javax.annotation:jsr250-api:jar:1.0:compile | | - javax.inject:javax.inject:jar:1:compile | - org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.3.3:compile +- org.apache.maven.wagon:wagon-http:jar:3.0.0:compile | - org.apache.maven.wagon:wagon-http-shared:jar:3.0.0:compile | - org.jsoup:jsoup:jar:1.7.2:compile +- org.jenkins-ci.plugins:apache-httpcomponents-client-4-api:jar:4.5.3-2.1:compile | +- org.apache.httpcomponents:httpclient:jar:4.5.3:compile | | - org.apache.httpcomponents:httpcore:jar:4.4.6:compile | +- org.apache.httpcomponents:httpmime:jar:4.5.3:compile | +- org.apache.httpcomponents:fluent-hc:jar:4.5.3:compile | - org.apache.httpcomponents:httpclient-cache:jar:4.5.3:compile +- org.jenkins-ci.plugins:jsch:jar:0.1.54.1:compile | +- com.jcraft:jsch:jar:0.1.54:compile | - org.jenkins-ci.plugins:ssh-credentials:jar:1.12:compile | - org.jenkins-ci.plugins:credentials:jar:1.21:compile +-
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps It would also be interesting to know whether setting the JVM option -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=false has any apparent effect. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Matt Friedman commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 fisnik hajredini It prevents us from upgrading Jenkins from a version that has security issues. I'd call that critical also. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis closed an issue as Not A Defect Jenkins / JENKINS-54162 Cannot delete pod that doesn't start properly Change By: Stefanos Kalantzis Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title fisnik hajredini commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 We run an open source software, and its quite important for our external contributors to be able to view their build progress. This bugs Priority was on Moderate but i increased it to Critical. I hope thats fine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Sam Van Oort Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53576) Configuration-as-Code compatibility
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-53576 Configuration-as-Code compatibility Change By: Tim Jacomb Released As: 2.9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53467) task Mailer misses getSmtpHost()
Title: Message Title Oleg Nenashev updated JENKINS-53467 Jenkins / JENKINS-53467 task Mailer misses getSmtpHost() Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Mailer 1.22 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick started work on JENKINS-54073 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps kutzi understood, and thanks for the thread dump—while it is not sufficient to conclusively diagnose the issue, it at least offers some hints. To anyone interested in trying an experimental patch, please install this update and let me know if it helps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54114) Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins?
Title: Message Title Devin Nusbaum commented on JENKINS-54114 Re: Why am I getting an error as couldn't find ssh agent even though the ssh agent is ruining in Jenkins? deepinside 14 Is the ssh-agent program installed on your build agent? What kind of build agent and shell are you running? Did this work for you previously, or is this the first time you are trying it? I am not sure why I am the default assignee here, as I am not very familiar with the plugins involved. CC Ivan Fernandez Calvo who may have a better idea of what to look at. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
