[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Aytunc BEKEN started work on JENKINS-61949 Change By: Aytunc BEKEN 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.205829.1587131764000.20190.1588312020436%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Aytunc BEKEN commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Cool! I will start working on this issue. 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.205829.1587131764000.20187.1588312020378%40Atlassian.JIRA.
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title Aytunc BEKEN closed an issue as Fixed Jenkins / JENKINS-61744 Remote file plugin should allow to use folders or wildcards as marker files Change By: Aytunc BEKEN 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.205573.158558355.20184.1588311900278%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 Great! 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.205573.158558355.20181.1588311840431%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt commented on JENKINS-62133 Re: Configure screen: Resource Root URL validation error - 404 instance-identity Daniel Beck - thanks for responding and diagnosing so quickly. 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.206049.1588285097000.20178.1588305180114%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck commented on JENKINS-62133 Re: Configure screen: Resource Root URL validation error - 404 instance-identity Just to confirm, I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page. This is correct; it's just the form validation that's affected, as it can no longer distinguish a 404 response from a resource root URL from just any other 404 response. 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.206049.1588285097000.20176.1588305000148%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck updated JENKINS-62133 Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Daniel Beck 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.206049.1588285097000.20173.1588304760606%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck started work on JENKINS-62133 Change By: Daniel Beck 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.206049.1588285097000.20170.1588304760496%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Daniel Beck Labels: lts-candidate regression winstone 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.206049.1588285097000.20167.1588303260190%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck commented on JENKINS-62133 Re: Configure screen: Resource Root URL validation error - 404 instance-identity Upstream regression is https://github.com/eclipse/jetty.project/issues/4154 (and rejected). 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.206049.1588285097000.20164.1588303200230%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck commented on JENKINS-62133 Re: Configure screen: Resource Root URL validation error - 404 instance-identity This broke in 2.205 because of the Winstone update that changed the 404 error message format. The form validation expects a message to occur in a 404 error response and it seems it no longer matches exactly. That's the only difference between the "404 Not Found" error, and "This is a previously set up resource domain". 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.206049.1588285097000.20158.1588303140361%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Daniel Beck Labels: regression winstone 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.206049.1588285097000.20161.1588303140450%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman edited a comment on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning > Credential domains are not intended to prevent credentials from being used against the wrong services.> Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this.Okay, so I get it . .. According to the documentation, since Since this plugin is refusing to use a credential that is in the wrong domain, it is a incorrect behavior related to credentials. Thus a security issue. Now what? Does this move into the SECURITY JIRA and get prioritized against other security issues? 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.201369.1566328715000.20154.1588302060182%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Daniel Beck Labels: regression 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.206049.1588285097000.20152.1588301940292%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck commented on JENKINS-62133 Re: Configure screen: Resource Root URL validation error - 404 instance-identity This worked as intended in 2.200. 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.206049.1588285097000.20149.1588301940246%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning > Credential domains are not intended to prevent credentials from being used against the wrong services. > Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this. Okay, so... According to the documentation, since this plugin is refusing to use a credential that is in the wrong domain, it is a security issue. Now what? Does this move into the SECURITY JIRA and get prioritized against other security issues? 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.201369.1566328715000.20145.1588301820129%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Daniel Beck Assignee: Daniel Beck 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.206049.1588285097000.20143.1588301700177%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck commented on JENKINS-62133 Re: Configure screen: Resource Root URL validation error - 404 instance-identity I am able to reproduce it with a 2.234 docker image. Weird, I specifically tested 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.206049.1588285097000.20140.1588301400131%40Atlassian.JIRA.
[JIRA] (JENKINS-62134) java.io.IOException: Process working directory doesn't exist!
Title: Message Title Saurabh Singh created an issue Jenkins / JENKINS-62134 java.io.IOException: Process working directory doesn't exist! Issue Type: Task Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 2020-05-01 02:13 Environment: Operating System:- MAC java version "1.8.0_251" Java(TM) SE Runtime Environment (build 1.8.0_251-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode) Jenkins - 2.222.3 I installed jenkins bvia the dmg file and I am running jenkins on Safari Priority: Minor Reporter: Saurabh Singh Hi, I am new to Jenkins. I created a simple pipeline, I get the below error when I start the build process. the ansible-playbook works fine if I run it as a freestyle project. > Deployin SNMP on ASA and Router ...[Pipeline] ansiblePlaybook[SNMP-PIPE] $ ansible-playbook /Users/saurabh/Ansible/Ansible-Roles/Jenkins-Project-1/Main.yml -i /Users/saurabh/Ansible/Ansible-Roles/Jenkins-Project-1/hosts FATAL: command execution failed java.io.IOException: Process working directory '/Users/Shared/Jenkins/Home/workspace/SNMP-PIPE' doesn't exist! at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:221) at hudson.Launcher$LocalLauncher.launch(Launcher.java:936) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at hudson.Launcher$ProcStarter.join(Launcher.java:465) at org.jenkinsci.plugins.ansible.CLIRunner.execute(CLIRunner.java:49) at org.jenkinsci.plugins.ansible.AbstractAnsibleInvocation.execute(AbstractAnsibleInvocation.java:290) at org.jenkinsci.plugins.ansible.AnsiblePlaybookInvocation.execute(AnsiblePlaybookInvocation.java:31) at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:261) at
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan The scan keeps a report of vulnerabilities and policy evaluations. This happens during each scan Clean up should always take place unless there was some edge case that stopped that from happening. Network latency, Jenkins hiccup, etc. Depending on how your scan job is configured, all jobs should retain the output of the report and there is a historical linkage in your workspace. Hope that helps 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.205931.1587715343000.20135.1588295820369%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Tony Wen commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Marky Jackson, thanks. we still have questions, forgive me not familiar with plugin code. Could you help us identifying under which condition we will have aritifacts. which artifacts/json report will be archived automatically under which condition when clean up case will be executed and when not? is it possible to keep those json output always? 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.205931.1587715343000.20132.1588295580319%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Summary: Configure screen : Resource Root URL validation error - 404 instance-identity 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.206049.1588285097000.20129.1588285980067%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: sample-resource-root-url-reachable-2020-04-30.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.206049.1588285097000.20128.1588285920165%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: sample-resource-root-url-reachale-2020-04-30.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.206049.1588285097000.20127.1588285920096%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt edited a comment on JENKINS-62133 Re: Configure screen Resource Root URL validation error - 404 instance-identity Jenkins 2.234, AWS ec2 instance running jenkins container.Jenkins URL: https://jenkins-backend.dev.cicdenv.com/Resoure Root URL: https://builds-backend.dev.cicdenv.com/Both DNS names go to an AWS ALB with host routing rules.jenkins: crumbIssuer:standard: excludeClientIPFromCrumb: trueThe server/resource root URLs are set in groovy hooky scripts:JenkinsLocationConfiguration.get().url = "">ResourceDomainConfiguration.get().url = "">I haven't used a separate resource root url before.https://github.com/jenkinsci/jenkins/pull/4239I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page. I don't think this problem is new in version 2.234. 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.206049.1588285097000.20126.1588285800049%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: sample-server-url-2020-04-30.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.206049.1588285097000.20123.1588285740324%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: sample-resource-root-url-reachale-2020-04-30.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.206049.1588285097000.20125.1588285740357%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: Screen Shot 2020-04-30 at 15.09.29.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.206049.1588285097000.20121.1588285740287%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: Screen Shot 2020-04-30 at 15.08.29.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.206049.1588285097000.20122.1588285740303%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: sample-resource-root-url-2020-04-30.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.206049.1588285097000.20124.1588285740347%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Attachment: Screen Shot 2020-04-30 at 15.06.40.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.206049.1588285097000.20120.1588285740243%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen Resource Root URL validation error - 404 instance-identity
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Configure screen Resource Root URL validation error - 404 instance-identity Change By: Fred Vogt Summary: Configure screen Resource Root URL shows 404 validation error in configure screen - 404 instance-identity 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.206049.1588285097000.20119.1588285620056%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Resource Root URL shows 404 validation error in configure screen
Title: Message Title Fred Vogt edited a comment on JENKINS-62133 Re: Resource Root URL shows 404 validation error in configure screen Jenkins 2.234, AWS ec2 instance running jenkins container.Jenkins URL: https://jenkins-backend.dev.cicdenv.com/Resoure Root URL: https://builds-backend.dev.cicdenv.com/Both DNS names go to an AWS ALB with host routing rules.jenkins: crumbIssuer:standard: excludeClientIPFromCrumb: trueThe server/resource root URLs are set in groovy hooky scripts:JenkinsLocationConfiguration.get().url = "">ResourceDomainConfiguration.get().url = ""> I haven't used a separate resource root url before.https://github.com/jenkinsci/jenkins/pull/4239I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page. 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.206049.1588285097000.20118.1588285560047%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Resource Root URL shows 404 validation error in configure screen
Title: Message Title Fred Vogt commented on JENKINS-62133 Re: Resource Root URL shows 404 validation error in configure screen Jenkins 2.234, AWS ec2 instance running jenkins container. Jenkins URL: https://jenkins-backend.dev.cicdenv.com/ Resoure Root URL: https://builds-backend.dev.cicdenv.com/ Both DNS names go to an AWS ALB with host routing rules. jenkins: crumbIssuer: standard: excludeClientIPFromCrumb: true The server/resource root URLs are set in groovy hooky scripts: JenkinsLocationConfiguration.get().url = ""> ResourceDomainConfiguration.get().url = ""> 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.206049.1588285097000.20117.1588285380045%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Resource Root URL shows 404 validation error in configure screen
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-62133 Resource Root URL shows 404 validation error in configure screen Change By: Fred Vogt Environment: Jenkins 2.234 , local or AWS ec2 instance running jenkins container.Jenkins URL: https://jenkins-backend.dev.cicdenv.com/Resoure Root URL: https://builds-backend.dev.cicdenv.com/Both DNS names go to an AWS ALB with host routing rules.jenkins: crumbIssuer:standard: excludeClientIPFromCrumb: trueJenkinsLocationConfiguration.get().url = "">ResourceDomainConfiguration.get().url = ""> 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.206049.1588285097000.20116.1588285320063%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Resource Root URL shows 404 validation error in configure screen
Title: Message Title Fred Vogt created an issue Jenkins / JENKINS-62133 Resource Root URL shows 404 validation error in configure screen Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2020-04-30 at 15.06.40.png, Screen Shot 2020-04-30 at 15.08.29.png, Screen Shot 2020-04-30 at 15.09.29.png Components: core Created: 2020-04-30 22:18 Environment: Jenkins 2.234, AWS ec2 instance running jenkins container. Jenkins URL: https://jenkins-backend.dev.cicdenv.com/ Resoure Root URL: https://builds-backend.dev.cicdenv.com/ Both DNS names go to an AWS ALB with host routing rules. jenkins: crumbIssuer: standard: excludeClientIPFromCrumb: true JenkinsLocationConfiguration.get().url = "" ResourceDomainConfiguration.get().url = "" Priority: Minor Reporter: Fred Vogt It seems that something is wrong in how this validation is performed. This is reproduceable running locally with: server url: https://localhost:8443 resource root url: https://127.0.0.1:8443
[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-62132
JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Change By:
Mark Waite
I upgraded my Bitbucket account to use two factor authentication. As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead.The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git. I changed the credential value from actual password to app password and the job continued to clone and run successfully.Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password. With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket. Alternatives to avoid the issue include:* Use CLI git instead of JGit* Use ssh protocol ( {{g...@bitbucket.org:markewaite/bin.git}} ) instead of https protocol ( {{https://markewa...@bitbucket.org/markewaite/bin.git}} )
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62132 JGit won't authenticate to 2FA enabled Bitbucket, CLI git does Change By: Mark Waite Assignee: 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.206047.1588282235000.20107.1588282440179%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Marky Jackson commented on JENKINS-61980 Re: Plugin Failed to load the Matrix Monil Patel I will take a look shortly 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.205870.1587423122000.20105.1588282380239%40Atlassian.JIRA.
[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-62132 JGit won't authenticate to 2FA enabled Bitbucket, CLI git does Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2020-04-30 21:30 Environment: Jenkins 2.222.3, git plugin 4.2.2, git client plugin 3.2.1 and pre-release versions from the master branch of the git plugin and git client plugin Priority: Major Reporter: Mark Waite I upgraded my Bitbucket account to use two factor authentication. As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead. The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git. I changed the credential value from actual password to app password and the job continued to clone and run successfully. Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password. With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel commented on JENKINS-61980 Re: Plugin Failed to load the Matrix Hi Marky Jackson I have added images for Jenkins Config for Prometheus and scrap config file of Prometheus service. 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.205870.1587423122000.20101.1588281420115%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel updated an issue Jenkins / JENKINS-61980 Plugin Failed to load the Matrix Change By: Monil Patel Attachment: promethesus-scrap-config.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.205870.1587423122000.20097.1588281300299%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel updated an issue Jenkins / JENKINS-61980 Plugin Failed to load the Matrix Change By: Monil Patel Attachment: promethesus-jenkins-config.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.205870.1587423122000.20099.1588281300417%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel updated an issue Jenkins / JENKINS-61980 Plugin Failed to load the Matrix Change By: Monil Patel Attachment: promethesus-scrap-config.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.205870.1587423122000.20095.1588281180286%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel updated an issue Jenkins / JENKINS-61980 Plugin Failed to load the Matrix Change By: Monil Patel Attachment: promethesus-scrap-config.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.205870.1587423122000.20093.1588281180259%40Atlassian.JIRA.
[JIRA] (JENKINS-62131) java.util.ConcurrentModificationException
Title: Message Title Maria Sabastian created an issue Jenkins / JENKINS-62131 java.util.ConcurrentModificationException Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2020-04-30 21:06 Environment: Jenkins ver. 2.204.2 Priority: Major Reporter: Maria Sabastian Hi, We've been running into this issue lately and I think the below line that’s throwing the exception: https://github.com/jenkinsci/s3-plugin/blob/master/src/main/java/hudson/plugins/s3/S3Profile.java#L240 Any ideas? java.util.ConcurrentModificationExceptionjava.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at hudson.plugins.s3.S3Profile.downloadAll(S3Profile.java:240) at hudson.plugins.s3.S3CopyArtifact.perform(S3CopyArtifact.java:270) at hudson.plugins.s3.S3CopyArtifact.perform(S3CopyArtifact.java:242) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Finished: FAILURE
[JIRA] (JENKINS-62130) Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-62130
Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Change By:
Karl Shultz
To allow for easier use of Git plugin's traits by other parts of the Jenkins universe (JobDSL, CasC, others), the addition of some [{{@Symbol}}|https://github.com/jenkinsci/structs-plugin/blob/6271388cca252b16cf5ff482036126bad30ee240/annotation/src/main/java/org/jenkinsci/Symbol.java] annotations would be good. most of the extenders of SCMSourceTrait already had {{@Symbol} annotations, and this ticket is intended to fill in what's left.
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-62130) Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-62130
Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Change By:
Karl Shultz
To allow for easier use of Git plugin's traits by other parts of the Jenkins universe (JobDSL, CasC, others), the addition of some [{{@Symbol}}|https://github.com/jenkinsci/structs-plugin/blob/6271388cca252b16cf5ff482036126bad30ee240/annotation/src/main/java/org/jenkinsci/Symbol.java] annotations would be good. most of the extenders of SCMSourceTrait already had {{@Symbol} } annotations, and this ticket is intended to fill in what's left.
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-62130) Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-62130
Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Change By:
Karl Shultz
To allow for easier use of Git plugin's traits by other parts of the Jenkins universe (JobDSL , CasC, others), the addition of some [{{@Symbol}}|https://github.com/jenkinsci/structs-plugin/blob/6271388cca252b16cf5ff482036126bad30ee240/annotation/src/main/java/org/jenkinsci/Symbol.java] annotations would be good.
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.206044.1588271994000.20086.1588274220068%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Kevin Williamson assigned an issue to Kevin Williamson Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Kevin Williamson 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.205823.1587087277000.20084.1588272840161%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Kevin Williamson updated JENKINS-61943 Ready for release Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Kevin Williamson Status: In Review 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
[JIRA] (JENKINS-62130) Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Title: Message Title Karl Shultz started work on JENKINS-62130 Change By: Karl Shultz 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.206044.1588271994000.20079.1588272060078%40Atlassian.JIRA.
[JIRA] (JENKINS-62130) Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-62130 Add @Symbol annotations to extenders of GitRepositoryBrowser and scm-api:SCMSourceTrait Issue Type: Improvement Assignee: Karl Shultz Components: git-plugin Created: 2020-04-30 18:39 Priority: Minor Reporter: Karl Shultz To allow for easier use of Git plugin's traits by other parts of the Jenkins universe, the addition of some @Symbol annotations would be good. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title Marc Brugger closed an issue as Not A Defect Jenkins / JENKINS-62072 The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary Change By: Marc Brugger Status: In Progress 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 visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205974.1588016722000.20077.1588267800218%40Atlassian.JIRA.
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title
Jesse Glick resolved as Won't Fix
I was trying
diff --git core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/lib/hudson/executors.jelly
index 4cd01bcadd..62eb9d3276 100644
--- core/src/main/resources/lib/hudson/executors.jelly
+++ core/src/main/resources/lib/hudson/executors.jelly
@@ -155,7 +155,7 @@ THE SOFTWARE.
-"${ajax==null and h.hasPermission(app.READ)}">
+"${ajax==null and h.hasPermission(app.READ) and not h.isCollapsed('executors')}">
"defer">
refreshPart('executors',"${rootURL}/${h.hasView(it,'ajaxExecutors')?it.url:''}ajaxExecutors");
diff --git core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/hudson/queue.jelly
index 776c4ed46a..93b6eb5560 100644
--- core/src/main/resources/lib/hudson/queue.jelly
+++ core/src/main/resources/lib/hudson/queue.jelly
@@ -101,7 +101,7 @@ THE SOFTWARE.
- "${ajax==null and h.hasPermission(app.READ)}">
+ "${ajax==null and h.hasPermission(app.READ) and not h.isCollapsed('buildQueue')}">
"defer">
refreshPart('buildQueue',"${rootURL}/${h.hasView(it,'ajaxBuildQueue')?it.url:''}ajaxBuildQueue");
until I realized that the original feature included dynamic updates to the pane titles, which still require HTTP requests to the master. Perhaps those should be dropped, to minimize load, but this would be a minor functional regression. And a three-way toggle (full, minimized, nonrefreshing) seems too awkward. The best we could do is slow down the refresh to, say, once per minute when minimized? Or use a lighter-weight REST call that does not involve rendering HTML?
Jenkins / JENKINS-62129
ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Change By:
Jesse Glick
Status:
In Progress Resolved
Resolution:
Won't Fix
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62129 ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed Change By: Jesse Glick Labels: lts-candidate performance 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.206043.1588266927000.20075.1588267620188%40Atlassian.JIRA.
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title Marc Brugger commented on JENKINS-62072 Re: The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary This Change was introduced in version 1.5 https://github.com/jenkinsci/badge-plugin/blob/master/CHANGELOG.md The change was triggered by the Jenkins Security Advisory https://www.jenkins.io/security/advisory/2018-06-25/#SECURITY-906 which gave to requirement, to prevent cross-site scripting. In version 1.8 I added the possibility to disable the Formatter in case the user wanted to have this feature. I will add a section to the readme about the config 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.205974.1588016722000.20073.1588267020236%40Atlassian.JIRA.
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title Jesse Glick started work on JENKINS-62129 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.206043.1588266927000.20071.1588266960195%40Atlassian.JIRA.
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-62129 ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed Issue Type: Bug Assignee: Jesse Glick Components: core Created: 2020-04-30 17:15 Labels: performance lts-candidate Priority: Major Reporter: Jesse Glick Normally Jenkins will post to ajaxBuildQueue and ajaxExecutors every few seconds to refresh these widgets. If you click the - button to collapse them, the results are not displayed...but the web requests are still sent, putting load on the master! We should just skip the refresh on a collapsed pane. Note that toggling the collapsed state involves a page refresh, so there is no risk of missing updates if you click + to expand. Add Comment
[JIRA] (JENKINS-60958) [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job
Title: Message Title Matt Murphy resolved as Fixed Jenkins / JENKINS-60958 [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job Change By: Matt Murphy Status: In Progress Resolved Resolution: Fixed Released As: HCL AppScan 1.0.1 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.204418.1580802631000.20069.1588266300252%40Atlassian.JIRA.
[JIRA] (JENKINS-60958) [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job
Title: Message Title Matt Murphy commented on JENKINS-60958 Re: [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job This has been fixed in version 1.0.1 of HCL AppScan. 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.204418.1580802631000.20065.1588266240234%40Atlassian.JIRA.
[JIRA] (JENKINS-60958) [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job
Title: Message Title Matt Murphy started work on JENKINS-60958 Change By: Matt Murphy 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.204418.1580802631000.20067.1588266240281%40Atlassian.JIRA.
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title Steven Fransen edited a comment on JENKINS-62072 Re: The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary i see 5 different plugins that are OWASAP [OWASP Dependency-Check|https://plugins.jenkins.io/dependency-check-jenkins-plugin][Official OWASP ZAP|https://plugins.jenkins.io/zap][ZAP Pipeline|https://plugins.jenkins.io/zap-pipeline][OWASP ZAP|https://plugins.jenkins.io/zapper][OWASP Dependency-Track|https://plugins.jenkins.io/dependency-track] can you help me a little bit more I do not understand what you are asking me to do they all look like Proxy and such how do I disable this feature? ThanksSteven Fransen never mind I found the answer no plugin required just in Jenkins Configure System in the Badge Plugin Section just check the Disabled OWASP Mark Formatter it would have been nice if in the released notes 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.205974.1588016722000.20062.1588264800219%40Atlassian.JIRA.
[JIRA] (JENKINS-62128) NonSerializable exceptions would be great to have more information about
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-62128 NonSerializable exceptions would be great to have more information about Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2020-04-30 16:35 Priority: Minor Reporter: Alex Taylor Issue: Recently I had an issue where I was getting a "Not Serializable Exception" when building a pipeline job (totally understandable error) caused by a LazyHashMap. I needed to just change the type of variable I was storing in order to make it serializable for CPS. The issue was that this was being stored as a ENV variable rather than a groovy variable and therefore threw an error on a very different step (in this case it was a email ext step) and was difficult to track down. Request: Would it be possible to get variable names or a pointer to the actual variable which threw the serialization error? That would be very helpful in the error message so I can find where it was potentially set much earlier and can be corrected Add Comment
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title Steven Fransen commented on JENKINS-62072 Re: The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary i see 5 different plugins that are OWASAP OWASP Dependency-Check Official OWASP ZAP ZAP Pipeline OWASP ZAP OWASP Dependency-Track can you help me a little bit more I do not understand what you are asking me to do they all look like Proxy and such how do I disable this feature? Thanks Steven Fransen 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.205974.1588016722000.20059.1588264380132%40Atlassian.JIRA.
[JIRA] (JENKINS-62118) Exception in nga log when do fortify SCA scan from jenkins and no vulnerbilities showing in ALM Octane pipeline
Title: Message Title Paul-Adrian Tofan assigned an issue to Radi Berkovich Jenkins / JENKINS-62118 Exception in nga log when do fortify SCA scan from jenkins and no vulnerbilities showing in ALM Octane pipeline Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Radi Berkovich 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.206030.1588232759000.20057.1588264080196%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Priority: Minor Major 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.185384.150594285.20046.1588263720623%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Labels: P4_A 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.185384.150594285.20048.1588263720692%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth commented on JENKINS-47005 Re: Let user specify p4 workspace root in manual config Comments from JENKINS-62123: In the P4Jenkins plugin, please add the functionality to "checkout to subdirectory" when defining either "Stream" or "View Mappings" (for Freestyle jobs). Customer would like to have the functionality to define a stream, and also have this stream checkout into a sub directory in the Jenkins workspace without having to fill in the "View Mappings" from a client spec by hand, with the directory present. 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.185384.150594285.20034.1588263660229%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-62123 P4 Plugin should allow checkout to subdirectory Change By: Karl Wirth Labels: P4_SUPPORT 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.206036.1588253201000.20032.1588263600259%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Karl Wirth commented on JENKINS-62123 Re: P4 Plugin should allow checkout to subdirectory Hi Dan Dawson - 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.206036.1588253201000.20030.1588263600226%40Atlassian.JIRA.
[JIRA] (JENKINS-62127) Dynamic Axis-Values for declarative Pipeline
Title: Message Title tharilya created an issue Jenkins / JENKINS-62127 Dynamic Axis-Values for declarative Pipeline Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: matrix-combinations-parameter-plugin, matrix-project-plugin, pipeline Created: 2020-04-30 16:06 Environment: System-Setup: My System: Jenkins-Version: Jenkins ver. 2.190.1 Declarative-Plugin-Version 1.5.0 Declarative Agent API: 1.1.1 Declarative Extension Points API: 1.5.0 (many other plugins, I think this are the important ones) The answer of the stackoverflow post say that it is currently not possible, even with the current version of the plugins. Priority: Minor Reporter: tharilya Hi there, I was asked to open a Ticket here, because it seems like the feature is interesting for many peoples. Stack Overflow - Declarative Pipeline with dynamic matrix axis values It would be nice to have the possibility to set the dynamically set the values of the "axis". Use-Case: I want to compile multiple plugins with the same Jenkins-pipeline. To do so I wrote a "JenkinsLibrary" with an interface the plugins can use for parameters. One of this parameters is the axis-value for compiler. e.g. I want to build Plugin "X" for gcc7 on armv8 and Plugin Y for vc15 x64. So I have a Jenkins-Library with the logic of the build parameters. And each plugin calls the library with the build-parameters. (e.g. compiler and arch )
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API I came across a similar issue today in the slack plugin which uses even lower level APIs: https://github.com/jenkinsci/slack-plugin/blob/master/src/main/java/jenkins/plugins/slack/CredentialsObtainer.java Seems like there's too much choice! 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.205677.1586203717000.20026.1588262580120%40Atlassian.JIRA.
[JIRA] (JENKINS-53751) The same parallel scripted and declarative pipelines rendered differently
Title: Message Title tharilya commented on JENKINS-53751 Re: The same parallel scripted and declarative pipelines rendered differently This Seems to be solved in the current version of the plugin. Can you confirm that? Taras Postument 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.194258.1537808551000.20015.1588262280262%40Atlassian.JIRA.
[JIRA] (JENKINS-62126) Not able to get checkbox for "Download now and Install after Restart" plugins dowload feature
Title: Message Title Brajesh Kumar created an issue Jenkins / JENKINS-62126 Not able to get checkbox for "Download now and Install after Restart" plugins dowload feature Issue Type: Bug Assignee: Natasha Stopa Attachments: image-2020-04-30-17-55-12-196.png, image-2020-04-30-17-55-31-294.png, image-2020-04-30-17-56-08-195.png Components: plugin-installation-manager-tool Created: 2020-04-30 15:56 Priority: Critical Reporter: Brajesh Kumar While doing the Plugins download , we are facing issue that Checkbox is missing in Jenkins for feature "Download now and install after Restart" feature. Actual: Expected: Add Comment
[JIRA] (JENKINS-62125) Installing Maven Plugins is throwing error for process "Install Without restart"
Title: Message Title Brajesh Kumar created an issue Jenkins / JENKINS-62125 Installing Maven Plugins is throwing error for process "Install Without restart" Issue Type: Bug Assignee: Adiveppa Kallur Components: active-choices-plugin Created: 2020-04-30 15:52 Priority: Critical Reporter: Brajesh Kumar Getting below error while installing Maven Plugins from Jenkins 2020-04-30 14:04:57.937+ [id=145] WARNING h.m.UpdateCenter$CompleteBatchJob#run: Failed to start some plugins java.lang.ClassNotFoundException: hudson.plugins.depgraph_view.model.graph.EdgeProvider at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) Caused: java.lang.NoClassDefFoundError: hudson/plugins/depgraph_view/model/graph/EdgeProvider at com.barchart.jenkins.cascade.GraphModule.configure(GraphModule.java:39) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) at com.google.inject.spi.Elements.getElements(Elements.java:110) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:226) at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:347) Caused: jenkins.ExtensionRefreshException at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:363) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2745) at hudson.PluginManager.start(PluginManager.java:977) Caused: java.io.IOException: Failed to refresh extensions after installing some plugins at hudson.PluginManager.start(PluginManager.java:979) at
[JIRA] (JENKINS-60464) Test 0124
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-60464 Test 0124 Change By: Tim Jacomb Labels: jenkins regression 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.203543.1576180048000.20009.1588260720192%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: 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.205626.1585843138000.20006.1588260600093%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Dan Dawson edited a comment on JENKINS-62123 Re: P4 Plugin should allow checkout to subdirectory Hi Karl [~p4karl] ,This ticket was tested with a 'Freestyle' job, as with the customer's setup. Linking it to that ticket sounds good to me. 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.206036.1588253201000.20005.1588259040179%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Dan Dawson commented on JENKINS-62123 Re: P4 Plugin should allow checkout to subdirectory Hi Karl, This ticket was tested with a 'Freestyle' job, as with the customer's setup. Linking it to that ticket sounds good to me. 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.206036.1588253201000.20003.1588258980220%40Atlassian.JIRA.
[JIRA] (JENKINS-11504) Weather popup can not be read.
Title: Message Title Sam Hrncir assigned an issue to Unassigned Jenkins / JENKINS-11504 Weather popup can not be read. Change By: Sam Hrncir Assignee: Sam Hrncir 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.141730.1319639251000.19993.1588257660519%40Atlassian.JIRA.
[JIRA] (JENKINS-49691) FilePath.installIfNecessaryFrom always download even if target already exists
Title: Message Title Sam Hrncir assigned an issue to Unassigned Jenkins / JENKINS-49691 FilePath.installIfNecessaryFrom always download even if target already exists Change By: Sam Hrncir Assignee: Sam Hrncir 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.188626.1519296535000.19991.1588257660484%40Atlassian.JIRA.
[JIRA] (JENKINS-60927) Use disconnect icon for Disconnect and Delete Agent
Title: Message Title Sam Hrncir assigned an issue to Unassigned Jenkins / JENKINS-60927 Use disconnect icon for Disconnect and Delete Agent Change By: Sam Hrncir Assignee: Sam Hrncir 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.204324.1580417196000.19988.1588257660444%40Atlassian.JIRA.
[JIRA] (JENKINS-10622) Cron Tab still running even when the job is disabled
Title: Message Title Sam Hrncir assigned an issue to Unassigned Jenkins / JENKINS-10622 Cron Tab still running even when the job is disabled Change By: Sam Hrncir Assignee: Sam Hrncir 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.140816.1312821348000.19986.1588257600604%40Atlassian.JIRA.
[JIRA] (JENKINS-49742) Multi-line string seems to be broken when triggered from the pipeline.
Title: Message Title Sam Hrncir assigned an issue to Unassigned Jenkins / JENKINS-49742 Multi-line string seems to be broken when triggered from the pipeline. Change By: Sam Hrncir Assignee: Sam Hrncir 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.188685.1519653887000.19981.1588257600535%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title
Karl Wirth edited a comment on JENKINS-47005
Re: Let user specify p4 workspace root in manual config
*Possible workarounds:* # Replace contents of Jenkinsfile with a simple non instruction so that no real build is performed. # Remove all access to the branch for the Jenkins user through Perforce protections. # JENKINS-47066 # If using pipleline you can use the 'ws' directive: {code:java}stage("SyncMyWorkspace") { steps { ws('/var/lib/jenkins/X/KarlTest/') {p4sync charset: 'none', credential: 'JenkinsMasterAdminUser', format: 'jenkins-${NODE_NAME}-${JOB_NAME}', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), source: depotSource('//depot/test/...')echo "DONE" } }}{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.185384.150594285.19962.1588255860326%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title
Karl Wirth commented on JENKINS-62123
Re: P4 Plugin should allow checkout to subdirectory
Hi Dan Dawson I think I'm going to link this request to JENKINS-47005 if that's acceptable. Are you using Freestyle or pipeline jobs? In pipeline you can use the 'ws' directive as workaround. For example the following sets the root directory for the command in brackets to '/var/lib/jenkins/X/KarlTest':
pipeline {
agent { label 'master' }
stages {
stage("SyncMyWorkspace") {
steps {
ws('/var/lib/jenkins/X/KarlTest/') {
p4sync charset: 'none', credential: 'JenkinsMasterAdminUser', format: 'jenkins-${NODE_NAME}-${JOB_NAME}', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), source: depotSource('//depot/test/...')
}
}
}
}
}
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-62124) Role based stratedy can't be showed in Config as Code - java null ptr exeption
Title: Message Title Bartosz Nowak created an issue Jenkins / JENKINS-62124 Role based stratedy can't be showed in Config as Code - java null ptr exeption Issue Type: Bug Assignee: Oleg Nenashev Components: configuration-as-code-plugin, role-strategy-plugin Created: 2020-04-30 14:00 Environment: * Operating System: Debian 9 x64 * All relevant JRE/JDK vendors and versions: 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) * Jenkins and plugin versions: Jenkins 2.233 Role base strategy 2.16 Config as a code 1.39 * My jenkins runs into docker container - 19.03 Labels: plugins plugin configuration exception Priority: Minor Reporter: Bartosz Nowak I want to try out config as code plugin. I went to Manage Jenkins -> Configuration as Code and then I clicked "View configuration" This is yaml output: authorizationStrategy: roleBased: roles: global: |- FAILED TO EXPORT org.jenkinsci.plugins.rolestrategy.casc.GrantedRoles#global: java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Matcher.java:1283) at java.util.regex.Matcher.reset(Matcher.java:309) at java.util.regex.Matcher.(Matcher.java:229) at java.util.regex.Pattern.matcher(Pattern.java:1093) at
[JIRA] (JENKINS-62119) Warnings Next Generation support Git Submodules
Title: Message Title Ulli Hafner commented on JENKINS-62119 Re: Warnings Next Generation support Git Submodules Please add yourself as watchee on JENKINS-56215. 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.206031.1588243563000.19954.1588253940244%40Atlassian.JIRA.
[JIRA] (JENKINS-62119) Warnings Next Generation support Git Submodules
Title: Message Title Ulli Hafner edited a comment on JENKINS-62119 Re: Warnings Next Generation support Git Submodules Please add yourself register as watchee watcher on JENKINS-56215. 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.206031.1588243563000.19956.1588253940283%40Atlassian.JIRA.
[JIRA] (JENKINS-62119) Warnings Next Generation support Git Submodules
Title: Message Title Ulli Hafner resolved as Duplicate Jenkins / JENKINS-62119 Warnings Next Generation support Git Submodules Change By: Ulli Hafner Status: Open Resolved Resolution: Duplicate 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.206031.1588243563000.19952.1588253880202%40Atlassian.JIRA.
[JIRA] (JENKINS-62119) Warnings Next Generation support Git Submodules
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62119 Warnings Next Generation support Git Submodules Change By: Ulli Hafner Assignee: Ulli Hafner 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.206031.1588243563000.19950.1588253700128%40Atlassian.JIRA.
[JIRA] (JENKINS-62119) Warnings Next Generation support Git Submodules
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62119 Warnings Next Generation support Git Submodules Change By: Ulli Hafner Labels: git 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.206031.1588243563000.19948.1588253580173%40Atlassian.JIRA.
[JIRA] (JENKINS-62123) P4 Plugin should allow checkout to subdirectory
Title: Message Title Dan Dawson created an issue Jenkins / JENKINS-62123 P4 Plugin should allow checkout to subdirectory Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 2020-04-30 13:26 Labels: P4_VERIFY P4_SUPPORT Priority: Minor Reporter: Dan Dawson In the P4Jenkins plugin, please add the functionality to "checkout to subdirectory" when defining either "Stream" or "View Mappings". Customer would like to have the functionality to define a stream, and also have this stream checkout into a sub directory in the Jenkins workspace without having to fill in the "View Mappings" from a client spec by hand, with the directory present. Add Comment
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Jesse Glick commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation No, I am not maintaining these plugins, sorry. 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.204432.1580891884000.19939.1588250940195%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Daniel Estermann commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation Jesse Glick May I hand over this issue to you? 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.204432.1580891884000.19931.1588250760168%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan I will leave.this open in till Friday. I think the main answer is mine from yesterday. Let me know if I am misinterpreting 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.205931.1587715343000.19928.1588250640186%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Jesse Glick commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation Not sure offhand. Bug somewhere. 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.204432.1580891884000.19925.1588250340249%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Tim Jacomb commented on JENKINS-62088 Re: Plugin manager loading incorrect fonts Well raised this 9 days after the conversation due to creating a PR for fixing 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.205996.1588144537000.19922.1588249140325%40Atlassian.JIRA.
[JIRA] (JENKINS-36625) Long group name increases size of 'Project-based security' group size breaking configuration UI
Title: Message Title Daniel Beck updated JENKINS-36625 Jenkins / JENKINS-36625 Long group name increases size of 'Project-based security' group size breaking configuration UI Change By: Daniel Beck Status: Fixed but Unreleased Closed Released As: 2. 5.1 / 2. 6 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.172652.1468325945000.19917.1588248480755%40Atlassian.JIRA.
