[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59682
EC2 Plugin terminates windows instance right after connecting when using ssh.
Change By:
George Cimpoies
{code:java}collapseBuild Executor StatusOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0b3686cd8938dd562Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0)Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as clujOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:55 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:10 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: connect fresh as rootOct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existThe syntax of the command is incorrect.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionjava full version "1.8.0_131-b11"Oct 07, 2019 10:55:31 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpOct 07, 2019 10:55:32 AM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpOct 07, 2019 10:55:33 AM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead
[JIRA] (JENKINS-59149) 'Test Connection' succesfully sends a message, but build-event notifications don't get sent
Title: Message Title Daniel Bocksteger commented on JENKINS-59149 Re: 'Test Connection' succesfully sends a message, but build-event notifications don't get sent Martin Reinhardt same question as Thomas Strohmeier sent yesterday. Is there any update on this issue? It's really annoying that the plugin is clearing the config every time you enter the Buildjob-Configs... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201585.1567146235000.3120.1570513380309%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59682
EC2 Plugin terminates windows instance right after connecting when using ssh.
Change By:
George Cimpoies
{code:java}collapseBuild Executor StatusOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0b3686cd8938dd562Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0)Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as clujOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:55 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:10 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: connect fresh as rootOct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existThe syntax of the command is incorrect.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionjava full version "1.8.0_131-b11"Oct 07, 2019 10:55:31 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpOct 07, 2019 10:55:32 AM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpOct 07, 2019 10:55:33 AM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59682
EC2 Plugin terminates windows instance right after connecting when using ssh.
Change By:
George Cimpoies
{code:java}collapseBuild Executor StatusOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0b3686cd8938dd562Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0)Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as clujOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:55 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:10 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: connect fresh as rootOct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existThe syntax of the command is incorrect.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionjava full version "1.8.0_131-b11"Oct 07, 2019 10:55:31 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpOct 07, 2019 10:55:32 AM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpOct 07, 2019 10:55:33 AM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title George Cimpoies commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Raihaan Shouhell sure, I've documented everything here: https://issues.jenkins-ci.org/browse/JENKINS-59682 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.3110.1570509720403%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Jordan Jennings - That is a completely separate issue. Jay Ache Jon Cormier Aðalsteinn Rúnarsson Would you be willing to try the OkHttp3 update in JENKINS-57411 ? It will not fix the issue while it is happening, but we are hoping it may prevent or reduce the occurrences, but we need more people that have actually seen the issue to try the fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.3018.1570502881844%40Atlassian.JIRA.
[JIRA] (JENKINS-59693) Trigger not removed when deleting a job
Title: Message Title minkeat wong created an issue Jenkins / JENKINS-59693 Trigger not removed when deleting a job Issue Type: Bug Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 2019-10-08 02:01 Environment: Jenkins ver. 2.198 Jira Trigger Plugin 1.0 Priority: Major Reporter: minkeat wong When deleting a job with Jira trigger enable (e.g. checked the "Build when an issue is updated in JIRA" option), the trigger appear not removed. Steps to re-produce: In Jenkins's system log, create a logger with "com.ceilfors.jenkins.plugins.jiratrigger" to trace Normal case Create a job, enable Jira trigger option and save. from the logger's log it show "Added [xxx/]:[JiraChangelogTrigger] to triggers list" Edit the job, disable Jira trigger option and save, from the logger's log, it show "Removed [xxx/]:[JiraChangelogTrigger] from triggers list" Potential Issue case Create a job, enable Jira trigger option and save. from the logger's log it show "Added [xxx/]:[JiraChangelogTrigger] to triggers list" Delete the job, in the logger's log, NO "Removed [xxx/]:[JiraChangelogTrigger] from triggers list" appear. <-- trigger remain active?
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Raihaan Shouhell commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version George Cimpoies can you provide a stacktrace if you have one? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.3009.1570495320213%40Atlassian.JIRA.
[JIRA] (JENKINS-59650) Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻
Title: Message Title Oleg Nenashev resolved as Duplicate Closing as a duplicate Jenkins / JENKINS-59650 Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻ Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Released As: 2.196 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-59691) Refresh the plugin
Title: Message Title Jesse Glick updated JENKINS-59691 Jenkins / JENKINS-59691 Refresh the plugin Change By: Jesse Glick Status: Fixed but Unreleased Resolved Released As: 1.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202389.1570475197000.3003.1570493820184%40Atlassian.JIRA.
[JIRA] (JENKINS-59580) NPE in OSProcess#hasMatchingEnvVars on Windows
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59580 NPE in OSProcess#hasMatchingEnvVars on Windows Change By: Oleg Nenashev Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202220.1569825441000.3001.1570493760247%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Oleg Nenashev Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201589.1567181048000.2999.1570493760216%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Oleg Nenashev updated JENKINS-59152 Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201589.1567181048000.2995.1570493700468%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201589.1567181048000.2997.1570493700496%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Oleg Nenashev updated JENKINS-59152 The fix was released in Jenkins 2.199 Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Jenkins 2.199 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are
[JIRA] (JENKINS-59691) Refresh the plugin
Title: Message Title Jesse Glick updated JENKINS-59691 Jenkins / JENKINS-59691 Refresh the plugin Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202389.1570475197000.2988.1570493640355%40Atlassian.JIRA.
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59267 Timeout exceptions in jenkins log when jenkins-cli executes a long-running command Change By: Oleg Nenashev Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201766.1567817431000.2990.1570493640382%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title Oleg Nenashev commented on JENKINS-58534 Re: Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) Thanks to Daniel Beck, the fix was released in 3.4: https://github.com/jenkinsci/promoted-builds-plugin/releases/tag/promoted-builds-3.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200683.1563381278000.2972.1570493581620%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Oleg Nenashev commented on JENKINS-58337 Re: Promotion Console Log Thanks to Daniel Beck, the fix was released in 3.4: https://github.com/jenkinsci/promoted-builds-plugin/releases/tag/promoted-builds-3.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200449.1562224689000.2974.1570493581644%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Oleg Nenashev updated JENKINS-59600 Thanks to Daniel Beck, the fix was released in 3.4: https://github.com/jenkinsci/promoted-builds-plugin/releases/tag/promoted-builds-3.4 Jenkins / JENKINS-59600 Promotion logs not accessible anymore after Jenkins upgrade Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Promoted Builds 3.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title William Brode commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. Oh, sorry - you are just wanting the fix so you can use the plugin huh? I could probably look at it in 1-2 weeks if that helps. Always more motivating to know someone is interested in the fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.2941.1570488600369%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title William Brode commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. I haven't had time to write tests for it yet - but its still something I plan to do eventually (unless someone else wants to take up the work). What was the planned change to the workflow? I can likely just redo the changes if you're worried about losing them. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.2933.1570488420423%40Atlassian.JIRA.
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title
Timothy Klopotoski edited a comment on JENKINS-59337
Re: "No such DSL method 'call'" when calling step within dynamically loaded library a second time
We've found a workaround to this problem.As a convention, with extensibility in mind, my team always uses the following signature when writing [custom steps ]( | https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-custom-steps ) ] : ``` {{ def call(Map args) { }} ``` This allows us to add optional step parameters later. We use this even for parameterless steps, in case we want to accept new parameters later on.The workaround is to change the signature to explicitly accept no parameters (`def call() {`). This results in no errors.It still seems to me that using the named args signature * * should* * work.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201888.1568317781000.2925.1570487760126%40Atlassian.JIRA.
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title
Timothy Klopotoski commented on JENKINS-59337
Re: "No such DSL method 'call'" when calling step within dynamically loaded library a second time
We've found a workaround to this problem. As a convention, with extensibility in mind, my team always uses the following signature when writing [custom steps](https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-custom-steps): ``` def call(Map args) { ``` This allows us to add optional step parameters later. We use this even for parameterless steps, in case we want to accept new parameters later on. The workaround is to change the signature to explicitly accept no parameters (`def call() {`). This results in no errors. It still seems to me that using the named args signature *should* work.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201888.1568317781000.2923.1570487640218%40Atlassian.JIRA.
[JIRA] (JENKINS-51544) Option to disable automatic tagging of docker images with dockerfile agents
Title: Message Title a b updated an issue Jenkins / JENKINS-51544 Option to disable automatic tagging of docker images with dockerfile agents Change By: a b Labels: agents docker docker-workflow-plugin pipeline pipeline-build-step-plugin tag tags Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190927.1527241943000.2889.1570482540284%40Atlassian.JIRA.
[JIRA] (JENKINS-51544) Option to disable automatic tagging of docker images with dockerfile agents
Title: Message Title a b commented on JENKINS-51544 Re: Option to disable automatic tagging of docker images with dockerfile agents I have run into this as well and would also like to be able to specify my own image name when built from a dockerfile instead of an arbitrary name. This makes it hard to manage all the images on the host. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190927.1527241943000.2885.1570482480205%40Atlassian.JIRA.
[JIRA] (JENKINS-59692) Provide pipeline examples
Title: Message Title Mez Pahlan created an issue Jenkins / JENKINS-59692 Provide pipeline examples Issue Type: Improvement Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-10-07 20:16 Priority: Minor Reporter: Mez Pahlan We probably need a small markdown file that can act as a guide with examples as this gets brought up quite often now. Acceptance Criteria: Provide an example markdown file that shows the mandatory parameters. Name the file EXAMPLES.md Provide examples of the optional parameters. For optional parameters describe their default values if not set. Add Comment
[JIRA] (JENKINS-59543) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title laurent gil commented on JENKINS-59543 Re: Unable to provision slaves due to network interface and subnet ID both being set Thank you for the fix i just encounter the same issue in production. BTW, i can we introduce automatic test for this kind of issue in my pipeline ? Do you have a good framework ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202173.1569501392000.2815.1570479120408%40Atlassian.JIRA.
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Mez Pahlan started work on JENKINS-59638 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202320.1570088671000.2802.1570478580177%40Atlassian.JIRA.
[JIRA] (JENKINS-59691) Refresh the plugin
Title: Message Title Pierre Beitz updated JENKINS-59691 Jenkins / JENKINS-59691 Refresh the plugin Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202389.1570475197000.2797.1570475700695%40Atlassian.JIRA.
[JIRA] (JENKINS-59400) Jenkins slave nodes hangs for up to 12+ minutes after build phase completes
Title: Message Title John Rocha commented on JENKINS-59400 Re: Jenkins slave nodes hangs for up to 12+ minutes after build phase completes Root cause - User calling error I ran the script manually from the CLI and observed that the MSBuild.exe processes never went away. Ever. I Googled for this and found this stackoverflow description/solution If parallel compiles are enabled and used, the default is for the MSBuild.exe process to stay around so it can be re-used by future compiles. This seems to cause a problem with the remote jenkins build pools. The MSBuild.exe reuse/linger functionality can be disabled by passing /nr:false for the build process. When I added this flag it resolved my issue. This problem doesn't happen if I am building without a build pool (i.e. one jenkins node that does it's own compiles). It only occurs when I go to a master/slave-build-pool scenario. Then it occurs when building on the slave nodes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201957.1568680052000.2794.1570475280048%40Atlassian.JIRA.
[JIRA] (JENKINS-59691) Refresh the plugin
Title: Message Title Pierre Beitz started work on JENKINS-59691 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202389.1570475197000.2793.1570475220388%40Atlassian.JIRA.
[JIRA] (JENKINS-59691) Refresh the plugin
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-59691 Refresh the plugin Issue Type: Task Assignee: Pierre Beitz Components: mock-security-realm-plugin Created: 2019-10-07 19:06 Priority: Minor Reporter: Pierre Beitz The plugin is quite old and depends on a really old Jenkins Core. While it's not an issue in itself, it means that it has dependencies (through detached plugins). We recently encountered an issue with those dependencies, and the easiest fix for us would be to depend on a more recent core. CC Arnaud Héritier Add Comment
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title Matthew Dews commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. Thanks for opening a PR for this William Brode. Has there been an opportunity to add tests in order to get this merged in? We had a request to change to our Jenkins workflow come in recently but we are unable to complete it because of this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.2791.1570475041300%40Atlassian.JIRA.
[JIRA] (JENKINS-59690) Support multiple Pod/Slave labels
Title: Message Title
Jake Remitz updated an issue
Jenkins / JENKINS-59690
Support multiple Pod/Slave labels
Change By:
Jake Remitz
- EDIT: This appears to be specific to the PodTemplate "Step" and not the global configuration. Bug JENKINS-37087 seems to imply that the kubernetes-plugin can support multiple pod labels, resulting in a jenkins slave having multiple labels. - I cannot seem to find documentation of this and any attempt at adding multiple labels such as "k8s python" for two slave labels fails with error:{quote}{{ERROR: Labels must follow required specs - [https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set]}}{quote}I've tried defining in a similar method with custom yaml: {code}podTemplate(label: "python", yaml: """ apiVersion: v1 kind: Pod metadata:labels: jenkins/python: "true" jenkins/k8s: "true" spec:containers:- command: - cat tty: true image: python:alpine name: python """{code}However only the {{python}} label shows, not the k8s, when the slave is created.Is this possible with the current design? The end goal is to match specific [CustomTools|https://plugins.jenkins.io/custom-tools-plugin] that require slave labels to run custom install scripts. Otherwise the labels aren't found and the tool cannot install.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59690) Support multiple Pod/Slave labels
Title: Message Title
Jake Remitz updated an issue
Jenkins / JENKINS-59690
Support multiple Pod/Slave labels
Change By:
Jake Remitz
- Bug JENKINS-37087 seems to imply that the kubernetes-plugin can support multiple pod labels, resulting in a jenkins slave having multiple labels. - I cannot seem to find documentation of this and any attempt at adding multiple labels such as "k8s python" for two slave labels fails with error:{quote}{{ERROR: Labels must follow required specs - [https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set]}}{quote}I've tried defining in a similar method with custom yaml: {code}podTemplate(label: "python", yaml: """ apiVersion: v1 kind: Pod metadata:labels: jenkins/python: "true" jenkins/k8s: "true" spec:containers:- command: - cat tty: true image: python:alpine name: python """{code}However only the {{python}} label shows, not the k8s, when the slave is created.Is this possible with the current design? The end goal is to match specific [CustomTools|https://plugins.jenkins.io/custom-tools-plugin] that require slave labels to run custom install scripts. Otherwise the labels aren't found and the tool cannot install.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59400) Jenkins slave nodes hangs for up to 12+ minutes after build phase completes
Title: Message Title John Rocha commented on JENKINS-59400 Re: Jenkins slave nodes hangs for up to 12+ minutes after build phase completes Update: The issue doesn't always happen. It seems to depend upon what is being done in the job. For example, if the job is to update perforce there is no noticeable delay. If it's to do a simple compile using Visual Studio there doesn't seem to be a delay for that either. By simple compile I mean few objects that don't seem to trigger parallel compilation. When it does happen it appears to be with bigger Visual Studio builds that have parallel compilation enabled. Moreover, I've noticed that there may be multiple MSBuild.exe processes still running even after Jenkins reports "build.bat existing with success" For example, during my most recent reproduction, there were 5 MSBuild.exe processes lingering after Jenkins reported the script exited with success, but the build didn't return the final result until ~8m later. The MSBuild.exe processes would slowly go away one by one. Once all of the MSBuild.exe processes terminated, the Jenkins job reported it's final "Finished: SUCCESS" result. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201957.1568680052000.2781.1570474260054%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Matt Sicker commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP An HMAC essentially, yes. That sounds fine. These are like super limited use JWTs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178741.1486645144000.2777.1570473420358%40Atlassian.JIRA.
[JIRA] (JENKINS-59690) Support multiple Pod/Slave labels
Title: Message Title
Jake Remitz updated an issue
Jenkins / JENKINS-59690
Support multiple Pod/Slave labels
Change By:
Jake Remitz
Bug JENKINS-37087 seems to imply that the kubernetes-plugin can support multiple pod labels, resulting in a jenkins slave having multiple labels. I cannot seem to find documentation of this and any attempt at adding multiple labels such as "k8s python" for three two slave labels fails with error:{quote}{{ERROR: Labels must follow required specs - [https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set]}}{quote}I've tried defining in a similar method with custom yaml: {code}podTemplate(label: "python", yaml: """ apiVersion: v1 kind: Pod metadata:labels: jenkins/python: "true" jenkins/k8s: "true" spec:containers:- command: - cat tty: true image: python:alpine name: python """{code}However only the {{python}} label shows, not the k8s, when the slave is created.Is this possible with the current design? The end goal is to match specific [CustomTools|https://plugins.jenkins.io/custom-tools-plugin] that require slave labels to run custom install scripts. Otherwise the labels aren't found and the tool cannot install.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59690) Support multiple Pod/Slave labels
Title: Message Title Jake Remitz created an issue Jenkins / JENKINS-59690 Support multiple Pod/Slave labels Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-10-07 18:32 Labels: labels Priority: Minor Reporter: Jake Remitz Bug JENKINS-37087 seems to imply that the kubernetes-plugin can support multiple pod labels, resulting in a jenkins slave having multiple labels. I cannot seem to find documentation of this and any attempt at adding multiple labels such as "k8s python alpine" for three slave labels fails with error: ERROR: Labels must follow required specs - https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set I've tried defining in a similar method with custom yaml: podTemplate(label: "python", yaml: """ apiVersion: v1 kind: Pod metadata: labels: jenkins/python: "true" jenkins/k8s: "true" spec: containers: - command: - cat tty: true image: python:alpine name: python """ However only the python label shows, not the k8s, when the slave is created. Is this possible with the current design? The end goal is to match specific CustomTools that require slave labels to run custom install scripts. Otherwise the labels aren't found and the tool cannot install.
[JIRA] (JENKINS-59690) Support multiple Pod/Slave labels
Title: Message Title
Jake Remitz updated an issue
Jenkins / JENKINS-59690
Support multiple Pod/Slave labels
Change By:
Jake Remitz
Bug JENKINS-37087 seems to imply that the kubernetes-plugin can support multiple pod labels, resulting in a jenkins slave having multiple labels. I cannot seem to find documentation of this and any attempt at adding multiple labels such as "k8s python alpine " for three slave labels fails with error:{quote}{{ERROR: Labels must follow required specs - [https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set]}}{quote}I've tried defining in a similar method with custom yaml: {code}podTemplate(label: "python", yaml: """ apiVersion: v1 kind: Pod metadata:labels: jenkins/python: "true" jenkins/k8s: "true" spec:containers:- command: - cat tty: true image: python:alpine name: python """{code}However only the {{python}} label shows, not the k8s, when the slave is created.Is this possible with the current design? The end goal is to match specific [CustomTools|https://plugins.jenkins.io/custom-tools-plugin] that require slave labels to run custom install scripts. Otherwise the labels aren't found and the tool cannot install.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59566) Automatically label Scientific Linux agents
Title: Message Title Mark Waite updated JENKINS-59566 Included in platformlabeler release 3.5 Oct 7, 2019 Jenkins / JENKINS-59566 Automatically label Scientific Linux agents Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202201.1569604755000.2772.1570471980262%40Atlassian.JIRA.
[JIRA] (JENKINS-59479) Automatically label Red Hat Enterprise Linux agents
Title: Message Title Mark Waite updated JENKINS-59479 Jenkins / JENKINS-59479 Automatically label Red Hat Enterprise Linux agents Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202094.1569240506000.2770.1570471920175%40Atlassian.JIRA.
[JIRA] (JENKINS-59479) Automatically label Red Hat Enterprise Linux agents
Title: Message Title Mark Waite updated JENKINS-59479 Jenkins / JENKINS-59479 Automatically label Red Hat Enterprise Linux agents Change By: Mark Waite Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202094.1569240506000.2768.1570471620274%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Aðalsteinn Rúnarsson commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Seeing this happen still, Jenkins 2.190.1 Github Branch Source Plugin. 2.5.8 Pipeline: Multibranch: 2.21 This has been happening from time to time for us and now again today. I did notice in a related/linked issue, https://issues.jenkins-ci.org/browse/JENKINS-57206, that this might be related to the webhook from github setting: "mergeable_state": "unknown", And I can confirm that it is what was sent in our case. And to recover we had to delete the cache at `$JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache/*` as it would not recover by re-scanning nor retriggering the webhook. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.2678.1570470061798%40Atlassian.JIRA.
[JIRA] (JENKINS-59689) Active directory 2.16 no test button when setting AD config
Title: Message Title Anna Shergold created an issue Jenkins / JENKINS-59689 Active directory 2.16 no test button when setting AD config Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 2019-10-07 17:25 Environment: jenkins 2.176.1, Active Directory Plugin 2.16, windows 10, using FF ESR 31 Labels: ActiveDirectory Priority: Major Reporter: Anna Shergold in configure global security: ticked active directory specified a domain name, DC, Bind DN & password under advanced, ticked use jenkins internal directory, and a local jenkins user There is no test button, but I can save this configuration. Having seen in examples a test button, is this something missing from this version? or is it indicative I've an error in my config? The active directory health shows domain, with DNS resolving and Global & LDAP catalogs exposed. But in order to perform Server Health it says need to disable the cache (which is not enabled). If I restart Jenkins neither my local jenkins user can login, nor can my domain user. Both get the invalid user name or password.
[JIRA] (JENKINS-59566) Automatically label Scientific Linux agents
Title: Message Title Mark Waite updated JENKINS-59566 Jenkins / JENKINS-59566 Automatically label Scientific Linux agents Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202201.1569604755000.2674.1570467900405%40Atlassian.JIRA.
[JIRA] (JENKINS-59479) Automatically label Red Hat Enterprise Linux agents
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-59479 Automatically label Red Hat Enterprise Linux agents Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202094.1569240506000.2672.1570467900316%40Atlassian.JIRA.
[JIRA] (JENKINS-59479) Automatically label Red Hat Enterprise Linux agents
Title: Message Title Mark Waite started work on JENKINS-59479 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202094.1569240506000.2668.1570467840395%40Atlassian.JIRA.
[JIRA] (JENKINS-59479) Automatically label Red Hat Enterprise Linux agents
Title: Message Title Mark Waite updated JENKINS-59479 Jenkins / JENKINS-59479 Automatically label Red Hat Enterprise Linux agents Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202094.1569240506000.2669.1570467840425%40Atlassian.JIRA.
[JIRA] (JENKINS-58772) Fall-back user for Active Directory plugin does not work
Title: Message Title Anna Shergold commented on JENKINS-58772 Re: Fall-back user for Active Directory plugin does not work Any update? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201078.1564682674000.2666.1570467360370%40Atlassian.JIRA.
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title Brian J Murrell commented on JENKINS-49347 Re: BlueOcean unusably slow, maybe related to having a lot of builds stored in history We are fully up to date with Jenkins and plugins and Blue Ocean is still terrible to have to sit and wait through all of the stuff it loads. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188212.1517587105000.2656.1570465680331%40Atlassian.JIRA.
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title RENEESH KOTTAKKALATHIL commented on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 Running into exact same error when integrating crowd with jenkins. Here are my versions Crowd - 3.4 Jenkins - [ 2.176.2|https://jenkins.io/] Jenkins JDK - OpenJDK11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201849.156813782.2649.1570465620300%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Daniel Beck commented on JENKINS-59600 Re: Promotion logs not accessible anymore after Jenkins upgrade 2.164.3 (promotion logs working) -> 2.190.1 (broken) Based on Filipe's analysis in a comment to JENKINS-58337 that's probably only because you're changing versions of both core and plugins here. The problem was introduced in Jenkins 2.138.2/2.147 and integrated into the plugin in 3.3. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2642.1570463340900%40Atlassian.JIRA.
[JIRA] (JENKINS-43310) Only java source files are processed, groovy, scala, gosu, etc. don't show coverage graphically
Title: Message Title Rafael Fonte commented on JENKINS-43310 Re: Only java source files are processed, groovy, scala, gosu, etc. don't show coverage graphically Hi centic, actually I tried it with the groovy pattern (**/.groovy*) but it did not work. It shows results as though all source files under the directory I chose were excluded. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180446.1491246747000.2640.1570463340867%40Atlassian.JIRA.
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Folder ownership from CLI/REST API
Title: Message Title Florian RUYNAT commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Folder ownership from CLI/REST API Oleg Nenashev Also bumping this issue back in your list if not already in it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188687.1519655291000.2633.1570463280740%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title Daniel Beck closed an issue as Duplicate I proposed a PR fixing this as JENKINS-59600 so closing this as a duplicate of that later issue. Jenkins / JENKINS-58534 Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-50792) Overall Admin access is required to create/copy a job, which wasn't required earlier
Title: Message Title Florian RUYNAT commented on JENKINS-50792 Re: Overall Admin access is required to create/copy a job, which wasn't required earlier Oleg Nenashev By any chance, are you still working on this issue ? I've got the workaround : create in a folder with copy from "../job" then move the project to root; but well it's a bit hacky and not really a proper UX Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189902.1523628817000.2605.1570463223606%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Daniel Beck closed an issue as Duplicate I proposed a PR fixing this as JENKINS-59600 so closing this as a duplicate of that later issue. FWIW the previous comment's analysis appears correct and that's essentially what my fix does (while keeping the remote API the same). Jenkins / JENKINS-58337 Promotion Console Log Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59600 Promotion logs not accessible anymore after Jenkins upgrade Change By: Daniel Beck Component/s: promoted-builds-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2568.1570463040387%40Atlassian.JIRA.
[JIRA] (JENKINS-59688) Collabnet jobs inside folders are invisible
Title: Message Title mohamed fouad created an issue Jenkins / JENKINS-59688 Collabnet jobs inside folders are invisible Issue Type: Bug Assignee: whsu Components: collabnet-plugin Created: 2019-10-07 15:41 Environment: jenkins 2.150.2, Collabnet Plugin 2.0.6 Priority: Blocker Reporter: mohamed fouad Hello All, I have configured the jenkins job to authorize from collabnet teamforge project and place it inside a folder. then I login to teamforge and give the read permission to specific user. when the user which have the read permission login to jenkins he can not see the job because its inside the folder. whats needed to be able to see the job even if it is inside a specific folder . Add Comment
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Jesse Glick commented on JENKINS-58656 Re: Wrapper process leaves zombie when no init process present Stephan Kirsten can you elaborate a bit here? You are using the kubernetes plugin? How many sh steps per pod? What kind of K8s installation? I do not want to have to document this; I want things to work out of the box. If adding this option to pod definitions reliably fixes what is otherwise a reproducible leak, and does not cause ill effects, then we can automate that in the kubernetes plugin. I see that there is a feature gate for this which might be turned off, and we would need to check what happens if the option is specified but the feature is disabled. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.2559.1570460760354%40Atlassian.JIRA.
[JIRA] (JENKINS-59687) Blacklist the 6.0.1-beta version
Title: Message Title Maria Narcisa Galan created an issue Jenkins / JENKINS-59687 Blacklist the 6.0.1-beta version Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-10-07 14:59 Priority: Minor Reporter: Maria Narcisa Galan Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are
[JIRA] (JENKINS-59673) Invalid Credentials Organization plugin job
Title: Message Title carlos cruz updated an issue Jenkins / JENKINS-59673 Invalid Credentials Organization plugin job Change By: carlos cruz Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202366.1570227921000.2557.1570460404379%40Atlassian.JIRA.
[JIRA] (JENKINS-59664) Agent config GUI shows Known Hosts file when no strategy set
Title: Message Title Steven Wadsworth commented on JENKINS-59664 Re: Agent config GUI shows Known Hosts file when no strategy set I understand that it's the default, but if it is not set and the configuration is inspected, it shows as Known Hosts but it really isn't. A concrete example: I looked at a server I didn't set up but needed to add a node. I got a warning that not all nodes used Known Hosts so looked at the one I needed to use as a template. It said that it used that strategy but it wan't. When a new node is added I agree that it should be the default, but when looking at an older configuration the UI should display what the actual settings currently are. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202356.1570213525000.2554.1570459980390%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Misleading log message when no e-mail is sent
Title: Message Title Adrien Lecharpentier updated JENKINS-58727 Jenkins / JENKINS-58727 Misleading log message when no e-mail is sent Change By: Adrien Lecharpentier Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.2548.1570459262826%40Atlassian.JIRA.
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title Benjamin Muschko closed an issue as Fixed Jenkins / JENKINS-55630 Support declarative pipelines Change By: Benjamin Muschko Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196806.154767430.2545.1570457701497%40Atlassian.JIRA.
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title Benjamin Muschko commented on JENKINS-55630 Re: Support declarative pipelines Closing the issue as Go Modules solves the problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196806.154767430.2543.1570457640225%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Jai Mishra commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Hi Mark Waite yes,only diff. is we are not triggering a pipeline but a simple job. We have a scheduled job which runs every hr to check if there is a new commit if its there,it will trigger the build process. This was working all fine with SVN, we recently moved to Bitbucket and we see this problem, even if there is no new commit ,build would trigger. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.2531.1570457160353%40Atlassian.JIRA.
[JIRA] (JENKINS-57326) Support jgit and jgitapache with Configuration as Code plugin
Title: Message Title Mark Waite updated JENKINS-57326 Jenkins / JENKINS-57326 Support jgit and jgitapache with Configuration as Code plugin Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199098.1556975157000.2526.1570456320285%40Atlassian.JIRA.
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title Ralf Gerasch commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 if resulting file log.gz is renamed to log jenkins is able to show the log content. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.2498.1570455781070%40Atlassian.JIRA.
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish Error
Title: Message Title Ricardo Nazareth updated an issue Jenkins / JENKINS-59686 MicroFocus Build Report Publish Error Change By: Ricardo Nazareth Summary: MicroFocus Build Report Publish Error Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202384.1570454666000.2496.1570455661154%40Atlassian.JIRA.
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title Marc Würth commented on JENKINS-58826 Re: "Aggregated Analysis Results" does not get updated after a few dozen builds Ulli Hafnerthe problem seems to be fixed. The aggregated graph got updated. Thank you very much and greetings from Basel, Switzerland. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.2481.1570455120143%40Atlassian.JIRA.
[JIRA] (JENKINS-59606) java.lang.NoSuchMethodError: com.google.gson.internal.bind.ReflectiveTypeAdapterFactory
Title: Message Title Tim Jacomb commented on JENKINS-59606 Re: java.lang.NoSuchMethodError: com.google.gson.internal.bind.ReflectiveTypeAdapterFactory Fixed in release configuration-as-code 1.32 (https://github.com/jenkinsci/configuration-as-code-plugin/releases/tag/configuration-as-code-1.32) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202247.156992804.2486.1570455180555%40Atlassian.JIRA.
[JIRA] (JENKINS-59606) java.lang.NoSuchMethodError: com.google.gson.internal.bind.ReflectiveTypeAdapterFactory
Title: Message Title Tim Jacomb updated JENKINS-59606 Jenkins / JENKINS-59606 java.lang.NoSuchMethodError: com.google.gson.internal.bind.ReflectiveTypeAdapterFactory Change By: Tim Jacomb Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202247.156992804.2494.1570455241345%40Atlassian.JIRA.
[JIRA] (JENKINS-59606) java.lang.NoSuchMethodError: com.google.gson.internal.bind.ReflectiveTypeAdapterFactory
Title: Message Title Tim Jacomb updated JENKINS-59606 Jenkins / JENKINS-59606 java.lang.NoSuchMethodError: com.google.gson.internal.bind.ReflectiveTypeAdapterFactory Change By: Tim Jacomb Status: Open Fixed but Unreleased Resolution: Fixed Released As: configuration-as-code-1.32 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202247.156992804.2490.1570455180657%40Atlassian.JIRA.
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title Marc Würth updated an issue Jenkins / JENKINS-58826 "Aggregated Analysis Results" does not get updated after a few dozen builds Change By: Marc Würth Attachment: image-2019-10-07-15-30-25-143.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.2478.1570455060249%40Atlassian.JIRA.
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish
Title: Message Title
Ricardo Nazareth updated an issue
Jenkins / JENKINS-59686
MicroFocus Build Report Publish
Change By:
Ricardo Nazareth
Hi, After we make a build run whit the option to save and report the results, Jenkins just freeze (can't refresh or nothing, need to stop the service and put back on).Seems that he can't conclude and compile the evidences to generate the report.Can't understand why, it works and saves results when run from pipeline. When i use a freestlye job blocks all the time. This is the console output when he start to freeze: Started by user [ Ricardo Nazareth xxx |http://s-ea311605:8282/user/rnazareth] Running as SYSTEM Building remotely on [ S-EA311601 |http://s-ea311605:8282/computer/S-EA311601] in workspace C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001 No credentials specified > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > C:\Program Files\Git\bin\git.exe config remote.origin.url [https://github.com/x|https://github.com/AssecoPST/TA.git] # timeout=10 Fetching upstream changes from [https://github.com/|https://github.com/AssecoPST/TA.git] > C:\Program Files\Git\bin\git.exe --version # timeout=10 > C:\Program Files\Git\bin\git.exe fetch --tags --progress – [https://github.com/|https://github.com/AssecoPST/TA.git] +refs/heads/*:refs/remotes/origin/* > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/master^\{commit}" # timeout=10 > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/origin/master^\{commit}" # timeout=10 Checking out Revision 9f553fad0e47fab354e3c007f45be96f69030db6 (refs/remotes/origin/master) > C:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10 > C:\Program Files\Git\bin\git.exe checkout -f 9f553fad0e47fab354e3c007f45be96f69030db6 Commit message: "Removido alerta. Label fica visível sempre. Reportado bug para ser possível as labels acionarem os switchs." > C:\Program Files\Git\bin\git.exe rev-list --no-walk 9f553fad0e47fab354e3c007f45be96f69030db6 # timeout=10 [MOB-DCS-AND-CHEQUES-001] $ cmd /c call C:\Users\tauto\AppData\Local\Temp\2\jenkins4348457191005987879.batC:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001>del /S /Q "P:\TA\Mobile\ANDROID\CHEQUES\001. Pedir Cheque Tipo 12\Report"C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001>exit 0 [MOB-DCS-AND-CHEQUES-001] $ C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001\HpToolsLauncher.exe -paramfile props07102019140211129.txt "Started..." Run build tests Launcher timeout is 10675199::02:48:05 Controller Polling Interval: 30 seconds PerScenarioTimeout: 00::00:10:00 minutes FileSystemTestRunner timeout is 10675199.02:48:05.4775807 Mc connection info is - Mc HostAddress: s-ea311604.promo.local, McPort: 8080, Username: d...@pst.asseco.com, TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: 1 tests found: C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001\Mobile\ANDROID\CHEQUES\001. Pedir Cheque Tipo 12
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish
Title: Message Title
Ricardo Nazareth updated an issue
Jenkins / JENKINS-59686
MicroFocus Build Report Publish
Change By:
Ricardo Nazareth
Hi, After we make a build run whit the option to save and report the results, Jenkins just freeze (can't refresh or nothing, need to stop the service and put back on).Seems that he can't conclude and compile the evidences to generate the report.Can't understand why it does this , it works and saves results when run from pipeline. When i use a freestlye job blocks all the time. This is the console output when he start to freeze: Started by user [Ricardo Nazareth|http://s-ea311605:8282/user/rnazareth]Running as SYSTEMBuilding remotely on [S-EA311601|http://s-ea311605:8282/computer/S-EA311601] in workspace C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001No credentials specified > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > C:\Program Files\Git\bin\git.exe config remote.origin.url [https://github.com/x|https://github.com/AssecoPST/TA.git] # timeout=10Fetching upstream changes from [https://github.com/|https://github.com/AssecoPST/TA.git] > C:\Program Files\Git\bin\git.exe --version # timeout=10 > C:\Program Files\Git\bin\git.exe fetch --tags --progress -- – [https://github.com/|https://github.com/AssecoPST/TA.git] +refs/heads/*:refs/remotes/origin/* > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/master^\{commit}" # timeout=10 > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/origin/master^\{commit}" # timeout=10Checking out Revision 9f553fad0e47fab354e3c007f45be96f69030db6 (refs/remotes/origin/master) > C:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10 > C:\Program Files\Git\bin\git.exe checkout -f 9f553fad0e47fab354e3c007f45be96f69030db6Commit message: "Removido alerta. Label fica visível sempre. Reportado bug para ser possível as labels acionarem os switchs." > C:\Program Files\Git\bin\git.exe rev-list --no-walk 9f553fad0e47fab354e3c007f45be96f69030db6 # timeout=10[MOB-DCS-AND-CHEQUES-001] $ cmd /c call C:\Users\tauto\AppData\Local\Temp\2\jenkins4348457191005987879.batC:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001>del /S /Q "P:\TA\Mobile\ANDROID\CHEQUES\001. Pedir Cheque Tipo 12\Report" C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001>exit 0 [MOB-DCS-AND-CHEQUES-001] $ C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001\HpToolsLauncher.exe -paramfile props07102019140211129.txt"Started..."Run build testsLauncher timeout is 10675199::02:48:05Controller Polling Interval: 30 secondsPerScenarioTimeout: 00::00:10:00 minutesFileSystemTestRunner timeout is 10675199.02:48:05.4775807Mc connection info is - Mc HostAddress: s-ea311604.promo.local, McPort: 8080, Username: d...@pst.asseco.com, TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: 1 tests found:C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001\Mobile\ANDROID\CHEQUES\001. Pedir Cheque Tipo
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish
Title: Message Title
Ricardo Nazareth created an issue
Jenkins / JENKINS-59686
MicroFocus Build Report Publish
Issue Type:
Bug
Assignee:
Maria Narcisa Galan
Components:
hp-application-automation-tools-plugin
Created:
2019-10-07 13:24
Environment:
Windows
Labels:
plugin
Priority:
Blocker
Reporter:
Ricardo Nazareth
Hi, After we make a build run whit the option to save and report the results, Jenkins just freeze (can't refresh or nothing, need to stop the service and put back on). Seems that he can't conclude and compile the evidences to generate the report. Can't understand why it does this, works and saves results when run from pipeline. When i use a freestlye job blocks all the time. This is the console output when he start to freeze: Started by user Ricardo Nazareth Running as SYSTEM Building remotely on S-EA311601 in workspace C:\Jenkins\workspace\MOB-DCS-AND-CHEQUES-001 No credentials specified > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > C:\Program Files\Git\bin\git.exe config remote.origin.url https://github.com/x
timeout=10 Fetching upstream changes from https://github.com/ > C:\Program Files\Git\bin\git.exe --version # timeout=10 > C:\Program Files\Git\bin\git.exe fetch --tags --progress – https://github.com/ +refs/heads/:refs/remotes/origin/ > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/master^{commit}" #
[JIRA] (JENKINS-59678) Add a time delay capability to the retry basic step
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-59678
Add a time delay capability to the retry basic step
Change By:
Devin Nusbaum
@ [~ dnusbaum ] suggested creating this ticket for an enhancement I am proposing to the retry basic step.The retry step is a great utility step, but adding the ability to add a time delay between retries would be great. It can be as basic as adding a fixed time delay as a property to the step or an extensible option that allows you to use different algorithms for the time delay (Fixed, incremental, exponential, random, random exponential.A pull request for the basic fixed implementation has already been created at [https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/97.] This allows the user to do something like {code:java}retry(count: 3, useRetryDelay: true, delay: 40, units: "SECONDS").{code}If the more advanced implementation is desired, it has also been implemented (and can be added to the pull request. @basil suggested modeling the extensible solution of other existing APIs that do something like this and proposed looking at [Tenacity|https://tenacity.readthedocs.io/en/latest/#waiting-before-retrying]. The algorithms currently implemented are fixed, random, incremental, exponential, random Exponential. This would allow the user to do something like: {code:java}retry(count: 3, useRetryDelay: true, delay: incremental(increment: 2, max: 10, min: 1, unit: 'SECONDS')){code}All of this while still remaining backwards compatible and supporting something as simple as: {code:java}retry(3){code}
Add Comment
[JIRA] (JENKINS-59359) Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-59359 Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min) Change By: Ulli Hafner URL: https://github.com/jenkinsci/acceptance-test-harness/pull/532 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201910.1568378623000.2466.1570453980182%40Atlassian.JIRA.
[JIRA] (JENKINS-59359) Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min)
Title: Message Title Ulli Hafner commented on JENKINS-59359 Re: Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min) Oliver Gondža Can you please have a look at #532? I get an error that I do not understand. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201910.1568378623000.2468.1570454040118%40Atlassian.JIRA.
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-58826 "Aggregated Analysis Results" does not get updated after a few dozen builds Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Released As: 6.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.2463.1570453920655%40Atlassian.JIRA.
[JIRA] (JENKINS-59514) Use @POST instead of @RequirePOST for form submission endpoints
Title: Message Title Daniel Beck commented on JENKINS-59514 Re: Use @POST instead of @RequirePOST for form submission endpoints Specifically, any URL that server-side then calls StaplerRequest#getSubmittedForm. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202137.156934393.2460.1570452000140%40Atlassian.JIRA.
[JIRA] (JENKINS-59514) Use @POST instead of @RequirePOST for form submission endpoints
Title: Message Title Daniel Beck commented on JENKINS-59514 Re: Use @POST instead of @RequirePOST for form submission endpoints This change is only about endpoints that inherently cannot support this kind of use. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202137.156934393.2457.1570451940178%40Atlassian.JIRA.
[JIRA] (JENKINS-59514) Use @POST instead of @RequirePOST for form submission endpoints
Title: Message Title Jim Klimov commented on JENKINS-59514 Re: Use @POST instead of @RequirePOST for form submission endpoints As long as this does not block "form"al resubmission suggestions for GET URLs, like below, this is LGTM This URL requires POST The URL you're trying to access requires that requests be sent using POST (like a form submission). The button below allows you to retry accessing this URL using POST. URL being accessed: https://jenkins.domain/quietDown If you were sent here from an untrusted source, please proceed with caution. With a 2.198 weekly running, this seems to still work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202137.156934393.2455.1570451700703%40Atlassian.JIRA.
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title
Jonas Linde commented on JENKINS-58141
Re: Jenkins Startup issues with jobConfigHistory
We get this issue with 2.190.1 and jobConfigHistory 2.23.1 or 2.24. It's indeed just a WARNING but at the same type a ProvisionException. It's reproducible with this Dockerfile:
FROM jenkins/jenkins:2.190.1
RUN /usr/local/bin/install-plugins.sh jobConfigHistory:2.24
and this command line
docker build -t jenkins . && docker run --rm jenkins
Our log output for reference:
Sending build context to Docker daemon 2.048kB
Step 1/2 : FROM jenkins/jenkins:2.190.1
---> 5721a6cac43c
Step 2/2 : RUN /usr/local/bin/install-plugins.sh jobConfigHistory:2.24
---> Using cache
---> 5640d5ba0796
Successfully built 5640d5ba0796
Successfully tagged jenkins:latest
Running from: /usr/share/jenkins/jenkins.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
2019-10-07 12:14:38.063+ [id=1] INFOorg.eclipse.jetty.util.log.Log#initialized: Logging initialized @334ms to org.eclipse.jetty.util.log.JavaUtilLog
2019-10-07 12:14:38.170+ [id=1] INFOwinstone.Logger#logInternal: Beginning extraction from war file
2019-10-07 12:14:39.228+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
2019-10-07 12:14:39.280+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: jetty-9.4.z-SNAPSHOT; built: 2019-05-02T00:04:53.875Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_222-b10
2019-10-07 12:14:39.549+ [id=1] INFOo.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
2019-10-07 12:14:39.594+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0
2019-10-07 12:14:39.594+ [id=1] INFOo.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults
2019-10-07 12:14:39.597+ [id=1] INFOo.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60ms
Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
2019-10-07 12:14:39.986+ [id=1] INFOo.e.j.s.handler.ContextHandler#doStart: Started w.@53499d85{Jenkins v2.190.1,/,file:///var/jenkins_home/war/,AVAILABLE}{/var/jenkins_home/war}
2019-10-07 12:14:39.999+ [id=1] INFOo.e.j.server.AbstractConnector#doStart: Started ServerConnector@302c971f{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2019-10-07 12:14:39.999+ [id=1] INFOorg.eclipse.jetty.server.Server#doStart: Started @2269ms
2019-10-07 12:14:39.999+ [id=22]INFOwinstone.Logger#logInternal: Winstone Servlet Engine v4.0 running: controlPort=disabled
2019-10-07 12:14:41.999+ [id=29]INFOjenkins.InitReactorRunner$1#onAttained: Started initialization
2019-10-07 12:14:42.176+ [id=36]INFO
[JIRA] (JENKINS-59608) Support new skipped feature for GoogleTests report since 1.8
Title: Message Title Nikolas Falco updated JENKINS-59608 Jenkins / JENKINS-59608 Support new skipped feature for GoogleTests report since 1.8 Change By: Nikolas Falco Status: Fixed but Unreleased Closed Released As: 2.3.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202249.1569935765000.2450.1570449960231%40Atlassian.JIRA.
[JIRA] (JENKINS-59608) Support new skipped feature for GoogleTests report since 1.8
Title: Message Title Nikolas Falco updated JENKINS-59608 Jenkins / JENKINS-59608 Support new skipped feature for GoogleTests report since 1.8 Change By: Nikolas Falco Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202249.1569935765000.2446.1570447440242%40Atlassian.JIRA.
[JIRA] (JENKINS-59608) Support new skipped feature for GoogleTests report since 1.8
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59608 Support new skipped feature for GoogleTests report since 1.8 Change By: Nikolas Falco Summary: Support new skipped feature for GoogleTests report since 1.8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202249.1569935765000.2444.1570447260274%40Atlassian.JIRA.
[JIRA] (JENKINS-59608) Support new skipped feature for GoogleTests report
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59608 Support new skipped feature for GoogleTests report Change By: Nikolas Falco Summary: Support new skipped feature for GoogleTests : Set Skipped tests state: Skipped instead of Passed report Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202249.1569935765000.2442.1570447260245%40Atlassian.JIRA.
[JIRA] (JENKINS-59581) Set job display name from GitLab project name
Title: Message Title Parichay Barpanda commented on JENKINS-59581 Re: Set job display name from GitLab project name Vladimir Konkov I think we tried to do what you are suggesting but it was not possible to implement at that time due to underlying architecture (I mean the SCM Plugin on which our plugin depends heavily). But Joseph Petersen is best placed to answer you issue as he implemented this feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202221.1569833435000.2440.1570446960133%40Atlassian.JIRA.
[JIRA] (JENKINS-59581) Set job display name from GitLab project name
Title: Message Title Parichay Barpanda commented on JENKINS-59581 Re: Set job display name from GitLab project name Joseph Petersen If you are free, can you take a look at this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202221.1569833435000.2438.1570446720382%40Atlassian.JIRA.
[JIRA] (JENKINS-7187) RFE: openSUSE Build Service Integration for Hudson
Title: Message Title Martin Habets commented on JENKINS-7187 Re: RFE: openSUSE Build Service Integration for Hudson I would be interested in this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137284.1281542493000.2436.1570446360362%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Daniel Beck started work on JENKINS-59600 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2422.1570444800765%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Daniel Beck updated JENKINS-59600 Jenkins / JENKINS-59600 Promotion logs not accessible anymore after Jenkins upgrade Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2428.1570444800846%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Daniel Beck commented on JENKINS-59600 Re: Promotion logs not accessible anymore after Jenkins upgrade PR with fix up at https://github.com/jenkinsci/promoted-builds-plugin/pull/140 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2430.1570444800869%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Jake Price edited a comment on JENKINS-59600 Re: Promotion logs not accessible anymore after Jenkins upgrade For what it's worth my upgrade path to 2.190.1 looked like this: 2.164.3 (promotion logs working) -> 2.190.1 (broken)I had to roll back and rolled back to 2.176.1 where it is once again working. 2.176.3 gave me LDAP plugin issues so that is why 2.176.1 was chosen. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2413.1570444620593%40Atlassian.JIRA.
[JIRA] (JENKINS-59600) Promotion logs not accessible anymore after Jenkins upgrade
Title: Message Title Jake Price edited a comment on JENKINS-59600 Re: Promotion logs not accessible anymore after Jenkins upgrade For what it's worth my upgrade path to 2.190.1 looked like this: 2.164.3 (promotion logs working) -> 2.190.1 (broken)I had to roll back and rolled back to 2.176.1 where it is once again working. 2.176.3 gave me LDAP plugin issues so that is why 2.176.1 was chosen. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202241.156991322.2408.1570444561274%40Atlassian.JIRA.
