[JIRA] (JENKINS-61752) JAXB-API is missing on JDK11
Title: Message Title An Nguyen commented on JENKINS-61752 Re: JAXB-API is missing on JDK11 any process on this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205583.158563766.5599.1585893420263%40Atlassian.JIRA.
[JIRA] (JENKINS-56871) EC2 Plugin fails to terminate spot instances after agent deleted
Title: Message Title Nigel Armstrong closed an issue as Not A Defect User found issue with iam role Jenkins / JENKINS-56871 EC2 Plugin fails to terminate spot instances after agent deleted Change By: Nigel Armstrong Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi Usama Tariq, Could you please let me know if got the fix for jira-trigger-plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201336.1566200967000.5585.1585889820338%40Atlassian.JIRA.
[JIRA] (JENKINS-54911) Windows Slave disconnects automatically
Title: Message Title Owen Mehegan closed an issue as Cannot Reproduce Jenkins / JENKINS-54911 Windows Slave disconnects automatically Change By: Owen Mehegan Status: Open Closed Assignee: Emilio Escobar Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.195919.1543406957000.5582.1585885020446%40Atlassian.JIRA.
[JIRA] (JENKINS-61706) InsightVM MultiBranch Jobs
Title: Message Title Gavin Schneider updated JENKINS-61706 Merged and released version 1.0.8 Jenkins / JENKINS-61706 InsightVM MultiBranch Jobs Change By: Gavin Schneider Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61706) InsightVM MultiBranch Jobs
Title: Message Title Gavin Schneider updated JENKINS-61706 Jenkins / JENKINS-61706 InsightVM MultiBranch Jobs Change By: Gavin Schneider Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205531.1585295263000.5573.1585877460497%40Atlassian.JIRA.
[JIRA] (JENKINS-52069) SEVERE: Failed to install Email Extension when running on Docker Java 10
Title: Message Title Mark Waite closed an issue as Fixed Java 10 is obsolete and won't ever be supported with Jenkins. Java 11 and the e-mail extension plugin work great with Java 11. Jenkins / JENKINS-52069 SEVERE: Failed to install Email Extension when running on Docker Java 10 Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61792) DoubleLaunchChecker false positive
Title: Message Title Wade Cline created an issue Jenkins / JENKINS-61792 DoubleLaunchChecker false positive Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-02 23:41 Environment: Debian GNU/Linux 10 openjdk 11.0.6 2020-01-14 OpenJDK Runtime Environment (build 11.0.6+10-post-Debian-1deb10u1) OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Debian-1deb10u1, mixed mode, sharing) Jenkins ver. 2.204.5 Launched & installed via standard Debian service Accessed directly Priority: Minor Reporter: Wade Cline (Copied from e-mail) A few weeks ago we ran into an issue where Jenkins reported that two instances were running with the same host directory: Error Jenkins detected that you appear to be running more than one instance of Jenkins that share the same home directory '/var/lib/jenkins'. This greatly confuses Jenkins and you will likely experience strange behaviors, so please correct the situation. This Jenkins:1541674003 contextPath="" at 29119@NPG-CID-Jenkins-OR Other Jenkins:1541674003 contextPath="" at 29119@NPG-CID-Jenkins-OR The two identifiers reported were exactly the same. Looking at the source, I found 'core/src/main/java/hudson/util/DoubleLaunchChecher.java', and, from there, found the following entry in the Jenkins log file: 2020-03-17 01:14:10.096+ [id=66] SEVERE hudson.util.DoubleLaunchChecker#execute: Collision detected. timestamp=158440393, expected=1584403930092 Note that the time stamps are a mere 92 milliseconds apart and appear to be from the same instance. At first I expected that this might be a filesystem timestamp resolution issue, but running 'ls -a --full-time' showed that the filesystem did indeed support high-resolution timestamps (output snipped): rw-rr- 1 jenkins
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Shivaji Thanneeru commented on JENKINS-61762 Re: Intermittent Socket closed or Read timed out error Naresh, Increased the Socket timeout or read timed at the global section is increased from 10 Seconds to 60 Seconds. I works now. Thanks a lot. Shivaji Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205599.1585716788000.5534.1585869600272%40Atlassian.JIRA.
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Shivaji Thanneeru updated JENKINS-61762 Jenkins / JENKINS-61762 Intermittent Socket closed or Read timed out error Change By: Shivaji Thanneeru Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205599.1585716788000.5536.1585869600300%40Atlassian.JIRA.
[JIRA] (JENKINS-61791) Failed to read XML file produced by maven spy after an execution threw an exception and color is enabled
Title: Message Title
Bertrand Renuart updated an issue
Jenkins / JENKINS-61791
Failed to read XML file produced by maven spy after an execution threw an exception and color is enabled
Change By:
Bertrand Renuart
The plugin fails to read the XML log file produced by the maven spy under the following circumstances: * maven is executed with ANSI color enabled * a plugin execution fails to execute The maven spy captures the exception thrown by the failed execution and writes it asis in its XML log file. Unfortunately, it appears that the exception message contains ANSI color escape codes when maven is executed with coloring enabled. These escape codes are not valid XML content hence causing the failure to read back the XML log file.The issue can be easily reproduced with the attached sample {{pom.xml}}. Note: according to issue JENKINS-55318, coloring is _not_ working because the plugin always invoke maven in batch mode. Our Jenkins installation is actually using a kind of post-processor that removes the --batch-mode argument from the generated wrapper script... so we have coloring working nicely.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61791) Failed to read XML file produced by maven spy after an execution threw an exception and color is enabled
Title: Message Title
Bertrand Renuart updated an issue
Jenkins / JENKINS-61791
Failed to read XML file produced by maven spy after an execution threw an exception and color is enabled
Change By:
Bertrand Renuart
The plugin fails to read the XML log file produced by the maven spy under the following circumstances: * maven is executed with ANSI color enabled * a plugin execution fails to execute The maven spy captures the exception thrown by the failed execution and writes it asis in its XML log file. Unfortunately, it appears that the exception message contains ANSI color escape codes when maven is executed with coloring enabled. These escape codes are not valid XML content hence causing the failure to read back the XML log file.The issue can be easily reproduced with the attached sample {{pom.xml}}. Note:
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Naresh Rayapati commented on JENKINS-61762 Re: Intermittent Socket closed or Read timed out error Socket timeout or read timed out occur when the actual server isn't responding within the given time, you configure site on global section with increased timeout settings. Here is the example screenshot. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205599.1585716788000.5512.1585865940575%40Atlassian.JIRA.
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-61762 Intermittent Socket closed or Read timed out error Change By: Naresh Rayapati Attachment: Screen Shot 2020-04-02 at 5.16.39 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205599.1585716788000.5509.1585865940321%40Atlassian.JIRA.
[JIRA] (JENKINS-61791) Failed to read XML file produced by maven spy after an execution threw an exception and color is enabled
Title: Message Title Bertrand Renuart created an issue Jenkins / JENKINS-61791 Failed to read XML file produced by maven spy after an execution threw an exception and color is enabled Issue Type: Bug Assignee: Alvaro Lobato Attachments: pom.xml Components: pipeline-maven-plugin Created: 2020-04-02 22:09 Environment: pipeline-maven-plugin: 3.8.2 Priority: Minor Reporter: Bertrand Renuart The plugin fails to read the XML log file produced by the maven spy under the following circumstances: maven is executed with ANSI color enabled a plugin execution fails to execute The maven spy captures the exception thrown by the failed execution and writes it asis in its XML log file. Unfortunately, it appears that the exception message contains ANSI color escape codes when maven is executed with coloring enabled. These escape codes are not valid XML content hence causing the failure to read back the XML log file. The issue can be easily reproduced with the attached sample pom.xml.
[JIRA] (JENKINS-61790) JunitTestPublisher - Tycho - wrong plugin GroupId
Title: Message Title Bertrand Renuart created an issue Jenkins / JENKINS-61790 JunitTestPublisher - Tycho - wrong plugin GroupId Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2020-04-02 21:43 Environment: pipeline-maven-plugin: 3.8.2 Priority: Minor Reporter: Bertrand Renuart The JunitTestPublisher looks for executions of the tycho-surefire-plugin under groupId org.apache.maven.plugins but the actual groupId of the plugin is org.eclipse.tycho. As result, surefire reports produced by the Tycho plugin are not detected and never published. Add Comment
[JIRA] (JENKINS-61789) Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting
Title: Message Title John Del Rosario updated an issue Jenkins / JENKINS-61789 Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting Change By: John Del Rosario We have set our agents to terminate after being idle for 30 minutes under the EC2 plugin settings page.We also have "Free Space Threshold" enabled under "Preventive Node Monitoring", to automatically mark agents as offline that whose disks fall under the threshold.We treat our agents as cattle, so ideally agents that are marked as offline would eventually terminate after being idle for 30 minutes.But that doesn't seem to be the case when both features are enabled. It seems that agents that are marked offline are being ignored by the idle termination check and are left running indefinitely. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-61789) Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting
Title: Message Title John Del Rosario updated an issue Jenkins / JENKINS-61789 Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting Change By: John Del Rosario We have set our agents to terminate after being idle for 30 minutes under the EC2 plugin settings page. We also have "Free Space Threshold" enabled under "Preventive Node Monitoring", to automatically mark agents as offline that fall under the threshold.We treat our agents as cattle, so ideally agents that are marked as offline would eventually terminate after being idle for 30 minutes.But that doesn't seem to be the case when both features are enabled. It seems that agents that are marked offline are being ignored by the idle termination check and are left running indefinitely. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-61789) Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting
Title: Message Title John Del Rosario created an issue Jenkins / JENKINS-61789 Agent nodes marked as 'offline' are not terminated when they have been idle beyond the idle termination time setting Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-04-02 21:13 Environment: OS: Amazon Linux 2 Java version: 1.8.0_242 Plugins: - Amazon EC2 plugin 1.49.1 - Amazon ECR plugin 1.6 Priority: Minor Reporter: John Del Rosario We have set our agents to terminate after being idle for 30 minutes under the We also have "Free Space Threshold" enabled under "Preventive Node Monitoring", to automatically mark agents as offline that fall under the threshold. We treat our agents as cattle, so ideally agents that are marked as offline would eventually terminate after being idle for 30 minutes. But that doesn't seem to be the case when both features are enabled. It seems that agents that are marked offline are being ignored by the idle termination check and are left running indefinitely. Add Comment
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Shivaji Thanneeru updated an issue Jenkins / JENKINS-61762 Intermittent Socket closed or Read timed out error Change By: Shivaji Thanneeru Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205599.1585716788000.5488.158586392%40Atlassian.JIRA.
[JIRA] (JENKINS-59858) Add ability to use an AMI query instead of a static AMI
Title: Message Title Dan Nicholson commented on JENKINS-59858 Re: Add ability to use an AMI query instead of a static AMI I would really love to have this. Every time I rebuild the worker image, I have to go back to Jenkins and update the static AMI. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202595.1571514701000.5486.1585858980228%40Atlassian.JIRA.
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title Jesse Glick resolved as Fixed Laurent Hory please do not reopen. If you believe you have discovered a regression, file a separate issue linked to this one with complete, minimal steps to reproduce from scratch. Jenkins / JENKINS-58290 WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Major Hayden created an issue Jenkins / JENKINS-61788 jclouds single-use slave never cleaned up Issue Type: Improvement Assignee: Fritz Elfert Components: jclouds-plugin Created: 2020-04-02 18:47 Environment: Jenkins 2.229 jclouds plugin 2.17 Priority: Minor Reporter: Major Hayden When I use the jclouds plugin to spawn instances at DigitalOcean and EC2, I noticed that the single-use slaves are never removed. They are marked offline as soon as the job finishes, but they remain offline in Jenkins and they are active with the cloud provider. As soon as the job finishes, I see this in the logs: 2020-04-02 18:30:42.634+ [id=3070] WARNING j.p.j.c.JCloudsOneOffSlave$JCloudsOneOffSlaveDisposer#tearDown: Taking single-use slave [COMPUTER_NAME] offline. I let it sit for two hours and nothing changed. I had to delete the agent manually from inside Jenkins' build executors listing. Am I missing a step? I'll gladly turn on more debug logging if that would help diagnose the issue.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d}Jenkins 2.229 & jenkins 2.204.2{color} * RocketChat Notification Plugin 1.4.8 * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8 & Centos7{color}but this version running * Jenkins 2.204.2 * RocketChat Notification Plugin 1.4.3 * openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode) * Centos8 & Centos7I am changing Notification message includes. then clicked "save".!image-2020-04-01-19-07-16-720.png|width=680,height=306!then again open but not saved !image-2020-04-01-19-08-22-300.png|width=724,height=339! maybe the bug is in version RocketChat Notification 1.4.8
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.202124.1569316263000.5444.1585849260493%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d} {color:#172b4d} Jenkins 2.229 & jenkins 2.204.2{color} {color} * {color:#172b4d} RocketChat Notification Plugin 1.4.8 {color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8 & Centos7{color}but this version running * Jenkins 2.204.2 * RocketChat Notification Plugin 1.4.3 * openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode) * Centos8 & Centos7I am changing Notification message includes. then clicked "save".!image-2020-04-01-19-07-16-720.png|width=680,height=306!then again open but not saved !image-2020-04-01-19-08-22-300.png|width=724,height=339! maybe the bug is in version RocketChat Notification 1.4.8
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.202124.1569316263000.5431.1585849200360%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title
Oguz halit sak edited a comment on JENKINS-59503
Re: Plugin does not save settings
similar problem here * {color:#172b4d} {color:#172b4d} Jenkins 2.229 & jenkins 2.204.2 {color} {color} * {color:#172b4d}Plugin 1.4.8{color} * {color:#172b4d}openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode){color} * {color:#172b4d}Centos8 & Centos7 {color} but this version running * Jenkins 2.204.2 * Plugin 1.4.3 * openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode) * Centos8 & Centos7 I am changing Notification message includes. then clicked "save".!image-2020-04-01-19-07-16-720.png|width=680,height=306!then again open but not saved !image-2020-04-01-19-08-22-300.png|width=724,height=339!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.202124.1569316263000.5418.1585849080400%40Atlassian.JIRA.
[JIRA] (JENKINS-51476) Git parameter plugin is not retrieving revision number
Title: Message Title Carlos Hortelano closed an issue as Fixed Jenkins / JENKINS-51476 Git parameter plugin is not retrieving revision number Change By: Carlos Hortelano Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.190836.152698213.5406.1585847820242%40Atlassian.JIRA.
[JIRA] (JENKINS-51476) Git parameter plugin is not retrieving revision number
Title: Message Title
Carlos Hortelano updated an issue
Jenkins / JENKINS-51476
Git parameter plugin is not retrieving revision number
Change By:
Carlos Hortelano
Hi, Trying to make some functional tests with git parameter plugin, I realised that when configuring "Revision" as input parameter, the list appears as it was empty. I don't have this problem when defining branch or tag as input parameters. In the image below you can see the issue I'm reporting:!revision_menu.jpg!However, I've seen that in this list there is content, because I'm able to click on any item on it and, when launching the job, it indicates me the revision I'm working with, and it is different depending on the row of the list I clicked. *In summary, the issue* *is that Jenkins doesn't show the revisions in the list, but they are really there.* Investigating this strange behaviour I've seen this message in Jenkins log: lo _Did not find author pattern author Carlos Beltran Hortelano Sancho 2017-11-28T08:27:05+0100_ This message is returned in java class *RevisionInfoFactory.java,* whose source code is here: *[https://github.com/jenkinsci/git-parameter-plugin/blob/master/src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/RevisionInfoFactory.java]*Analysing the code I assume that _author Carlos Beltran Hortelano Sancho 2017-11-28T08:27:05+0100_ __ corresponds to _authorLine_ variable. In this case, it seems clear that the pattern that Jenkins Git parameter plugin is obtaining from Git doesn't match with the one defined here in *RevisionInfoFactory.java:*_public static final Pattern AUTHOR_LINE_PATTERN = Pattern.compile("author (.* <.*@.*>) (__d\{10}) ([\\+-|file://+-/]__d\{4})");_ Have you found any similar issue before? Is there a plan to resolve this? Regards
Add Comment
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title
Félix Queiruga Balado commented on JENKINS-61480
Re: Dark Theme
I don't know how well would that play on normal UI development. I think it would be a bit of an annoyance to need to always remember the dark mode. My ideal solution would be to use CSS variables that a dark theme could override. Example:
// Jenkins core stylesheet
:root {
--body-background: #fefefe;
}
body {
background-color: var(--body-background);
}
// On the dark theme stylesheet
:root {
--body-background: #000;
}
I think it's the only way to make it so that the changes will scale. It still has coupling problems, as the CSS variables would then become an API that plugin stylesheets could use. It also needs some deep refactors and changes to happen, but no lesser than having to add a dark comment to all styleshets.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205164.1584202104000.5393.1585846440232%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Vincent Letarouilly commented on JENKINS-60143 Re: Behaviour SSH Checkout not working after Jenkins restart I added a few logs in GitLabSCMBuilder.java and it seems that his httpRemote & sshRemote fields are null when Jenkins restarted: serverUrl: [https://git.example.io] httpRemote: [null] sshRemote: [null] credentialsId: [gitlab-deploy-key] projectPath: [opa/jenkins-test] I added this log just before withGitLabRemote(); on line 205 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203004.1573562285000.5389.1585846260307%40Atlassian.JIRA.
[JIRA] (JENKINS-61706) InsightVM MultiBranch Jobs
Title: Message Title Francisco Javier Vasquez commented on JENKINS-61706 Re: InsightVM MultiBranch Jobs Suggested solution done in the following pull request: https://github.com/jenkinsci/rapid7-insightvm-container-assessment-plugin/pull/8 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205531.1585295263000.5386.1585846140117%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title
Gábor Tasnádi commented on JENKINS-61480
Re: Dark Theme
That's exactly what I want to avoid. My goal with it would be to be more persistent. You would just need to add a css comment on the line that would look different on the dark theme, so in 1 css file you could define the support for the dark-mode plugin. For example you have in the main css: body { background-color: #ff; /* D@RK: #00 */ } If in a new Jenkins version you decided to rename the css tag to like '#body', but you still have that comment, the program can still substitute it when dark mode is on.This way you only have 1 css file but it has a dark mode and a normal mode. It wouldn't be at runtime though. Only at startup, plugin upgrading, installing or removing. It would cache the substituted css in a folder, and render it if a view needs it.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205164.1584202104000.5384.1585846080153%40Atlassian.JIRA.
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title
Laurent Hory reopened an issue
Hi, fix for this issue cause also a freeze during pytest execution on docker node The sh command are block during execution With the diagnostics parameters the execution works correctly
-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true
The context is an pipeline to launch pytest with tox
docker_img_version='0.17'
launch_container_with_user='jenkins'
parser_name='sweep_tools'
github_cred_id='xx'
github_url='g...@github.com:xxx.git'
pipeline {
agent {
docker {
image 'x/analytics/ci_process:'+docker_img_version
label 'slaves_host'
args '-u jenkins -e POSTGRESQL_USER= -e POSTGRESQL_PASSWORD= -e POSTGRESQL_DATABASE=x'
customWorkspace "/home/jenkins/workspace/${env.JOB_NAME}"
}
}
stages {
stage('Delete tox cache') {
steps {
dir("${env.WORKSPACE}/.tox") {
deleteDir()
}
}
}
stage('Test execution') {
steps {
sh 'tox'
junit 'tests/results/results.xml'
cobertura autoUpdateHealth: false, autoUpdateStability: false, coberturaReportFile: 'tests/results/coverage.xml', conditionalCoverageTargets: '70, 0, 0', failUnhealthy: false, failUnstable: false, lineCoverageTargets: '80, 0, 0', maxNumberOfBuilds: 0, methodCoverageTargets: '80, 0, 0', onlyStable: false, sourceEncoding: 'ASCII', zoomCoverageChart: false
}
}
}
}
The code in tox.ini file is
[tox]
envlist = py36[testenv]
install_command = pip install {opts} {packages}
deps =
pytest
pytest-cov
pytest-flask
chardet
commands = pytest --cov=sweep_tools --cov-report term-missing --cov-report xml:tests/results/coverage.xml --junitxml tests/results/results.xml
Actually the command line executed in step is and freeze just after pytest execution:
sh -c "({ while [ -d '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d' -a \! -f '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/jenkins-result.txt' ]; do touch '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/jenkins-log.txt'; sleep 3; done } & jsc=durable-07cc39a960911d2b0363cd9d28761c7c; JENKINS_SERVER_COOKIE=$jsc 'sh' -xe '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/script.sh' > '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/jenkins-result.txt.tmp'; mv '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/jenkins-result.txt.tmp' '/home/jenkins/workspace/auto_ci/sweep_tools/dev@tmp/durable-d4d01f8d/jenkins-result.txt'; wait) >&- 2>&- &"
I can fix the the freeze with following command line:
[JIRA] (JENKINS-61773) Docker images for IBM s390x
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61773 Docker images for IBM s390x Change By: Mark Waite Summary: Improve Docker images for IBM s390x support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205611.1585798038000.5375.1585844400196%40Atlassian.JIRA.
[JIRA] (JENKINS-61773) Docker images for IBM s390x
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61773 Docker images for IBM s390x Change By: Mark Waite Epic Name: Improve Docker images for IBM s390x support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205611.1585798038000.5376.1585844400216%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Docker images for IBM PowerPC 64
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Docker images for IBM PowerPC 64 Change By: Mark Waite Epic Name: Improve Docker images for IBM PowerPC support 64 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205613.1585800393000.5374.1585844400149%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Docker images for IBM PowerPC 64
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Docker images for IBM PowerPC 64 Change By: Mark Waite Summary: Improve Docker images for IBM PowerPC support 64 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205613.1585800393000.5373.1585844340206%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Docker images for ARM 64
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Docker images for ARM 64 Change By: Mark Waite Epic Name: Improve Docker images for ARM 64 support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205614.1585801513000.5372.1585844340189%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Docker images for ARM 64
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Docker images for ARM 64 Change By: Mark Waite Summary: Improve Docker images for ARM 64 support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205614.1585801513000.5371.1585844340142%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title R. Fitzner edited a comment on JENKINS-61780 Re: Git working dir detection not working Concerning your suggestion of using recordIssues ... maybe you remember this ticket ...https://issues.jenkins-ci.org/browse/JENKINS-61196 I haven't had time to overwork it yet (updated Jira ticket) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5370.1585844280109%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick updated JENKINS-61787 Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205626.1585843138000.5368.1585844160181%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick started work on JENKINS-61787 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205626.1585843138000.5367.1585844160152%40Atlassian.JIRA.
[JIRA] (JENKINS-61196) Display one aggregation trend chart independently how often *Issues steps are used
Title: Message Title R. Fitzner reopened an issue updated description Jenkins / JENKINS-61196 Display one aggregation trend chart independently how often *Issues steps are used Change By: R. Fitzner Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205626.1585843138000.5366.1585844100315%40Atlassian.JIRA.
[JIRA] (JENKINS-61196) Display one aggregation trend chart independently how often *Issues steps are used
Title: Message Title
R. Fitzner updated an issue
Jenkins / JENKINS-61196
Display one aggregation trend chart independently how often *Issues steps are used
Change By:
R. Fitzner
Please make the steps {{recordIssues}} and {{publishIssues}} configurable in the way that Jenkins will display one aggregation trend chart and no scanner-specific trend chart on the Jenkins job status page independent how often the steps are configured/called. For example:For the {{publishIssues}} step you could add the option like this:{code:java}publishIssues trendChartType: 'AGGREGATION_ONLY'{code}This option would allow me using multipe {{publishIssues}} steps.Instead of {{this}}:{code:java}recordIssues aggregatingResults: true{code}you could align it with {{publishIssues}} and add the same options trendChartTypeWhat do you think?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Félix Queiruga Balado commented on JENKINS-61480 Re: Dark Theme AFAIK ui-theme is unmaintained, only simple-theme is active. I'm not really sure what your goal with modifying all css files is, is it at runtime? still looks really intense and brittle (changes on the main css would always break the dark mode) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.5361.1585844040227%40Atlassian.JIRA.
[JIRA] (JENKINS-61077) Impossible to save Publish over SSH settings: net.sf.json.JSONException: null object
Title: Message Title Matt Sicker commented on JENKINS-61077 Re: Impossible to save Publish over SSH settings: net.sf.json.JSONException: null object That error appears to be from the zephyr-for-jira-test-management plugin, not ssh-plugin. Considering that plugin was listed as unfixed in a previous advisory (https://jenkins.io/security/advisory/2020-03-09/), I'd imagine there's an issue with that plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204568.1581595236000.5358.1585843920215%40Atlassian.JIRA.
[JIRA] (JENKINS-61196) Display one aggregation trend chart independently how often *Issues steps are used
Title: Message Title R. Fitzner updated an issue Jenkins / JENKINS-61196 Display one aggregation trend chart independently how often *Issues steps are used Change By: R. Fitzner Summary: Display one aggregation trend chart independently how often *Issues step is steps are used Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204744.1582539544000.5355.1585843810153%40Atlassian.JIRA.
[JIRA] (JENKINS-61196) Display one aggregation trend chart independently how often *Issues step is used
Title: Message Title
R. Fitzner updated an issue
Jenkins / JENKINS-61196
Display one aggregation trend chart independently how often *Issues step is used
Change By:
R. Fitzner
Please make the steps {{recordIssues}} and {{publishIssues}} configurable in the way that Jenkins will display one aggregation trend chart and no scanner-specific trend chart on the Jenkins job status page independent how often the steps are configured/called.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.204744.1582539544000.5353.1585843740139%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi commented on JENKINS-61480 Re: Dark Theme I mean, regex is really fast and it only needs to be done when a new plugin is added or existing plugin was updated. The problem isn't necessarily how I get the css files, because I can just search them in the static resources folders. It is how can I tell which css is currently being rendered on a page. Because if I render all the substituted css at all the time I can cause conflicts or overrides. I dont really understand how the page rendering works in Stapler. From what I've seen it takes the bound classes then serializes them to xml, but where the actual html rendering is? I made the plugin based on how simple-theme works. The main class extends PageDecorator so it gets called on every page, my header.jelly contains all the css. It also has a location-based automatic turn-on when the sun goes down. Of course the manual way for plugin style support would be to add additional stylesheets on the plugin config page. But it would be nice if I could just get the css currently being rendered on a page and search for the /*D@RK: #ff */ tag or something similar, so if people want to add dark mode support on their plugin they can do that. But anyway, thank you for replying, I'll check out ui-theme. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61196) Display one aggregation trend chart independently how often *Issues step is used
Title: Message Title R. Fitzner updated an issue Jenkins / JENKINS-61196 Display one aggregation trend chart independently how often *Issues step is used Change By: R. Fitzner As soon as the pipeline measures more issues because a new tool is detected used by the git repository then it is quite possible that the defined quality gate will always fail. This is a gap in the plugin. It is not possible to define tool-specific quality gates. Please make Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204744.1582539544000.5348.1585843560178%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick commented on JENKINS-61787 Re: jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Only apparent implementation: https://github.com/jenkinsci/scala-junit-name-decoder-plugin/blob/e172d93fd3e74f3610db658f0b94d029321d2305/src/main/java/org/jenkinsci/plugins/scalajunitnamedecoder/ScalaTestNameTransformer.java Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205626.1585843138000.5346.1585843560118%40Atlassian.JIRA.
[JIRA] (JENKINS-61196) Display one aggregation trend chart independently how often *Issues step is used
Title: Message Title R. Fitzner updated an issue Jenkins / JENKINS-61196 Display one aggregation trend chart independently how often *Issues step is used Change By: R. Fitzner Summary: Define tool-specific quality gates Display one aggregation trend chart independently how often *Issues step is used Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204744.1582539544000.5345.1585843440159%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2020-04-02 15:58 Labels: remoting Priority: Blocker Reporter: Jesse Glick https://ci.jenkins.io/job/Plugins/job/github-branch-source-plugin/job/PR-291/4/console failed with Recording test results Remote call on EC2 (aws) - Ubuntu 18.04 LTS (i-011fe09e35adc9532) failed Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (aws) - Ubuntu 18.04 LTS (i-011fe09e35adc9532) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:998) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137) at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) java.lang.NoClassDefFoundError: Could not
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title R. Fitzner edited a comment on JENKINS-61780 Re: Git working dir detection not working Concerning your suggestion of using recordIssues ... maybe you remember this ticket ...https://issues.jenkins-ci.org/browse/JENKINS-61196I haven't had time to overwork it yet Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5342.1585842420221%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title R. Fitzner commented on JENKINS-61780 Re: Git working dir detection not working Concerning your suggestion of using recordIssues ... maybe you remember this ticket ... https://issues.jenkins-ci.org/browse/JENKINS-61196 I haven't had time to overwork it Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5340.1585842420194%40Atlassian.JIRA.
[JIRA] (JENKINS-61786) Add example Jenkinsfile
Title: Message Title Dolan Murvihill created an issue Jenkins / JENKINS-61786 Add example Jenkinsfile Issue Type: Improvement Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-02 15:40 Priority: Minor Reporter: Dolan Murvihill I haven't been using declarative pipelines for all that long, and I am completely at a loss for where to integrate the bbs_checkout step into my Jenkinsfile. The tutorial video completely skipped this step. A brief example in the README would go a long way. Add Comment
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title R. Fitzner commented on JENKINS-61780 Re: Git working dir detection not working Yes there is one calculated folder too much. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5336.1585841880329%40Atlassian.JIRA.
[JIRA] (JENKINS-44823) Set up artifactory server using Groovy
Title: Message Title
Sarath racer edited a comment on JENKINS-44823
Re: Set up artifactory server using Groovy
you can use below script to update or Bypass HTTP server.based on true or false it will enable/disable the check box (Bypass HTTP Proxy) {code:java}/* Bypass the HTTP proxy in Artifactory plugin */import jenkins.model.* import org.jfrog.* import org.jfrog.hudson.* import org.jfrog.hudson.util.Credentials;def inst = Jenkins.getInstance()def desc = inst.getDescriptor("org.jfrog.hudson.ArtifactoryBuilder")def deployerCredentials = new CredentialsConfig("", "", "")def sinst = [new ArtifactoryServer( "Artifactory", "https://demo-test.com/artifactory", deployerCredentials,deployerCredentials,300, true ,1,1) ]desc.setArtifactoryServers(sinst){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.182881.1497276562000.5334.1585841580363%40Atlassian.JIRA.
[JIRA] (JENKINS-44823) Set up artifactory server using Groovy
Title: Message Title
Sarath racer commented on JENKINS-44823
Re: Set up artifactory server using Groovy
you can use below script to update or Bypass HTTP server.
/* Bypass the HTTP proxy in Artifactory plugin */
import jenkins.model.*
import org.jfrog.*
import org.jfrog.hudson.*
import org.jfrog.hudson.util.Credentials;
def inst = Jenkins.getInstance()
def desc = inst.getDescriptor("org.jfrog.hudson.ArtifactoryBuilder")
def deployerCredentials = new CredentialsConfig("", "", "")
def sinst = [new ArtifactoryServer(
"Artifactory",
"https://demo-test.com/artifactory",
deployerCredentials,deployerCredentials,
300,
true ,1,1) ]
desc.setArtifactoryServers(sinst)
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.182881.1497276562000.5331.1585841460186%40Atlassian.JIRA.
[JIRA] (JENKINS-44823) Set up artifactory server using Groovy
Title: Message Title Sarath racer assigned an issue to Sarath racer Jenkins / JENKINS-44823 Set up artifactory server using Groovy Change By: Sarath racer Assignee: Eyal Ben Moshe Sarath racer Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.182881.1497276562000.5328.1585841100252%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Improve ARM 64 support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Improve ARM 64 support Change By: Mark Waite Support Provide ARM 64 processors running Linux JVM's in docker images from the Jenkins project, including:* Agents (ssh, JNLP, WebSockets) with Java 8 Hotspot and Java 11 Hotspot* Masters with Java 8 Hotspot and Java 11 Hotspot * Masters in Docker with Java 8 and Java 11 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205614.1585801513000.5324.1585840740134%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Improve ARM 64 support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Improve ARM 64 support Change By: Mark Waite Epic Name: Improve ARM 64 support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205614.1585801513000.5323.1585840740104%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Improve IBM PowerPC support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Improve IBM PowerPC support Change By: Mark Waite Support Provide Docker images for IBM PowerPC running Linux JVM's in the Jenkins project, including:* Agents (ssh, JNLP, WebSockets) with Java 8 Hotspot and Java 11 Hotspot* Masters with Java 8 Hotspot and Java 11 Hotspot * Masters in Docker with Java 8 and Java 11 See INFRA-2519 for the necessary infrastructure (PowerPC and s390x) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205613.1585800393000.5321.1585840680157%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Improve IBM PowerPC support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Improve IBM PowerPC support Change By: Mark Waite Epic Name: Improve IBM PowerPC support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205613.1585800393000.5320.1585840680136%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Improve ARM 64 support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Improve ARM 64 support Change By: Mark Waite Summary: Support Improve ARM 64 in Jenkins support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205614.1585801513000.5322.1585840680172%40Atlassian.JIRA.
[JIRA] (JENKINS-61773) Improve IBM s390x support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61773 Improve IBM s390x support Change By: Mark Waite Epic Name: Improve IBM s390x support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205611.1585798038000.5318.1585840620104%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Improve IBM PowerPC support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Improve IBM PowerPC support Change By: Mark Waite Summary: Support Improve IBM PowerPC in Jenkins support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205613.1585800393000.5319.1585840620189%40Atlassian.JIRA.
[JIRA] (JENKINS-61773) Improve IBM s390x support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61773 Improve IBM s390x support Change By: Mark Waite Summary: Support Improve IBM s390x in Jenkins support Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205611.1585798038000.5316.1585840560147%40Atlassian.JIRA.
[JIRA] (JENKINS-61773) Improve IBM s390x support
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61773 Improve IBM s390x support Change By: Mark Waite Support Provide IBM s390x running Linux JVM's in Docker images from the Jenkins project, including:* Agents (ssh, JNLP, WebSockets) with Java 8 OpenJ9, Java 11 Hotspot, and Java 11 OpenJ9* Masters with Java 8 OpenJ9, Java 11 Hotspot, and Java 11 OpenJ9 * Masters in Docker with Java 8 and Java 11 See INFRA-2519 for the necessary infrastructure Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205611.1585798038000.5317.1585840560182%40Atlassian.JIRA.
[JIRA] (JENKINS-22006) IBM JDK agent disconnects in 1.532.2
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-22006 IBM JDK agent disconnects in 1.532.2 Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.153783.1393673328000.5312.1585840020574%40Atlassian.JIRA.
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Kevin Williamson started work on JENKINS-61783 Change By: Kevin Williamson Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205622.1585835118000.5310.1585839900372%40Atlassian.JIRA.
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title Aytunc BEKEN commented on JENKINS-61744 Re: Remote file plugin should allow to use folders or wildcards as marker files I will check it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205573.158558355.5308.1585839900336%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Aytunc BEKEN edited a comment on JENKINS-61601 Re: Unable to trigger job on deletion of branch when configured with job DSL. [~shadycuz] Thanks for the feedback and detailed explanation. You are right, * character comes from the UI not defined in the code. I think this is the reason why It was failing with JOB dsl. I am happy that fix is worked. I will check this situation for other variables in the plugin to prevent future possible error.Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205299.1584706587000.5304.1585839660185%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Aytunc BEKEN commented on JENKINS-61601 Re: Unable to trigger job on deletion of branch when configured with job DSL. Levi Blaney Thanks for the feedback and detailed explanation. You are right, * character comes from the UI not defined in the code. I think this is the reason why It was failing with JOB dsl. I am happy that fix is worked. I will check this situation for other variables in the plugin to prevent future possible error. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205299.1584706587000.5300.1585839540152%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Task/Build permission
Title: Message Title
Juan Pablo Santos Rodríguez updated an issue
Jenkins / JENKINS-61785
REST API requires Task/Build permission
Change By:
Juan Pablo Santos Rodríguez
After upgrading to Jenkins LTS 2.222.1 + role-strategy-plugin 2.16, REST API calls have stopped working. On the Log we can see {code}2020-04-02 14:42:46.468+ [id=20318] INFO o.e.j.s.h.ContextHandler$Context#log: While serving http://XXX/jenkins/job/YY-pipeline/buildWithParameters: hudson.security.AccessDeniedException2: inetic is missing the Job/Build permission{code}which is exactly what we get through the REST APIinetic has Admin permissions granted to a role, set throuch role-strategy-plugin and is able to execute any jobs through the UI.We're using user+token for auth, which should not need Jenkins-Crumb header. Nevertheless, we've also tried user+password+crumb and user+token+crumb and we get the same results. We've also tried setting {{hudson.security.csrf.GlobalCrumbIssuerConfiguration.DISABLE_CSRF_PROTECTION}} to either {{true}} or {{false}}, but again, it makes no difference.May be the security hardening done on 2.222.1 / 2.204.6 affects the role-strategy-plugin?Only workaround found so far is to set global Read + Build permissions, however that allows every user to execute everything without being logged which is not so funny.EDIT: forgot to add, $JENKINS/whoAmI for user yields:{code}Name: INETICIsAuthenticated?: trueAuthorities: * "authenticated"{code}
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Oleg Nenashev commented on JENKINS-61480 Re: Dark Theme https://github.com/jenkinsci/uithemes-plugin can partially help also, but it is not as flexible as Simple Theme plugin (CC Mark Waite) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.5295.1585839420331%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Task/Build permission
Title: Message Title
Juan Pablo Santos Rodríguez updated an issue
Jenkins / JENKINS-61785
REST API requires Task/Build permission
Change By:
Juan Pablo Santos Rodríguez
After upgrading to Jenkins LTS 2.222.1 + role-strategy-plugin 2.16, REST API calls have stopped working. On the Log we can see {code}2020-04-02 14:42:46.468+ [id=20318] INFO o.e.j.s.h.ContextHandler$Context#log: While serving http://XXX/jenkins/job/YY-pipeline/buildWithParameters: hudson.security.AccessDeniedException2: inetic is missing the Job/Build permission{code}which is exactly what we get through the REST APIinetic has Admin permissions set throuch role-strategy-plugin and is able to execute any jobs through the UI.We're using user+token for auth, which should not need Jenkins-Crumb header. Nevertheless, we've also tried user+password+crumb and user+token+crumb and we get the same results. We've also tried setting {{hudson.security.csrf.GlobalCrumbIssuerConfiguration.DISABLE_CSRF_PROTECTION}} to either {{true}} or {{false}}, but again, it makes no difference.May be the security hardening done on 2.222.1 / 2.204.6 affects the role-strategy-plugin?Only workaround found so far is to set global Read + Build permissions, however that allows every user to execute everything without being logged which is not so funny. EDIT: forgot to add, $JENKINS/whoAmI for user yields:{code}Name: INETICIsAuthenticated?: trueAuthorities: * "authenticated"{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61785) REST API requires Task/Build permission
Title: Message Title Juan Pablo Santos Rodríguez created an issue Jenkins / JENKINS-61785 REST API requires Task/Build permission Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2020-04-02 14:54 Environment: Jenkins LTS 2.222.1 role-strategy-plugin 2.16 Priority: Major Reporter: Juan Pablo Santos Rodríguez After upgrading to Jenkins LTS 2.222.1 + role-strategy-plugin 2.16, REST API calls have stopped working. On the Log we can see 2020-04-02 14:42:46.468+ [id=20318] INFO o.e.j.s.h.ContextHandler$Context#log: While serving http://XXX/jenkins/job/YY-pipeline/buildWithParameters: hudson.security.AccessDeniedException2: inetic is missing the Job/Build permission which is exactly what we get through the REST API inetic has Admin permissions set throuch role-strategy-plugin and is able to execute any jobs through the UI. We're using user+token for auth, which should not need Jenkins-Crumb header. Nevertheless, we've also tried user+password+crumb and user+token+crumb and we get the same results. We've also tried setting hudson.security.csrf.GlobalCrumbIssuerConfiguration.DISABLE_CSRF_PROTECTION to either true or false, but again, it makes no difference. May be the security hardening done on 2.222.1 / 2.204.6 affects the role-strategy-plugin? Only workaround found so far is to set global Read + Build permissions, however that allows every user to execute everything without being logged which is not so funny.
[JIRA] (JENKINS-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Jaroslav Lhotak commented on JENKINS-61772 Re: Multibranch pipeline cannot be disabled in GUI, only in config.xml thanks Aytunc BEKEN, I as not sure which component to use. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205610.1585773108000.5288.1585839180181%40Atlassian.JIRA.
[JIRA] (JENKINS-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Aytunc BEKEN commented on JENKINS-61772 Re: Multibranch pipeline cannot be disabled in GUI, only in config.xml I think this is not related to multibranch-action-triggers-plugin, therefore I will change the components. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205610.1585773108000.5280.1585839000515%40Atlassian.JIRA.
[JIRA] (JENKINS-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Aytunc BEKEN assigned an issue to Unassigned Jenkins / JENKINS-61772 Multibranch pipeline cannot be disabled in GUI, only in config.xml Change By: Aytunc BEKEN Assignee: Aytunc BEKEN Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205610.1585773108000.5286.1585839000764%40Atlassian.JIRA.
[JIRA] (JENKINS-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Aytunc BEKEN updated an issue Jenkins / JENKINS-61772 Multibranch pipeline cannot be disabled in GUI, only in config.xml Change By: Aytunc BEKEN Component/s: workflow-multibranch-plugin Component/s: multibranch-action-triggers-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205610.1585773108000.5283.1585839000667%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Félix Queiruga Balado commented on JENKINS-61480 Re: Dark Theme TBH I don't think scanning and substituting existing files will scale well, and it may not be ressilient to changes. I agree with Oleg Nenashev that a better alternative would be to use a custom theme using the simple-theme-plugin. You can take inspiration on the material or neo2 themes. In the medium/long term I would like to have the UI themable using CSS variables, but we lack infrastructure at the moment for that. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.5276.1585838820246%40Atlassian.JIRA.
[JIRA] (JENKINS-61759) PipelineJob trigger deprecation for gitlabpush error
Title: Message Title William Hunzicker started work on JENKINS-61759 Change By: William Hunzicker Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205596.1585680916000.5267.1585836480215%40Atlassian.JIRA.
[JIRA] (JENKINS-61784) Pipeline Status - Unstable builds are reported as failed.
Title: Message Title Tobias Günther created an issue Jenkins / JENKINS-61784 Pipeline Status - Unstable builds are reported as failed. Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2020-04-02 13:59 Priority: Minor Reporter: Tobias Günther Current Mapping: Success -> Success Unstable -> Failure Failure -> Failure Desired Mapping: Success -> Success Unstable -> Success Failure -> Failure Unfortunately Gitlab does not have an "unstable" status, so a mapping is required. I would prefer an option, to leave this decision to the user. The current solution is giving us lot's of false alerts. Add Comment
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Karl Wirth assigned an issue to Kevin Williamson Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Change By: Karl Wirth Assignee: Kevin Williamson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205622.1585835118000.5258.1585835280224%40Atlassian.JIRA.
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205622.1585835118000.5260.1585835280317%40Atlassian.JIRA.
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Issue Type: Improvement Assignee: Unassigned Attachments: image-2020-04-02-14-43-10-072.png, image-2020-04-02-14-43-53-073.png Components: p4-plugin Created: 2020-04-02 13:45 Environment: p4-plugin 1.10.12 Priority: Critical Reporter: Karl Wirth A recent security change has enforced that Swarm needs to send the paramaters of the job as a POST not GET. To acheive this in Swarm you need to move the paramaters that were in the URL after '?' to the 'Post BODY' section. For example: becomes: Add Comment
[JIRA] (JENKINS-25304) Job polling hangs while a build is running - only when branch specifier contains wildcard
Title: Message Title Alexey Bychko commented on JENKINS-25304 Re: Job polling hangs while a build is running - only when branch specifier contains wildcard I faced the same issue with wildcard in branch name Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.158814.1414194728000.5248.1585834980376%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title
Ulli Hafner edited a comment on JENKINS-61780
Re: Git working dir detection not working
What I do not understand in your log: is the path to the git repository correct: {{/var/lib/jenkins/workspace/kins_pipeline_library_ci_develop/jenkins_pipeline_library_ci/jenkins_pipeline_library_ci}}? Or is there one {{jenkins_pipeline_library_ci}} too much?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205619.1585826585000.5246.1585834500347%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title Ulli Hafner commented on JENKINS-61780 Re: Git working dir detection not working What I do not understand in your log: is the path to the git repository correct: /var/lib/jenkins/workspace/kins_pipeline_library_ci_develop/jenkins_pipeline_library_ci/jenkins_pipeline_library_ci? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5244.1585834440121%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title Ulli Hafner commented on JENKINS-61780 Re: Git working dir detection not working Side note (unrelated to the issue): Is there a reason that you use this scripted call as part of your DSL pipeline? Actually `recordIssues` should work in pure DSL as well. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5242.1585834380126%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61780 Git working dir detection not working Change By: Ulli Hafner Component/s: analysis-model-api-plugin Component/s: forensics-api-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5240.1585834260223%40Atlassian.JIRA.
[JIRA] (JENKINS-61780) Git working dir detection not working
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61780 Git working dir detection not working Change By: Ulli Hafner Summary: In declarative pipelines "SCM Blames" (git blamer) is Git working dir detection not working since version 8.x Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205619.1585826585000.5238.1585834200147%40Atlassian.JIRA.
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Ben Faucher commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
I just ran into this issue. Is this going to be addressed? Why is the entrypoint overridden in the first place?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.178090.1485167605000.5205.1585833961010%40Atlassian.JIRA.
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Jesse Glick resolved as Cannot Reproduce Hard to say offhand what might be wrong. Most likely something in your environment / configuration. Jenkins / JENKINS-59096 Mercurial plugin stops working after password change Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60455) Credentials block in mercurial plugins shows Oops!
Title: Message Title Jesse Glick resolved as Incomplete Perhaps you somehow updated the mercurial plugin without a matching update to credentials plugin. Should not happen if you use the update center but who knows. Jenkins / JENKINS-60455 Credentials block in mercurial plugins shows Oops! Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-37739) Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline
Title: Message Title Andrej Staruch commented on JENKINS-37739 Re: Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline Hi, something similar was addressed in the warning-ng plugin https://issues.jenkins-ci.org/browse/JENKINS-54027?attachmentViewMode=list. Maybe if the id and name parameters would be added, it could solve this issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.173871.1472384428000.5184.1585831860498%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Peter Krefting updated an issue Jenkins / JENKINS-61779 Regression: Job stuck in queue waiting forever after upgrade Change By: Peter Krefting Summary: Regression: Job stock stuck in queue waiting forever after upgrade Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205618.158582599.5181.1585831800075%40Atlassian.JIRA.
