[JIRA] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env
Title: Message Title Roy Lu updated JENKINS-55718 Jenkins / JENKINS-55718 Support ALM15SSO/Make sure the login process could work in some problematic ALM env Change By: Roy Lu 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-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jean-Paul G updated an issue Jenkins / JENKINS-55308 intermittent "terminated" messages using sh in Pipelines Change By: Jean-Paul G Component/s: docker 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-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jean-Paul G commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines Not specific to docker. Have the very same issue when running sh step with parallel 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Did a bit of socializing, but I do enjoy a quiet corner and a book, or hotel room with good Internet connection and some project to work on Alex, I had a look at the bug and it is indeed quite easy to reproduce with your XML. From what I remember, we were using the analysis plugin... but looks like... it's no more? Looks like there's a new warnings plugin. And they suggest for others to write a groovy parser... which would be simple to do for CCM. But if that works well, this plugin would probably be deprecated in favour of this new warnings plugin. Does that make sense to you? I'll see when I have time to continue investigating this new plugin (haven't used Jenkins in a while, sorry) 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-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jean-Paul G edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines Not specific to docker.Have the very same issue when running sh step with parallel , on ssh slave with Jenkins 2.156 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55738 NodeMonitor out of disk space message is wrong for master Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-01-23 08:33 Labels: evergreen-triggered newbie-friendly fosdem2019 Priority: Trivial Reporter: Baptiste Mathus When the master goes out of disk space, it is put offline by the hudson.node_monitors.AbstractDiskSpaceMonitor system. The message has a blank where the node name should be: Putting back online as there is enough disk space again I think this is just because c.getName() returns an empty string in https://github.com/jenkinsci/jenkins/blob/9d61a9a13171c94e55779d166d81599cdd0f9cb7/core/src/main/java/hudson/node_monitors/AbstractDiskSpaceMonitor.java#L43-L71. Acceptance criteria This should show master instead of a space as the node name
[JIRA] (JENKINS-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Oh, actually, looks like they support CCM too. Would you be willing to give it a try on your Windows computer. If that works, I will update CCM README and Wiki, asking users to use the Warnings NG instead. 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-55547) Change base image for Evergreen (move away from Alpine)
Title: Message Title Baptiste Mathus updated JENKINS-55547 Jenkins / JENKINS-55547 Change base image for Evergreen (move away from Alpine) Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53955) Move Job NullPointerException jfrog artifactory
Title: Message Title
Stefan Rink commented on JENKINS-53955
Re: Move Job NullPointerException jfrog artifactory
I have experienced the same problem on jenkins 2.150.2 with Artifactory Plugin 3.1.0, freshly installed from scratch, no pre-existing jobs or configuration. Problem occurs when viewing job config history plugin page on a new job without any builds, but with only one config version. However, job config history plugin is not seen in the stack trace. Copying the global artifactory configuration from a working jenkins instance did not change the problem. The exception does not occur if I run this tiny groovy script:
(new org.jfrog.hudson.action.ArtifactoryProjectAction("foo", "bar")).getUrlName()
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-55567) Windows cannot delete job workspace
Title: Message Title veniamin b updated an issue Jenkins / JENKINS-55567 Windows cannot delete job workspace Change By: veniamin b Attachment: update.rtf 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-55567) Windows cannot delete job workspace
Title: Message Title veniamin b commented on JENKINS-55567 Re: Windows cannot delete job workspace We have very similar issue with maven type jobs on windows. Quick head dump analysis showed files are opened by jgit components. Here is list of plugins being updated. update.rtf 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-55733) Wrong parsing of CppCheck results
Title: Message Title Ulli Hafner commented on JENKINS-55733 Re: Wrong parsing of CppCheck results Tomas Bjerre thanks for clarifying! 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-55567) Windows cannot delete job workspace
Title: Message Title veniamin b commented on JENKINS-55567 Re: Windows cannot delete job workspace UPD: upgrading workflow-job to 2.31 causes such behavior with pipeline type job, but we didn't done any heap dump analysis, so it could be something different. 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-55739) Make trend chart customizable (y-axis, type, etc.)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-55739 Make trend chart customizable (y-axis, type, etc.) Issue Type: Epic Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-23 09:36 Priority: Major Reporter: Ulli Hafner Currently the warnings plugin provides a trend chart that shows the number of warnings for each tool for each build in a stacked area chart. This chart should be made customizable. Add Comment This message was sent by Atlassian Jira (v7.11
[JIRA] (JENKINS-52359) Cannot use custom CA Cert with vault plugin
Title: Message Title Michael Tabolsky commented on JENKINS-52359 Re: Cannot use custom CA Cert with vault plugin For anyone bumping into this, the plugin uses better cloud's code to access vault and all the communication stuff is done there. FWIW, you can disable the certificate validation by setting the environment variable VAULT_SSL_VERIFY to "false" or in case of custom CA you have to extend the plugin's capabilities to allow the keystore to be configured as described here 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-55567) Windows cannot delete job workspace
Title: Message Title veniamin b edited a comment on JENKINS-55567 Re: Windows cannot delete job workspace UPD: upgrading workflow-job to 2.31 causes such behavior with _pipeline_ type job, but we didn't done any heap dump analysis, so it could be something different. EDIT: it seems it is not the same issue, at least no word about jgit in this dump. 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-55740) Pipeline not work after update
Title: Message Title
Владислав Ненашев created an issue
Jenkins / JENKINS-55740
Pipeline not work after update
Issue Type:
Bug
Assignee:
Daniel Gront
Components:
hp-application-automation-tools-plugin
Created:
2019-01-23 09:58
Priority:
Blocker
Reporter:
Владислав Ненашев
After updating the plugin Micro Focus Application Automation Tools up to version 5.6.2, we received an error in all the pipelines that completely blocked their work. After rollback to the old version of the plugin 5.4, the error disappeared. An example of a simple pipeline for which you received an error:
pipeline {
agent {
label 'rhel7'
}
options {
timeout(time: 60, unit: 'SECONDS')
disableConcurrentBuilds()
buildDiscarder(logRotator(artifactDaysToKeepStr: '7', artifactNumToKeepStr: '10', daysToKeepStr: '7', numToKeepStr: '50'))
}
triggers {
cron 'H/3 * * * *'
}
stages {
stage('sleep') {
steps {
sleep 5
}
}
}
}
[JIRA] (JENKINS-55740) Pipeline not work after update
Title: Message Title Владислав Ненашев updated an issue Jenkins / JENKINS-55740 Pipeline not work after update Change By: Владислав Ненашев Attachment: build_log.txt 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-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Charusheela Bopardikar started work on JENKINS-39107 Change By: Charusheela Bopardikar 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-55740) Pipeline not work after update
Title: Message Title Владислав Ненашев commented on JENKINS-55740 Re: Pipeline not work after update Error log when starting the build task: build_log.txt 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-55740) Pipeline not work after update
Title: Message Title
Daniel Gront updated an issue
Jenkins / JENKINS-55740
Pipeline not work after update
Change By:
Daniel Gront
After updating the plugin [Micro Focus Application Automation Tools|https://plugins.jenkins.io/hp-application-automation-tools-plugin] up to version 5.6.2, we received an error in all the pipelines that completely blocked their work. After rollback to the old version of the plugin 5.4, the error disappeared.An example of a simple pipeline for which you received an error:{code:java}pipeline {agent {label 'rhel7'}options {timeout(time: 60, unit: 'SECONDS')disableConcurrentBuilds()buildDiscarder(logRotator(artifactDaysToKeepStr: '7', artifactNumToKeepStr: '10', daysToKeepStr: '7', numToKeepStr: '50'))}triggers { cron 'H/3 * * * *'}stages {stage('sleep') {steps {sleep 5}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27245) Performance graph does not appear if the slave node is offline
Title: Message Title Paul Cosma updated an issue Jenkins / JENKINS-27245 Performance graph does not appear if the slave node is offline Change By: Paul Cosma Comment: I have the same issue for the jobs that are running tests using docker container slaves (with docker plugin) as it is a short-lived slave. 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-27245) Performance graph does not appear if the slave node is offline
Title: Message Title Paul Cosma commented on JENKINS-27245 Re: Performance graph does not appear if the slave node is offline Manuel Carrasco I have the same issue for the jobs that are running tests using docker container slaves (with docker plugin) as it is a short-lived slave. 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-46086) A changelog should be recorded for the first build of a PR
Title: Message Title Chen Fliesher commented on JENKINS-46086 Re: A changelog should be recorded for the first build of a PR This issue is still relevant even if more than 1 year had passed. For example, this is the dump for a changelog for the 1st PR ChangeSets 17:49:01 The first ChangeSets 17:49:01 , I think there should be a way to follow the branch on the Pull Request, this example if from Github 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-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55737 "No polling baseline - Changes found" causing runaway polling Change By: Karl Wirth Labels: P4_SUPPORT 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-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Karl Wirth commented on JENKINS-55737 Re: "No polling baseline - Changes found" causing runaway polling Hi Jay Spang. Thanks for letting us know. I tried to contact you directly by email because I'd like to get more information about the problem job. If you haven't received an email from me, please let me know. 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-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-55737 "No polling baseline - Changes found" causing runaway polling Change By: Karl Wirth Assignee: Karl Wirth 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Paul Allen commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Hi Brad, thank you for looking into this with Nancy. Were you able to take a copy of the failing build.xml file and config.xml before you deleted the Job? I suspect the issue may be a result of changing the Global Library syncID in 1.9.2->1.9.3 from an encoded depot path to a UUID. I'd like to try and find the cause so I can potentially cleanup the old data to avoid users having to delete and re-create Jobs. 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-55725) p4 sync pipeline script not syncing files after p4 plugin update from 1.8.12 to 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55725 Re: p4 sync pipeline script not syncing files after p4 plugin update from 1.8.12 to 1.9.6 Hi Sasidhar A. Can you please send an email into 'supp...@perforce.com' and mark it for my attention. I'd like to ask you for additional information that is related to the security setup and depot structures. 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-55725) p4 sync pipeline script not syncing files after p4 plugin update from 1.8.12 to 1.9.6
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-55725 p4 sync pipeline script not syncing files after p4 plugin update from 1.8.12 to 1.9.6 Change By: Karl Wirth Assignee: Karl Wirth 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-51016) Azure VM can't start (infinte loop)
Title: Message Title Kinga Naras commented on JENKINS-51016 Re: Azure VM can't start (infinte loop) Chenyang Liu do you know if there's a chance for fix? It's really blocking our CI. 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-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Dominik Bartholdi commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline Oleg Nenashev no, its not related to Jenkins X - it just happens that we use a Tool provided by Jenkins X in a standalone way 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-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Dominik Bartholdi commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline Oleg Nenashev no, its not related to Jenkins X - it just happens that we use a Tool provided by Jenkins X in a standalone way 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-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Dominik Bartholdi commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline Oleg Nenashev no, its not related to Jenkins X - it just happens that we use a Tool provided by Jenkins X in a standalone way 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 Juho Saarinen started work on JENKINS-37739 Change By: Juho Saarinen 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-37739) Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline
Title: Message Title Juho Saarinen assigned an issue to Juho Saarinen Jenkins / JENKINS-37739 Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline Change By: Juho Saarinen Assignee: jpiironen Juho Saarinen 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-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu assigned an issue to Jie Shen Jenkins / JENKINS-51016 Azure VM can't start (infinte loop) Change By: Chenyang Liu Assignee: Chenyang Liu 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-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu commented on JENKINS-51016 Re: Azure VM can't start (infinte loop) Jie Shen maintains the plugin now. Could you help to take a look. 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-55735) Trend line chart with type, category or origin
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55735 Trend line chart with type, category or origin Change By: Ulli Hafner Summary: Graph Trend line chart with type instead of severity as content , category or origin 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-55735) Trend line chart with type, category or origin
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55735 Trend line chart with type, category or origin Change By: Ulli Hafner Currently the graph contains only severity Add another trend chart ( low, normal, high line chart ) as content. It would be nice to can adjust that displays the graph to display other content, like type, because severity alone has sometimes really less information. number of warnings per build by the following properties: * Type * Category* Origin (Name of the Tool) At result it should look similar to this: * [Cppcheck Plugin example image|https://wiki.jenkins.io/download/attachments/37749668/1.16_project.png] * [Analysis Collector image|https://wiki.jenkins.io/download/attachments/42469302/analysis-trend.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-55741) Customizable number of builds in trend chart
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-55741 Customizable number of builds in trend chart Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-23 11:25 Priority: Minor Reporter: Ulli Hafner Make number of builds in trend chart customizable (additionally maybe a time constraint would make sense). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55735) Trend line chart by type, category or origin (y-axis)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55735 Trend line chart by type, category or origin (y-axis) Change By: Ulli Hafner Summary: Trend line chart with by type, category or origin (y-axis) 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-55738
NodeMonitor out of disk space message is wrong for master
Change By:
Baptiste Mathus
When the master goes out of disk space, it is put offline by the {{hudson.node_monitors.AbstractDiskSpaceMonitor}} system.The message has a blank where the node name should be:{{Putting back online as there is enough disk space again}}I think this is just because {{c.getName()}} returns an empty string in https://github.com/jenkinsci/jenkins/blob/9d61a9a13171c94e55779d166d81599cdd0f9cb7/core/src/main/java/hudson/node_monitors/AbstractDiskSpaceMonitor.java#L43-L71.h3. Acceptance criteria* This should show {{master}} instead of a space as the node 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-55738
NodeMonitor out of disk space message is wrong for master
Change By:
Baptiste Mathus
When the master goes out of disk space, it is put offline by the {{hudson.node_monitors.AbstractDiskSpaceMonitor}} system.The message has a blank where the node name should be:{{Putting back online as there is enough disk space again}}I think this is just because {{c.getName()}} returns an empty string in https://github.com/jenkinsci/jenkins/blob/9d61a9a13171c94e55779d166d81599cdd0f9cb7/core/src/main/java/hudson/node_monitors/AbstractDiskSpaceMonitor.java#L43-L71.h3. Acceptance criteria* This should show {{master}} instead of a space as the node 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-55742) New vs. fixed warnings trend chart
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-55742 New vs. fixed warnings trend chart Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-23 11:30 Priority: Minor Reporter: Ulli Hafner Add a new trend chart (bar chart) that shows the number of new vs. fixed issues. Example: old warnings plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-40127) Declarative Pipeline GDSL
Title: Message Title James Howe commented on JENKINS-40127 Re: Declarative Pipeline GDSL Gonzalo Garcia if you have code that generates the GSDL please share it. The result will be different for every Jenkins instance depending on what plugins (and versions thereof) are installed. 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-46052) GIT: UserIdentity does not work on pipeline
Title: Message Title
Jan Pesta commented on JENKINS-46052
Re: GIT: UserIdentity does not work on pipeline
I think that problem is in CliGitAPIImpl: Where author and commuter are stored into envinronments only, but not in .git/config. When you later use sh(git) you will get this problem.
/** {@inheritDoc} */
public void setAuthor(String name, String email) throws GitException {
env("GIT_AUTHOR_NAME", name);
env("GIT_AUTHOR_EMAIL", email);
}
/** {@inheritDoc} */
public void setCommitter(String name, String email) throws GitException {
env("GIT_COMMITTER_NAME", name);
env("GIT_COMMITTER_EMAIL", email);
}
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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Denis Zakharov commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Behavior and appearance in single and in parallel stages have difference. There are no link on child job if it was executed from parallel block. Can someone change bug status? 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-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Jakub Pawlinski commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We are affected as well. I intentionally postponed 2.4.0 update as we are using bitbucket/stash 4.5.2, but this problem exists on 2.2.16. It wasn't happening in 2.2.13 that we upgraded from. Thanks for workaround. 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-55743) performance signature dynatrace plugin integration: Getting response code 503
Title: Message Title suraj panda created an issue Jenkins / JENKINS-55743 performance signature dynatrace plugin integration: Getting response code 503 Issue Type: New Feature Assignee: Raphael Pionke Components: performance-signature-dynatrace-plugin Created: 2019-01-23 12:46 Environment: test Priority: Critical Reporter: suraj panda We are creating a pipeline from jenkins to create createDeployementEvent and reportPerfSignatureReport event in dynatrace using performance signature dynatrace plugin. Plugin connection shows sucessfull when we enter dynatrace URL with api token. But when are using the plugin in pipeline with providing the dynatrace managed server api URL, authentication, api token it doesn't work. It gives the below exception. We are not getting any other information from log files. Please help what could be the issue. Started by user [FSSTAR|http://localhost:8080/user/fsstar]Building in workspace C:\Program Files (x86)\Jenkins\workspace\DynatraceHttp_Jan23HttpMethod: POSTURL: [https://dtserverxxx/e/74fdd165-d231-48b9-8bb2-8f955d5a75bd/api/v1/|https://apac01.safelinks.protection.outlook.com/?url="" color="">Content-type: application/jsonAccept: application/jsonAuthorization: *Sending request to url: [https://dtserverxxx/e/74fdd165-d231-48b9-8bb2-8f955d5a75bd/api/v1/|https://apac01.safelinks.protection.outlook.com/?url="" color="">Response Code: HTTP/1.1 503 Service UnavailableERROR: Build step failed with exceptionhudson.AbortException: Fail: the returned code 503 is not in the accepted range: [[100?399]] at jenkins.plugins.http_request.HttpRequestExecution.responseCodeIsValid(HttpRequestExecution.java:306) at jenkins.plugins.http_request.HttpRequestExecution.processResponse(HttpRequestExecution.java:316) at jenkins.plugins.h
[JIRA] (JENKINS-49601) Triggering downstream pipeline from a replayed one ends in a NullPointerException
Title: Message Title Marcin Kłopotek updated an issue Jenkins / JENKINS-49601 Triggering downstream pipeline from a replayed one ends in a NullPointerException Change By: Marcin Kłopotek Attachment: image-2019-01-23-13-51-41-500.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-49601) Triggering downstream pipeline from a replayed one ends in a NullPointerException
Title: Message Title Marcin Kłopotek updated an issue Jenkins / JENKINS-49601 Triggering downstream pipeline from a replayed one ends in a NullPointerException Change By: Marcin Kłopotek Attachment: image-2019-01-23-13-51-41-500.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-49601) Triggering downstream pipeline from a replayed one ends in a NullPointerException
Title: Message Title Marcin Kłopotek commented on JENKINS-49601 Re: Triggering downstream pipeline from a replayed one ends in a NullPointerException I can confirm the issue as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49601) Triggering downstream pipeline from a replayed one ends in a NullPointerException
Title: Message Title Marcin Kłopotek commented on JENKINS-49601 Re: Triggering downstream pipeline from a replayed one ends in a NullPointerException I can confirm the issue as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution
Title: Message Title Alexander Shcherbakov closed an issue as Fixed Jenkins / JENKINS-55609 Submitted JCL no longer supports variable substitution Change By: Alexander Shcherbakov Status: Resolved Closed 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Baptiste Mathus started work on JENKINS-54903 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Baptiste Mathus updated JENKINS-54903 Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55744) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe created an issue Jenkins / JENKINS-55744 Migrate from analysis-core to warnings-ng Issue Type: Task Assignee: David van Laatum Components: email-ext-plugin Created: 2019-01-23 13:10 Priority: Minor Reporter: James Howe This plugin currently depends on Static Analysis Utilities, which is EOL and replaced by Warnings Next Generation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55745) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe created an issue Jenkins / JENKINS-55745 Migrate from analysis-core to warnings-ng Issue Type: Task Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-01-23 13:15 Priority: Minor Reporter: James Howe This plugin currently depends on Static Analysis Utilities, which is EOL and replaced by Warnings Next Generation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55746) Unable to trigger the release build
Title: Message Title Kranthi K created an issue Jenkins / JENKINS-55746 Unable to trigger the release build Issue Type: Bug Assignee: Eyal Ben Moshe Attachments: Capture.PNG Components: artifactory-plugin Created: 2019-01-23 13:16 Environment: CI Priority: Blocker Reporter: Kranthi K Hi All, Our team is getting an error stating that: Processing failed due to a bug in the code. Please report this to the issue tracker (https://jenkins.io/redirect/report-an-issue). java.lang.NullPointerException at org.jfrog.hudson.release.maven.MavenReleaseWrapper$2.tearDown(MavenReleaseWrapper.java:207) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:908) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1798) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Here we are able to give normal CI build but we are unable to give the release build rest all modules are getting success in case of release! We have updated the artifactory plugin also, we need help ?
[JIRA] (JENKINS-55746) Unable to trigger the release build
Title: Message Title Kranthi K updated an issue Jenkins / JENKINS-55746 Unable to trigger the release build Change By: Kranthi K Hi All,Our team is getting an error stating that:Processing failed due to a bug in the code. Please report this to the issue tracker ( [ https://jenkins.io/redirect/report-an-issue ] ).java.lang.NullPointerExceptionat org.jfrog.hudson.release.maven.MavenReleaseWrapper$2.tearDown(MavenReleaseWrapper.java:207)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:908)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)at hudson.model.Run.execute(Run.java:1798)at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)*Here we are able to give normal CI build but we are unable to give the release build rest all modules are getting success in case of release!**We have updated the artifactory plugin also, we need help ?* *For your info : Jenkins version is 2.121.2 & Artifactory plugin version is 3.1.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 emai
[JIRA] (JENKINS-55747) Expose loaded LibraryRecords for internally reporting
Title: Message Title
Michael Werner created an issue
Jenkins / JENKINS-55747
Expose loaded LibraryRecords for internally reporting
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2019-01-23 13:37
Priority:
Minor
Reporter:
Michael Werner
And the end of our pipeline we report some metrics about the run to a Elasticsearch stack. The code for accessing the loaded pipelines is kinda ugly.
Run rawBuild = currentBuild.rawBuild
def result
def action = ""
if (action != null) {
result = [:]
for (library in action.libraries) {
result[library.name] = library.version
}
}
An easier way to access these information would be nice
Add Comment
[JIRA] (JENKINS-55743) performance signature dynatrace plugin integration: Getting response code 503
Title: Message Title Raphael Pionke closed an issue as Not A Defect suraj panda This has nothing to do with the Performance Signature plugins. What you are seeing is a stack trace from the http request plugin. Jenkins / JENKINS-55743 performance signature dynatrace plugin integration: Getting response code 503 Change By: Raphael Pionke 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-55050) Performance improvement for large archive symlink outside of workspace
Title: Message Title Wadeck Follonier updated JENKINS-55050 Jenkins / JENKINS-55050 Performance improvement for large archive symlink outside of workspace Change By: Wadeck Follonier 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-49833) getApiJson: (url=...) failed due to Http error #403
Title: Message Title Christian Häussler commented on JENKINS-49833 Re: getApiJson: (url="" failed due to Http error #403 I'm experiencing the same 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master I would like to work on this issue. So can I assign this to 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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jesse Glick commented on JENKINS-39598 Re: MultiSCM/config.jelly passes descriptors=null Of course. My tendency is just to leave issues in deprecated or abandoned components untouched, for archaeological reasons—no one will come back later and wonder whether there was a reason that this issue in particular was closed. 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-55748) Jemnkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once
Title: Message Title
Alexandr Panshin created an issue
Jenkins / JENKINS-55748
Jemnkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once
Issue Type:
Bug
Assignee:
vjuranek
Attachments:
screen0.jpg, screen1.jpg
Components:
groovy-plugin
Created:
2019-01-23 14:44
Environment:
Jenkins 2.150.1, Pipeline-Groovy Plugin 2.57
Labels:
groovy parallel
Priority:
Minor
Reporter:
Alexandr Panshin
I want to execute same job with same parameters five times But the following code leads to only one actual execution:
pipeline {
agent none
stages {
stage('Processing same project 5 times') {
steps {
script {
def projectsBuilds = [:]
for (int i = 0; i < 5; i++) {
int currentIteration = i
String uniqueRunName = String.format('Run #%d', currentIteration);
def labelParameters = []
labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])
labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'Sample-
[JIRA] (JENKINS-55748) Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once
Title: Message Title Alexandr Panshin updated an issue Jenkins / JENKINS-55748 Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once Change By: Alexandr Panshin Summary: Jemnkins Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Baptiste Mathus commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Nisarg Shah absolutely, please do. Thanks! If you need help, please reach out to us either on IRC, on on the developers mailing list. Thanks again! 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-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title Alexandr Panshin closed an issue as Duplicate Found the source of the problem, created new defect, which better describes problem Jenkins / JENKINS-55600 Parallel execution of same job N times with different parameters leads to only 1 execution of the job Change By: Alexandr Panshin Status: Open Closed Resolution: Duplicate 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-55748) Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once
Title: Message Title
Alexandr Panshin updated an issue
Jenkins / JENKINS-55748
Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once
Change By:
Alexandr Panshin
I want to execute same job with same parameters five timesBut the following code leads to only one actual execution:{code:java}pipeline {agent nonestages {stage('Processing same project 5 times') {steps {script {def projectsBuilds = [:]for (int i = 0; i < 5; i++) { int currentIteration = i String uniqueRunName = String.format('Run #%d', currentIteration); def labelParameters = [] labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux']) labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'Sample-Job']) print(String.format("This parameters set hash is \"%s\"", labelParameters.hashCode())) projectsBuilds[uniqueRunName] = { stage(String.format('Sample-Job execution #%d', currentIteration)) { build job: 'Sample-Job', parameters: labelParameters } }}parallel projectsBuilds;}}}}}{code}As you see from execution log screen (screen0), though I explicitly instantiate "labelParameters" on each iteration, it has the same hash code in every iteration. Seems, Jenkins groovy plugin consider this situation as "one parameters container - one run" Meanwhile if I just add one more parameter to container - current iteration index, groovy stops to "optimize" my code and now "labelParameters" has different hash code on every iteration. This leads to execution of "Sample-Job" 5 times, as intended (screen1){code:java}pipeline {agent nonestages {stage('Processing same project 5 times') {steps {script {def projectsBuilds = [:]for (int i = 0; i < 5; i++) { int currentIteration = i String uniqueRunName = String.format('Run #%d', currentIteration); def labelParameters = [] labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux']) labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'Sample-Job']) labelParameters.add([$class: "StringParameterValue", name: "ITERATION_INDEX", value: currentIteration.toString()]) print(String.format("This parameters set hash is \"%s\"", labelParameters.hashCode())) projectsBuilds[uniqueRunName] = { stage(String.format('Sample-Job execution #%d', currentIteration)) { build job: 'Sample-Job', parameters: labelParameters
[JIRA] (JENKINS-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah assigned an issue to Nisarg Shah Jenkins / JENKINS-55738 NodeMonitor out of disk space message is wrong for master Change By: Nisarg Shah Assignee: Nisarg Shah 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-55748) Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once
Title: Message Title Alexandr Panshin commented on JENKINS-55748 Re: Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once Probably is a special case of this 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-55748) Jenkins cannot execute one job with the same (by value, not adress) parameters, more than once
Title: Message Title Alexandr Panshin updated an issue Jenkins / JENKINS-55748 Jenkins cannot execute one job with the same (by value, not adress) parameters, more than once Change By: Alexandr Panshin Summary: Jenkins cannot execute more, than one job with the same (by value, not adress) parameters, more than once 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Sure. Thank you!! Actually I am new to open source and also very much excited to contribute. 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Sure. Thank you!! Actually I am new to open source and also very much excited to contribute. 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Alex Gray commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph OMG! That did the trick!!! I had no idea that this "Next Generation Warnings Plugin" even existed! Wow! Thank you so much, Bruno P. Kinoshita!!! This is awesome! 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-55447) Remote call on JNLP4-connect connection from ... failed
Title: Message Title Jakub Pawlinski updated JENKINS-55447 Jenkins / JENKINS-55447 Remote call on JNLP4-connect connection from ... failed Change By: Jakub Pawlinski 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-55447) Remote call on JNLP4-connect connection from ... failed
Title: Message Title Jakub Pawlinski commented on JENKINS-55447 Re: Remote call on JNLP4-connect connection from ... failed Ok, found an issue - it was old version of jenkins agent, after update it works fine Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55447) Remote call on JNLP4-connect connection from ... failed
Title: Message Title Jakub Pawlinski updated JENKINS-55447 Jenkins / JENKINS-55447 Remote call on JNLP4-connect connection from ... failed Change By: Jakub Pawlinski Status: Fixed but Unreleased Closed 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-55713) No agents created when using google compute engine and missing instance template entry
Title: Message Title Emanuele Massara commented on JENKINS-55713 Re: No agents created when using google compute engine and missing instance template entry Hi, we have just run into this issue. We have updated the plugin time ago, and today I was on the general Jenkins configuration page (Jenkins -> Manage Jenkins -> Configure System), where I have clicked the save button. Instantly, my Jenkins was not able to create nodes anymore because of that error. I think that the save caused the tag to be added to the configuration file, and from now on the empty string is sent every time when creating a node, and GCP API complains because it's invalid. In my opinion this a Critical/Blocker issue as it completely breaks the functionality. 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-55749) Support Rocket.Chat via Incoming Webhook for all Job types
Title: Message Title Sokratis Galiatsis created an issue Jenkins / JENKINS-55749 Support Rocket.Chat via Incoming Webhook for all Job types Issue Type: New Feature Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2019-01-23 14:58 Environment: OS: CentOS release 6.10 (Final) Jenkins server version: 2.161 Jenkins server Java version: Java JDK 1.8.0_162 Jenkins rocket-chat-notifier plugin version: 1.3.2 Rocket.Chat server version: 0.69.2 Priority: Major Reporter: Sokratis Galiatsis As noted in JENKINS-41650 and JENKINS-49407, the Webhook API seems to be only supported in Pipeline based jobs. Believe it would be much better if the Webhook based integration was supported system-wide so you can configure-enable it in Jenkins system config and have it available even in Freestyle jobs. Not sure how much work this would require but it would mean a lot for organizations that have Rocket.Chat working with an LDAP backend and not having to create an LDAP account just for integrating with Jenkins. After all, that's the whole benefit of having a webhook based integration instead of that classic username/password based one. Glad to test if anyone has anything to submit in a develop or beta branch of this plugin.
[JIRA] (JENKINS-42816) Slave to Agent renaming leftovers
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-42816 Slave to Agent renaming leftovers Change By: Baptiste Mathus Labels: fosdem2019 jenkins2.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-55730) Show absolute/relative path for source files
Title: Message Title Stefan Schletterer updated an issue Jenkins / JENKINS-55730 Show absolute/relative path for source files Change By: Stefan Schletterer In the The legacy version of the warnings plugin there was had an option to show absolute file path for the source files. This came with the additional option of sorting the issues by folder. The warnings-ng-plugin doesn't seem to offer the same option (use absolute paths and group by folder). Also, there is now way to show the absolute or module-relative paths of a source file, only the file 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-52477) XML Parsers should use encoding given in XML file
Title: Message Title Stefan Schletterer commented on JENKINS-52477 Re: XML Parsers should use encoding given in XML file I second that, especially for larger C/C++ projects it is difficult to specify an encoding since most newer .cpp / .h files are UTF-8 but older .c Files in the same project are ANSI encoded (We use cppCheck and ClangTidy). The current workaround is to convert all files to UTF-8 just before the analysis. 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-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Sami Korhonen commented on JENKINS-38906 Re: Remove lock resource name from global configuration when lock is released Aaron Marasco You should synchronize access to LocalbleResouceManager, otherwise you might cause race condition. Considering LocakbleResourcesManager relies on synchronization, it should actually be a trivial task to delete lock after it has been released. 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-55750) IAR parser not finding warnings of IAR ARM compiler
Title: Message Title Torben Stößel created an issue Jenkins / JENKINS-55750 IAR parser not finding warnings of IAR ARM compiler Issue Type: Bug Assignee: Ulli Hafner Components: analysis-model Created: 2019-01-23 16:18 Environment: IAR C/C++ Compiler for ARM 8.22.2 Priority: Minor Reporter: Torben Stößel Using the above compiler version, warnings are output in following way: "c:\external\specific\cpp\iar_cxxabi.cpp",432 Warning[Pe852]: _expression_ must be a pointer to a complete object type With a look to IarParser.java:22, it's clear that the regex does not match. With regard to warning-ng-plugin, paths without drive letter have to be recognized as well so that they can be resolved within jenkins workspace. Add Comment
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Verified that upgrading the agent worked 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-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title
Sami Korhonen commented on JENKINS-38906
Re: Remove lock resource name from global configuration when lock is released
We're using this to delete locks after our ansible plays:
@NonCPS
def deleteLocks(lockNames) {
def manager = org.jenkins.plugins.lockableresources.LockableResourcesManager.get()
synchronized (manager) {
manager.getResources().removeAll { r -> lockNames.contains(r.name) && !r.locked && !r.reserved }
manager.save()
}
}
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-52477) XML Parsers should use encoding given in XML file
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-52477
XML Parsers should use encoding given in XML file
Change By:
Ulli Hafner
Currently, the encoding needs to defined for the parser as parameter, it would be handy if the parser could detect the encoding. {code}...{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52477) XML Parsers should use encoding given in XML file
Title: Message Title Ulli Hafner commented on JENKINS-52477 Re: XML Parsers should use encoding given in XML file Stefan Schletterer This issue is about XML report files, they have the encoding of the file already given in the xml tag. You comment is about the source code encoding, isn't 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-52477) XML Parsers should use encoding given in XML file
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-52477
XML Parsers should use encoding given in XML file
Change By:
Ulli Hafner
Currently, the encoding needs to defined for the parser as parameter, it would be handy if the parser could detect the encoding.{code} . 1"> .. . {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52477) XML Parsers should use report encoding given in XML file
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-52477 XML Parsers should use report encoding given in XML file Change By: Ulli Hafner Summary: XML Parsers should use report encoding given in XML file 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-52477) XML Parsers should use report encoding given in XML file
Title: Message Title Ulli Hafner edited a comment on JENKINS-52477 Re: XML Parsers should use report encoding given in XML file [~sschlet] This issue is about XML report files, they have the encoding of the file already given in the xml tag. You Your comment is about the source code encoding, isn't 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-52477) XML Parsers should use report encoding given in XML file
Title: Message Title Ulli Hafner commented on JENKINS-52477 Re: XML Parsers should use report encoding given in XML file If your problem is similar to last comment in JENKINS-55350, then we should create a new issue about to handle projects that use different source code encodings. 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-55750) IAR parser not finding warnings of IAR ARM compiler
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-55750 IAR parser not finding warnings of IAR ARM compiler Change By: Ulli Hafner Labels: help-wanted newbie-friendly Assignee: Ulli Hafner 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-48134) system config page fails to render - org.apache.commons.jelly.JellyTagException: java.lang.StackOverflowError
Title: Message Title
Noël Bardelot commented on JENKINS-48134
Re: system config page fails to render - org.apache.commons.jelly.JellyTagException: java.lang.StackOverflowError
We can reproduce this issue with the following configuration : Jenkins LTS 2.150.1 as a .war in Tomcat, with the following plugins : {{{}} {{ "plugin": "ace-editor",}} {{ "version": "1.1"}} {{ },}} {{ {}} {{ "plugin": "ant",}} {{ "version": "1.9"}} {{ },}} {{ {}} {{ "plugin": "antisamy-markup-formatter",}} {{ "version": "1.5"}} {{ },}} {{ {}} {{ "plugin": "apache-httpcomponents-client-4-api",}} {{ "version": "4.5.5-3.0"}} {{ },}} {{ {}} {{ "plugin": "authentication-tokens",}} {{ "version": "1.3"}} {{ },}} {{ {}} {{ "plugin": "blueocean",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-autofavorite",}} {{ "version": "1.2.3"}} {{ },}} {{ {}} {{ "plugin": "blueocean-bitbucket-pipeline",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-commons",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-config",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-core-js",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-dashboard",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-display-url",}} {{ "version": "2.2.0"}} {{ },}} {{ {}} {{ "plugin": "blueocean-events",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-github-pipeline",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-git-pipeline",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-i18n",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-jira",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-jwt",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-personalization",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-pipeline-api-impl",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-pipeline-editor",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-pipeline-scm-api",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-rest",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-rest-impl",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "blueocean-web",}} {{ "version": "1.10.1"}} {{ },}} {{ {}} {{ "plugin": "branch-api",}} {{ "version": "2.1.2"}} {{ },}} {{ {}} {{ "plugin": "build-environment",}} {{ "version": "1.6"}} {{ },}} {{ {}} {{ "plugin": "build-failure-analyzer",}} {{ "version": "1.21.0"}} {{ },}} {{ {}} {{ "plugin": "build-timeout",}} {{ "version": "1.19"}} {{ },}} {{ {}} {{ "plugin": "build-user-vars-plugin",}} {{ "version": "1.5"}} {{ },}} {{ {}} {{ "plugin": "cloudbees-bitbucket-branch-source",}} {{ "version": "2.4.0"}} {{ },}} {{ {}} {{ "plugin": "cloudbees-folder",}} {{ "version": "6.7"}} {{ },}} {{ {}} {{ "plugin": "conditional-buildstep",}} {{ "version": "1.3.6"}} {{ },}} {{ {}} {{ "plugin": "config-file-provider",}} {{ "version": "3.4.1"}} {{ },}} {{ {}} {{ "plugin": "credentials",}} {{ "version": "2.1.18"}} {{ },}} {{ {}} {{ "plugin": "credentials-binding",}} {{ "version": "1.17"}} {{ },}} {{ {}} {{ "plugin": "date-parameter",}} {{ "version": "0.0.4"}} {{ },}} {{ {}} {{ "plugin": "disk-usage",}} {{ "version": "0.28"}} {{ },}} {{ {}} {{ "plugin": "display-url-api",}} {{ "version": "2.3.0"}} {{ },}} {{ {}} {{ "plugin": "docker-commons",}} {{ "version": "1.13"}} {{ },}} {{ {}} {{ "plugin": "docker-workflow",}} {{ "version": "1.17"}} {{ },}} {{ {}} {{ "plugin": "durable-task",}} {{ "version": "1.28"}} {{ },}} {{ {}} {{ "plugin": "envinject",}} {{ "version": "2.1.6"}} {{ },}} {{ {}} {{ "plugin": "envinject-api
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Benjamin Heilbrunn commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once We already encountered multiple use cases where we needed to parse STDOUT in case a certain exit code happened. Would be great to have this feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Jesse Glick commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master I think it would suffice to use Computer.getDisplayName, which is overridden for MasterComputer. 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.
