[JIRA] (JENKINS-62025) workflow-job plugin js error with IE11
Title: Message Title Olivier Lamy commented on JENKINS-62025 Re: workflow-job plugin js error with IE11 pr https://github.com/jenkinsci/workflow-job-plugin/pull/161 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.205914.1587618166000.16229.1587619080051%40Atlassian.JIRA.
[JIRA] (JENKINS-61304) EC2 Plugin terminates instances temporarily offline
Title: Message Title Umberto Nicoletti commented on JENKINS-61304 Re: EC2 Plugin terminates instances temporarily offline Ara Yapejian FYI I've put together a PR https://github.com/jenkinsci/ec2-plugin/pull/437 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.204884.1583219883000.16227.1587618960191%40Atlassian.JIRA.
[JIRA] (JENKINS-62025) workflow-job plugin js error with IE11
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-62025 workflow-job plugin js error with IE11 Change By: Olivier Lamy Issue Type: Improvement Bug 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.205914.1587618166000.16225.1587618240100%40Atlassian.JIRA.
[JIRA] (JENKINS-62025) workflow-job plugin js error with IE11
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-62025 workflow-job plugin js error with IE11 Issue Type: Improvement Assignee: Olivier Lamy Components: workflow-job-plugin Created: 2020-04-23 05:02 Priority: Critical Reporter: Olivier Lamy 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
[JIRA] (JENKINS-61304) EC2 Plugin terminates instances temporarily offline
Title: Message Title Ara Yapejian commented on JENKINS-61304 Re: EC2 Plugin terminates instances temporarily offline Just wondering if anyone else is experiencing this? We ran into the same symptoms, rolling back to EC2 Plugin 1.47 resolved the problem without any other changes being made. The fact that the issue hasn't got more traction has me second guessing what else could be the issue if it's only happening to a select few. 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.204884.1583219883000.16223.1587613140183%40Atlassian.JIRA.
[JIRA] (JENKINS-62024) Add quick filter box for dropdown lists
Title: Message Title John Lin updated an issue Jenkins / JENKINS-62024 Add quick filter box for dropdown lists Change By: John Lin It's almost always tedious and annoying to find an item in the dropdown list.For example, I have to spend lots of time searching for the build action to start/stop control a docker container in this dropdown list:!dropdown-without-filter.png|thumbnail!I think it's easier if we add a quick filter for the dropdown list, and I can just type "con" in the filter box:!dropdown-with-filter.png|thumbnail! 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.205913.1587604995000.16220.1587605100065%40Atlassian.JIRA.
[JIRA] (JENKINS-62024) Add quick filter box for dropdown lists
Title: Message Title John Lin updated an issue Jenkins / JENKINS-62024 Add quick filter box for dropdown lists Change By: John Lin It's almost always tedious and annoying to find an item in the dropdown list.For example, I have to spend lots of time searching for the build action to start/stop a docker container in this dropdown list:!dropdown-without-filter.png|thumbnail!I think it's easier if we add a quick filter for the dropdown list , and I can just type "con" in the filter box :!dropdown-with-filter.png|thumbnail! 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.205913.1587604995000.16219.1587605040303%40Atlassian.JIRA.
[JIRA] (JENKINS-62024) Add quick filter box for dropdown lists
Title: Message Title John Lin created an issue Jenkins / JENKINS-62024 Add quick filter box for dropdown lists Issue Type: Improvement Assignee: Unassigned Attachments: dropdown-with-filter.png, dropdown-without-filter.png Components: core Created: 2020-04-23 01:23 Priority: Minor Reporter: John Lin It's almost always tedious and annoying to find an item in the dropdown list. For example, I have to spend lots of time searching for the build action to start/stop a docker container in this dropdown list: I think it's easier if we add a quick filter for the dropdown list: Add Comment
[JIRA] (JENKINS-61982) jenkins..io docs for 'wait' parameter of pipeline 'build' step are incomplete
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61982 jenkins..io docs for 'wait' parameter of pipeline 'build' step are incomplete Change By: Mark Waite Summary: jenkins..io docs for ' waite wait ' parameter of pipeline 'build' step are 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, 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.205872.1587443136000.16216.1587601440069%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) Only reject servers whose name ends with bitbucket.org
Title: Message Title Daniel Kjellin updated JENKINS-61915 Jenkins / JENKINS-61915 Only reject servers whose name ends with bitbucket.org Change By: Daniel Kjellin 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.205789.1586958535000.16211.1587598381112%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) Only reject servers whose name ends with bitbucket.org
Title: Message Title Daniel Kjellin assigned an issue to Stefan Marklund Jenkins / JENKINS-61915 Only reject servers whose name ends with bitbucket.org Change By: Daniel Kjellin Assignee: Kristy Hughes Stefan Marklund 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.205789.1586958535000.16205.1587598381018%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) Only reject servers whose name ends with bitbucket.org
Title: Message Title Daniel Kjellin updated JENKINS-61915 Jenkins / JENKINS-61915 Only reject servers whose name ends with bitbucket.org Change By: Daniel Kjellin 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 visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205789.1586958535000.16214.1587598381141%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) Only reject servers whose name ends with bitbucket.org
Title: Message Title Daniel Kjellin started work on JENKINS-61915 Change By: Daniel Kjellin 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.205789.1586958535000.16208.1587598381071%40Atlassian.JIRA.
[JIRA] (JENKINS-62023) Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62023 Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2592 62023 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62023) Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-62023 Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Closed 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.205242.1584621529000.16201.1587596400351%40Atlassian.JIRA.
[JIRA] (JENKINS-62022) Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-62022 Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Closed 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.205243.1584621563000.16196.1587596340201%40Atlassian.JIRA.
[JIRA] (JENKINS-62022) Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62022 Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2591 62022 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62021) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-62021 Parameter is not interpreted in GIT Plugin - Branch Specifier 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.205251.1584621682000.16191.1587596280336%40Atlassian.JIRA.
[JIRA] (JENKINS-62020) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62020 Jenkins / JENKINS-62020 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased 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.205254.1584621792000.16186.1587596220307%40Atlassian.JIRA.
[JIRA] (JENKINS-62021) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62021 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2590 62021 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-62020) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62020 Jenkins / JENKINS-62020 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased 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.205254.1584621792000.16184.1587596160498%40Atlassian.JIRA.
[JIRA] (JENKINS-62020) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62020 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2589 62020 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-62017) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62017 Jenkins / JENKINS-62017 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased 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.205265.1584621968000.16179.1587596040470%40Atlassian.JIRA.
[JIRA] (JENKINS-62017) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62017 Jenkins / JENKINS-62017 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased 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.205265.1584621968000.16177.1587596040445%40Atlassian.JIRA.
[JIRA] (JENKINS-62019) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62019 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2588 62019 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-61550) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61550 Parameter is not interpreted in GIT Plugin - Branch Specifier 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.205247.1584621644000.16172.1587595920210%40Atlassian.JIRA.
[JIRA] (JENKINS-62018) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62018 Jenkins / JENKINS-62018 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased 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.205255.1584621821000.16168.1587595864370%40Atlassian.JIRA.
[JIRA] (JENKINS-62018) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62018 Jenkins / JENKINS-62018 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased 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.205255.1584621821000.16170.1587595864468%40Atlassian.JIRA.
[JIRA] (JENKINS-62018) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62018 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2587 62018 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-62016) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62016 Jenkins / JENKINS-62016 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased 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.205911.158759559.16162.1587595800162%40Atlassian.JIRA.
[JIRA] (JENKINS-62016) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62016 Jenkins / JENKINS-62016 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased 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.205911.158759559.16163.1587595800210%40Atlassian.JIRA.
[JIRA] (JENKINS-62017) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62017 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2586 62017 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-62016) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title
Mark Waite created an issue
Jenkins / JENKINS-62016
Parameter is not interpreted in GIT Plugin Branch Specifier
Issue Type:
Bug
Assignee:
Unassigned
Components:
git-plugin
Created:
2020-04-22 22:46
Environment:
Git plugin 4.2.2
Priority:
Minor
Reporter:
Mark Waite
I have a pipeline with one branch to be build, it's a paramterized pipeline: refs/tags/${BuildTag} The BuildTag gets not interpreted anymore:
hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune -- origin +refs/tags/${BuildTag}:refs/remotes/origin/${BuildTag}" returned status code 128:
stdout:
stderr: fatal: Couldn't find remote ref refs/tags/${BuildTag}
fatal: the remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:81)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:569)
at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:361)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:115)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303)
at
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Karl, I did the workaround as suggested on the jenkin master 'Configure System' by adding P4CLIENT to the "Global properties" as follows. It worked. Name: P4CLIENT Value: $P4_CLIENT I'm wondering if the Jenkins Guild below should also mention this issue for "Freestyle jobs configured for P4" Helix Plugin for Jenkins Guide (1.10.x), Freestyle job - Manual Workspace setup https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/workspace-manual.html Thanks again. David 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.16157.1587594900242%40Atlassian.JIRA.
[JIRA] (JENKINS-61568) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-61568 Parameter is not interpreted in GIT Plugin Branch Specifier 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.205265.1584621968000.16153.1587594720197%40Atlassian.JIRA.
[JIRA] (JENKINS-61568) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61568 Parameter is not interpreted in GIT Plugin Branch Specifier 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.205265.1584621968000.16155.1587594720228%40Atlassian.JIRA.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title Morgan Robertson commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly Do we all have the 'Discard old items' item enabled in Jenkins? I have a suspicion that what's happening is that GitHub or Bitbucket or whatever git service we use occasionally fails to properly respond to the Jenkins poll request and then Jenkins removes the branch due to the 'Discard old items' option. I'm going to try disabling this. If so, two potential fixes: Allow certain branches to be excepted from the 'Discard old items' job. Make every Bitbucket / GitHub / etc. reliably respond to requests (hah). 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.196496.1546519053000.16139.1587594420338%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Morgan Robertson commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Do we all have the 'Discard old items' item enabled in Jenkins? I have a suspicion that what's happening is that GitHub or Bitbucket or whatever git service we use occasionally fails to properly respond to the Jenkins poll request and then Jenkins removes the branch due to the 'Discard old items' option. I'm going to try disabling this. If so, two potential fixes: Allow certain branches to be excepted from the 'Discard old items' job. Make every Bitbucket / GitHub / etc. reliably respond to requests (hah). 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.196298.154504211.16119.1587594360433%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Alex xu commented on JENKINS-59192 Re: configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines I can not get git_previous_successful_commit by pipeline , free style , with git plug-in 4.22 installed, also tried other version of the plug-ins, none of them can get git_previous_successful_commit who can help ? 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.201633.1567448335000.16108.1587590760323%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Oleksandr Khomenko edited a comment on JENKINS-59192 Re: configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Are there any updates on this issue? I also faced with 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.201633.1567448335000.16105.1587589260148%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Oleksandr Khomenko commented on JENKINS-59192 Re: configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Are there any updates on this issue? I also faced with. 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.201633.1567448335000.16103.1587589200326%40Atlassian.JIRA.
[JIRA] (JENKINS-59573) Non-stored password parameter not working in freestyle project
Title: Message Title santhosh voodem commented on JENKINS-59573 Re: Non-stored password parameter not working in freestyle project could you please let me know if this issue got resolved. I am facing same issue for both kind of password parameters 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.202209.1569681004000.16100.1587587700143%40Atlassian.JIRA.
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title Constantin Bugneac commented on JENKINS-61998 Re: Jenkins upgrade fails on CentOS - Public key is not installed Just wondering - can the WiKI page updated or removed so that a single source of truth is kept ? Otherwise it's gonna mislead other people too. 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.205889.1587495153000.16098.1587585840776%40Atlassian.JIRA.
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title Constantin Bugneac commented on JENKINS-61998 Re: Jenkins upgrade fails on CentOS - Public key is not installed Oleksandr Shmyrko Thanks, it worked! 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.205889.1587495153000.16094.1587585720196%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title Calvin Park commented on JENKINS-61956 Re: ItemGroupMixing#createProject() does not call Jenkins#checkGoodName Opened https://github.com/jenkinsci/jenkins/pull/4684 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.205840.1587161495000.16081.1587585120058%40Atlassian.JIRA.
[JIRA] (JENKINS-62015) Deployment on server
Title: Message Title Khurram Shahzad created an issue Jenkins / JENKINS-62015 Deployment on server Issue Type: Task Assignee: Unassigned Components: jenkinsfile-runner Created: 2020-04-22 17:49 Environment: Jenkins ver. 2.176.1 Priority: Major Reporter: Khurram Shahzad I have set up a job to deploy my .net code to the production server. It runs fine, and it finishes with the success but I never published code to the server. I do see code in the workspace folder on Jenkins c:\jenkinsdata\workspaces\project. CopyFilesToOutputDirectory: Copying file from "D:\Program Files (x86)\Jenkins\workspace\myproject - Staging\myproject.Service\obj\Staging\myproject.Service.exe" to "D:\Program Files (x86)\Jenkins\workspace\myproject - Staging\myproject.Service\bin\Staging\myproject.Service.exe". myproject.Service -> D:\Program Files (x86)\Jenkins\workspace\myproject - Staging\myproject.Service\bin\Staging\myproject.Service.exe Copying file from "D:\Program Files (x86)\Jenkins\workspace\myproject - Staging\myproject.Service\obj\Staging\myproject.Service.pdb" to "D:\Program Files (x86)\Jenkins\workspace\myproject - Staging\myproject.Service\bin\Staging\myproject.Service.pdb". Done Building Project "D:\Program Files (x86)\Jenkins\workspace\myproject - Staging\myproject.Service\myproject.Service.csproj" (Clean;Build target(s)). Build succeeded.
[JIRA] (JENKINS-62004) Parameterized Remote Trigger expects case-sensitive http headers
Title: Message Title
Steven Christenson edited a comment on JENKINS-62004
Re: Parameterized Remote Trigger expects case-sensitive http headers
3.2. Header Fields Each header field consists of a **case-insensitive** field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.[https://tools.ietf.org/html/rfc7230#appendix-A.2]Looks like most things are expected to be case-insensitive... So if the receiving Jenkins doesn't work ... it is in error. Of course the wonderful thing about standards is that everyone can have their own!The version of the invoker in this case is: Parameterized-Remote-Trigger:3.1.2
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.205896.1587535152000.16046.1587575100395%40Atlassian.JIRA.
[JIRA] (JENKINS-62004) Parameterized Remote Trigger expects case-sensitive http headers
Title: Message Title
Steven Christenson edited a comment on JENKINS-62004
Re: Parameterized Remote Trigger expects case-sensitive http headers
3.2. Header Fields Each header field consists of a **case-insensitive** field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.[https://tools.ietf.org/html/rfc7230#appendix-A.2]Looks like most things are expected to be case-insensitive... So if the receiving Jenkins doesn't work ... it is in error. Of course the wonderful thing about standards is that everyone can have their own! To be clear, this isn't so much a problem with the plugin it is *Jenkins 2.164.32.0.1-fixed* That is failing to accept what should be a case-insensitive value. The version of the invoker in this case is: Parameterized-Remote-Trigger:3.1.2
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.205896.1587535152000.16042.1587575100333%40Atlassian.JIRA.
[JIRA] (JENKINS-62014) Allow fine-grained control over environment variables passed to build steps
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-62014 Allow fine-grained control over environment variables passed to build steps Issue Type: New Feature Assignee: Daniel Beck Components: core, pipeline Created: 2020-04-22 17:00 Priority: Minor Reporter: Daniel Beck The behavior of many (build) tools and scripts is dependent on the environment variables passed to them. Unfortunately, environment variables are frequently difficult or impossible to see inside Jenkins. It should be possible to have control over which environment variables are passed to specific build steps. This would also allow having a UI for keeping processes around. Add Comment
[JIRA] (JENKINS-62011) Compatibility breakage AzureCredentials#getClientId()
Title: Message Title Tim Jacomb commented on JENKINS-62011 Re: Compatibility breakage AzureCredentials#getClientId() Raised https://github.com/jenkins-infra/update-center2/pull/370 for blacklisting this version 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.205904.1587563236000.16034.1587574500148%40Atlassian.JIRA.
[JIRA] (JENKINS-62013) AdoptOpenJDK Crawler is using deprecated v2 api
Title: Message Title Mads Mohr Christensen updated an issue Jenkins / JENKINS-62013 AdoptOpenJDK Crawler is using deprecated v2 api Change By: Mads Mohr Christensen Summary: AdoptOpenJDK Crawler is using deprecated v2 api 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.205906.1587569281000.16028.1587574020068%40Atlassian.JIRA.
[JIRA] (JENKINS-62004) Parameterized Remote Trigger expects case-sensitive http headers
Title: Message Title
Steven Christenson edited a comment on JENKINS-62004
Re: Parameterized Remote Trigger expects case-sensitive http headers
3.2. Header Fields Each header field consists of a **case-insensitive** field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.[https://tools.ietf.org/html/rfc7230#appendix-A.2]Looks like most things are expected to be case-insensitive... So if the receiving Jenkins doesn't work ... it is in error. Of course the wonderful thing about standards is that everyone can have their own!To be clear, this isn't so much a problem with the plugin it is *Jenkins 2.164.32.0.1-fixed*That is failing to accept what should be a case-insensitive value. The version of the invoker in this case is: Parameterized-Remote-Trigger:3.1.2
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.205896.1587535152000.16026.1587573480181%40Atlassian.JIRA.
[JIRA] (JENKINS-62004) Parameterized Remote Trigger expects case-sensitive http headers
Title: Message Title
Steven Christenson commented on JENKINS-62004
Re: Parameterized Remote Trigger expects case-sensitive http headers
3.2. Header Fields Each header field consists of a *case-insensitive* field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace. https://tools.ietf.org/html/rfc7230#appendix-A.2 Looks like most things are expected to be case-insensitive... So if the receiving Jenkins doesn't work ... it is in error. Of course the wonderful thing about standards is that everyone can have their own! To be clear, this isn't so much a problem with the plugin it is Jenkins 2.164.32.0.1-fixed That is failing to accept what should be a case-insensitive value.
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.205896.1587535152000.16022.1587573360203%40Atlassian.JIRA.
[JIRA] (JENKINS-62011) Compatibility breakage AzureCredentials#getClientId()
Title: Message Title
David Maciel commented on JENKINS-62011
Re: Compatibility breakage AzureCredentials#getClientId()
I was having the same issue and it broke my whole Jenkins instance (all jobs failing) I manage Jenkins using a helm chart and even my rollbacks where failing. A temporary workaround is to install the azure-credentials version 3.0.0 ("azure-credentials:3.0.0"). Still have to investigate which plugin is bringing this as a dependency without selecting a specific version
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.205904.1587563236000.16019.1587572100154%40Atlassian.JIRA.
[JIRA] (JENKINS-62013) Crawler is using deprecated v2 api
Title: Message Title Mads Mohr Christensen updated an issue Jenkins / JENKINS-62013 Crawler is using deprecated v2 api Change By: Mads Mohr Christensen The current crawler for AdoptOpenJDK is using the v2 version of the rest api which has been deprecated. Please update crawler to use v3.[https://api.adoptopenjdk.net/] [https://api.adoptopenjdk.net/swagger-ui/] 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.205906.1587569281000.16014.1587569640060%40Atlassian.JIRA.
[JIRA] (JENKINS-62013) Crawler is using deprecated v2 api
Title: Message Title Mads Mohr Christensen created an issue Jenkins / JENKINS-62013 Crawler is using deprecated v2 api Issue Type: Bug Assignee: Mads Mohr Christensen Components: adoptopenjdk-plugin Created: 2020-04-22 15:28 Priority: Minor Reporter: Mads Mohr Christensen The current crawler for AdoptOpenJDK is using the v2 version of the rest api which has been deprecated. Please update crawler to use v3. https://api.adoptopenjdk.net/ Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-45315) bfa cannot connect to mongodb using SSL
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-45315 bfa cannot connect to mongodb using SSL Change By: Tim Jacomb Assignee: Tomas Westling Tim Jacomb 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.183455.1499264665000.16009.1587569040738%40Atlassian.JIRA.
[JIRA] (JENKINS-45315) bfa cannot connect to mongodb using SSL
Title: Message Title Tim Jacomb started work on JENKINS-45315 Change By: Tim Jacomb 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.183455.1499264665000.16006.1587569040647%40Atlassian.JIRA.
[JIRA] (JENKINS-62008) Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-62008 Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts Change By: David Rodriguez The old community P4 plugin used to expose the variables P4PORT, P4USER and P4CLIENT as environment variables for scripts to use. The new plugin on purpose uses different variables to ensure we dont override variables that are already set in the environment. Would be good if we had the option to also automatically set P4PORT=P4_PORT, P4USER=P4_USER and P4_CLIENT P4CLIENT =P4_CLIENT. 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-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Mads Mohr Christensen commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down This issue also deleted my build history because of a temporary outage at a bad time. I have opened a [PR|https://github.com/jenkinsci/mercurial-plugin/pull/144] implementing the suggestion by Dave E 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.187660.1515518637000.15992.1587566460427%40Atlassian.JIRA.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Mads Mohr Christensen edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down This issue also deleted my build history because of a temporary outage at a bad time.I have opened a [ PR | [https://github.com/jenkinsci/mercurial-plugin/pull/144] ] implementing the suggestion by [~brewmook] 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.187660.1515518637000.15994.1587566460462%40Atlassian.JIRA.
[JIRA] (JENKINS-62011) Compatibility breakage AzureCredentials#getClientId()
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-62011 Compatibility breakage AzureCredentials#getClientId() Change By: Tim Jacomb Issue Type: Task Bug 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.205904.1587563236000.15985.1587566100349%40Atlassian.JIRA.
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report displays first row with black text on black background?
Title: Message Title Socrates Sidereas updated JENKINS-61993 Indeed the first row has font color via inline css and due to jenkins-content-security-policy the color is not displayed. Characters are black on black background. By following the proposal solution from https://stackoverflow.com/questions/37618892/jenkins-content-security-policy all instyle elements are working fine. Nevertheless to avoid this the font color declaration will be changed inside html tags instead of a generic css. Available in the next release 1.0.8 Jenkins / JENKINS-61993 Test Results Aggregator - HTML report displays first row with black text on black background? Change By: Socrates Sidereas Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62012) Allow global yaml to be merged into yaml of jobs
Title: Message Title Arjan Tijms created an issue Jenkins / JENKINS-62012 Allow global yaml to be merged into yaml of jobs Issue Type: New Feature Assignee: Unassigned Components: kubernetes-plugin Created: 2020-04-22 14:30 Priority: Minor Reporter: Arjan Tijms A Jenkinsfile in a project may contain an embedded agent -> kubernetes -> yaml file that is tailored for one environment, for instance a Jenkins running jobs on OpenShift where it assumes a (random) user ID is assigned, and demands that no securityContext: runAsUser is defined. Another environment, such as e.g. a local Jenkins instance using a local Kubernetes cluster may not do this, and pods using multiple images where the docker file sets different users will not run correctly then. It would be useful in this case if the Jenkins instance could define a global pod yaml at manage jenkins -> Manage nodes and clouds -> Kubernetes Cloud Details that will be merged into the yaml created by org.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder If this is an acceptable feature, I can create a PR for this. Add Comment
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report displays first row with black text on black background?
Title: Message Title Socrates Sidereas updated JENKINS-61993 Jenkins / JENKINS-61993 Test Results Aggregator - HTML report displays first row with black text on black background? Change By: Socrates Sidereas 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.205884.1587481979000.15980.1587565680210%40Atlassian.JIRA.
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report displays first row with black text on black background?
Title: Message Title Socrates Sidereas started work on JENKINS-61993 Change By: Socrates Sidereas 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.205884.1587481979000.15978.1587565320494%40Atlassian.JIRA.
[JIRA] (JENKINS-62010) add possibility to define iterations mode uft tests in mtbx format
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-62010 add possibility to define iterations mode uft tests in mtbx format Change By: Radi Berkovich < Parameter Name="mee" Value="12" Type="Integer"/>< Iterations mode="rngIterations|rngAll|oneIteration" start="2" end="3"/> 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.205903.1587563222000.15976.1587563340063%40Atlassian.JIRA.
[JIRA] (JENKINS-62011) Compatibility breakage AzureCredentials#getClientId()
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-62011 Compatibility breakage AzureCredentials#getClientId() Issue Type: Task Assignee: Azure DevOps Components: azure-credentials-plugin, azure-vm-agents-plugin Created: 2020-04-22 13:47 Environment: jenkins: 2.233 azure-credentials: 3.0.1 azure-vm-agents: 1.4.1 Priority: Blocker Reporter: Tim Jacomb At least the azure vm agents plugin has been broken by the azure-credentials 3.0.1 release, probably most of the plugins that depend on azure-credentials https://github.com/jenkinsci/azure-credentials-plugin/compare/azure-credentials-3.0.0...azure-credentials-3.0.1 I can't see an issue or pull request referencing why this change was made, as far as I know those values aren't sensitive, and if you wish to treat them in such way it needs to be done by deprecating the old methods and adding new methods jenkins| 2020-04-22 13:42:04.022+ [id=73] SEVERE c.m.a.v.AzureVMAgentCleanUpTask#execute: AzureVMAgentCleanUpTask: execute: Got execution exception while cleaning jenkins| java.lang.NoSuchMethodError: com.microsoft.azure.util.AzureCredentials.getClientId()Ljava/lang/String; jenkins| at org.jenkinsci.plugins.azurekeyvaultplugin.AzureKeyVaultCredentialRetriever.getCredentialById(AzureKeyVaultCredentialRetriever.java:85) jenkins| at org.jenkinsci.plugins.azurekeyvaultplugin.AzureCredentialsProvider.fetchCredentials(AzureCredentialsProvider.java:98) jenkins| at com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:173) jenkins| at
[JIRA] (JENKINS-62010) add possibility to define iterations mode uft tests in mtbx format
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-62010 add possibility to define iterations mode uft tests in mtbx format Issue Type: New Feature Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-04-22 13:47 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this
[JIRA] (JENKINS-62010) add possibility to define iterations mode uft tests in mtbx format
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-62010 add possibility to define iterations mode uft tests in mtbx format Change By: Radi Berkovich Labels: 6.2.1-BETA 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.205903.1587563222000.15975.1587563280437%40Atlassian.JIRA.
[JIRA] (JENKINS-62010) add possibility to define iterations mode uft tests in mtbx format
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-62010 add possibility to define iterations mode uft tests in mtbx format Change By: 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.205903.1587563222000.15972.1587563280394%40Atlassian.JIRA.
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Govind Sureka commented on JENKINS-61520 Re: At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Hello Anda, Thanks for this. Per solution I restarted my Agent and run the job again. At the end of job it generated the JNLP-4 error. My agent is of Windows Services type. Could you please let me know what needs to be updated for Jenkins Agent. 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.205217.1584601273000.15970.1587561840127%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Yves Schumann commented on JENKINS-60969 Re: Unwanted job interaction if using global pipeline libraries Any news here? Spot the same issue again... 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.15950.1587560340200%40Atlassian.JIRA.
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title
Jean-Pierre Fouche edited a comment on JENKINS-27134
Re: Permission for input approval, or choice of Jenkins-specific group as submitter
Please would you be able to address the issue with RBAC stated in the description?i.e. {code:java}"Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees."{code}I find that the 'submitter' attribute does not work on the input step. We are using Keycloak role-based AuthorizationStrategy. (Our code for the input step has not changed, but we recently changed Jenkins setup from a matrix based authorisation strategy to Keycloak). Code below. Expected result is that if there is a * user * in Keycloak, it should verify that the logged in user matches. Similarly, if there is a * group * in Keycloak, the logged in user should be a member of the specified group.{code:java}isApproved = input(id: 'someId',message: 'Approve?',submitter: 'someuser', // <== 'does not query Keycloak; ignores this parameters: [choice(choices: ['No', 'Yes'],description: 'some description',name: 'some name')]) == 'Yes'{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
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title
Jean-Pierre Fouche edited a comment on JENKINS-27134
Re: Permission for input approval, or choice of Jenkins-specific group as submitter
Please would you be able to address the issue with RBAC stated in the description?i.e. {code:java}"Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees."{code}I find that the 'submitter' attribute does not work on the input step. We are using Keycloak role-based AuthorizationStrategy. (Our code for the input step has not changed, but we recently changed Jenkins setup from a matrix based authorisation strategy to Keycloak). Code below. Expected result is that if there is a *user* in Keycloak, it should verify that the logged in user matches. Similarly, if there is a *group* in Keycloak, the logged in user should be a member of the specified group.{code:java}isApproved = input(id: 'applyPlan',message: 'Approve?',submitter: 'someuser', // <== 'does not query Keycloak; ignores this parameters: [choice(choices: ['No', 'Yes'],description: config. 'some description ' ,name: config. 'some name ' )]) == 'Yes'{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
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title
Jean-Pierre Fouche edited a comment on JENKINS-27134
Re: Permission for input approval, or choice of Jenkins-specific group as submitter
Please would you be able to address the issue with RBAC stated in the description?i.e. {code:java}"Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees."{code}I find that the 'submitter' attribute does not work on the input step. We are using Keycloak role-based AuthorizationStrategy. (Our code for the input step has not changed, but we recently changed Jenkins setup from a matrix based authorisation strategy to Keycloak). Code below. Expected result is that if there is a *user* in Keycloak, it should verify that the logged in user matches. Similarly, if there is a *group* in Keycloak, the logged in user should be a member of the specified group.{code:java}isApproved = input(id: ' applyPlan someId ',message: 'Approve?',submitter: 'someuser', // <== 'does not query Keycloak; ignores this parameters: [choice(choices: ['No', 'Yes'],description: 'some description',name: 'some name')]) == 'Yes'{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
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title
Jean-Pierre Fouche edited a comment on JENKINS-27134
Re: Permission for input approval, or choice of Jenkins-specific group as submitter
Please would you be able to address the issue with RBAC stated in the description?i.e. {code:java}"Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees."{code}I find that the 'submitter' attribute does not work on the input step. We are using Keycloak role-based AuthorizationStrategy. (Our code for the input step has not changed, but we recently changed Jenkins setup from a matrix based authorisation strategy to Keycloak). Code below. Expected result is that if there is a *user* in Keycloak, it should verify that the logged in user matches. Similarly, if there is a *group* in Keycloak, the logged in user should be a member of the specified group.{code:java}isApproved = input(id: 'applyPlan',message: 'Approve?',submitter: 'someuser', // <== 'does not query Keycloak; ignores this parameters: [choice(choices: ['No', 'Yes'],description: config.description,name: config.name)]) == 'Yes'{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
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title
Jean-Pierre Fouche edited a comment on JENKINS-27134
Re: Permission for input approval, or choice of Jenkins-specific group as submitter
Please would you be able to address the issue with RBAC stated in the description?i.e. {code:java}"Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees."{code}I find that the 'submitter' attribute does not work on the input step. We are using Keycloak role-based AuthorizationStrategy. (Our code for the input step has not changed, but we recently changed Jenkins setup from a matrix based authorisation strategy to Keycloak).
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.160927.1424899264000.15844.1587558661054%40Atlassian.JIRA.
[JIRA] (JENKINS-27134) Permission for input approval, or choice of Jenkins-specific group as submitter
Title: Message Title
Jean-Pierre Fouche commented on JENKINS-27134
Re: Permission for input approval, or choice of Jenkins-specific group as submitter
Please would you be able to address the issue with RBAC stated in the description? i.e.
"Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees."
I find that the 'submitter' attribute does not work on the input step. We are using Keycloak role-based AuthorizationStrategy. (Our code has not changed, but we recently changed from a matrix based authorisation strategy to Keycloak).
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.160927.1424899264000.15790.1587558120584%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Ramon Leon updated JENKINS-61854 Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: Ramon Leon Status: In Review Resolved Resolution: Fixed Released As: ldap plugin 1. 23 24 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.205717.1586439894000.15784.1587557940624%40Atlassian.JIRA.
[JIRA] (JENKINS-62009) Warnings Next Generation generates java.lang.IllegalAccessError
Title: Message Title
David Riemens updated an issue
Jenkins / JENKINS-62009
Warnings Next Generation generates java.lang.IllegalAccessError
Change By:
David Riemens
after doing an update to my Jenkins setup from v2.141 to 2.194 I am having issues with jobs that use the 'recordIssues()'. recordIssues(aggregatingResults: false, tools: [mavenConsole(id: "MVN_${componentName}")]) This generates an error like: {quote}[Pipeline] End of Pipelinejava.lang.IllegalAccessError: tried to access method edu.hm.hafner.analysis.Report.remove(Ljava/util/UUID;)Ledu/hm/hafner/analysis/Issue; from class io.jenkins.plugins.analysis.core.model.IssueDifferenceat java.lang.invoke.MethodHandleNatives.resolve(Native Method)at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:975)at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1000)at java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1394)at java.lang.invoke.MethodHandles$Lookup.linkMethodHandleConstant(MethodHandles.java:1750)at java.lang.invoke.MethodHandleNatives.linkMethodHandleConstant(MethodHandleNatives.java:477)Caused: java.lang.BootstrapMethodErrorat io.jenkins.plugins.analysis.core.model.IssueDifference.(IssueDifference.java:40)at io.jenkins.plugins.analysis.core.model.DeltaReport.(DeltaReport.java:48)at io.jenkins.plugins.analysis.core.steps.IssuesPublisher.createAnalysisResult(IssuesPublisher.java:146)at io.jenkins.plugins.analysis.core.steps.IssuesPublisher.attachAction(IssuesPublisher.java:106)at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.publishResult(IssuesRecorder.java:641)at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:575)at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:540)at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:956)at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:919)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 {quote}This is afaict not thrown as an exception, so I cannot catch this error. I tried clearing the workspace (on the executing node), but that does not help. In some cases, a replay of the same code does pass, but mostly all runs generate this error.I have searched for known issues, but could not find anything.I have tried updating to 2.204 (as given in the issue environment), but that does not help either. Note that my Jenkins is running in an air-gapped system,
[JIRA] (JENKINS-62009) Warnings Next Generation generates java.lang.IllegalAccessError
Title: Message Title David Riemens created an issue Jenkins / JENKINS-62009 Warnings Next Generation generates java.lang.IllegalAccessError Issue Type: New Feature Assignee: Ulli Hafner Attachments: plugins.txt Components: warnings-ng-plugin Created: 2020-04-22 12:14 Environment: Jenkins v2.204 Warnings Next Generation Plugin (warnings-ng): 6.1.0 (full list of plugins attached) master: WindowsServer2012 (VM) nodes: WindowsServer2016 (VM) connect: JNLP4 Priority: Minor Reporter: David Riemens after doing an update to my Jenkins setup from v2.141 to 2.194 I am having issues with jobs that use the 'recordIssues()'. This generates an error like: [Pipeline] End of Pipeline java.lang.IllegalAccessError: tried to access method edu.hm.hafner.analysis.Report.remove(Ljava/util/UUID;)Ledu/hm/hafner/analysis/Issue; from class io.jenkins.plugins.analysis.core.model.IssueDifference at java.lang.invoke.MethodHandleNatives.resolve(Native Method) at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:975) at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1000) at java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1394) at java.lang.invoke.MethodHandles$Lookup.linkMethodHandleConstant(MethodHandles.java:1750) at java.lang.invoke.MethodHandleNatives.linkMethodHandleConstant(MethodHandleNatives.java:477) Caused: java.lang.BootstrapMethodError at
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez - Thanks for those kind words. The developers have confirmed that 1.3.35 was the old community plugin. That did set the variables. The new plugin developed by Perforce has never set the variables because we were worried about stamping on environment variables that had been preconfigured already on build slaves. I have therefore raised the following enhancement request: https://issues.jenkins-ci.org/browse/JENKINS-62008 The workaround would still be the same that you need to manually set P4CLIENT in the build script based on P4_CLIENT. 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.15770.1587556740612%40Atlassian.JIRA.
[JIRA] (JENKINS-62008) Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-62008 Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-04-22 11:54 Environment: 1.10.12 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth The old community P4 plugin used to expose the variables P4PORT, P4USER and P4CLIENT as environment variables for scripts to use. The new plugin on purpose uses different variables to ensure we dont override variables that are already set in the environment. Would be good if we had the option to also automatically set P4PORT=P4_PORT, P4USER=P4_USER and P4_CLIENT=P4_CLIENT. Add Comment
[JIRA] (JENKINS-1878) Ability to move job to top of queue
Title: Message Title Ronny Borchert edited a comment on JENKINS-1878 Re: Ability to move job to top of queue The plugin this is not working anymore right after installation . The It is needed a restart of jenkins that the menu entry is missing appearing . 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.131951.1213683192000.15693.1587555361734%40Atlassian.JIRA.
[JIRA] (JENKINS-62007) "filePaths" filter is not working for "ref-update" (refUpdated)
Title: Message Title
S. Panchenko created an issue
Jenkins / JENKINS-62007
"filePaths" filter is not working for "ref-update" (refUpdated)
Issue Type:
Bug
Assignee:
rsandell
Components:
gerrit-trigger-plugin
Created:
2020-04-22 11:26
Environment:
Jenkins ver. 2.186 Gerrit-Trigger: 2.30.4 Pipeline: Groovy: 2.65 SCM API: 2.4.0 Pipeline: Step API: 2.22
Labels:
plugin
Priority:
Minor
Reporter:
S. Panchenko
Example of plugin configuration:
[
@gerrit(gerritProjects=[
{
branches=[{compareType=PLAIN, pattern=unstable}],
compareType=PLAIN,
disableStrictForbiddenFileVerification=false,
pattern=dev_manifest_project,
filePaths=[
{
compareType=PLAIN,
pattern=some_manifest.xml
}
]
}
],
serverName=gerrit.internal.com,
triggerOnEvents=[@refUpdated()]
)])
Found info in old thread:
Feb 24, 2014. When there is ref-updated the option to choose path is taken under consideration. It just not working for ref-update.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Félix Queiruga Balado updated JENKINS-62001 Jenkins / JENKINS-62001 Autocompletion dropdown UI looks broken Change By: Félix Queiruga Balado 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.205893.1587500364000.15678.1587554460229%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Vincent Latombe updated JENKINS-62006 Jenkins / JENKINS-62006 Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get() Change By: Vincent Latombe 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.205898.1587552961000.15676.1587553260220%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Vincent Latombe started work on JENKINS-62006 Change By: Vincent Latombe 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.205898.1587552961000.15674.1587553020486%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-62006 Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get() Issue Type: Bug Assignee: Vincent Latombe Components: core Created: 2020-04-22 10:56 Priority: Minor Reporter: Vincent Latombe When running Kubernetes agents, upon shutting them down (not sure how that is related), I sometimes get the following stacktrace AVERTISSEMENT: failed to shut down 1c62c2d9-920c-479c-94fe-9292dea21a67 java.io.IOException: Remote call on JNLP4-connect connection from localhost/127.0.0.1:53049 failed at hudson.remoting.Channel.call(Channel.java:1004) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1083) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$2.run(ExecutorStepExecution.java:740) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) at java.util.concurrent.FutureTask.run(FutureTask.java) 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) Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletException at hudson.util.ProcessTree.get(ProcessTree.java:432) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. Ramon Leon looks like it is working as expected. Thank y'all for the fix! William 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.205717.1586439894000.15666.1587552420373%40Atlassian.JIRA.
[JIRA] (JENKINS-56311) github-coverage-reporter-plugin missing pipeline instructions
Title: Message Title Jack Newcombe closed an issue as Fixed Jenkins / JENKINS-56311 github-coverage-reporter-plugin missing pipeline instructions Change By: Jack Newcombe 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.197879.1551213782000.15663.1587552240352%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Ramon Leon commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. William Gillaspy 1.24 just released, could you please confirm it works as expected? Thank 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.205717.1586439894000.15655.1587550380707%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Ramon Leon updated JENKINS-61854 Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: Ramon Leon Resolution: Fixed Status: Resolved In 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.205717.1586439894000.15657.1587550380751%40Atlassian.JIRA.
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title Oleksandr Shmyrko commented on JENKINS-61998 Re: Jenkins upgrade fails on CentOS - Public key is not installed See WEBSITE-741 for details. You can find correct public key here: http://mirrors.jenkins-ci.org/redhat/ 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.205889.1587495153000.15648.1587547080160%40Atlassian.JIRA.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Tim Jacomb assigned an issue to Félix Queiruga Balado Jenkins / JENKINS-62001 Autocompletion dropdown UI looks broken Change By: Tim Jacomb Assignee: Félix Queiruga Balado 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.205893.1587500364000.15643.1587547020393%40Atlassian.JIRA.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Tim Jacomb started work on JENKINS-62001 Change By: Tim Jacomb 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.205893.1587500364000.15646.1587547020535%40Atlassian.JIRA.
[JIRA] (JENKINS-42655) Active choices parameters not rendering after dsl generation
Title: Message Title Helen Turner commented on JENKINS-42655 Re: Active choices parameters not rendering after dsl generation Could you please share more information about how you got this working as a post build step? 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.179605.1489140109000.15620.1587546420278%40Atlassian.JIRA.
[JIRA] (JENKINS-61974) Test Results Aggregator - Special character in Job name
Title: Message Title Socrates Sidereas updated JENKINS-61974 Fix will be available in next release 1.0.8 Jenkins / JENKINS-61974 Test Results Aggregator - Special character in Job name Change By: Socrates Sidereas Status: In Review 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 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-60429) Replace @ symbol in workspace suffix path for parallel builds
Title: Message Title Stefan Drissen commented on JENKINS-60429 Re: Replace @ symbol in workspace suffix path for parallel builds While it's great that the default symbol can be changed, it is very unfortunate that the default is @ to start with. In addition to the cases named above, I just spent way too much time figuring out that the @ in the workspace directory that was being passed to a batch file (mergeprop.bat) that was calling another batch file (ubutil.bat) that was starting a JVM with -m silent, was silently failing. After removing the silent option I finally saw the error starting JVM 'unable to parse parameter' - since @ has a special meaning when starting a JVM. 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.203501.1576018208000.15614.1587545280283%40Atlassian.JIRA.
