[JIRA] (JENKINS-56194) Not able to run UFT ALM Scripts from master when the slave machine is logged off
Title: Message Title Daniel Gront closed an issue as Not A Defect Jenkins / JENKINS-56194 Not able to run UFT ALM Scripts from master when the slave machine is logged off Change By: Daniel Gront 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-56194) Not able to run UFT ALM Scripts from master when the slave machine is logged off
Title: Message Title Daniel Gront commented on JENKINS-56194 Re: Not able to run UFT ALM Scripts from master when the slave machine is logged off Hey Sakthi Isai Bharathi Samundeeswari, Since the master needs to communicate with the slave so it could tell it to: Execute Copy relevant files like HpToolLauncher.exce It isn't possible to do it while you're not connected to a master as a slave. I am closing this issue since it's not a defect but a limitation of Jenkins itself. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56214) PHP CodeSniffer errors treated as warnings
Title: Message Title Cătălin Nicolescu commented on JENKINS-56214 Re: PHP CodeSniffer errors treated as warnings Yes, if you could point me to where the culprit code is Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56225) Usage Statistics configuration is invalid on jenkins GUI
Title: Message Title
jack you edited a comment on JENKINS-56225
Re: Usage Statistics configuration is invalid on jenkins GUI
Hi,Actually, we configure java paramenter, like{color:#00}-Dhudson.model.UsageStatistics.disabled=true {color}{color:#00}We expect UsageStatistics should be unchecked on GUI. but it not. {color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56225) Usage Statistics configuration is invalid on jenkins GUI
Title: Message Title jack you commented on JENKINS-56225 Re: Usage Statistics configuration is invalid on jenkins GUI Hi, Actually, we configure java paramenter, like -Dhudson.model.UsageStatistics.disabled=true We expect UsageStatistics unchecked on GUI. but it not. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56098) Not a git repository after unstash when useDefaultExcludes: false
Title: Message Title Grzegorz Zieba assigned an issue to rsandell Jenkins / JENKINS-56098 Not a git repository after unstash when useDefaultExcludes: false Change By: Grzegorz Zieba Assignee: rsandell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44611) Any way to restrict build for non-whitelisted users?
Title: Message Title Jonathan Gray commented on JENKINS-44611 Re: Any way to restrict build for non-whitelisted users? It's also a human interfacing issue too. Once the concept of trust apart from committership/ownership exists, the existing solution uses the PR itself as the CI interface to permit/retry/whitelist the build/submitter. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23667) Error message is displaying after config
Title: Message Title Owen Mehegan closed an issue as Fixed Jenkins / JENKINS-23667 Error message is displaying after config Change By: Owen Mehegan Status: Open 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-56226) missing instruction how to use 'yet-another-build-visualizer' plugin
Title: Message Title Michal Nowikowski created an issue Jenkins / JENKINS-56226 missing instruction how to use 'yet-another-build-visualizer' plugin Issue Type: Improvement Assignee: Gustaf Lundh Components: yet-another-build-visualizer-plugin Created: 2019-02-21 06:39 Priority: Blocker Reporter: Michal Nowikowski On wiki or on github page there is no instruction how to use this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55935) adding template without credentials results in multiple devil pages
Title: Message Title Jie Shen commented on JENKINS-55935 Re: adding template without credentials results in multiple devil pages PC created https://github.com/jenkinsci/azure-vm-agents-plugin/pull/135 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55935) adding template without credentials results in multiple devil pages
Title: Message Title Jie Shen edited a comment on JENKINS-55935 Re: adding template without credentials results in multiple devil pages PC PR created [ https://github.com/jenkinsci/azure-vm-agents-plugin/pull/135 ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44611) Any way to restrict build for non-whitelisted users?
Title: Message Title Brian J Murrell commented on JENKINS-44611 Re: Any way to restrict build for non-whitelisted users? Stephen Connolly Your workaround suggestion in the first comment along with Jenkinsfile's input step could lead to a more useful workaround. The only thing that is missing is the ability for a Jenkinsfile to determine the "trust"ability of the PR. Is that at all possible? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49045) Support a trusted list of fork authors in GitHub Branch Source Plugin
Title: Message Title Brian J Murrell commented on JENKINS-49045 Re: Support a trusted list of fork authors in GitHub Branch Source Plugin Should this be closed/resolved given the comments on the PR? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Alex Earl commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection The message says "Auth fail" right in it in jenkin.png: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [dev]. Message [*Auth fail*]]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection i already verified ,it is not Auth Fail,but it is Plug-in error. Because i am getting SFTP Channel error.please see my attachments. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56225) Usage Statistics configuration is invalid on jenkins GUI
Title: Message Title jack you created an issue Jenkins / JENKINS-56225 Usage Statistics configuration is invalid on jenkins GUI Issue Type: Bug Assignee: Unassigned Attachments: image-2019-02-21-11-41-50-703.png Components: core Created: 2019-02-21 03:43 Environment: Jenkins 2.150.2 Priority: Major Reporter: jack you when I configure UsageStatistics from GUI. but seems it is invalid whatever I check it or uncheck it. and get value always "true" in script console print hudson.model.UsageStatistics.DISABLED Add Comment
[JIRA] (JENKINS-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar started work on JENKINS-56190 Change By: Denys Digtiar 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-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar updated JENKINS-56190 Jenkins / JENKINS-56190 Master /proc files are added twice to the support bundle Change By: Denys Digtiar 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-56224) TLS Configuration dropdown disappeared on Windows master
Title: Message Title Brian Ray updated an issue Jenkins / JENKINS-56224 TLS Configuration dropdown disappeared on Windows master Change By: Brian Ray h2. Expected Behavior Following upgrade of Active Directory plugin to 2.12 (well, 2.11 or above), the TLS Configuration dropdown control should have migrated from the *Configure Global Security* page's *Advanced* group up to that of the individual *Domain* group/ group groups . h2. Current Behavior On a Windows master the control has disappeared from the form entirely. See the screenshots attached, one of which shows our production Jenkins running a pre-2.11 version of the plugin, where the control still lives in the *Advanced* group. And one showing my local Jenkins running a post-2.11 version of the plugin. The underlying AD configuration is functionally identical. h2. Suspected Cause It looks like the Stapler refactor under [SECURITY-859 and 520faf5|https://github.com/jenkinsci/active-directory-plugin/commit/520faf5bb1078d75e5fed10b7bf5ac6241fe2fc4#diff-8afbdeeabe606370a664d00b0fc841e2] moved the control up to the individual *Domain* group. But only when the master is running on Unix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-56224) TLS Configuration dropdown disappeared on Windows master
Title: Message Title Brian Ray created an issue Jenkins / JENKINS-56224 TLS Configuration dropdown disappeared on Windows master Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: firefox_2019-02-20_14-55-18.png, firefox_2019-02-20_15-05-09.png Components: active-directory-plugin Created: 2019-02-20 23:36 Environment: Local -- LTS core: 150.3 Active Directory plugin: 2.12 OS: Win 8.1 Pro JRE: Zulu x64 1.8.0.202 Production - LTS core: 2.138.1 Active Directory plugin: 2.8 OS: Win Server 2012 R2 JRE: Zulu x64 1.8.0.202 Browser - Firefox x64 63.0.3 Priority: Minor Reporter: Brian Ray Expected Behavior Following upgrade of Active Directory plugin to 2.12 (well, 2.11 or above), the TLS Configuration dropdown control should have migrated from the Configure Global Security page's Advanced group up to that of the individual Domain group/group. Current Behavior On a Windows master the control has disappeared from the form entirely. See the screenshots attached, one of which shows our production Jenkins running a pre-2.11 version of the plugin, where the control still lives in the Advanced group. And one showing my local Jenkins running a post-2.11 version of the plugin. The underlying AD configuration is functionally identical. Suspected Cause It looks like the Stapler refactor under SECURITY-859 and 520faf5 moved the control up to the individual Domain group. But only when the master is running on Unix.
[JIRA] (JENKINS-56223) Jenkins discard-old-build caused open file handles
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-56223
Jenkins discard-old-build caused open file handles
Change By:
Rick Liu
After Jenkins upgraded from 2.46.2 to 2.138.4 on Jan 5. 2019, I started to see many (deleted) open file handles.Those (deleted) open file handles seem caused by "discard old build" rotate. The "{{builds/.${old-build-number}}}" folder doesn't exist anymore, but when using "{{lsof}}" command to check, it showed up . : {{sudo lsof -a -p $(pgrep -P $(sudo cat /var/run/jenkins/jenkins.pid)) | grep '(deleted)'}} egbq. java34189 jenkins 5199r REG 252,0 1818111 17044616 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1394/log (deleted)bq. java34189 jenkins 5200r REG 252,0 1813394 17052273 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1388/log (deleted)bq. java34189 jenkins 5201r REG 252,0 1813394 17052273 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1388/log (deleted)bq. java34189 jenkins 5212r REG 252,0 1815212 17053470 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1398/log (deleted)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you
[JIRA] (JENKINS-56223) Jenkins discard-old-build caused open file handles
Title: Message Title
Rick Liu created an issue
Jenkins / JENKINS-56223
Jenkins discard-old-build caused open file handles
Issue Type:
Bug
Assignee:
nkns165
Attachments:
lsof_deleted.list
Components:
core, discard-old-build-plugin
Created:
2019-02-20 22:53
Environment:
Ubuntu 16.04 Java 1.8.0_191 Jenkins 2.138.4
Priority:
Major
Reporter:
Rick Liu
After Jenkins upgraded from 2.46.2 to 2.138.4 on Jan 5. 2019, I started to see many (deleted) open file handles. Those (deleted) open file handles seem caused by "discard old build" rotate. The "builds/.${old-build-number}" folder doesn't exist anymore, but when using "lsof" command to check, it showed up. sudo lsof -a -p $(pgrep -P $(sudo cat /var/run/jenkins/jenkins.pid)) | grep '(deleted)'
Add Comment
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Daniel Beck commented on JENKINS-56217 Re: allow to hide version number The regular UI footer won't do it, as the X-Jenkins header will do that, even with no permissions, on the login screen. It would certainly be feasible to limit the version information to users with Overall/Read, or perhaps Overall/Administer permission. Something like that seems nicer than a hidden switch nobody knows about anyway – IF we manage to properly implement it (and these kinds of ideas typically fail at this stage). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55369) Background step that passed is displayed as undefined
Title: Message Title Lawrence Ajayi commented on JENKINS-55369 Re: Background step that passed is displayed as undefined Hi, I also observed that the problem has not been fixed. Initially I thought the problem has been fixed and that, it will be applied in the next release but, this has not happened. At the moment all our tests are still showing the background steps as undefined and the features as failed despite the fact that all the scenario steps are shown as passed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56161) EnvVars deserialisation failure due to changed serialVersionUID
Title: Message Title Josh Soref commented on JENKINS-56161 Re: EnvVars deserialisation failure due to changed serialVersionUID Filed https://issues.jenkins-ci.org/browse/JENKINS-56222 for the general case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56222) All Serializable should have serialVersionUID
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56222 All Serializable should have serialVersionUID Issue Type: Task Assignee: Unassigned Components: core Created: 2019-02-20 22:32 Priority: Minor Reporter: Josh Soref serialVersionUID is essentially a required field for Serializable to work. If it's omitted, different compilers will generate one in an unspecified (and thus not necessarily compatible) manner. There are a number of issues involving cases where jenkins code changed which resulted in bugs. This happens throughout the java ecosystem. OpenGrok hit it: https://github.com/oracle/opengrok/issues/192 and then added a check to avoid hitting it in the future. This issue is to track adding serialVersionUID for all existing classes in core. Someone could also use this ticket to add a check to catch future offenders. Add Comment
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Oleg Nenashev commented on JENKINS-56217 Re: allow to hide version number CC Daniel Beck Wadeck Follonier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56219) Jenkins System.exit() leaves systemd in an incorrect state
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-56219 Jenkins System.exit() leaves systemd in an incorrect state Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Daniel Beck closed an issue as Not A Defect Please do not use the Jenkins project issue tracker as your personal to-do list. Jenkins / JENKINS-56218 Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS Change By: Daniel Beck 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-56217) allow to hide version number
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56217 allow to hide version number Change By: Oleg Nenashev Component/s: core Component/s: jenkinsfile-runner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56217 allow to hide version number Change By: Oleg Nenashev Labels: security-hardening Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Oleg Nenashev commented on JENKINS-56218 Re: Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS have no idea what is this request about Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30843) Jobs that are in (CloudBees) folders cannot be selected to the view.
Title: Message Title John Rocha commented on JENKINS-30843 Re: Jobs that are in (CloudBees) folders cannot be selected to the view. I just found this plugin and noticed that it only shows jobs at the "top level." If we add a folder using the "CloudBees Folders Plugin" https://wiki.jenkins.io/display/JENKINS/CloudBees+Folders+Plugin Only the name of the folder is displayed, we are not able to view the jobs inside the folder. Also don't forget jobs inside of folders that are inside other folders. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56218 Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS Change By: Oleg Nenashev Component/s: _unsorted Component/s: aptly-publisher-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-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-56218 Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS Change By: Oleg Nenashev Assignee: Simas Cepaitis Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Guillaume Egles commented on JENKINS-36776 Re: Support Windows Server Containers Any progress update on this? It would be so nice to be able to leverage Windows Container support for our jenkins build! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56208) Problem with latest jenkins/jenkins:lts docker image
Title: Message Title john snow commented on JENKINS-56208 Re: Problem with latest jenkins/jenkins:lts docker image Hello, New to Docker It seems I made some mistakes and I am running latest Jenkins ver. 2.165 , instead of lts: 2.150.3(anyway I attached the plugin list). I didn`t know that not mentioning a label at the start of the container, starts it with label latest automatically. I deleted the jenkins:latest image and installed the lts one. Everything is ok. Thank you Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56208) Problem with latest jenkins/jenkins:lts docker image
Title: Message Title john snow updated an issue Jenkins / JENKINS-56208 Problem with latest jenkins/jenkins:lts docker image Change By: john snow Attachment: plugins.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-56216) "OutOfMemoryError: Java heap space" while parsing warnings
Title: Message Title Ulli Hafner commented on JENKINS-56216 Re: "OutOfMemoryError: Java heap space" while parsing warnings This code is running on the agent. 2000 lines are not that much... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56201) GCE plugin shouldn't cleanup nodes from different jenkins masters
Title: Message Title Karol Lassak commented on JENKINS-56201 Re: GCE plugin shouldn't cleanup nodes from different jenkins masters At the moment slaves dont have any connection with "jenkins master", except instanceUniqueId so its not possible to distinguish from what master they were created.. There is another issue with that that all jenskins instances with same cloud name uses same pool (limit) of instances as mentioned here. https://issues.jenkins-ci.org/browse/JENKINS-52649 There are two options: 1. Either use different cloud name for each cloud (Info how to use it should be added to help), It allows of creating shared pools of slaves, but cleaning needs to be fixed somehow (probably by adding extra ID mentioned in point 2) 2. Another solution would be to just generate some random instance ID and use it as id. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56206) rubocop parser should use machine-parsable format
Title: Message Title Ulli Hafner updated JENKINS-56206 Fixed with commit#226d72 Jenkins / JENKINS-56206 rubocop parser should use machine-parsable format Change By: Ulli Hafner 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-53694) Add event "Pull request review comments" to the webhook trigger
Title: Message Title Priyatham Tadikonda updated an issue Jenkins / JENKINS-53694 Add event "Pull request review comments" to the webhook trigger Change By: Priyatham Tadikonda Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53694) Add event "Pull request review comments" to the webhook trigger
Title: Message Title Priyatham Tadikonda edited a comment on JENKINS-53694 Re: Add event "Pull request review comments" to the webhook trigger I would like to resume my pipeline when the code-review is submitted for the PR.I am pushing all the web hook events from Github. I created a multi branch pipeline project and I am able to start a pipeline and run the tests when a PR is created in Github, I want to merge the PR when the code-review is completed. I would like to know how can I process the code-review push event from GITHUB in Jenkins. Please help me if anyone has achieved 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-53694) Add event "Pull request review comments" to the webhook trigger
Title: Message Title Priyatham Tadikonda commented on JENKINS-53694 Re: Add event "Pull request review comments" to the webhook trigger I would like to resume my pipeline when the code-review is submitted for the PR. I am pushing all the web hook events from Github. I created a multi branch pipeline project and I am able to start a pipeline and run the tests when a PR is created in Github, I want to merge the PR when the code-review is completed. Please help me if anyone has achieved 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-56220) Artifactory Plugin not Publishing Build Information
Title: Message Title
Jed Jacobs updated an issue
Jenkins / JENKINS-56220
Artifactory Plugin not Publishing Build Information
Change By:
Jed Jacobs
We are testing our Jenkins upgrade to version 2.150.2. Using the UI, we are running existing jobs as a test. Note, these jobs run fine on version 2.121.3, which is our current version. This is preventing us from upgrading.This is what we call a health check job running every 30 minutes to confirm our connection to Artifactory is working. *Errors:*17:46:11 [consumer_0] Deploying artifact: [ https://us-artifactory.ourURL.com/artifactory/ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt |https://us-artifactory.oururl.com/artifactory/ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt] 17:46:11 Deploying build info to: [ https://us-artifactory.ourURL.com/artifactory/api/build |https://us-artifactory.oururl.com/artifactory/api/build] 17:46:11 ERROR: Could not publish build-info: Failed to send build descriptor. 400 Response message: {17:46:11 "errors" : [ { { 17:46:11 "status" : 400, 17:46:11 "message" : "Dependency id name cannot be null!" 17:46:11 } ]17:46:11 }17:46:11 java.io.IOException: Could not publish build-info: Failed to send build descriptor. 400 Response message: {17:46:11 "errors" : [ { { 17:46:11 "status" : 400, 17:46:11 "message" : "Dependency id name cannot be null!" 17:46:11 } ]17:46:11 }17:46:11 at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:261)17:46:11 at org.jfrog.build.extractor.retention.Utils.sendBuildAndBuildRetention(Utils.java:63)17:46:11 at org.jfrog.hudson.generic.GenericBuildInfoDeployer.deploy(GenericBuildInfoDeployer.java:62)17:46:11 at org.jfrog.hudson.generic.ArtifactoryGenericConfigurator$1.tearDown(ArtifactoryGenericConfigurator.java:360)17:46:11 at hudson.model.Build$BuildExecution.doRun(Build.java:174)17:46:11 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)17:46:11 at hudson.model.Run.execute(Run.java:1810)17:46:11 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)17:46:11 at hudson.model.ResourceController.execute(ResourceController.java:97)17:46:11 at hudson.model.Executor.run(Executor.java:429)*Configuration:*{ "files": [ { { "pattern": "TestUpload.txt", "target": "ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt", "props": "build.latest=true;dateDeploy.dev=1/16/18" } ]} Updated Information:We have isolated this error to the download using the plugin. It looks like it tries to publish build information on the download before even trying to download the artifact. In the output below, you'll see a directory listing from a prior job step. Then it will show it's trying to publish the build information and the failure. I don't see it trying to download the artifact, which I though would happen before the
[JIRA] (JENKINS-56146) Unable to connect to REST service
Title: Message Title Luba Pyat commented on JENKINS-56146 Re: Unable to connect to REST service Radek Antoniuk Hi, any pointers, info, thoughts? Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47430) SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-47430 SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock Change By: Devin Nusbaum Summary: SandboxResolvingClassLoader uses inefficient caching, imposes a use of Guava cache can cause classloading bottleneck /deadlock Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz commented on JENKINS-55462 Re: "shelve project" button missing for all non-admin users Roger Wang Sorry for the delay. No issue, I didn't have time to work on the plugin lately... Fix is straightforward, I just need to make some time to test it properly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz commented on JENKINS-56181 Re: Shelve project plugin broken backward compatibility Sergey Ryazantsev API wasn't documented as an API...thus the changes. That being said it's a good point that one could want to use the plugin programatically (I'm thinking bulk update for instance...). I'll make a fix making sure to add Javadoc so that it doesn't happen 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-56215) git submodule support
Title: Message Title Ulli Hafner assigned an issue to Unassigned Which git plugin and git client plugin versions are you using? Can you please check if it is possible to obtain a git blame from your Jenkins workspace using the git command line? I'm not sure if this is a problem in the jgit library or if such a workspace can't provide blames at all using the git command line. Jenkins / JENKINS-56215 git submodule support Change By: Ulli Hafner Labels: git plugin help-wanted 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-55459) failFast option for parallel stages should be able to set build result to FAILED
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-55459
failFast option for parallel stages should be able to set build result to FAILED
Change By:
Devin Nusbaum
If a user has a Declarative Pipeline script with parallel stages, and they set 'failFast true' for those stages, if one of the stages fails then the build is immediately aborted. The result of the build is set to ABORTED. It would be better if there was a way to optionally have the build result be FAILED FAILURE in this case (in a scripted pipeline the result will be FAILURE) . Although it makes a kind of logical sense for it to be ABORTED, because we have told Jenkins to abort the build, we did so because a stage failed. If we didn't failFast, the build's result would always be FAILED FAILURE . Here is an example Declarative Pipeline that demonstrates the problem:{noformat}pipeline {agent anystages {stage('Parallel Stage') {failFast trueparallel {stage('Branch A') {steps { sh 'false'}}stage('Branch B') {steps { sleep 10 echo "On Branch B"}}}}}}{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56214) PHP CodeSniffer errors treated as warnings
Title: Message Title Ulli Hafner assigned an issue to Unassigned Yes, the parser has been contributed before I added errors to the API. Interested in providing a PR? Jenkins / JENKINS-56214 PHP CodeSniffer errors treated as warnings Change By: Ulli Hafner Component/s: analysis-model-api-plugin Component/s: warnings-ng-plugin Priority: Major Minor Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56185) Cucumber report link not working after renaming or moving jenkins job
Title: Message Title Aparna Nittala updated an issue Jenkins / JENKINS-56185 Cucumber report link not working after renaming or moving jenkins job Change By: Aparna Nittala Attachment: Screen Shot 2019-02-20 at 1.38.40 PM.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-55459) failFast option for parallel stages should be able to set build result to FAILED
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55459 failFast option for parallel stages should be able to set build result to FAILED Change By: Devin Nusbaum Component/s: pipeline-model-definition-plugin Component/s: workflow-cps-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-56185) Cucumber report link not working after renaming or moving jenkins job
Title: Message Title Aparna Nittala updated an issue Jenkins / JENKINS-56185 Cucumber report link not working after renaming or moving jenkins job Change By: Aparna Nittala Attachment: Screen Shot 2019-02-20 at 1.30.17 PM.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-56221) github-sqs-plugin fails with blueocean > 1.10.1
Title: Message Title Idikoro Eradiri updated an issue Jenkins / JENKINS-56221 github-sqs-plugin fails with blueocean > 1.10.1 Change By: Idikoro Eradiri after upgrading to blueocean to 1.10.2, the github-sqs-plugin:2.1 stopped pulling github messages off of the SQS queue. We use the github-sqs-plugin to receive github webhooks from behind our firewall. We also use an IAM role, so we don't hard code the AWS creds. When I roll back to the previous docker image with blueocean:1.10.1, The github-sqs-plugin:2.1 receives messages from the SQS queue successfully. Unfortunately I'm not seeing any exceptions in the Jenkins logs related to the sqs plugin, this issue seems to happen silently.Right now we are stuck on blueocean 1.10.1 & I cannot upgrade our jenkins instance or plugins until this issue is resolved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56185) Cucumber report link not working after renaming or moving jenkins job
Title: Message Title Aparna Nittala updated an issue Jenkins / JENKINS-56185 Cucumber report link not working after renaming or moving jenkins job Change By: Aparna Nittala Environment: Jenkins ver. 2.101Cucumber report plugin : cucumber-reports@3.15.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-56221) github-sqs-plugin fails with blueocean > 1.10.1
Title: Message Title Idikoro Eradiri created an issue Jenkins / JENKINS-56221 github-sqs-plugin fails with blueocean > 1.10.1 Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, github-sqs-plugin Created: 2019-02-20 18:55 Environment: jenkins:2.150.2-alpine docker image blueocean:1.10.2 swarm:3.15 matrix-auth:2.3 job-dsl:1.71 github:1.29.2 prometheus:2.0.0 htmlpublisher:1.18 workflow-aggregator:2.5 junit:1.26.1 slack:2.4 timestamper:1.8.10 github-sqs-plugin:2.1 lockable-resources:2.4 saml:1.1.2 github-oauth:0.31 github-pr-coverage-status:2.0.0 Priority: Minor Reporter: Idikoro Eradiri after upgrading to blueocean to 1.10.2, the github-sqs-plugin:2.1 stopped pulling github messages off of the SQS queue. We use the github-sqs-plugin to receive github webhooks from behind our firewall. When I roll back to the previous docker image with blueocean:1.10.1, The github-sqs-plugin:2.1 receives messages from the SQS queue successfully. Unfortunately I'm not seeing any exceptions in the Jenkins logs related to the sqs plugin, this issue seems to happen silently. Right now we are stuck on blueocean 1.10.1 & I cannot upgrade our jenkins instance or plugins until this issue is resolved.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Mark Waite commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches delo delo the git plugin uses command line git to clone the repository. Command line git requires a script file that provides the private key for authentication to ssh repositories. That script file invokes the command ssh to provide authenticated transport between command line git and your git repository. That script can't find the ssh command on the path. That could be because the /tmp directory on the master is mounted with the noexec option. Refer to stackexchange for instructions to check the file system mount options. That could be because the PATH environment variable has been damaged or altered so that ssh is not on the PATH when running from the Jenkins master. The Jenkins "System Information" page will show you the value of the PATH environment variable on that Jenkins server. That could be because the ssh command has been removed from the master. Seems unlikely, but possible. Check for /usr/bin/ssh or /bin/ssh to confirm that you have an ssh command installed in the environment where Jenkins is running. The git plugin uses command line git to clone https repositories as well, but cloning an https repository uses a username / password instead of a private key. Cloning an https repository does not use ssh, while cloning an ssh based repository does use the ssh command. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title delo delo commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches Please also note that the bug is present only when using SSH Git. When I use HTTPS connection, it works flawlessly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title delo delo commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches I still have the bug. However, the error message id not displayed the same way. Remember that the first time you create a build in a job, this does work. It's only from the second build that the issue occurs. Prior 0.9.10: After 0.9.10: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title delo delo updated an issue Jenkins / JENKINS-45480 GIT Build with Parameters is not listing branches Change By: delo delo Attachment: chrome_2019-02-20_18-41-40.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-45480) GIT Build with Parameters is not listing branches
Title: Message Title delo delo updated an issue Jenkins / JENKINS-45480 GIT Build with Parameters is not listing branches Change By: delo delo Attachment: chrome_2019-02-20_18-34-30.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-45480) GIT Build with Parameters is not listing branches
Title: Message Title delo delo updated an issue Jenkins / JENKINS-45480 GIT Build with Parameters is not listing branches Change By: delo delo Attachment: chrome_2019-02-20_18-34-30.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-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title Jesse Glick commented on JENKINS-32709 Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server Best to post to the Jenkins users’ list or similar for usage questions like 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-56038) NPE in SonarQubePointGenerator
Title: Message Title Aleksi Simell updated JENKINS-56038 Jenkins / JENKINS-56038 NPE in SonarQubePointGenerator Change By: Aleksi Simell 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-50297) WinSW logs not being cleaned up for cloud-provisioned (ephemeral) agents
Title: Message Title Darío Villadiego commented on JENKINS-50297 Re: WinSW logs not being cleaned up for cloud-provisioned (ephemeral) agents PR sent Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45648) Agents keep disconnecting after some time
Title: Message Title Ryan White commented on JENKINS-45648 Re: Agents keep disconnecting after some time I recently had a similar problem after upgrading the Jenkins master from LTS 2.150.2 to LTS 2.89.4, and the swarm plugin from 3.10 (both master and agent) to 3.15. I can run the agent process in the foreground from a regular login shell and it would stay connected, but when the agent is run via the system init system, it disconnects and reconnects constantly. The original java process runs the whole time. The agent systems where I noticed the issue were CentOS 7. The init scripts are SystemV style configured by an old version of the jenkins Puppet module maintained by rtyler. The only thing that has consistently worked for me to keep the agent processes connected to the master is clearing out the agent workspace directory. When the agent it stopped, the workspace dir is renamed and the agent restarted, the agent stays connected as expected. Putting the old workspace directory back causes the agents to again disconnect and reconnect. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")
Title: Message Title Kevin Bowen edited a comment on JENKINS-55769 Re: Tag match filter shows more entries than direct command (git tag -l "$tagFilter") I tried the updated plugin.Thank you for the adjustments and functional explanation.I fully realize that there are limitations to how the standard "git ls-remote \-t" works.Your suggestion to prepend "refs/tags/" to the match helps with one of our job config cases.However, it does not help with our need for a "refs/tags/ \ * \ -MBP \ - \ *" match in other cases.The wildcarding picks up the extra "release/" still.I believe that I saw another ticket/request for a regex style filter for the tags.Given my use case and other user cases, you may want to consider it as a future enhancement.Thank you again for the adjustments/update for this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")
Title: Message Title Kevin Bowen commented on JENKINS-55769 Re: Tag match filter shows more entries than direct command (git tag -l "$tagFilter") I tried the updated plugin. Thank you for the adjustments and functional explanation. I fully realize that there are limitations to how the standard "git ls-remote -t" works. Your suggestion to prepend "refs/tags/" to the match helps with one of our job config cases. However, it does not help with our need for a "refs/tags/MBP" match in other cases. The wildcarding picks up the extra "release/" still. I believe that I saw another ticket/request for a regex style filter for the tags. Given my use case and other user cases, you may want to consider it as a future enhancement. Thank you again for the adjustments/update for this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55770) Intrusive and misleading warning text from the parameter selection display
Title: Message Title Kevin Bowen commented on JENKINS-55770 Re: Intrusive and misleading warning text from the parameter selection display I tried the updated plugin. Thanks for the fix. The misleading warning text no longer shows for our configured 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-56220) Artifactory Plugin not Publishing Build Information
Title: Message Title
Jed Jacobs created an issue
Jenkins / JENKINS-56220
Artifactory Plugin not Publishing Build Information
Issue Type:
New Feature
Assignee:
Eyal Ben Moshe
Components:
artifactory-plugin
Created:
2019-02-20 16:31
Environment:
Jenkins v2.121.3 Artifactory Plug-in Version 3.1.0
Labels:
plugin
Priority:
Critical
Reporter:
Jed Jacobs
We are testing our Jenkins upgrade to version 2.150.2. Using the UI, we are running existing jobs as a test. Note, these jobs run fine on version 2.121.3, which is our current version. This is preventing us from upgrading. This is what we call a health check job running every 30 minutes to confirm our connection to Artifactory is working. Errors: 17:46:11 [consumer_0] Deploying artifact: https://us-artifactory.ourURL.com/artifactory/ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt 17:46:11 Deploying build info to: https://us-artifactory.ourURL.com/artifactory/api/build 17:46:11 ERROR: Could not publish build-info: Failed to send build descriptor. 400 Response message: { 17:46:11 "errors" : [ { 17:46:11 "status" : 400, 17:46:11 "message" : "Dependency id name cannot be null!" 17:46:11 } ] 17:46:11 } 17:46:11 java.io.IOException: Could not publish build-info: Failed to send build descriptor. 400 Response message: { 17:46:11 "errors" : [ { 17:46:11 "status" : 400, 17:46:11 "message" : "Dependency id name cannot be null!" 17:46:11 } ] 17:46:11 } 17:46:11 at
[JIRA] (JENKINS-56219) Jenkins System.exit() leaves systemd in an incorrect state
Title: Message Title Steven Deal created an issue Jenkins / JENKINS-56219 Jenkins System.exit() leaves systemd in an incorrect state Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: packaging Created: 2019-02-20 16:24 Environment: Ubuntu Priority: Minor Reporter: Steven Deal Using Ubuntu Bionic (latest LTS), if you kill the Jenkins process such as via the script console (System.exit(0)), Jenkins shuts down, pidfile is removed. However, systemd still believes the process is running and a start command becomes a no-op. Add Comment
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes each build-step and returns via jnlp the console log messages to the master.This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use a predefined docker template. But we don't want to make use of docker templates. Our development-teams should specify an image of their choice inside the jenkinsfile. We want to have the configuration unter git control.We need a way to provide these informations* User* Jenkins URL* Connect method,* Remote File System Root,* etc. (normally given by the docker template configuration) inside the jenkinsfile. Is there a way to achieve this? Below is a PoC, where the container is spawned at out our remote docker host but the checkout happens locally at the jenkins-master. We have defined a DOCKER_HOST environment variable that's pointing to our remote docker-host. {code:java}pipeline {agent {docker {image 'cloudbees/java-with-docker-client'}}stages {stage('Example Build') {steps {echo 'Step1'git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X/Y/Z.git'}}}} {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
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes each build-step and returns via jnlp the console log messages to the master.This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use a predefined docker template. But we don't want to make use of docker templates. Our development-teams should specify an image of their choice inside the jenkinsfile. We want to have the configuration unter git control.We need a way to provide these informations* User* Jenkins URL* Connect method,* Remote File System Root,* etc. (normally given by the docker template configuration) inside the jenkinsfile. Is there a way to achieve this? Below is a PoC, where the container is spawned at out remote docker host but the checkout happens locally at the jenkins-master. {code:java}pipeline {agent {docker {image 'cloudbees/java-with-docker-client'}}stages {stage('Example Build') {steps {echo 'Step1'git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X/Y/Z.git'}}}} {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
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes each build-step and returns via jnlp the console log messages to the master.This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use a predefined docker template. But we don't want to make use of docker templates. Our development-teams should specify an image of their choice inside the jenkinsfile. We want to have the configuration unter git control.We need a way to provide these informations* User* Jenkins URL* Connect method,* Remote File System Root,* etc. (normally given by the docker template configuration) inside the jenkinsfile. Is there a way to achieve this? {code:java}pipeline {agent {docker {image 'cloudbees/java-with-docker-client'}}stages {stage('Example Build') {steps {echo 'Step1'git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X/Y/Z.git'}}}} {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-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes each build-step and returns via jnlp the console log messages to the master.This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use a predefined docker template. But we don't want to make use of docker templates. Our development-teams should specify an image of their choice inside the jenkinsfile. We want to have the configuration unter git control. What we We need a way to provide these informations* User* Jenkins URL* Connect method,* Remote File System Root,* etc. (normally given by the docker template configuration) inside the jenkinsfile.{code:java}pipeline {agent {docker {image 'cloudbees/java-with-docker-client'}}stages {stage('Example Build') {steps {echo 'Step1'git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X/Y/Z.git'}}}} {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-56211) Fix broken ATH test for rvm plugin
Title: Message Title Oleg Nenashev commented on JENKINS-56211 Re: Fix broken ATH test for rvm plugin > FWIW I think Oleg Nenashev recently pointed out that ruby-runtime does not work with Java 11 anyway? I do not remember that, sorry. I definitely see some architectural problems in the Ruby Runtime for Java 11, but I do not think we have ever tested it. There were issues around JAXB which would impact Ruby runtime, but it should be fixed now in 2.163+ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes the each build- steps step and returns via jnlp the console log messages to the master . This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use a predefined docker template. But we don't wann used the dockertemplates want to make use of docker templates . Our development-teams should specify an image of their choice inside the jenkinsfile. We want to have the configuration unter git control. What we need is a way to define provide these informations* User* Jenkins URL* Connect method,* Remote File System Root,* etc. (normally given by the same information from the docker template configuration ) inside the jenkinsfile.{code:java}pipeline {agent {docker {image 'cloudbees/java-with-docker-client'}}stages {stage('Example Build') {steps {echo 'Step1'git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X/Y/Z.git'}}}} {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
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes the build-steps and returns via jnlp the console log messages. This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use predefined docker template. But we don't wann used the dockertemplates. Our development-teams should specify an image of their choice inside the jenkinsfile. What we need is a way to define the same information from the docker template configuration inside the jenkinsfile. { { code:java} pipeline { }} {{ agent { }} {{ docker { }} {{ image 'cloudbees/java-with-docker-client' }} {{ } }} {{ } }}{{ stages { }} {{ stage('Example Build') { }} {{ steps { }} {{ echo 'Step1' }} {{ git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X : / Y/Z /P .git' } } {{ } }} {{ } }}{{}}} { { code:java } }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes the build-steps and returns via jnlp the console log messages. This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use predefined docker template. But we don't wann used the dockertemplates. Our development-teams should specify an image of their choice inside the jenkinsfile. What we need is a way to define the same information from the docker template configuration inside the jenkinsfile.{code:java}pipeline {agent {docker {image 'cloudbees/java-with-docker-client'}}stages {stage('Example Build') {steps {echo 'Step1'git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X/Y/Z.git'}}}} {code :java }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil edited a comment on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
[~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes the build-steps and returns via jnlp the console log messages.This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use predefined docker template. But we don't wann used the dockertemplates. Our development-teams should specify an image of their choice inside the jenkinsfile.What we need is a way to define the same information from the docker template configuration inside the jenkinsfile. {{ pipeline { }} {{ agent { }} {{ docker { }} {{ image 'cloudbees/java-with-docker-client' } } {{ } }} {{ }}}{{ stages { }} {{ stage('Example Build') { }} {{ steps { }} {{ echo 'Step1' }} {{ git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@ Q.W.E.R X : 1234 Y/Z/P.git ' } } {{ } }} {{ } }}{{}}} {{ }} }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title
Sven Scheil commented on JENKINS-32709
Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Jesse Glick How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes the build-steps and returns via jnlp the console log messages. This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use predefined docker template. But we don't wann used the dockertemplates. Our development-teams should specify an image of their choice inside the jenkinsfile. What we need is a way to define the same information from the docker template configuration inside the jenkinsfile. {{ pipeline { agent { docker { image 'cloudbees/java-with-docker-client' } } stages { stage('Example Build') { steps { echo 'Step1' git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@Q.W.E.R:1234' } } } } }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Krishnamoorthy S M updated an issue Jenkins / JENKINS-56218 Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS Change By: Krishnamoorthy S M *Description:* Jenkins is an open source automation server written in Java. Jenkins helps to automate the non-human part of the software development process, with continuous integration and facilitating technical aspects of continuous delivery. Following vulnerabilities are reported in Jenkins:- Code execution through crafted URLs- Forced migration of user records- Work space Workspace browser allowed accessing files outside the work space workspace - Potential denial of service through cron _expression_ form validation Affected Versions: Jenkins weekly up to and including 2. 153 Jenkins 153Jenkins LTS up to and including 2.138.3QID Detection Logic:(Unauthenticated)This QID checks for vulnerable version by sending a crafted GET request to Jenkins. This QID also detects the vulnerable version from login page or HTTP header. *Solution:*Customers are advised to upgrade to Jenkins weekly version 2.154,Jenkins LTS version 2.138.4 or 2.150.1 or later to remediate these vulnerabilities.Patch: Following are links for downloading patches to fix the vulnerabilities: Jenkins Security Advisory 2018-12-05 *Current version:*Jenkins ver. 2.141 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Krishnamoorthy S M updated an issue Jenkins / JENKINS-56218 Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS Change By: Krishnamoorthy S M Jenkins is an open source automation server written in Java. Jenkins helps to automate the non-human part of the software development process, with continuous integration and facilitating technical aspects of continuous delivery. Following vulnerabilities are reported in Jenkins:- Code execution through crafted URLs- Forced migration of user records- Work space browser allowed accessing files outside the work space- Potential denial of service through cron _expression_ form validation Affected Versions: Jenkins weekly up to and including 2.153 Jenkins LTS up to and including 2.138.3QID Detection Logic:(Unauthenticated)This QID checks for vulnerable version by sending a crafted GET request to Jenkins. This QID also detects the vulnerable version from login page or HTTP header. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56218) Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS
Title: Message Title Krishnamoorthy S M created an issue Jenkins / JENKINS-56218 Steps to follow JENKINS upgrade 2.154 in Ubuntu 14.04 LTS Issue Type: Improvement Assignee: Simas Cepaitis Attachments: Jenkins upgrade details.png Components: aptly-publisher-plugin Created: 2019-02-20 15:48 Environment: Linux Ubuntu 14.04.05 LTS Labels: jenkins pipeline security configuration Priority: Blocker Reporter: Krishnamoorthy S M Add Comment
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Thomas Wabner created an issue Jenkins / JENKINS-56217 allow to hide version number Issue Type: Improvement Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-02-20 15:35 Environment: LTS Priority: Trivial Reporter: Thomas Wabner It would be nice to have a option (-D or something similar) to hide the version information of the running jenkins master instance. This would avoid (make it harder) for hackers to attack a jenkins instance which has known vulnerabilities. Currently the website shows in the footer the current running jenkins version. I would like to hide this information or overwrite it with "-1" or similar. Such option can be set a java system property. We are running jenkins master as WAR archive inside a tomcat container. So the java system property would be the best way to solve this. PS: feel free to change the component .. there seems to be no component for jenkins master or the general UI available. Add Comment
[JIRA] (JENKINS-55303) [PCT] check script-security latest (jenkins-test-harness - Using JDK internal classes )
Title: Message Title Adrien Lecharpentier commented on JENKINS-55303 Re: [PCT] check script-security latest (jenkins-test-harness - Using JDK internal classes ) Filled as PR-238 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Alex Earl commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection I can't reproduce this at all. Verify the authentication setup since you are getting an auth fail message. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55303) [PCT] check script-security latest (jenkins-test-harness - Using JDK internal classes )
Title: Message Title Adrien Lecharpentier updated JENKINS-55303 Jenkins / JENKINS-55303 [PCT] check script-security latest (jenkins-test-harness - Using JDK internal classes ) Change By: Adrien Lecharpentier 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Alex any updates. Pls help to expediete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Vitaly Karasik commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time Daniel - thanks you, got it. So it's not related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56211) Fix broken ATH test for rvm plugin
Title: Message Title Jesse Glick commented on JENKINS-56211 Re: Fix broken ATH test for rvm plugin Huh. Daniel Beck do you intend to push JEP-7 forward? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56211) Fix broken ATH test for rvm plugin
Title: Message Title Daniel Beck commented on JENKINS-56211 Re: Fix broken ATH test for rvm plugin FWIW I think Oleg Nenashev recently pointed out that ruby-runtime does not work with Java 11 anyway? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Please ask Baptiste Mathus in JENKINS-21942, who was the last to work on that area. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56211) Fix broken ATH test for rvm plugin
Title: Message Title Jesse Glick commented on JENKINS-56211 Re: Fix broken ATH test for rvm plugin I am not interested. Daniel Beck drafted JEP-7 which would make it deprecated. The plugin has not had a release in three years. The test was introduced to verify the core workaround for JENKINS-48116; the plugin side of the fix is to my knowledge still unreleased, hence JEP-7. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server
Title: Message Title Jesse Glick commented on JENKINS-32709 Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server Yes you can that sort of command if you prefer to avoid Image.inside. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Daniel Beck commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time RequesterRecipientProvider' IMHO should "Sends email to the user who initiated the build" exactly as its help says To clarify, requester is the user who clicked "Build Now", not the Git username/email addresses associated with the commits. Is someone manually starting builds and this does not work? If so, that would be a separate bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Brian J Murrell edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
This ticket has added 26 more votes and 20 more watchers in just a hair over a month for a total of 175 and 189, respectively.Could somebody please provide an update on the status of this issue to those 189 watchers please? Is this *+really+* (after all of this time and attention) still just in the {color:#4c9aff}Planned{color} state that the [Blue Ocean Roadmap|https://jenkins.io/projects/blueocean/roadmap/] indicates?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Brian J Murrell commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should This ticket has added 26 more votes and 20 more watchers in just a hair over a month for a total of 175 and 189, respectively. Could somebody please provide an update on the status of this issue to those 189 watchers please? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
