[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Aleš Dolenc commented on JENKINS-61822 Re: Unable to authorize blueocean with github I have the same issue as people above, but the downgrade button isn't there. Since I'm running a clean install, and Jenkins installs the latest plugins, the downgrade button isn't there (nothing to downgrade to?). Is there a way to manually downgrade or alternative route to downgrade a plugin? Thanks in advance. 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.205672.1586165744000.8538.1586416140317%40Atlassian.JIRA.
[JIRA] (JENKINS-52168) Dockerfile is not in sync with current image name
Title: Message Title Adrien Lecharpentier stopped work on JENKINS-52168 Change By: Adrien Lecharpentier Status: In Progress Open 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.191920.1529967337000.8549.1586416860174%40Atlassian.JIRA.
[JIRA] (JENKINS-61849) Emailext no longer sending emails
Title: Message Title Alison Earney created an issue Jenkins / JENKINS-61849 Emailext no longer sending emails Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 2020-04-09 08:07 Environment: JDK8 Priority: Minor Reporter: Alison Earney Jenkins file has not been changed. Emails were being sent out no problem all day Tuesday. No emails have been sent out since then even though all builds have been successful. Just checking no one else has been having similar issues Add Comment
[JIRA] (JENKINS-61849) Emailext no longer sending emails
Title: Message Title Alison Earney closed an issue as Fixed Added a different email with a different ending and emails arrived. Potentially new security filter for work email blocking any emails from the test suite running Jenkins / JENKINS-61849 Emailext no longer sending emails Change By: Alison Earney Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Change By: Oliver Gondža Labels: 2.222.2-rejected jcasc-compatibility lts-candidate 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.205519.1585231269000.8562.1586427120623%40Atlassian.JIRA.
[JIRA] (JENKINS-61479) java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61479 java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date Change By: Oliver Gondža Labels: 2.222.2-rejected fingerprints lts-candidate 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.205163.1584190858000.8556.1586427120516%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Oliver Gondža Labels: 2.222.2-rejected lts-candidate regression ux 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.205161.1584140786000.8560.1586427120600%40Atlassian.JIRA.
[JIRA] (JENKINS-49159) Cannot run Powershell Start-Job with credentials passed from Jenkins
Title: Message Title Alexander Bakker commented on JENKINS-49159 Re: Cannot run Powershell Start-Job with credentials passed from Jenkins I'm currently working around this issue by using Invoke-Command instead, and allowing PowerShell Remoting sessions with CredSSP authentication on localhost from localhost. 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.187996.1516871515000.8565.1586429280185%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Martin Lee commented on JENKINS-60482 Re: EC2 Alternate Endpoint and Region are reset when managing jenkins configuration This is an issue for me as well for a different reason - we have the us-east-1 region blocked org-wide for reasons various. This means we rely on this setting to get the region list. 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.203569.1576277084000.8573.1586435520276%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Alex Gray commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade One more piece of information: If you configure your job, and select "Restrict where this project can be run" and enter "master_node" as the node label, you'll get "Waiting for next available executor on 'master'". NOT "master_node". It's like it's tripping up on the underscore. If I change that to "masternode", then it correctly says "Waiting for next available executor on 'masternodde'" (but it still doesn't work, even if I have a node with that label.) Hope this bit of information helps! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.8578.1586435880186%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm created an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
2020-04-09 12:40
Environment:
Jenkins 2.222.1, TFS plugin 5.157.1
Priority:
Minor
Reporter:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of https://github.com/jenkinsci/tfs-plugin. The pull request commints are found on branches named remotes/origin/pull/n/merge, so I added an additional branch specifier {{/merge }}to the *Branches to build section of my Jenkins job definition. However, when the build runs, Git refuses to accept the commit from the merge }}branch with the error message skipping resolution of commit ..., since it originates from another repository but builds with the {{HEAD commit of the master branch. Here is an excerpt of git log --oneline --graph --decorate --all: * 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master {{|\ }} | * 37f0c7d (origin/feature-one) Test * | c7e2002 (HEAD, origin/master) Merged PR 2: change 5 Here is the console log: Lightweight checkout support not available, falling back to full checkout. Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile using credential c0c927b7-0a3a-4051-af13-91ef394cd497 {{ > git rev-parse --is-inside-work-tree # timeout=10}} Fetching changes from the remote Git repository {{ > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10}} Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git {{ > g
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commints are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier {{ " */merge }} " to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the " {{merge }} " branch with the error message {{ _skipping resolution of commit ..., since it originates from another repository_ }} but builds with the {{HEAD}} commit of the {{master}} branch.Here is an excerpt of *git log --oneline --graph --decorate --all*:{{* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master}} \ {{|\ }}{{| * 37f0c7d (origin/feature-one) Test}}{{* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5}}Here is the console log:{{Lightweight checkout support not available, falling back to full checkout.}}{{Checking out git [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile}}{{using credential c0c927b7-0a3a-4051-af13-91ef394cd497}} \ {{ > git rev-parse --is-inside-work-tree # timeout=10}}{{Fetching changes from the remote Git repository}}{{ > git config remote.origin.url [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] # timeout=10}}{{Fetching upstream changes from [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] }} \ {{ > git --version # timeout=10}} \ {{using GIT_ASKPASS to set credentials }}{{ > git fetch --tags --progress -- – [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10}}{{skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repository}}{{Seen branch in repository origin-pull/2/merge}}{{Seen branch in repository origin-pull/3/merge}}{{Seen branch in repository origin/feature-one}}{{Seen branch in repository origin/master}}{{Seen 4 remote branches}} \ {{ > git show-ref --tags -d # timeout=10}}{{Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master)}} \ {{ > git config core.sparsecheckout # timeout=10}} \ {{ > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}}{{Commit message: "Merged PR 2: change 5"}} \ {{ > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}}{{Running in Durability level: MAX_SURVIVABILITY}}{{[Pipeline] Start of Pipeline}}{{[Pipeline] node}}{{Running on Jenkins in /var/jenkins_home/workspace/pull-request-verification}}{{[Pipeline] {}}{{[Pipeline] stage}}{{[Pipeline] { (Declarative: Checkout SCM)}}{{[Pipeline] checkout}}{{using c
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commints are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier "*/merge" to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the "{{merge}}" branch with the error message {{ _skipping resolution of commit ..., since it originates from another repository_ }} but builds with the {{HEAD}} commit of the {{master}} branch.Here is an excerpt of *git log --oneline --graph --decorate --all*:{{* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master}} \{{|\ }} {{| * 37f0c7d (origin/feature-one) Test}} {{* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5}}Here is the console log:{{Lightweight checkout support not available, falling back to full checkout.}} {{Checking out git [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git] into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile}} {{using credential c0c927b7-0a3a-4051-af13-91ef394cd497}} \{{ > git rev-parse --is-inside-work-tree # timeout=10}} {{Fetching changes from the remote Git repository}} {{ > git config remote.origin.url [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git] # timeout=10}} {{Fetching upstream changes from [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git]}} \{{ > git --version # timeout=10}} \{{using GIT_ASKPASS to set credentials }} {{ > git fetch --tags --progress – [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git] +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10}} {{skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repository}} {{Seen branch in repository origin-pull/2/merge}} {{Seen branch in repository origin-pull/3/merge}} {{Seen branch in repository origin/feature-one}} {{Seen branch in repository origin/master}} {{Seen 4 remote branches}} \{{ > git show-ref --tags -d # timeout=10}} {{Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master)}} \{{ > git config core.sparsecheckout # timeout=10}} \{{ > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}} {{Commit message: "Merged PR 2: change 5"}} \{{ > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}} {{Running in Durability level: MAX_SURVIVABILITY}} {{[Pipeline] Start of Pipeline}} {{[Pipeline] node}} {{Running on Jenkins in /var/jenkins_home/workspace/pull-request-verification}} {{[Pipeline] {}} {{[Pipeline] stage}} {{[Pipeline] { (Declarative: Checkout SCM)}} {{[Pipeline] checkout}} {{using credential c0c927b7-0a3a-4051-af1
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commints commits are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier " {{\ */merge " }} to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the " {{merge}} " branch with the error message _skipping resolution of commit ..., since it originates from another repository_ but builds with the {{HEAD}} commit of the {{master}} branch.Here is an excerpt of *git log --oneline --graph --decorate --all*:{ { noformat} * 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master }} \{{ |\ }} {{ | * 37f0c7d (origin/feature-one) Test }} {{ * | c7e2002 (HEAD, origin/master) Merged PR 2: change 5 {noformat } } Here is the console log:{ { noformat} Lightweight checkout support not available, falling back to full checkout. }} {{ Checking out git [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile }} {{ using credential c0c927b7-0a3a-4051-af13-91ef394cd497 }} \{{ > git rev-parse --is-inside-work-tree # timeout=10 }} {{ Fetching changes from the remote Git repository }} {{ > git config remote.origin.url [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] # timeout=10 }} {{ Fetching upstream changes from [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ]}} \{{ > git --version # timeout=10 }} \{{ using GIT_ASKPASS to set credentials }} {{> git fetch --tags --progress – [ -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10 }} {{ skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repository }} {{ Seen branch in repository origin-pull/2/merge }} {{ Seen branch in repository origin-pull/3/merge }} {{ Seen branch in repository origin/feature-one }} {{ Seen branch in repository origin/master }} {{ Seen 4 remote branches }} \{{ > git show-ref --tags -d # timeout=10 }} {{ Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master) }} \{{ > git config core.sparsecheckout # timeout=10 }} \{{ > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10 }} {{ Commit message: "Merged PR 2: change 5" }} \{{ > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10 }} {{ Running in Durability level: MAX_SURVIVABILITY }} {{ [Pipeline] Start of Pipeline }} {{ [Pipeline] node }} {{ Running on Jenkins in /var/jenkins_home
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commits are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier {{\*/merge}} to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the {{merge}} branch with the error message _skipping resolution of commit ..., since it originates from another repository_ but builds with the {{HEAD}} commit of the {{master}} branch. Here is an excerpt of *git log --oneline --graph --decorate --all*:{noformat}* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master|\ | * 37f0c7d (origin/feature-one) Test* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5{noformat}Here is the console log:{noformat}Lightweight checkout support not available, falling back to full checkout.Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repositorySeen branch in repository origin-pull/2/mergeSeen branch in repository origin-pull/3/mergeSeen branch in repository origin/feature-oneSeen branch in repository origin/masterSeen 4 remote branches > git show-ref --tags -d # timeout=10Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Commit message: "Merged PR 2: change 5" > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/pull-request-verification[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commits are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier {{\*/merge}} to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the {{merge}} branch with the error message _skipping resolution of commit ..., since it originates from another repository_ but builds with the {{HEAD}} commit of the {{master}} branch instead of {{origin-pull/3/merge}} . Here is an excerpt of *git log --oneline --graph --decorate --all*:{noformat}* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master|\ | * 37f0c7d (origin/feature-one) Test* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5{noformat}Here is the console log:{noformat}Lightweight checkout support not available, falling back to full checkout.Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repositorySeen branch in repository origin-pull/2/mergeSeen branch in repository origin-pull/3/mergeSeen branch in repository origin/feature-oneSeen branch in repository origin/masterSeen 4 remote branches > git show-ref --tags -d # timeout=10Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Commit message: "Merged PR 2: change 5" > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/pull-request-verification[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git co
[JIRA] (JENKINS-53062) k8s slave should automatically deleted
Title: Message Title Karl-Philipp Richter commented on JENKINS-53062 Re: k8s slave should automatically deleted Possible duplicate of https://issues.jenkins-ci.org/browse/JENKINS-53431 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.193053.1534401153000.8599.1586437380159%40Atlassian.JIRA.
[JIRA] (JENKINS-47144) Kubernetes pod slaves that never start successfully never get cleaned up
Title: Message Title Karl-Philipp Richter commented on JENKINS-47144 Re: Kubernetes pod slaves that never start successfully never get cleaned up Possible duplicate of https://issues.jenkins-ci.org/browse/JENKINS-53431 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.185546.1506446945000.8602.1586437620290%40Atlassian.JIRA.
[JIRA] (JENKINS-53540) Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
Title: Message Title Meghana V commented on JENKINS-53540 Re: Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter How do I access these input values in jenkins pipeline? 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.194016.1536789673000.8614.1586438040168%40Atlassian.JIRA.
[JIRA] (JENKINS-61851) Repeated build failures after agent disconnection
Title: Message Title
Mikaël Barbero created an issue
Jenkins / JENKINS-61851
Repeated build failures after agent disconnection
Issue Type:
Bug
Assignee:
Jeff Thompson
Components:
remoting
Created:
2020-04-09 13:17
Environment:
master = Jenkins 2.229, in docker image (linux) proxy passed by nginx, openjdk 1.8.0_242 agent = remoting 4.3 (with -webSocket connection), windows10, openjdk 1.9.0_202
Priority:
Major
Reporter:
Mikaël Barbero
We've been facing a couple of build failure because of agent disconnection for no apparent reasons. Failures are following the same pattern: The build logs say (time of error): {{ 9:45:50 FATAL: command execution failed java.nio.channels.ClosedChannelException at jenkins.agents.WebSocketAgents$Session.closed(WebSocketAgents.java:141) at jenkins.websocket.WebSocketSession.onWebSocketSomething(WebSocketSession.java:91) ... Caused: java.io.IOException: Backing channel 'our-windows10-agent' is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)}} On the agent, the logs say: {{ Apr 09, 2020 9:45:50 AM hudson.Launcher$RemoteLaunchCallable$1 join INFO: Failed to synchronize IO streams on the channel hudson.remoting.Channel@11010e5e:our-windows10-agent hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@11010e5e:our-windows10-agent": Remote call on our-windows10-agent failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:991) at hudson.remoting.Channel.syncIO(Channel.java:1730) ... Caused by: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@11010e5e:our-windows10-agent": channel is already closed at hudson.remoting.Engine$1AgentEndpoint.onClose(Engine.java:590) at io.jenkins.remoting.shaded.org.glassfish
[JIRA] (JENKINS-47144) Kubernetes pod slaves that never start successfully never get cleaned up
Title: Message Title Karl-Philipp Richter edited a comment on JENKINS-47144 Re: Kubernetes pod slaves that never start successfully never get cleaned up Possible duplicate of https://issues.jenkins-ci.org/browse/JENKINS- 53431 54540 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.185546.1506446945000.8632.1586438401153%40Atlassian.JIRA.
[JIRA] (JENKINS-53062) k8s slave should automatically deleted
Title: Message Title Karl-Philipp Richter edited a comment on JENKINS-53062 Re: k8s slave should automatically deleted Possible duplicate of https://issues.jenkins-ci.org/browse/JENKINS- 53431 54540 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.193053.1534401153000.8621.1586438400623%40Atlassian.JIRA.
[JIRA] (JENKINS-61851) Repeated build failures after agent disconnection
Title: Message Title
Mikaël Barbero updated an issue
Jenkins / JENKINS-61851
Repeated build failures after agent disconnection
Change By:
Mikaël Barbero
We've been facing a couple of build failure because of agent disconnection for no apparent reasons. Failures are following the same pattern:The build logs say (time of error):{ { noformat} 9:45:50 FATAL: command execution failedjava.nio.channels.ClosedChannelException at jenkins.agents.WebSocketAgents$Session.closed(WebSocketAgents.java:141) at jenkins.websocket.WebSocketSession.onWebSocketSomething(WebSocketSession.java:91)...Caused: java.io.IOException: Backing channel 'our-windows10-agent' is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216) {noformat } } On the agent, the logs say:{ { noformat} Apr 09, 2020 9:45:50 AM hudson.Launcher$RemoteLaunchCallable$1 joinINFO: Failed to synchronize IO streams on the channel hudson.remoting.Channel@11010e5e:our-windows10-agenthudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@11010e5e:our-windows10-agent": Remote call on our-windows10-agent failed. The channel is closing down or has closed downat hudson.remoting.Channel.call(Channel.java:991)at hudson.remoting.Channel.syncIO(Channel.java:1730)...Caused by: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@11010e5e:our-windows10-agent": channel is already closedat hudson.remoting.Engine$1AgentEndpoint.onClose(Engine.java:590)at io.jenkins.remoting.shaded.org.glassfish.tyrus.core.TyrusEndpointWrapper.onClose(TyrusEndpointWrapper.java:1251)Apr 09, 2020 9:45:50 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:UserRPCRequest:hudson.Launcher$RemoteProcess.join[](4)java.lang.LinkageError: Failed to load hudson.util.ProcessTreeat hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:391)...Caused by: java.lang.NoClassDefFoundError: hudson/util/ProcessTreeRemoting$IProcessTreeat java.lang.ClassLoader.defineClass1(Native Method)...Caused by: java.lang.ClassNotFoundException: hudson.util.ProcessTreeRemoting$IProcessTreeat java.net.URLClassLoader.findClass(URLClassLoader.java:382) {noformat } } On the master, the agent logs say (file slave.log.1, mtime = Apr 9 09:45):{ { noformat} Inbound agent connected from x.x.x.xRemoting version: 4.3This is a Windows agentonOnline: class org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl reported an exception: java.net.MalformedURLException: no protocol: jnlpJars/slave.jarAgent successfully connected and onlineERROR: Connection terminatedjava.nio.channels.ClosedChannelException at jenkins.agents.WebSocketAgents$Session.closed(WebSocketAgents.java:141) at jenkins.websocket.WebSocketSession.onWebSocketSomething(WebSocketSession.java:91) at jenkins.websocket.WebSockets$$Lambda$282/940934C0.invoke(Unknown Source) at com.sun.proxy.$Proxy74.onWebSocketClose(Unknown Source) at org.eclipse.jetty.websoc
[JIRA] (JENKINS-61852) Allow use of Kubernetes Jobs
Title: Message Title Karl-Philipp Richter created an issue Jenkins / JENKINS-61852 Allow use of Kubernetes Jobs Issue Type: New Feature Assignee: Unassigned Components: kubernetes-plugin Created: 2020-04-09 13:22 Priority: Minor Reporter: Karl-Philipp Richter As a user I want to make sure that Kubernetes Objects created by the Jenkins Kubernetes Plugin don't exist longer than a certain deadline in order make sure that automatic downscaling of k8s node pools can be performed. This avoids unnecessary costs for pods which are stuck in error state. Even though and issue with pods remaining in error state is tracked at https://issues.jenkins-ci.org/browse/JENKINS-54540 the use of jobs would introduce an additional safety using built-in functions of the Kubernetes scheduler. The concept of jobs is described at https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/. Add Comment
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title Michał Kochanowicz created an issue Jenkins / JENKINS-61853 Broken links to pull requests Issue Type: Bug Assignee: Jakub Bochenski Components: stash-pullrequest-builder-plugin Created: 2020-04-09 13:25 Environment: Jenkins 2.222.1 Stash Pullrequest Builder Plugin 1.17 Priority: Minor Reporter: Michał Kochanowicz Within job, there is a build list. On this list, there used to be links to PRs. Currently I can see HTML tags instead of links: #13872 3 MB Apr 9, 2020 2:22 PM PR #8260 XXX-26550] Xx Add Comment
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title
Michał Kochanowicz updated an issue
Jenkins / JENKINS-61853
Broken links to pull requests
Change By:
Michał Kochanowicz
Within job, there is a build list. On this list, there used to be links to PRs. Currently I can see HTML tags instead of links: {panel}#13872 3 MBApr 9, 2020 2:22 PMPR #8260 XXX-26550] Xx {panel} !broken-links.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.205716.158643871.8641.1586438940219%40Atlassian.JIRA.
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title Michał Kochanowicz updated an issue Jenkins / JENKINS-61853 Broken links to pull requests Change By: Michał Kochanowicz Attachment: broken-links.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205716.158643871.8639.1586438940191%40Atlassian.JIRA.
[JIRA] (JENKINS-61852) Allow use of Kubernetes Jobs
Title: Message Title Karl-Philipp Richter updated an issue Jenkins / JENKINS-61852 Allow use of Kubernetes Jobs Change By: Karl-Philipp Richter As a user I want to make sure that Kubernetes Objects created by the Jenkins Kubernetes Plugin don't exist longer than a certain deadline in order make sure that automatic downscaling of k8s node pools can be performed. This avoids unnecessary costs for pods which are stuck in error state.Even though and issue with pods remaining in error state is tracked at https://issues.jenkins-ci.org/browse/JENKINS-54540 the use of jobs would introduce an additional safety using built-in functions of the Kubernetes scheduler.The concept of jobs is described at https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/. It's the preferred way of performing tasks that terminate in Kubernetes. 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 Iss
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy created an issue Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Issue Type: Bug Assignee: Unassigned Components: ldap-plugin Created: 2020-04-09 13:44 Environment: Jenkins 2.230 Labels: ldap Priority: Critical Reporter: William Gillaspy Clicking the "Test LDAP Settings" button in the "Configure Global Security" page no longer functions. Expected: A form to appear requesting a user to test against. F12 console reveals: Uncaught TypeError: Connot read property 'realm' of undefined. at ldapValidateButton (validate.js:24) at HTMLButtonElement.onClick((index):140) Add Comment
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title Jakub Bochenski closed an issue as Not A Defect This is caused by the upgraded markup formatter https://github.com/jenkinsci/antisamy-markup-formatter-plugin/releases/tag/antisamy-markup-formatter-2.0 Jenkins / JENKINS-61853 Broken links to pull requests Change By: Jakub Bochenski Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-61855) Doxygen parser doesn't detect Doxygen Warnings
Title: Message Title Nils Gerke created an issue Jenkins / JENKINS-61855 Doxygen parser doesn't detect Doxygen Warnings Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-09 14:10 Environment: Jenkins 2.222.1, Warnings Next Generation Plugin 8.1.0, Doxygen 1.8.13 Priority: Minor Reporter: Nils Gerke I got lots of Doxygen warnings similar to these: /repo/src/libraries/base/include/configuration.h(115): warning: Member Notify(const IProperty &oProperty) override (function) of class property_variable< T > is not documented. /repo/src/libraries/base/include/configuration.h(120): warning: Member GetType(IString &&strType) const override (function) of class property_variable< T > is not documented. /repo/src/libraries/base/include/configuration.h(125): warning: Member GetValue() const override (function) of class property_variable< T > is not documented. /repo/src/libraries/base/include/configuration.h(130): warning: Member operator*() const (function) of class property_variable< T > is not documented. /repo/src/libraries/base/include/configuration.h(135): warning: Member operator const T &() const (function) of class property_variable< T > is not documented. /repo/src/libraries/base/include/configuration.h(140): warning: Member operator==(const T &oVal) (function) of class property_variable< T > is not documented. /repo/src/libraries/base/include/configuration.h(145): warning: Member operator!=(const T &oVal) (function) of class property_variable< T > is not documented.
[JIRA] (JENKINS-61856) Add the ability to "Delete workspace before build starts" in a declarative pipeline
Title: Message Title Dennis Lundberg created an issue Jenkins / JENKINS-61856 Add the ability to "Delete workspace before build starts" in a declarative pipeline Issue Type: Bug Assignee: Oliver Gondža Components: ws-cleanup-plugin Created: 2020-04-09 14:25 Priority: Minor Reporter: Dennis Lundberg It is possible to find the declarative pipeline syntax for cleanWs in the pipeline-syntax snippet generator inside a Jenkins instance. I have however not found any instructions on how to use preBuildCleanup in a declarative pipeline. I don't even know if it is possible. Add Comment
[JIRA] (JENKINS-11257) Stopping a parent job doesn't stop the triggered child jobs
Title: Message Title Ploutarchos Spyridonos commented on JENKINS-11257 Re: Stopping a parent job doesn't stop the triggered child jobs Is there any update on this? My team would be very interested in this feature request. 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.141476.1317990849000.8655.1586442480683%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Michael McClaren commented on JENKINS-61822 Re: Unable to authorize blueocean with github Grab the previous version of the plugin here http://updates.jenkins-ci.org/download/plugins/github-api/ then stop jenkins, rename the existing file/directories for this plugin in the plugins folder and place the .hpi file in the folder. restart jenkins, verify that the plugin manager recognizes the older version, it should now be prompting you to upgrade. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.8685.1586442840251%40Atlassian.JIRA.
[JIRA] (JENKINS-61855) Doxygen parser doesn't detect Doxygen Warnings
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-61855 Doxygen parser doesn't detect Doxygen Warnings Change By: Ulli Hafner Component/s: analysis-model Component/s: warnings-ng-plugin Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Michael McClaren edited a comment on JENKINS-61822 Re: Unable to authorize blueocean with github Grab the previous version of the plugin here[http://updates.jenkins-ci.org/download/plugins/github-api/]then stop jenkins, rename the existing file/directories for this plugin in the plugins folder and place the .hpi file in the folder.restart jenkins, verify that the plugin manager recognizes the older version, it should now be prompting you to upgrade update this plugin . Do not update obviously. 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.205672.1586165744000.8695.1586443860352%40Atlassian.JIRA.
[JIRA] (JENKINS-61857) Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exception
Title: Message Title Simon Renger updated an issue Jenkins / JENKINS-61857 Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exception Change By: Simon Renger Summary: Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exceiption exception 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.205720.1586446415000.8703.1586446440225%40Atlassian.JIRA.
[JIRA] (JENKINS-61857) Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exceiption
Title: Message Title
Simon Renger created an issue
Jenkins / JENKINS-61857
Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exceiption
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-04-09 15:33
Environment:
Jenkins: 2.228 Windows
Priority:
Minor
Reporter:
Simon Renger
Side Note: I do not have access to install plugins etc this is why I am using pipeline scripts etc extensive which might not be optimal. I am just a user of our school's build server. The following code part of my shared library. Situation: I have a global function
p4c.withSwarm(credentials,p4Port,client,mapping,Closure body)
Implementation:
def withSwarmUrl(credentials,client,mapping,Closure body){
withCredentials([usernamePassword(credentialsId: credentials, passwordVariable: 'p4USERPASS', usernameVariable: 'p4USER' )]) {
def url = swarmUrl(credentials,client,mapping)
body(url,env.p4User,env.p4USERPASS)
}
}
def withSwarm(credentials,p4Port,client,mapping,Closure body){
withSwarmUrl(env.P4USER,env.P4CLIENT,env.P4MAPPING)
{
url,user->
def p4Ticket = ticket(credentials,p4Port)
body(user,p4Ticket,url)
}
}
[JIRA] (JENKINS-61858) GitLab git repository job showing errors on Configuration page
Title: Message Title J A created an issue Jenkins / JENKINS-61858 GitLab git repository job showing errors on Configuration page Issue Type: Bug Assignee: Unassigned Attachments: image-2020-04-09-16-53-09-636.png Components: core Created: 2020-04-09 15:53 Priority: Blocker Reporter: J A Using Jenkins 2.230 Migrated Bitbucket repository location to a new GitLab remote, and saving details of git endpoint was applied successfully, and the job runs correctly pulling from the new GitLab repo, but on going back to the Configuration for the job, I am presented with this screen: Add Comment
[JIRA] (JENKINS-61858) GitLab git repository job showing errors on Configuration page
Title: Message Title J A updated an issue Jenkins / JENKINS-61858 GitLab git repository job showing errors on Configuration page Change By: J A Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205721.1586447601000.8705.1586447880107%40Atlassian.JIRA.
[JIRA] (JENKINS-61858) GitLab git repository job showing errors on Configuration page
Title: Message Title J A updated an issue Jenkins / JENKINS-61858 GitLab git repository job showing errors on Configuration page Change By: J A Using Jenkins 2.230Migrated Bitbucket repository location to a new GitLab remote, and saving details of git endpoint was applied successfully, and the job runs correctly pulling from the new GitLab repo, but on going back to the Configuration for the job, I am presented with this screen with top section stuck in a constant state of "loading" (see screenshot attached) and nothing below the screenshot below appears... :!image-2020-04-09-16-53-09-636.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205721.1586447
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Alex Earl commented on JENKINS-61798 Re: New Windows Installer always redirects to 8080 after completing the installation See https://github.com/jenkinsci/packaging/pull/158 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.205642.1585912413000.8708.1586448420156%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Alex Earl updated JENKINS-61798 Jenkins / JENKINS-61798 New Windows Installer always redirects to 8080 after completing the installation Change By: Alex Earl Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205642.1585912413000.8712.1586448480353%40Atlassian.JIRA.
[JIRA] (JENKINS-61857) Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exception
Title: Message Title
Simon Renger updated an issue
Jenkins / JENKINS-61857
Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exception
Change By:
Simon Renger
_Side Note:_ I do not have access to install plugins etc this is why I am using pipeline scripts etc extensive which might not be optimal. I am just a user of our school's build server. The following code part of my shared library.*Situation:*I have a global function {code:java}p4c.withSwarm(credentials,p4Port,client,mapping,Closure body){code} _Implementation:_{code:java}def withSwarmUrl(credentials,client,mapping,Closure body){withCredentials([usernamePassword(credentialsId: credentials, passwordVariable: 'p4USERPASS', usernameVariable: 'p4USER' )]) {def url = swarmUrl(credentials,client,mapping)body(url,env.p4User,env.p4USERPASS)}}def withSwarm(credentials,p4Port,client,mapping,Closure body){withSwarmUrl(env.P4USER,env.P4CLIENT,env.P4MAPPING){ url,user->def p4Ticket = ticket(credentials,p4Port)body(user,p4Ticket,url)}}{code} Which I am using like this in my Jenkinsfile in a step: {code:java}p4c.withSwarm(env.P4USER,env.P4HOST,env.P4CLIENT,env.P4MAPPING,{user,ticket,swarmUrl ->swarm.setup(user,ticket,swarmUrl)def reviewObject = swarm.reviewInfo(reviewId)msg = swarmReviewToMessage(reviewObject)msg = discord.mentionUser(msg)}){code}The mention function is implemented as follows: {code:java}def mentionUser(message,filterFile="discord_filter.json"){if(!fileExists(filterFile)){error("Could not find ${filterFile}")return null;}def content = ""script {content = readFile file: filterFile}def jsonSlurper = new JsonSlurper()def filterObject = jsonSlurper.parseText(content)filterObject.discord_users.each{ key, value -> message = message.replace("${key}","<@${value}>")}return message}{code}Whenever I am using this setup I end up with the following exception:{code:java}an exception which occurred: in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@fcafd7 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@13817e5 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@220483 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@f8c2f3 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@60419e in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@aea904 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@18f41ab in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@11b98b6 in f
[JIRA] (JENKINS-55992) Offer official Windows Jenkins installer for Java 11
Title: Message Title Alex Earl updated JENKINS-55992 This will be part of the release automation roll out. Jenkins / JENKINS-55992 Offer official Windows Jenkins installer for Java 11 Change By: Alex Earl Status: In Progress 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 w
[JIRA] (JENKINS-61857) Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exception
Title: Message Title Simon Renger closed an issue as Not A Defect Jenkins / JENKINS-61857 Pipeline: Scope triggers in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals exception Change By: Simon Renger Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205720.1586446415000.8716.1586449320097%40Atlassian.JIRA.
[JIRA] (JENKINS-61810) Post build script not showing
Title: Message Title Daniel Heid commented on JENKINS-61810 Re: Post build script not showing Hi there! Thanks for the ticket and sorry for answering so late. I will look into it now. 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.205655.1585973841000.8718.1586451780199%40Atlassian.JIRA.
[JIRA] (JENKINS-61810) Post build script not showing
Title: Message Title Daniel Heid commented on JENKINS-61810 Re: Post build script not showing I need to reproduce the problem. Would you please be so kind and attach your config.xml? Just add "/config.xml" (without the quotes) to the URL, download the file and attach it here. 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.205655.1585973841000.8720.1586452020123%40Atlassian.JIRA.
[JIRA] (JENKINS-26724) "Delete build" and "Delete project" actions are confusingly similar
Title: Message Title Hector Fontanez commented on JENKINS-26724 Re: "Delete build" and "Delete project" actions are confusingly similar I would like to point out that (maybe) your Jenkins admin should remove DELETE privileges to authenticated users. I had this issue happen today to one of my QAs and I decided to take this course of action. That said, if you are a Jenkins admin and made that mistake, I can see something like this to be of some benefit. 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.160399.1422786306000.8722.1586452680220%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover should abort early to avoid creating enormous CompositeIOExceptions
Title: Message Title Devin Nusbaum updated JENKINS-61841 Jenkins / JENKINS-61841 PathRemover should abort early to avoid creating enormous CompositeIOExceptions Change By: Devin Nusbaum 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.205701.1586366831000.8728.1586453820211%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover should abort early to avoid creating enormous CompositeIOExceptions
Title: Message Title Devin Nusbaum commented on JENKINS-61841 Re: PathRemover should abort early to avoid creating enormous CompositeIOExceptions PR is up: https://github.com/jenkinsci/jenkins/pull/4639. 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.205701.1586366831000.8727.1586453820122%40Atlassian.JIRA.
[JIRA] (JENKINS-61859) Fails to load with "Illegal use of nonvirtual function call" error
Title: Message Title David Leatherman created an issue Jenkins / JENKINS-61859 Fails to load with "Illegal use of nonvirtual function call" error Issue Type: Bug Assignee: sue445 Components: yaml-axis-plugin Created: 2020-04-09 18:26 Environment: Jenkins 2.230 yaml-axis-plugin 0.2.1 Priority: Major Reporter: David Leatherman The yaml-axis-plugin fails to load with the error "Illegal use of nonvirtual function call". Jenkins does start but all builds using the yaml matrix will fail. I've pasted the error below but it also appears here: https://ci.jenkins.io/job/Plugins/job/yaml-axis-plugin/job/SECURITY-1825/1/console 1) Error injecting constructor, java.lang.VerifyError: (class: org/jenkinsci/plugins/yamlaxis/YamlAxis, method: super$1$spliterator signature: ()Ljava/util/Spliterator;) Illegal use of nonvirtual function call at org.jenkinsci.plugins.yamlaxis.YamlAxis$DescriptorImpl.(YamlAxis.groovy:75)1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:440) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hu
[JIRA] (JENKINS-61859) Fails to load with "Illegal use of nonvirtual function call" error
Title: Message Title
Jonah Bull commented on JENKINS-61859
Re: Fails to load with "Illegal use of nonvirtual function call" error
The root cause seems to be that the plugin is configured with groovy 1.8.9 as a runtime dependency, but the version of groovy shipped with Jenkins (as of the current release) is 2.4.12:
dependencies {
// NOTE: groovy version included in Jenkins is 1.8.9
runtime 'org.codehaus.groovy:groovy-all:1.8.9'
After updating both the groovy dependency (I added both runtime and compile entries, not sure they're both necessary) and the spock dependency I was able to build a version of the plugin off of master that works. Diff of the changes:
diff --git a/build.gradle b/build.gradle
index 66231ac..789574b 100644
--- a/build.gradle
+++ b/build.gradle
@@ -46,10 +46,11 @@ repositories {
dependencies {
// NOTE: groovy version included in Jenkins is 1.8.9
- runtime 'org.codehaus.groovy:groovy-all:1.8.9'
+ runtime 'org.codehaus.groovy:groovy-all:2.4.12'
+ compile 'org.codehaus.groovy:groovy-all:2.4.12'
compile 'org.yaml:snakeyaml:1.26'
- testCompile 'org.spockframework:spock-core:0.7-groovy-1.8'
+ testCompile 'org.spockframework:spock-core:1.0-groovy-2.4'
jenkinsPlugins 'org.jenkins-ci.plugins:matrix-project:1.6@jar'
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-26002) Send ALM test execution summary email
Title: Message Title Phil Ritz reopened an issue ALM 14.53. Execute Micro Focus functional tests From Micro Focus ALM Publish Micro Focus tests result The testset has Automation tab\Execution Summary\Send Summary... checked with my email entered. If I run the testset from ALM, the summary is emailed. If I run the testset from the Jenkins build step, no ALM summary is emailed. Jenkins / JENKINS-26002 Send ALM test execution summary email Change By: Phil Ritz Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You re
[JIRA] (JENKINS-26002) Send ALM test execution summary email
Title: Message Title Phil Ritz assigned an issue to Unassigned Jenkins / JENKINS-26002 Send ALM test execution summary email Change By: Phil Ritz Assignee: Roy Lu 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.159580.1418221135000.8761.1586464560223%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Currently: antisamy-markup-formatter 1.8 true timestamper 1.11.1 true > no owasp-java-html-sanitizer find ./ name 'owasp-java-html-sanitizer*' -print I re-tried the plugins archive updates, but it failed wih Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy at hudson.markup.RawHtmlMarkupFormatter.translate(RawHtmlMarkupFormatter.java:44) at hudson.markup.MarkupFormatter.translate(MarkupFormatter.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTTernaryNode.value(ASTTernaryNode.java:41) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly.tags.core.ExprTag.doTag(ExprTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) ... 140 more with: antisamy-markup-formatter 2.0 true timestamper 1.11.2 true uno-choice 2.2.2 true find ./ name 'owasp-java-html-sanitizer*' -print ./plugins/antisamy-markup-formatter/WEB-INF/lib/owasp-java-html-sanitizer-20191001.1.jar ./plugins/timestamper/WEB-INF/lib/owasp-java-html-sanitizer-20191001.1.jar and tried old the update with the proxy, but i fails with another error: java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:23
[JIRA] (JENKINS-26002) Send ALM test execution summary email
Title: Message Title Phil Ritz commented on JENKINS-26002 Re: Send ALM test execution summary email Jenkins ver. 2.176.2 Micro Focus Application Automation Tools 6.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159580.1418221135000.8771.1586465040330%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris edited a comment on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Currently:antisamy-markup-formatter 1.8 truetimestamper 1.11.1 true - > no owasp-java-html-sanitizer - find ./ - name 'owasp-java-html-sanitizer - *' -print I re-tried the plugins archive updates, but it failed wih Could not initialize class hudson.markup.BasicPolicy at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)... Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy at hudson.markup.RawHtmlMarkupFormatter.translate(RawHtmlMarkupFormatter.java:44) at hudson.markup.MarkupFormatter.translate(MarkupFormatter.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTTernaryNode.value(ASTTernaryNode.java:41) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly.tags.core.ExprTag.doTag(ExprTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) ... 140 more with:antisamy-markup-formatter 2.0 truetimestamper 1.11.2 trueuno-choice 2.2.2 true find ./ -name 'owasp-java-html-sanitizer-*' -print./plugins/antisamy-markup-formatter/WEB-INF/lib/owasp-java-html-sanitizer-20191001.1.jar./plugins/timestamper/WEB-INF/lib/owasp-java-html-sanitizer-20191001.1.jar and tried old the update with the proxy, but i fails with another error: java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.St
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris edited a comment on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Currently:antisamy-markup-formatter 1.8 true timestamper 1.11.1 true> no owasp-java-html-sanitizer find ./ name 'owasp-java-html-sanitizer*' -print I re-tried the plugins archive updates, but it failed wih Could not initialize class hudson.markup.BasicPolicy at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)...Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy at hudson.markup.RawHtmlMarkupFormatter.translate(RawHtmlMarkupFormatter.java:44) at hudson.markup.MarkupFormatter.translate(MarkupFormatter.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTTernaryNode.value(ASTTernaryNode.java:41) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly.tags.core.ExprTag.doTag(ExprTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) ... 140 more with:antisamy-markup-formatter 2.0 truetimestamper 1.11.2 trueuno-choice 2.2.2 truefind ./ -name 'owasp-java-html-sanitizer-*' -print ./plugins/antisamy-markup-formatter/WEB-INF/lib/owasp-java-html-sanitizer-20191001.1.jar ./plugins/timestamper/WEB-INF/lib/owasp-java-html-sanitizer-20191001.1.jar and tried old the plugins update with the proxy, but i it fails with another error: java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapl
[JIRA] (JENKINS-26002) Send ALM test execution summary email
Title: Message Title Phil Ritz commented on JENKINS-26002 Re: Send ALM test execution summary email I need the ALM report unless there is a similar report from Jenkins 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.159580.1418221135000.8781.1586465640177%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover methods can throw enormous CompositeIOExceptions
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-61841 PathRemover methods can throw enormous CompositeIOExceptions Change By: Devin Nusbaum Summary: PathRemover should abort early to avoid creating methods can throw enormous CompositeIOExceptions 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.205701.1586366831000.8784.1586467440172%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover methods can throw enormous CompositeIOExceptions
Title: Message Title Devin Nusbaum updated JENKINS-61841 Jenkins / JENKINS-61841 PathRemover methods can throw enormous CompositeIOExceptions Change By: Devin Nusbaum Status: In Review 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.205701.1586366831000.8786.1586467620232%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover methods can throw enormous CompositeIOExceptions
Title: Message Title Devin Nusbaum commented on JENKINS-61841 Re: PathRemover methods can throw enormous CompositeIOExceptions Daniel Beck Recommended a different approach: Instead of aborting the deletion early, just truncate the list of exceptions if it gets too large. The benefits of this approach are that the actual deletion behavior is unchanged, and it avoids issues where one problematic subdirectory could result in a deletion operation not being able to remove a significant number of files because the problematic subdirectory is visited first. 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.205701.1586366831000.8785.1586467620116%40Atlassian.JIRA.
[JIRA] (JENKINS-53540) Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
Title: Message Title Bruno P. Kinoshita commented on JENKINS-53540 Re: Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter Not sure if that will work well with pipelines Meghana V, the plug-in is not developed with pipelines in mind (though it may work). It's designed for the HTML DOM of Jenkins UI, which can act different when using pipelines. 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.194016.1536789673000.8788.1586472660239%40Atlassian.JIRA.
[JIRA] (JENKINS-61408) Git executable is randomly set to empty string
Title: Message Title Stephane Odul commented on JENKINS-61408 Re: Git executable is randomly set to empty string We have some additional data about the issue. The empty string is because our git installer did not have a fallback value and so the git command ended up being null. The root cause is `Failed to get git executable` which is probably returned by the installer but we have no information as to why it is failing. In our case the installer is a just a shell script that writes an other shell script which becomes a wrapper for the git commands so that we can have smarter retry logic and better tuned ref specs than possible with the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205062.1583793463000.8793.1586475060264%40Atlassian.JIRA.
[JIRA] (JENKINS-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title Martin Karing commented on JENKINS-41805 Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. Steven Christenson: I don't think the directory is required for the replay operation. If I delete the @libs workspace on the master by hand, replay still work fine. There is a copy of the required files of the library in the directory of all builds. I am guessing this one is utilized for what ever the replay requires it for, or the required commit is just checked out from the repository again. No matter, there is still a @libs directory in the directory for the master workspaces, that just sits there forever. It contains the in my case implicitly loaded shared libraries for each job. And there are a lot of them due to heavy use of feature branches and pull requests. It can't be deleted by the pipeline and it's not automatically deleted if the associated job in Jenkins is deleted. Also I do not have any build processors enabled on the master node, so that workaround with switching to the problematic directory directly does not fly as well, because I can't get into the master workspaces with the pipelines as far as I know. The one way to get rid of those directories I was able to come up with is to have the server run a nightly cron job that clears our the workspace directory of the master, so the issue does not get out of hand. That solution works, but I'd rather solve that issue inside of Jenkins. 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" g
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title Basil Crow commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Bisection shows this was introduced in jenkinsci/timestamper-plugin#52. 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.205703.1586369761000.8879.1586490480219%40Atlassian.JIRA.
[JIRA] (JENKINS-61860) Jenkins pipeline terraform for azure using azure service principle
Title: Message Title muragaiah muthirevula created an issue Jenkins / JENKINS-61860 Jenkins pipeline terraform for azure using azure service principle Issue Type: Bug Assignee: Azure DevOps Components: azure-credentials-plugin Created: 2020-04-10 04:22 Priority: Minor Reporter: muragaiah muthirevula I am trying to build the pipeline to azure using terraform ,i have used azure credential plugin ,created golbal credential . getting below error .Please kindly advise . Error: Error building AzureRM Client: Authenticating using the Azure CLI is only supported as a User (not a Service Principal). To authenticate to Azure using a Service Principal, you can use the separate 'Authenticate using a Service Principal' auth method - instructions for which can be found here: https://www.terraform.io/docs/providers/azurerm/guides/service_principal_client_secret.html Alternatively you can authenticate using the Azure CLI by using a User Account. Add Comment
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title Basil Crow commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. I opened jenkinsci/timestamper-plugin#59 with a fix. John Rocha, can you please try this incremental build and confirm that the issue is resolved? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.8883.1586495160129%40Atlassian.JIRA.
[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit
Title: Message Title Anvesh Ramaswamy created an issue Jenkins / JENKINS-61861 Jenkins Job is Triggering twice for a single Commit Issue Type: Task Assignee: Mark Waite Attachments: Screenshot 2020-04-09 at 6.53.39 PM.png Components: git-client-plugin, git-plugin Created: 2020-04-10 06:01 Priority: Blocker Reporter: Anvesh Ramaswamy Hi Team, When i am committing the changes to Master it is triggering the Jenkins Job, immediately it is triggering the same job without any changes in the code stating "Started by SCM" Add Comment
[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit
Title: Message Title Anvesh Ramaswamy updated an issue Jenkins / JENKINS-61861 Jenkins Job is Triggering twice for a single Commit Change By: Anvesh Ramaswamy Attachment: Screenshot 2020-04-09 at 6.53.39 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205725.1586498472000.8887.1586498520426%40Atlassian.JIRA.
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title Michał Kochanowicz commented on JENKINS-61853 Re: Broken links to pull requests I have downgraded "OWASP Markup Formatter" to 1.8 and see no improvement. Maybe there is something else causing this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205716.158643871.8889.1586499120116%40Atlassian.JIRA.
[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.
Title: Message Title prakash raj assigned an issue to prakash raj Jenkins / JENKINS-60801 Variable changes are shared between matrix (parallel) stages. Change By: prakash raj Assignee: prakash raj 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.204130.1579197922000.8891.1586501580179%40Atlassian.JIRA.
[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.
Title: Message Title prakash raj assigned an issue to Unassigned Jenkins / JENKINS-60801 Variable changes are shared between matrix (parallel) stages. Change By: prakash raj Assignee: prakash raj 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.204130.1579197922000.8893.1586501640125%40Atlassian.JIRA.
