[JIRA] (JENKINS-53127) Parallel sequential stages should display stage label
Title: Message Title Hokwang Lee commented on JENKINS-53127 Re: Parallel sequential stages should display stage label No responses... For now, I use pipeline after creating stages for marking name. 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-35308) Improve display of non-AbortException stack traces such as MissingPropertyException
Title: Message Title
Craig Ringer commented on JENKINS-35308
Re: Improve display of non-AbortException stack traces such as MissingPropertyException
People who get stuck here, check for WorkflowScript in your stack traces. That's your Jenkinsfile. This has caused me a lot of difficulty as I learn to work with pipelines, though knowing the above makes life much easier. So a big +1 for improving it. *I worked around it in my pipelines; see below for code*. The simplest improvement would be to use [StackTraceUtils](http://docs.groovy-lang.org/latest/html/api/org/codehaus/groovy/runtime/StackTraceUtils.html) to sanitize the Groovy stuff. It could also use `StackTraceUtils.addClassTest(...)` to filter out some limited Jenkins and pipeline internals, though some care is needed not to remove important info "above" the application failure. Can't Jenkins potentially just walk the stack trace and transform `WorkflowScript` to the `${pipeline-script}` name, or annotate the name with the script-name? That alone would be a huge help, and pretty simple. Bonus points for abbreviating stack traces at `WorkflowScript.run`with a `...` - the rest of the stack isn't really that interesting if you know you got to the point of successful pipeline execution. I tried to work around it in my Groovy scripts with an outer try/catch block in which I ran:
try {
// pipeline here
} catch (e) {
currentBuild.result = 'FAILURE'
StackTraceUtils.sanitize(e)
throw e
}
... but it doesn't seem to remove anything much. Even when I add my own class filters (see below). Using `StackTraceUtils.printSanitizedStackTrace(e)` has the same effect. Note that the docs for StackTraceUtils.sanitize appear to be wrong. It doesn't return the exception - it returns null. Attempting to
// this is wrong, do not do this
throw StackTraceUtils.sanitize(e)
will yield the amazingly uninformative exception:
java.lang.NullPointerException
at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:42)
when you try to throw null. I also wrote a filter to cut some of the crud out:
StackTraceUtils.addClassTest({
def result
switch (it) {
/* The Jenkinsfile itself */
case 'WorkflowScript':
result = true
break
/* Innards we don't care about */
case ~/^org.jenkinsci.plugins.workflow/:
result = false
break
case ~/^org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox/:
result = false
break
case ~/^hudson.remoting/:
result = false
break
case
[JIRA] (JENKINS-54112) Jenkins fails to restart after EC2 plugin upgrade
Title: Message Title Grant Pedersen commented on JENKINS-54112 Re: Jenkins fails to restart after EC2 plugin upgrade I added the new permission and upgraded the plugin. I had to update the Groovy script that I use to register the EC2 Cloud due to a constructor change to the UnixData class. Unfortunately I encountered a similar error message after spinning up a build executor and then rebooting: java.lang.NullPointerException at hudson.plugins.ec2.EC2Computer.getState(EC2Computer.java:128) at hudson.plugins.ec2.EC2RetentionStrategy.start(EC2RetentionStrategy.java:176) at hudson.plugins.ec2.EC2RetentionStrategy.start(EC2RetentionStrategy.java:48) at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:145) at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) at hudson.model.Queue._withLock(Queue.java:1380) at hudson.model.Queue.withLock(Queue.java:1257) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) at jenkins.model.Nodes$9.run(Nodes.java:348) at hudson.model.Queue._withLock(Queue.java:1380) at hudson.model.Queue.withLock(Queue.java:1257) at jenkins.model.Nodes.load(Nodes.java:339) at jenkins.model.Jenkins$13.run(Jenkins.java:3113) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1069) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Add Comment This message
[JIRA] (JENKINS-54199) Error loading Blue Ocean for Project
Title: Message Title
Martin Reinhardt updated an issue
Jenkins / JENKINS-54199
Error loading Blue Ocean for Project
Change By:
Martin Reinhardt
When viewing a pipeline job in blue ocean I'm getting the following error in the browser console: {code:bash}TypeError: undefined is not an object (evaluating 'result.toLowerCase'){code} With this stack trace:{code:bash} [Error] Error fetching page – TypeError: undefined is not an object (evaluating 'result.toLowerCase')TypeError: undefined is not an object (evaluating 'result.toLowerCase')getI18nTitle — blueocean-core-js.js:54379render — blueocean-core-js.js:53687_renderValidatedComponentWithoutOwnerOrContext — jenkins-design-language.js:49621_renderValidatedComponent — jenkins-design-language.js:49644performInitialMount — jenkins-design-language.js:49184mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420updateChildren — jenkins-design-language.js:48743_reconcilerUpdateChildren — jenkins-design-language.js:54357_updateChildren — jenkins-design-language.js:54456updateChildren — jenkins-design-language.js:54443_updateDOMChildren — jenkins-design-language.js:50747updateComponent — jenkins-design-language.js:50565receiveComponent — jenkins-design-language.js:50527receiveComponent — jenkins-design-language.js:55499_updateRenderedComponent — jenkins-design-language.js:49576_performComponentUpdate — jenkins-design-language.js:49546updateComponent — jenkins-design-language.js:49467receiveComponent —
[JIRA] (JENKINS-54199) Error loading Blue Ocean for Project
Title: Message Title Martin Reinhardt created an issue Jenkins / JENKINS-54199 Error loading Blue Ocean for Project Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-10-23 05:04 Priority: Minor Reporter: Martin Reinhardt TypeError: undefined is not an object (evaluating 'result.toLowerCase') [Error] Error fetching page – TypeError: undefined is not an object (evaluating 'result.toLowerCase') TypeError: undefined is not an object (evaluating 'result.toLowerCase')getI18nTitle — blueocean-core-js.js:54379render — blueocean-core-js.js:53687_renderValidatedComponentWithoutOwnerOrContext — jenkins-design-language.js:49621_renderValidatedComponent — jenkins-design-language.js:49644performInitialMount — jenkins-design-language.js:49184mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent —
[JIRA] (JENKINS-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title remi P edited a comment on JENKINS-40501 Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter "When referring to a "List Subversion Tags" parameter I got an empty string."That's the defect.To reproduce: * create a parametrized job * use a List Subversion tag parameter named "myTag" * try to reference $myTag parameter inside AC Reference Parameter plugin * you will get an empty string instead of the tag string valueReproduced with Jenkins 2.138.2, Subversion plugin 2.12.1 and Active Choice plugin 2.1This issue should be reopened. 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title remi P edited a comment on JENKINS-40501 Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter "When referring to a "List Subversion Tags" parameter I got an empty string."That's the defect.To reproduce: * create parametrized job * use a List Subversion tag parameter named "myTag" * try to reference $myTag parameter inside AC Reference Parameter plugin * you will get an empty string instead of the tag string valueReproduced with Jenkins 2.138.2, Subversion plugin 2.12.1 and Active Choice plugin 2.1 This issue should be reopened. 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title remi P commented on JENKINS-40501 Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter "When referring to a "List Subversion Tags" parameter I got an empty string." That's the defect. To reproduce: create parametrized job use a List Subversion tag parameter named "myTag" try to reference $myTag parameter inside AC Reference Parameter plugin you will get an empty string instead of the tag string value Reproduced with Jenkins 2.138.2, Subversion plugin 2.12.1 and Active Choice plugin 2.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-54198) Results are overriden with parallel builds
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54198 Results are overriden with parallel builds Change By: Olivier Lamy Labels: maven-invoker-plugin-1.6 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-54198) Results are overriden with parallel builds
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-54198 Results are overriden with parallel builds Issue Type: Bug Assignee: Olivier Lamy Components: maven-invoker-plugin Created: 2018-10-23 04:05 Priority: Critical Reporter: Olivier Lamy 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-40999) Recursive symlink causes high resource utilization, termination of slave process in ArchiveArtifact and Publish JUnit results steps.
Title: Message Title Michael Barker commented on JENKINS-40999 Re: Recursive symlink causes high resource utilization, termination of slave process in ArchiveArtifact and Publish JUnit results steps. This issue is also affecting us. Our build tool (Buck) creates symlinks that create loops within the directory structure. I think a general fix for infinitely recursing issue would be to track the canonical path current being traversed and stop if it is revisited. If I were to get this patched in Ant, would updating the ant version for Jenkins fix this for all of the plugins that use FileSet based scanning (TAP Results, Checkstyle, etc.)? What version of Ant does Jenkins need to use. I see that it is currently on 1.9.2. Does it need to stay on the 1.9.x line? 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Mark Waite edited a comment on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Thanks for a clear bug report. Much appreciated!I can't duplicate the problem with the systems currently available to me. I've created a [test job|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-54186/Jenkinsfile] which uses `milestone` and `checkout scm` as described in the bug report and have run it successfully in several different multibranch Pipelines on my [test server|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/README.md].I don't have convenient access to install the Disable GitHub Multibranch Status plugin on that test server. The hotel where I'm staying on business travel blocks my ssh access to my test servers at home.Could you attempt to run your failing Declarative Pipeline on a server which does not have the 'Disable GitHub Multibranch Status' plugin installed?I won't be able to explore this further for at least another two weeks due to business and personal travel. In the interest of full disclosure, I ran my tests on the latest released versions of all the workflow plugins and the latest pre-release of the git plugin and git client plugin. The specific plugin binaries I used are on the lts-with-plugins branch of my docker-lfs repository. 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Mark Waite Component/s: disable-github-multibranch-status-plugin Component/s: git-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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Mark Waite Assignee: Mark Waite 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Mark Waite commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Thanks for a clear bug report. Much appreciated! I can't duplicate the problem with the systems currently available to me. I've created a test job which uses `milestone` and `checkout scm` as described in the bug report and have run it successfully in several different multibranch Pipelines on my test server. I don't have convenient access to install the Disable GitHub Multibranch Status plugin on that test server. The hotel where I'm staying on business travel blocks my ssh access to my test servers at home. Could you attempt to run your failing Declarative Pipeline on a server which does not have the 'Disable GitHub Multibranch Status' plugin installed? I won't be able to explore this further for at least another two weeks due to business and personal travel. 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-54190) All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-54190 All of the parallel stages with a regression post trigger will trigger if one of the stages fail. Change By: Andrew Bayer Assignee: Mads Nielsen Andrew Bayer 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-54190) All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54190 All of the parallel stages with a regression post trigger will trigger if one of the stages fail. Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: blueocean-plugin Component/s: pipeline Component/s: postbuild-task-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-47131) Jenkinsfile errors shows Java stacktrace without Jenkinsfile line number
Title: Message Title
Craig Ringer commented on JENKINS-47131
Re: Jenkinsfile errors shows Java stacktrace without Jenkinsfile line number
It'd be a massive help to transform `WorkflowScript` in traces to the value of `${pipeline-script}` or annotate it with the same. Even better to also abbreviate the trace after `WorkflowScript.run`. See related JENKINS-35308 .
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-54197) Allow combining site and room fields
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-54197 Allow combining site and room fields Issue Type: Improvement Assignee: Naresh Rayapati Components: hubot-steps-plugin Created: 2018-10-23 01:57 Priority: Minor Reporter: Steve Todorov Currently you are limited to using either `site` or the `room` fields. You cannot combine them. This is not very convenient, because you might want to configure multiple `sites` globally and then just fine-tune the `room` in the specific job's pipeline. Consider the following example: hubotSend message: 'Releasing Test project.', site: 'devops-report-site', status: 'FAILURE', room: 'devops' Add Comment
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Thank you very much for your help, looking forward to your good news. 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-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template
Title: Message Title Yunge Zhu commented on JENKINS-54188 Re: Allow "tool locations" to be configured per Azure Virtual Machine Template thanks for reporting the issue. we're evaluating it and update later. 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 Robert Middleton updated JENKINS-54120 Jenkins / JENKINS-54120 Output directory or source file null. Change By: Robert Middleton Status: Open Fixed but Unreleased 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-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template
Title: Message Title Yunge Zhu started work on JENKINS-54188 Change By: Yunge Zhu 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-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template
Title: Message Title Yunge Zhu assigned an issue to Jie Shen Jenkins / JENKINS-54188 Allow "tool locations" to be configured per Azure Virtual Machine Template Change By: Yunge Zhu Assignee: Azure DevOps Jie Shen 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 Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. My best guess is that it is a problem with the packaging; I've never encountered that error under normal circumstances. It almost seems like it's trying to install the pbuilder dependency package twice, since just before it fails it says "pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0)" Here's an example of a good build: https://jenkins.rm5248.com/view/CSerial/job/CSerial-debian/23/architecture=armhf/console Note that there could also be a problem with the buster build at the moment; try making sure it works with stretch first. Finally, closing this issue since it appears to be a packaging problem now; I did however add a new check for a bad source directory: https://github.com/jenkinsci/debian-pbuilder-plugin/commit/1ceda90ce782f73d0b0f67210d524fc01d7db7c6 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-30184) Macros in "Commit Status URL" lead to bad triggered and started commit status
Title: Message Title Ryan Gilbert edited a comment on JENKINS-30184 Re: Macros in "Commit Status URL" lead to bad triggered and started commit status Also having this issue on 1.42.0. This appears to be because variables such as $BUILD_NUMBER are not available at the time GHPRB tries to find it. 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-30184) Macros in "Commit Status URL" lead to bad triggered and started commit status
Title: Message Title Ryan Gilbert commented on JENKINS-30184 Re: Macros in "Commit Status URL" lead to bad triggered and started commit status Also having this issue on 1.42.0. 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Oh, the one from JNA 4.2.1 worked fine for me. 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Craig Rodrigues commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I'm asking you which JNA release has the library you need: https://github.com/java-native-access/jna/releases 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies edited a comment on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I did not have the above problem when install installing Jenkins 2.135.1-1 from https://pkg.jenkins.io/redhat -stable /. I can see from https://jenkins.io/changelog/ that in Jenkins 2.136 the following: Update JNA from 4.2.1 to 4.5.2 to add support for s390x, update GNU C minimal requirement to 2.7 on Unix platforms. (issue 52771) Apparently, the JNA 4.5.2 version added support for some things but removed support for other things. Can the JNA version included with Jenkins add back the Linux ppc64 support for libjnidispatch.so? 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I did not have the above problem when install Jenkins 2.135.1-1 from https://pkg.jenkins.io/redhat-stable/. I can see from https://jenkins.io/changelog/ that in Jenkins 2.136 the following: Update JNA from 4.2.1 to 4.5.2 to add support for s390x, update GNU C minimal requirement to 2.7 on Unix platforms. (issue 52771) Apparently, the JNA 4.5.2 version added support for some things but removed support for other things. Can the JNA version included with Jenkins add back the Linux ppc64 support for libjnidispatch.so? 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-37739) Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline
Title: Message Title Matt Calderaz commented on JENKINS-37739 Re: Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline Just encountered this issue today in overhauling CI for our RF tests; it's not critical, but a fix would be greatly appreciated. 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Hi, Craig. I am not sure what you are asking me. 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Josh McDonald updated JENKINS-53900 Jenkins / JENKINS-53900 Stage graph in Blue Ocean not showing all stages for large workflows Change By: Josh McDonald 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Josh McDonald commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows PR (waiting on some dogfood issues for building) https://github.com/jenkinsci/blueocean-plugin/pull/1836 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-1878) Ability to move job to top of queue
Title: Message Title Palash Hedau updated an issue Jenkins / JENKINS-1878 Ability to move job to top of queue Change By: Palash Hedau 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-50576) EC2 plugin provisions only one worker at a time
Title: Message Title FABRIZIO MANFREDI closed an issue as Fixed From 1.40.x there is a new algorithm to raise nodes, and in 1.41 there is a option to "no wait" to speed up the operation. Jenkins / JENKINS-50576 EC2 plugin provisions only one worker at a time Change By: FABRIZIO MANFREDI Status: Open Closed Resolution: Fixed Released As: 1.40 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-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio updated JENKINS-49713 Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: lucamilanesio 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-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio commented on JENKINS-49713 Re: gerrit-plugin exposes change-requests as normal branches instead of pull-requests It was a bit tricky, but I've managed to introduce the new 'Changes' category: https://github.com/jenkinsci/gerrit-code-review-plugin/pull/18 More work will follow to make the branch name more "readable" 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Craig Rodrigues commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Which release has it: https://github.com/java-native-access/jna/releases ? 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Devin Nusbaum edited a comment on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin Fixed in Pipeline Nodes and Processes 2.24. See [ my comment here |https://issues.jenkins-ci.org/browse/JENKINS-28822?focusedCommentId=350058=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-350058] for an overview of the changes , but in short, externally aborted tasks should throw FlowInterruptedException, while tasks that fail in the script itself should throw AbortException . 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Devin Nusbaum edited a comment on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin Fixed in Pipeline Nodes and Processes 2.24. See my comment here for an overview of the changes. 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Devin Nusbaum edited a comment on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin Fixed in Pipeline Nodes and Processes 2.24. See [ my comment here |https://issues.jenkins-ci.org/browse/JENKINS-28822?focusedCommentId=350058=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-350058] for an overview of the changes. 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Devin Nusbaum updated JENKINS-28822 Fixed in Pipeline Nodes and Processes 2.24. See my comment here for an overview of the changes. Jenkins / JENKINS-28822 Can't distinguish between durable task abort and failure in workflow plugin Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-durable-task-step 2.24 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-53837) Node steps are not correctly associated with their WorkflowRun through the Queue.Task API when restarting Pipelines
Title: Message Title Devin Nusbaum commented on JENKINS-53837 Re: Node steps are not correctly associated with their WorkflowRun through the Queue.Task API when restarting Pipelines Fixed in workflow-durable-task-step 2.24. 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-53837) Node steps are not correctly associated with their WorkflowRun through the Queue.Task API when restarting Pipelines
Title: Message Title Devin Nusbaum updated JENKINS-53837 Jenkins / JENKINS-53837 Node steps are not correctly associated with their WorkflowRun through the Queue.Task API when restarting Pipelines Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-durable-task-step 2.24 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I opened https://issues.jenkins-ci.org/browse/JENKINS-54196 for the problem I found today related to this. 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-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies created an issue Jenkins / JENKINS-54196 Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-22 21:44 Environment: # uname -a Linux localhost 3.10.0-693.el7.ppc64 #1 SMP Thu Jul 6 20:01:28 EDT 2017 ppc64 ppc64 ppc64 GNU/Linux java -version java version "1.8.0_171" Java(TM) SE Runtime Environment (build 8.0.5.16 - pxp6480sr5fp16-20180524_01(SR5 FP16)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux ppc64-64-Bit Compressed References 20180523_387150 (JIT enabled, AOT enabled) OpenJ9 - c81abfb OMR - f3f8112 IBM - 4f87eeb) JCL - 20180515_01 based on Oracle jdk8u171-b11 Labels: jenkins Priority: Major Reporter: Peter Toennies rpm -q jenkins jenkins-2.138.2-1.1.noarch Today I tried upgrade from jenkins-2.89.4-1.1 to jenkins 2.138.2-1.1 on a RHEL7 ppc64 machine. I am getting a java.lang.UnsatisfiedLinkError for 'Native library (com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path'. The complete output is: Unit jenkins.service has begun starting up. Oct 22 12:57:10 runuser[20830]: pam_unix(runuser:session): session opened for user root by (uid=0) Oct 22 12:57:12 jenkins[20825]: Starting Jenkins Exception in
[JIRA] (JENKINS-54168) Jacoco: "RuntimeException: While reading class directory"
Title: Message Title Cyrille Le Clerc commented on JENKINS-54168 Re: Jacoco: "RuntimeException: While reading class directory" Keith Collison how often do you face this error? I faced it once or twice and then it disappeared so I ignored assuming it was a problem with my development environment 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-54195) Add support for p4 clean
Title: Message Title John Rocha created an issue Jenkins / JENKINS-54195 Add support for p4 clean Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2018-10-22 21:18 Priority: Minor Reporter: John Rocha I would like to have the ability to invoke 'p4 clean'. I want my workspace cleaned of all files that are not part of the repo. So I start fresh again, but without doing a 'get latest.' We have a build environment where we will build for 32B, and then our quality process requires that the workspace be reset/cleaned and then build for 64B. I do not want to do a sync and clean, because new commits could have occurred after the 32B started, meaning a sync and clean just before 64B would pull in new changes and and they would not contain the same contents. Add Comment
[JIRA] (JENKINS-54192) Add missing help description for sorting and number of columns configuration options
Title: Message Title Tommy Tynjä commented on JENKINS-54192 Re: Add missing help description for sorting and number of columns configuration options Proposed solution: https://github.com/Diabol/delivery-pipeline-plugin/pull/286 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-54194) Support paging for Jenkins pipelines based views
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-54194 Support paging for Jenkins pipelines based views Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2018-10-22 21:10 Environment: Delivery Pipeline plugin 1.2.0 Priority: Major Reporter: Tommy Tynjä Currently, Jenkins pipeline based views does not support paging as the view for traditional build jobs do. This is a feature which is handy when there is a desire to retain a larger number of pipeline runs where not all of them are necessarily needed to be visualized in the view. Limiting the amount of rendered pipelines by using paging also allows for improved performance for this use case. Proposed solution is to address the paging option for the class WorkflowPipelineView in the same manner as for DeliveryPipelineView. Add Comment
[JIRA] (JENKINS-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä started work on JENKINS-54193 Change By: Tommy Tynjä 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-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä commented on JENKINS-54193 Re: Ability to limit number of pipelines shown in Jenkins pipeline based views Proposed solution: https://github.com/Diabol/delivery-pipeline-plugin/pull/287 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-54192) Add missing help description for sorting and number of columns configuration options
Title: Message Title Tommy Tynjä started work on JENKINS-54192 Change By: Tommy Tynjä 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-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-54193 Ability to limit number of pipelines shown in Jenkins pipeline based views Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2018-10-22 21:01 Environment: Delivery Pipeline plugin 1.2.0 Priority: Minor Reporter: Tommy Tynjä Currently, it is not possible to limit the number of pipelines shown in Jenkins pipelines based views (implemented in WorkflowPipelineView). This is an option that is available for views based on traditional build jobs chained together with downstream dependencies (implemented in DeliveryPipelineView). This configuration is particularly of interest when combined with e.g. sorting functionality to limit the number of pipelines shown in the view (e.g. when displayed on a big screen TV). Add Comment
[JIRA] (JENKINS-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä assigned an issue to Tommy Tynjä Jenkins / JENKINS-54193 Ability to limit number of pipelines shown in Jenkins pipeline based views Change By: Tommy Tynjä Assignee: Patrik Boström Tommy Tynjä 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 updated an issue
Jenkins / JENKINS-54168
Jacoco: "RuntimeException: While reading class directory"
Change By:
Cyrille Le Clerc
* multibranch pipeline* Jenkinsversion 2.144. {noformat}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 com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:182) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at
[JIRA] (JENKINS-54192) Add missing help description for sorting and number of columns configuration options
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-54192 Add missing help description for sorting and number of columns configuration options Issue Type: Improvement Assignee: Tommy Tynjä Components: delivery-pipeline-plugin Created: 2018-10-22 20:53 Environment: Delivery Pipeline Plugin 1.2.0 Priority: Minor Reporter: Tommy Tynjä The sorting and number of columns configuration options lacks a help description on the UI configuration page for Jenkins pipeline based views. Add Comment
[JIRA] (JENKINS-54191) Persist task finished time
Title: Message Title Tommy Tynjä updated an issue Jenkins / JENKINS-54191 Persist task finished time Change By: Tommy Tynjä Attachment: dpp_task_persist_2.png Attachment: dpp_task_persist_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-54191) Persist task finished time
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-54191 Persist task finished time Issue Type: Improvement Assignee: Patrik Boström Attachments: dpp_task_persist_1.png, dpp_task_persist_2.png Components: delivery-pipeline-plugin Created: 2018-10-22 20:45 Environment: Delivery Pipeline Plugin 1.2.0 Priority: Minor Reporter: Tommy Tynjä The Delivery Pipeline plugin allows for fine grained visualization of tasks within a Jenkins pipeline stage if the task pipeline step is used. However, the task specific status of a finished task is not persisted so the information is lost in case the Jenkins master requires a restart. Example of a finished pipeline run: However, if Jenkins is restarted, the whole stage is shown as failed (as the information is currently derived directly from the stage, instead of the task): This Jira issue is aiming to address the current behavior and to provide a solution for persisting information about successfully finished pipeline tasks.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio updated an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: lucamilanesio Comment: Duplicate of JENKINS-49897 ? 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies updated JENKINS-15792 Jenkins / JENKINS-15792 jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Change By: Peter Toennies Status: In Review 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies updated JENKINS-15792 Jenkins / JENKINS-15792 jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Change By: Peter Toennies Status: Resolved In 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-53757) Exec Failure: Expected HTTP 101 response but was '403 Forbidden'
Title: Message Title Brett Cashman commented on JENKINS-53757 Re: Exec Failure: Expected HTTP 101 response but was '403 Forbidden' Hi, any update on this? Still running into the same issue, and based on what I'm seeing in the logs it's unclear what the problem might be. 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-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing Olivier Lamy Can you please just tell us when is it expected to tackle this issue ? 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I compared the jenkins.war file between jenkins-2.89.4-1.1 and jenkins 2.138.2-1.1 and found these differences affecting the above. The 2.89 jenkins.war file contains jna-4.2.1.jar and the 2.138 jenkins.war file contains jna-4.5.2.jar. I unjarred both of these and found that the 2.89 jna-4.2.1.jar file has these these libjnidispatch.so files: ./com/sun/jna/linux-x86/libjnidispatch.so ./com/sun/jna/linux-x86-64/libjnidispatch.so ./com/sun/jna/linux-arm/libjnidispatch.so ./com/sun/jna/linux-aarch64/libjnidispatch.so ./com/sun/jna/linux-ppc64/libjnidispatch.so ./com/sun/jna/linux-ppc64le/libjnidispatch.so ./com/sun/jna/linux-sparcv9/libjnidispatch.so ./com/sun/jna/sunos-x86/libjnidispatch.so ./com/sun/jna/sunos-x86-64/libjnidispatch.so ./com/sun/jna/sunos-sparc/libjnidispatch.so ./com/sun/jna/sunos-sparcv9/libjnidispatch.so ./com/sun/jna/freebsd-x86/libjnidispatch.so ./com/sun/jna/freebsd-x86-64/libjnidispatch.so ./com/sun/jna/openbsd-x86/libjnidispatch.so ./com/sun/jna/openbsd-x86-64/libjnidispatch.so and then jna-4.5.2 jar file has these: ./com/sun/jna/linux-x86/libjnidispatch.so ./com/sun/jna/linux-x86-64/libjnidispatch.so ./com/sun/jna/linux-arm/libjnidispatch.so ./com/sun/jna/linux-armel/libjnidispatch.so ./com/sun/jna/linux-aarch64/libjnidispatch.so ./com/sun/jna/linux-ppc/libjnidispatch.so ./com/sun/jna/linux-ppc64le/libjnidispatch.so ./com/sun/jna/linux-mips64el/libjnidispatch.so ./com/sun/jna/linux-s390x/libjnidispatch.so ./com/sun/jna/sunos-x86/libjnidispatch.so ./com/sun/jna/sunos-x86-64/libjnidispatch.so ./com/sun/jna/sunos-sparc/libjnidispatch.so ./com/sun/jna/sunos-sparcv9/libjnidispatch.so ./com/sun/jna/freebsd-x86/libjnidispatch.so ./com/sun/jna/freebsd-x86-64/libjnidispatch.so ./com/sun/jna/openbsd-x86/libjnidispatch.so ./com/sun/jna/openbsd-x86-64/libjnidispatch.so It looks like the jna-4.5.2.jar file is not including these: ./com/sun/jna/linux-ppc64/libjnidispatch.so ./com/sun/jna/linux-sparcv9/libjnidispatch.so And added these: ./com/sun/jna/linux-armel/libjnidispatch.so ./com/sun/jna/linux-ppc/libjnidispatch.so ./com/sun/jna/linux-mips64el/libjnidispatch.so ./com/sun/jna/linux-s390x/libjnidispatch.so I think I really need ./com/sun/jna/linux-ppc64/libjnidispatch.so in order for Jenkins to work on our ppc64 machines. Can this be added back? Is there a workaround? Add Comment
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Tiger Cheng commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Also following and in agreement with Vasily that it is expected that if the childjob is asking for a node that is run by the parent node, that it should be allowed access to the node. Without this expectation working, our complex pipeline is unable to properly archive artifacts in the ideal clean manner it was designed for. The alternative is to seek for a solution to archive from nodes 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-54147) SSH protocol not supported
Title: Message Title Andy Airey commented on JENKINS-54147 Re: SSH protocol not supported Seems Bitbucket Server support is not yet fully implemented in Jenkins X: https://github.com/jenkins-x/jx/issues/38 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-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio started work on JENKINS-49713 Change By: lucamilanesio 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-54190) All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Title: Message Title
Junze He created an issue
Jenkins / JENKINS-54190
All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Issue Type:
Bug
Assignee:
Mads Nielsen
Components:
blueocean-plugin, pipeline, postbuild-task-plugin
Created:
2018-10-22 19:03
Environment:
Worker Operating Systems: Debian Stretch Jenkins ver 2.138 Pipeline ver 2.5 Blue Ocean 1.8.3
Priority:
Minor
Reporter:
Junze He
This happens only if that stage fails before the other stages. If the failing stage happens last then the stages which have already completed as passing do not have their regression post conditions triggered. Otherwise, the currentBuild.currentResult of the other stages, which should be passing, become FAILURE despite all of the steps being green.
// Sample Jenkinsfile to test this
#!groovy
pipeline {
agent {
node {
label ""
customWorkspace "workspace/test_regression"
}
}
options {
buildDiscarder(logRotator(numToKeepStr: '50'))
compressBuildLog()
timestamps()
}
stages {
stage('Parallel'){
parallel {
stage("Passing Stage 1") {
options {
timeout(time: 120, unit: 'MINUTES')
}
steps {
sh "ls"
}
post {
regression {
echo "This stage has a regression"
echo "Current Result: ${currentBuild.currentResult}"
echo "Previous Build Result: ${currentBuild.previousBuild.result}"
}
}
}
stage("Failing Stage 1") {
options {
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Since this ticket was already resolved fixed, should I open a new one to report the problem? 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-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title James Housley edited a comment on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) I was having this issue when using " origin " as the "Name" of my git repository in the job's settings, and then using e.g. "abc/def" as my branch specifier. Removing the Name and instead using "origin/abc/def" as my branch specifier fixed the issue. 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-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title James Housley commented on JENKINS-50401 Re: Checkout resolution misbehaves with local branch and forward slashes I was having this issue when using "origin" as the "Name" of my git repository in the job's settings, and then using e.g. "abc/def" as my branch specifier. Removing the Name and instead using "origin/abc/def" as my branch specifier fixed the issue. 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Today I tried upgrade from jenkins-2.89.4-1.1 to jenkins 2.138.2-1.1 on a RHEL7 ppc64 machine. I am getting a java.lang.UnsatisfiedLinkError for 'Native library (com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path'. The complete output is: – Unit jenkins.service has begun starting up. Oct 22 12:57:10 runuser[20830]: pam_unix(runuser:session): session opened for user root by (uid=0) Oct 22 12:57:12 jenkins[20825]: Starting Jenkins Exception in thread "main" java.lang.reflect.InvocationTargetException Oct 22 12:57:12 jenkins[20825]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Oct 22 12:57:12 jenkins[20825]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) Oct 22 12:57:12 jenkins[20825]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) Oct 22 12:57:12 jenkins[20825]: at java.lang.reflect.Method.invoke(Method.java:508) Oct 22 12:57:12 jenkins[20825]: at Main._main(Main.java:227) Oct 22 12:57:12 jenkins[20825]: at Main.main(Main.java:160) Oct 22 12:57:12 jenkins[20825]: Caused by: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path (file:/tmp/jna7389605851826903872jar, file:/tmp/akuma9008425977486382467jar) Oct 22 12:57:12 jenkins[20825]: at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:962) Oct 22 12:57:12 jenkins[20825]: at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) Oct 22 12:57:12 jenkins[20825]: at com.sun.jna.Native.(Native.java:190) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.CLibrary.(CLibrary.java:89) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:128) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:116) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.Daemon.daemonize(Daemon.java:106) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.Daemon.all(Daemon.java:88) Oct 22 12:57:12 jenkins[20825]: ... 6 more Oct 22 12:57:12 runuser[20830]: pam_unix(runuser:session): session closed for user root Oct 22 12:57:12 jenkins[20825]: [FAILED] Oct 22 12:57:12 systemd[1]: jenkins.service: control process exited, code=exited status=1 Oct 22 12:57:12 systemd[1]: Failed to start LSB: Jenkins Automation Server. – Subject: Unit jenkins.service has failed – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – -- Unit jenkins.service has failed. – -- The result is failed. Jenkins starts up fine with 2.89.4-1.1, but not with the most recent stable version of 2.138.2-1.1. Is this a regression? Does anyone have suggestions on how to get Jenkins to start? Do I need to download something additional? Also, I tried to search for libjnidispatch.so on my system with Jenkins 2.89 but could not find it. Where should this file be at? Thank you, Peter
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title James Housley commented on JENKINS-37263 Re: Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) I was having this issue when using origin as the "Name" of my git repository in the job's settings, and then using e.g. "abc/def" as my branch specifier. Removing the Name and instead using "origin/abc/def" as my branch specifier fixed the issue. 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-45927) CauseOfBlockage of items in Queue is extremely verbose
Title: Message Title
Alex Taylor commented on JENKINS-45927
Re: CauseOfBlockage of items in Queue is extremely verbose
OK there is a way to workaround this issue by installing the Simple Theme Plugin which is to add a Theme Element of `Extra CSS` under `Manage Jenkins> Configre System` which contains the following data:
.build-details {
max-height:100px !important;
overflow: auto !important;
width:100% !important;
}
#tt {
overflow:hidden;max-height:200px;
}
This will restrict any pop up box to a certain size and truncate the rest which stops the UI from being blocked by this popup
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-17984) Changing "Idle termination time" on a cloud instance killed the running job
Title: Message Title FABRIZIO MANFREDI closed an issue as Fixed Solved in a more recent version of the plugin Jenkins / JENKINS-17984 Changing "Idle termination time" on a cloud instance killed the running job Change By: FABRIZIO MANFREDI Status: Open Closed Assignee: Francis Upton FABRIZIO MANFREDI 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-33004) Regression: Describe instances finding instances from another jenkins
Title: Message Title FABRIZIO MANFREDI updated JENKINS-33004 A jenkins ID tag is added to instance Jenkins / JENKINS-33004 Regression: Describe instances finding instances from another jenkins Change By: FABRIZIO MANFREDI Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.41 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-34412) EC2 plugin finds nodes that match the AMI associated with a label, but not the label itself
Title: Message Title FABRIZIO MANFREDI resolved as Fixed from 1.40 the nodes are matched also with the description not only by AMI Jenkins / JENKINS-34412 EC2 plugin finds nodes that match the AMI associated with a label, but not the label itself Change By: FABRIZIO MANFREDI Status: Open 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-43628) Jenkins slaves were started and stopped during master restart
Title: Message Title FABRIZIO MANFREDI updated JENKINS-43628 In the 1.39 has been solved the problem of stopped node, in 1.41 there are several improvements on stopped nodes Jenkins / JENKINS-43628 Jenkins slaves were started and stopped during master restart Change By: FABRIZIO MANFREDI Status: Open Fixed but Unreleased Assignee: Francis Upton FABRIZIO MANFREDI Resolution: Fixed Released As: 1.41 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
[JIRA] (JENKINS-43677) Update use of AWS SDK plugin to 1.11.119
Title: Message Title FABRIZIO MANFREDI resolved as Fixed Jenkins / JENKINS-43677 Update use of AWS SDK plugin to 1.11.119 Change By: FABRIZIO MANFREDI Status: Open Resolved Resolution: Fixed Released As: 1.40 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-43791) Make launch timeout configurable
Title: Message Title FABRIZIO MANFREDI updated JENKINS-43791 From 1.40 there is a new algorithm to raise nodes, that is much faster, in the 1.41 there is also a option for no wait. Jenkins / JENKINS-43791 Make launch timeout configurable Change By: FABRIZIO MANFREDI Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.41 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-43855) Not able to use ec2-plugin
Title: Message Title FABRIZIO MANFREDI closed an issue as Not A Defect Jenkins / JENKINS-43855 Not able to use ec2-plugin Change By: FABRIZIO MANFREDI 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-54139) Jacoco report rendering problem in multi module projects
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-54139 Re: Jacoco report rendering problem in multi module projects 33 [~prospero238] can you please test version 3 .5.15-beta-3 no longer disabling the Jacoco publisher. withMaven will detect that multiple jacoco reports have been generated and will not publish reports automatically.https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.15-beta-3 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-46850) When does the plugin decide to launch a new instance
Title: Message Title FABRIZIO MANFREDI updated JENKINS-46850 Jenkins / JENKINS-46850 When does the plugin decide to launch a new instance Change By: FABRIZIO MANFREDI Status: In Review Closed 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-54139) Jacoco report rendering problem in multi module projects
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-54139 Re: Jacoco report rendering problem in multi module projects 33.5.15-beta- 4 3 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-46850) When does the plugin decide to launch a new instance
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-46850 Change By: FABRIZIO MANFREDI 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-46850) When does the plugin decide to launch a new instance
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-46850 Re: When does the plugin decide to launch a new instance The ec2-plugin implements very simple algorithm (vers > 1.40): if NodeProvisioner requested X executors, start to raise X/N nodes (N is number of executors on each node). if there is any orphant nodes (~not known by Jenkins at all), take them in account (and start if it's neccessary) if there is not enough orphant nodes - raise needed nodes in parallel give them back to NodeProvisioner in RUNNING state 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-46850) When does the plugin decide to launch a new instance
Title: Message Title FABRIZIO MANFREDI updated JENKINS-46850 Jenkins / JENKINS-46850 When does the plugin decide to launch a new instance Change By: FABRIZIO MANFREDI 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-46963) ec2-plugin
Title: Message Title FABRIZIO MANFREDI closed an issue as Cannot Reproduce Jenkins / JENKINS-46963 ec2-plugin Change By: FABRIZIO MANFREDI Status: Open Closed Resolution: Cannot Reproduce 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-49814) Jenkins trying to stop already stopped agent
Title: Message Title FABRIZIO MANFREDI updated JENKINS-49814 Fixed in the 1.41 Jenkins / JENKINS-49814 Jenkins trying to stop already stopped agent Change By: FABRIZIO MANFREDI Status: Open Fixed but Unreleased 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-50472) Doesn't work with AWS Beijing Region (cn-north-1)
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-50472 Re: Doesn't work with AWS Beijing Region (cn-north-1) The list of the regions depends on he AWS SDK plugin version, and also of the account configured, not by ec2-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-50472) Doesn't work with AWS Beijing Region (cn-north-1)
Title: Message Title FABRIZIO MANFREDI closed an issue as Fixed Jenkins / JENKINS-50472 Doesn't work with AWS Beijing Region (cn-north-1) Change By: FABRIZIO MANFREDI Status: In Progress Closed 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-50472) Doesn't work with AWS Beijing Region (cn-north-1)
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-50472 Change By: FABRIZIO MANFREDI 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-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI updated an issue Jenkins / JENKINS-53952 Linux slaves are not starting anymore Change By: FABRIZIO MANFREDI Comment: [https://github.com/jenkinsci/ec2-plugin/pull/252 :|https://github.com/jenkinsci/ec2-plugin/pull/252]It implements very simple algorithm: * if NodeProvisioner requested X executors, start to raiseX/N nodes (N is number of executors on each node). * if there is any orphant nodes (~not known by Jenkins at all), takethem in account (and start if it's neccessary) * if there is not enough orphant nodes - raise needed nodes in parallel * give them back to NodeProvisioner in RUNNING state 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-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53952 Re: Linux slaves are not starting anymore https://github.com/jenkinsci/ec2-plugin/pull/252 : It implements very simple algorithm: if NodeProvisioner requested X executors, start to raise X/N nodes (N is number of executors on each node). if there is any orphant nodes (~not known by Jenkins at all), take them in account (and start if it's neccessary) if there is not enough orphant nodes - raise needed nodes in parallel give them back to NodeProvisioner in RUNNING state 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-46963) ec2-plugin
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-46963 Re: ec2-plugin Hi, I think is is in the wrong queue. Can I close it ? 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-48111) EC2 plugin: update instance types list
Title: Message Title FABRIZIO MANFREDI updated JENKINS-48111 Fixed in 1.41. it is enough to update the AWS sdk plugin Jenkins / JENKINS-48111 EC2 plugin: update instance types list Change By: FABRIZIO MANFREDI 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-48111) EC2 plugin: update instance types list
Title: Message Title FABRIZIO MANFREDI updated JENKINS-48111 Jenkins / JENKINS-48111 EC2 plugin: update instance types list Change By: FABRIZIO MANFREDI 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.
