[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Charles Jones commented on JENKINS-59503 Re: Plugin does not save settings orhan yılmaz Yeah that's what I've had to do for now. I want custom messages back though I tried the suggestion to change logging via the init.groovy, didn't seem to help. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202124.1569316263000.8471.1574926800312%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title orhan yılmaz commented on JENKINS-59503 Re: Plugin does not save settings Same problem here. Charles Jones workaround fixed my problem. I think plugin has a problem with Custom Message option. If you remove custom message everything works fine. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202124.1569316263000.8462.1574923920280%40Atlassian.JIRA.
[JIRA] (JENKINS-60311) contentReplace does not appear in the Snippet Generator
Title: Message Title Vlad Frost updated an issue Jenkins / JENKINS-60311 contentReplace does not appear in the Snippet Generator Change By: Vlad Frost After updating plugin from 1.0.10 to 1.2.0 it disappears from Snipped Snippet Generator and seems to have stopped working at all.I can't find any diagnostics message so just rolled back to 1.0.10.Could you please help me to identify the problem?Before update (1.0.10):!2019-11-28 09_28_50.png!After update (1.2.0):!2019-11-28 09_30_45.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203307.1574923665000.8459.1574923800207%40Atlassian.JIRA.
[JIRA] (JENKINS-60311) contentReplace does not appear in the Snippet Generator
Title: Message Title Vlad Frost created an issue Jenkins / JENKINS-60311 contentReplace does not appear in the Snippet Generator Issue Type: Bug Assignee: mo xun Attachments: 2019-11-28 09_28_50.png, 2019-11-28 09_30_45.png Components: content-replace-plugin Created: 2019-11-28 06:47 Environment: org.jenkins-ci.main:jenkins-war:2.206 org.jenkins-ci.plugins:content-replace:1.2.0 Priority: Blocker Reporter: Vlad Frost After updating plugin from 1.0.10 to 1.2.0 it disappears from Snipped Generator and seems to have stopped working at all. I can't find any diagnostics message so just rolled back to 1.0.10. Could you please help me to identify the problem? Before update (1.0.10): After update (1.2.0): Add Comment
[JIRA] (JENKINS-49317) Combination of '-daemon' and '-XX:+AlwaysPreTouch' will not let you use more than ~40% of all available memory
Title: Message Title Owen Mehegan commented on JENKINS-49317 Re: Combination of '-daemon' and '-XX:+AlwaysPreTouch' will not let you use more than ~40% of all available memory This problem can be avoided by setting -Xms to a value less than half of physical RAM. I realize that there is some performance penalty to each allocation of more RAM above the min heap size value, but once allocated the JVM will not deallocate that heap, so this might only occur a couple of times in the Jenkins service life cycle. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188180.1517514201000.8452.1574923560660%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Federico Pellegrin commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar Sure I saw you were doing 4 of them, that's what triggers the problem in the first place So the: step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']) Is correct as it will search for all of them, since the second asterisk-asterisk pattern will iterate through all of them. Of course if you prefer you can also be more explicit with: step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/NunitFast/Cobertura.xml,**/build/Tests/NUnitTestsUpdateCws/Cobertura.xml,**/build/Tests/NUnitTestsSlow/Cobertura.xml,**/build/Tests/PerformanceTests/Cobertura.xml']) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated JENKINS-59640 Jenkins / JENKINS-59640 Migrate versioncolumn plugin documentation from Wiki to GitHub Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202322.1570091047000.8446.1574916720226%40Atlassian.JIRA.
[JIRA] (JENKINS-45735) Mercurial "Clean Build" trait is available with GitHub option from SCMNavigator
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-45735 Mercurial "Clean Build" trait is available with GitHub option from SCMNavigator Change By: Mark Waite Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183936.1500729584000.8444.1574916540124%40Atlassian.JIRA.
[JIRA] (JENKINS-58325) Some pipeline stages keep running after pipeline build was aborted
Title: Message Title xiong wei commented on JENKINS-58325 Re: Some pipeline stages keep running after pipeline build was aborted Hi, I have met the same issue. My pipeline is aborted by fastfail, with be StackOverflowError, some executors are still used by the build, I have to click X button to abort it mannually. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200434.156216522.8442.1574913840175%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Pipeline git step doesn't handle commit hashes
Title: Message Title Mark Waite edited a comment on JENKINS-60267 Re: Pipeline git step doesn't handle commit hashes Commited to git client plugin 3 4 .0.1 pre-release Nov 27, 2019 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203255.1574683768000.8440.1574913600227%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long now, although most often seen on real branches (masters and releases of our project that are really providing a Jenkinsfile)Yes we do use GitHub caching, advocated for it to appear, and hope it stays :) with the poor internet uplink we have, and with github REST API quotas for uncached requests abound, and no possibility to get hooks thus requiring polling, - our farm couldn't really work without it.So I set out digging in the data, and found that cached HTTP-404s in \*.0 files correlate with very short \*.1 files (the compact error message from Github REST API), so selecting those to look deeper:{code}:; find . -name '*.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F"* ; done{code}Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file:{code}{"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"}{code}and the corresponding `hashstring.0` file looks like:{code}:; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTYGET1Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw==HTTP/1.1 404 Not Found31X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deploymentX-Accepted-OAuth-Scopes:X-GitHub-Media-Type: github.v3; format=jsonContent-Encoding: gzipTransfer-Encoding: chunkedConnection: keep-aliveContent-Type: application/octet-streamX-Cache: MISS from thunderbolt.localdomainX-Cache-Lookup: MISS from thunderbolt.localdomain:8080Via: 1.1 thunderbolt.localdomain (squid/3.4.4)Server: GitHub.comDate: Thu, 28 Nov 2019 00:41:22 GMTStatus: 304 Not ModifiedX-RateLimit-Limit: 5000X-RateLimit-Remaining: 5000X-RateLimit-Reset: 1574905280Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5"Last-Modified: Wed, 05 Dec 2018 10:54:24 GMTAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1OkHttp-Sent-Millis: 1574901681913OkHttp-Received-Millis:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long now , although most often seen on real branches (masters and releases of our project that are really providing a Jenkinsfile) Yes we do use GitHub caching, advocated for it to appear, and hope it stays :) with the poor internet uplink we have, and with github REST API quotas for uncached requests abound, and no possibility to get hooks thus requiring polling, - our farm couldn't really work without it.So I set out digging in the data, and found that cached HTTP-404s in \*.0 files correlate with very short \*.1 files (the compact error message from Github REST API), so selecting those to look deeper:{code}:; find . -name '*.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F"* ; done{code}Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file:{code}{"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"}{code}and the corresponding `hashstring.0` file looks like:{code}:; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTYGET1Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw==HTTP/1.1 404 Not Found31X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deploymentX-Accepted-OAuth-Scopes:X-GitHub-Media-Type: github.v3; format=jsonContent-Encoding: gzipTransfer-Encoding: chunkedConnection: keep-aliveContent-Type: application/octet-streamX-Cache: MISS from thunderbolt.localdomainX-Cache-Lookup: MISS from thunderbolt.localdomain:8080Via: 1.1 thunderbolt.localdomain (squid/3.4.4)Server: GitHub.comDate: Thu, 28 Nov 2019 00:41:22 GMTStatus: 304 Not ModifiedX-RateLimit-Limit: 5000X-RateLimit-Remaining: 5000X-RateLimit-Reset: 1574905280Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5"Last-Modified: Wed, 05 Dec 2018 10:54:24 GMTAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1OkHttp-Sent-Millis: 1574901681913OkHttp-Received-Millis:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long nowYes we do use GitHub caching, advocated for it to appear, and hope it stays :) with the poor internet uplink we have, and with github REST API quotas for uncached requests abound, and no possibility to get hooks thus requiring polling, - our farm couldn't really work without it. So I set out digging in the data, and found that cached HTTP-404s in \*.0 files correlate with very short \*.1 files (the compact error message from Github REST API), so selecting those to look deeper: {code} :; find . -name '*.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F"* ; done {code} Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file: {code} {"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"} {code} and the corresponding `hashstring.0` file looks like: {code} :; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTYGET1Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw==HTTP/1.1 404 Not Found31X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deploymentX-Accepted-OAuth-Scopes:X-GitHub-Media-Type: github.v3; format=jsonContent-Encoding: gzipTransfer-Encoding: chunkedConnection: keep-aliveContent-Type: application/octet-streamX-Cache: MISS from thunderbolt.localdomainX-Cache-Lookup: MISS from thunderbolt.localdomain:8080Via: 1.1 thunderbolt.localdomain (squid/3.4.4)Server: GitHub.comDate: Thu, 28 Nov 2019 00:41:22 GMTStatus: 304 Not ModifiedX-RateLimit-Limit: 5000X-RateLimit-Remaining: 5000X-RateLimit-Reset: 1574905280Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5"Last-Modified: Wed, 05 Dec 2018 10:54:24 GMTAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1OkHttp-Sent-Millis: 1574901681913OkHttp-Received-Millis:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov commented on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long now Yes we do use GitHub caching, advocated for it to appear, and hope it stays So I set out digging in the data, and found that cached HTTP-404s in *.0 files correlate with very short *.1 files (the compact error message from Github REST API), so selecting those to look deeper: :; find . -name '.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F" ; done Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file: {"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"} and the corresponding `hashstring.0` file looks like: :; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0 https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTY GET 1 Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw== HTTP/1.1 404 Not Found 31 X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deployment X-Accepted-OAuth-Scopes: X-GitHub-Media-Type: github.v3; format=json Content-Encoding: gzip Transfer-Encoding: chunked Connection: keep-alive Content-Type: application/octet-stream X-Cache: MISS from thunderbolt.localdomain X-Cache-Lookup: MISS from thunderbolt.localdomain:8080 Via: 1.1 thunderbolt.localdomain (squid/3.4.4) Server: GitHub.com Date: Thu, 28 Nov 2019 00:41:22 GMT Status: 304 Not Modified X-RateLimit-Limit: 5000 X-RateLimit-Remaining: 5000 X-RateLimit-Reset: 1574905280 Cache-Control: private, max-age=60, s-maxage=60 Vary: Accept, Authorization, Cookie, X-GitHub-OTP ETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5" Last-Modified: Wed, 05 Dec 2018 10:54:24 GMT Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type Access-Control-Allow-Origin: * Strict-Transport-Security: max-age=31536000; includeSubdomains; preload X-Frame-Options: deny X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin Content-Security-Policy: default-src 'none' X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1 OkHttp-Sent-Millis: 1574901681913 OkHttp-Received-Millis: 1574901682110 TLS_RSA_WITH_AES_128_GCM_SHA256 2
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for *NunitFast* test the location is '/build/Tests/*NunitFast*/Cobertura.xml'. For *NunitSlow* test the location is * * * '**/build/Tests/*NunitSlow*/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code above ?{code:java}step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']){code}So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8047.1574905980428%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for *NunitFast* test the location is '/build/Tests/*NunitFast*/Cobertura.xml'. For *NunitSlow* test the location is * * * '**/build/Tests/*NunitSlow*/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code above?{code:java}step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']){code}So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8051.1574905980562%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for *NunitFast* test the location is '/build/Tests/*NunitFast*/Cobertura.xml'. For *NunitSlow* test the location is * * * '**/build/Tests/*NunitSlow*/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code?{code:java}step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']){code}So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8039.1574905920326%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for *NunitFast* test the location is '/build/Tests/*NunitFast*/Cobertura.xml'. For *NunitSlow* test the location is * * * '**/build/Tests/*NunitSlow*/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code?{code:java}step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']){code}So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8041.1574905920356%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for * NunitFast * test the location is '/build/Tests/ * NunitFast * /Cobertura.xml'. For * NunitSlow * test the location is * * * '**/build/Tests/ * NunitSlow * /Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code?{code:java}step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']){code}So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8033.1574905860402%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for NunitFast test the location is ' * /build/Tests/NunitFast/Cobertura.xml'. For NunitSlow test the location is * * '**/build/Tests/NunitSlow/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code?{code:java}step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']){code}So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8031.1574905860358%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file)So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for NunitFast test the location is '* * /build/Tests/NunitFast/Cobertura.xml'. For NunitSlow test the location is * '**/build/Tests/NunitSlow/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code? {code:java} step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/ {color:#FF} ** {color} / {color:#FF} Cobertura.xml {color} ']) {code} So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8025.1574905800464%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar Federico Pellegrin Thanks for the reply. Before try the second option I have a question about your first option - (Merging all 4 different Cobertura.xml files into a one file) So here I'm using 4 Cobertura.xml files but in different 4 locations as well; such as for NunitFast test the location is '*/build/Tests/NunitFast/Cobertura.xml'. For NunitSlow test the location is '*/build/Tests/NunitSlow/Cobertura.xml' like that. If you could open the below attached my entire Jenkinsfile you will see it. So in that case how could I merge those 4 files in 4 different folder locations as per your given code? step([$class: 'CoberturaPublisher', coberturaReportFile: '**/build/Tests/**/Cobertura.xml']) So am I correct here or you may aware about that situation before ? Sorry, I couldn't tell you that before that I'm having 4 different folder locations for Cobertura.xml. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.8023.1574905800393%40Atlassian.JIRA.
[JIRA] (JENKINS-49290) Could not find com.android.tools.build:gradle:3.0.1.
Title: Message Title
leo xue edited a comment on JENKINS-49290
Re: Could not find com.android.tools.build:gradle:3.0.1.
can someone help?I got this issue for some days!Used mac to create jenkins server,now we cannot even build an android demo.here's my scriptbuildscript { repositories { { google() jcenter() mavenCentral() } dependencies { { classpath 'com.android.tools.build:gradle:3.3.2'// NOTE: Do not place your application dependencies here; they belong // in the individual module build.gradle files } } * What went wrong:A problem occurred configuring root project 'AndroidPackageTest'.> Could not resolve all artifacts for configuration ':classpath'. > Could not download builder.jar (com.android.tools.build:builder:3.3.2) > Could not get resource '[https://dl.google.com/dl/android/maven2/com/android/tools/build/builder/3.3.2/builder-3.3.2.jar]'. > SSL peer shut down incorrectly
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188148.1517389181000.8016.1574905680278%40Atlassian.JIRA.
[JIRA] (JENKINS-49290) Could not find com.android.tools.build:gradle:3.0.1.
Title: Message Title
leo xue commented on JENKINS-49290
Re: Could not find com.android.tools.build:gradle:3.0.1.
can someone help? I got this issue for some days! Used mac to create jenkins server,now we cannot even build an android demo. here's my script buildscript { repositories { google() jcenter() mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:3.3.2' // NOTE: Do not place your application dependencies here; they belong // in the individual module build.gradle files } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188148.1517389181000.8010.1574905020289%40Atlassian.JIRA.
[JIRA] (JENKINS-59776) workflow-basic-steps-plugin "waitUntil" should have a quiet mode
Title: Message Title shay bc commented on JENKINS-59776 Re: workflow-basic-steps-plugin "waitUntil" should have a quiet mode can you please accept this merge, it is pretty annoying to see a print every 0.3 seconds, we all count on the console for everything, Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202500.1571053928000.8005.1574904420232%40Atlassian.JIRA.
[JIRA] (JENKINS-60308) CompositeIOException is unhelpful for diagnostics
Title: Message Title
James Nord commented on JENKINS-60308
Re: CompositeIOException is unhelpful for diagnostics
this is highly obvious in the TestHarness code https://github.com/jenkinsci/jenkins-test-harness/blob/e72678d347373228b6d81097d792e968376a6aa1/src/main/java/org/jvnet/hudson/test/TemporaryDirectoryAllocator.java#L87-L97
/**
* Deletes all allocated temporary directories.
*/
public synchronized void dispose() throws IOException, InterruptedException {
IOException x = null;
for (File dir : tmpDirectories)
try {
new FilePath(dir).deleteRecursive();
} catch (IOException e) {
x = e;
}
tmpDirectories.clear();
if (x!=null)throw new IOException("Failed to clean up temp dirs",x);
}
the IoException causes the actual cause to be lost (and only the most recent one is throw,) this specific case can be fixed by actually throwing a CompositeIOException - but we can not control all the code that catches and handles exceptions.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title
Jorge Cordoba edited a comment on JENKINS-60307
Re: CreateItem with rest api impossible with some character
[~yatho], it seems you are not escaping the & in your XML body.For XML files the ilegal characters are {{&}}, {{<}} and {{>}} (as well as {{"}} or {{'}} in attributes).Writing "& + amp;" (without the + sign) instead of "&" should have no problems. As far as I can tell this is not a Jenkins issue, but an issue in the side of the one who sends the xml file.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.7999.1574899920156%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title
Jorge Cordoba edited a comment on JENKINS-60307
Re: CreateItem with rest api impossible with some character
[~yatho], it seems you are not escaping the & in your XML body.For XML files the ilegal characters are {{&}}, {{<}} and {{>}} (as well as {{"}} or {{'}} in attributes).Writing "" instead of "&" should have no problems.As far as I can tell this is not a Jenkins issue, but an issue in the side of the one who sends the xml file.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.7995.1574899810163%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Jorge Cordoba commented on JENKINS-60307 Re: CreateItem with rest api impossible with some character Yann-Thomas Le Moigne, it seems you are not escaping the & in your XML body. For XML files the ilegal characters are &, < and > (as well as " or ' in attributes). Writing "&" instead of "&" should have no problems. As far as I can tell this is not a Jenkins issue, but an issue in the side of the one who sends the xml file. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.7993.1574899740181%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Jorge Cordoba started work on JENKINS-60307 Change By: Jorge Cordoba Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.7989.1574898660369%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class with old Java 8
Title: Message Title Mark Waite updated JENKINS-60203 Jenkins / JENKINS-60203 Git client plugin 3.0 fails to load trilead class with old Java 8 Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.7987.1574898660336%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Jorge Cordoba assigned an issue to Jorge Cordoba Jenkins / JENKINS-60307 CreateItem with rest api impossible with some character Change By: Jorge Cordoba Assignee: Jorge Cordoba Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.7991.1574898660395%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class with old Java 8
Title: Message Title Mark Waite started work on JENKINS-60203 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.7983.1574898600337%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class with old Java 8
Title: Message Title Mark Waite updated JENKINS-60203 Cannot duplicate, no response from submitter Jenkins / JENKINS-60203 Git client plugin 3.0 fails to load trilead class with old Java 8 Change By: Mark Waite Status: In Progress Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this
[JIRA] (JENKINS-60267) Pipeline git step doesn't handle commit hashes
Title: Message Title Mark Waite updated JENKINS-60267 Commited to git client plugin 3.0.1 pre-release Nov 27, 2019 Jenkins / JENKINS-60267 Pipeline git step doesn't handle commit hashes Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Jorge Cordoba commented on JENKINS-60307 Re: CreateItem with rest api impossible with some character I would like to try and fix this if no one is working in it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.7979.1574898120219%40Atlassian.JIRA.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194261.1537815457000.7977.1574896980209%40Atlassian.JIRA.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title Mark Waite resolved as Won't Fix Won't attempt to make the git plugin consistent with Subversion plugin because it risks breaking too many existing users. Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-34309 git-client-plugin: StringIndexOutOfBoundsException when parsing branches Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169863.1460974434000.7971.1574896800816%40Atlassian.JIRA.
[JIRA] (JENKINS-60090) Job builds tags even though there is no change in Bitbucket
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-60090 Job builds tags even though there is no change in Bitbucket Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202935.1573143966000.7973.1574896800852%40Atlassian.JIRA.
[JIRA] (JENKINS-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-38179 Authentication Error with GIT Client version 2.0.0 Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174340.1473802585000.7958.1574896740887%40Atlassian.JIRA.
[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!
Title: Message Title John McCullough commented on JENKINS-55996 Re: jacoco: Error while reading the sourcefile! I think that you are correct that it is unrelated. In fact when I attempted to reproduce the errors that I previously encountered, they are no longer occurring. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197412.1549469008000.7952.1574896740735%40Atlassian.JIRA.
[JIRA] (JENKINS-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Mark Waite closed an issue as Fixed
Jenkins / JENKINS-37391
Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Change By:
Mark Waite
Status:
Resolved Closed
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173488.1471099744000.7956.1574896740841%40Atlassian.JIRA.
[JIRA] (JENKINS-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-37899 Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174041.1472741835000.7947.1574896680344%40Atlassian.JIRA.
[JIRA] (JENKINS-43198) JGit Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Mark Waite closed an issue as Fixed Fixed in git client plugin 3.0.0 Jenkins / JENKINS-43198 JGit Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180319.1490810443000.7943.1574896620515%40Atlassian.JIRA.
[JIRA] (JENKINS-39780) Git clone timesout
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-39780 Git clone timesout Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176369.1479312775000.7945.1574896620601%40Atlassian.JIRA.
[JIRA] (JENKINS-53279) java.lang.NoClassDefFoundError: javax/servlet/ServletException
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-53279 java.lang.NoClassDefFoundError: javax/servlet/ServletException Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193355.1535451904000.7935.1574896560621%40Atlassian.JIRA.
[JIRA] (JENKINS-36092) Pipeline Syntax Generator throws 500 on merge before build
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-36092 Pipeline Syntax Generator throws 500 on merge before build Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172054.146644828.7933.1574896560593%40Atlassian.JIRA.
[JIRA] (JENKINS-46683) Multibranch pipeline failing at Checkout SCM step (unable to resolve tag)
Title: Message Title Mark Waite closed an issue as Incomplete Jenkins / JENKINS-46683 Multibranch pipeline failing at Checkout SCM step (unable to resolve tag) Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185023.1504704585000.7937.1574896560646%40Atlassian.JIRA.
[JIRA] (JENKINS-49111) fatal: ssh variant 'simple' does not support setting port
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-49111 fatal: ssh variant 'simple' does not support setting port Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187946.1516723922000.7929.1574896500525%40Atlassian.JIRA.
[JIRA] (JENKINS-46344) During git checkout, jgit core crashes on a stackoverflow on an infinite openPackedFromSelfOrAlternate loop.
Title: Message Title Mark Waite closed an issue as Fixed Fixed in git client plugin 3.0.0 Jenkins / JENKINS-46344 During git checkout, jgit core crashes on a stackoverflow on an infinite openPackedFromSelfOrAlternate loop. Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184607.1503405489000.7927.1574896500484%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Pipeline git step doesn't handle commit hashes
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60267 Pipeline git step doesn't handle commit hashes Change By: Mark Waite Summary: Shorthand Pipeline git step doesn't handle commit hashes Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203255.1574683768000.7925.1574896260162%40Atlassian.JIRA.
[JIRA] (JENKINS-42679) Allow lock retrieval based on requested priority
Title: Message Title
William Brode commented on JENKINS-42679
Re: Allow lock retrieval based on requested priority
Tobias Gruetzmacher thanks for all your great work! Would definitely be interested in this feature. Not sure if people are handling this another way but we use the lock(inversePrecedence: true) { milestone() } paradigm to "roll up" builds when multiple builds are ready to enter that stage of the pipeline. There is an issue with this: If change 1 starts, then change 2, but change 2 goes faster and gets to the lock first, it would abort change 2 and build change 1 (since change 1 called the lock step last). So at least for SCMs with increasing numeric change numbers, it would be preferable to use the change number as the priority - to ensure we always let the newest change get the lock.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179631.1489173063000.7923.1574895000519%40Atlassian.JIRA.
[JIRA] (JENKINS-46553) Maven surefire timeout treated as successful build
Title: Message Title Falko Modler commented on JENKINS-46553 Re: Maven surefire timeout treated as successful build What we would need is another Maven Surefire property/feature, that differentiates between regular test failures and timeouts. I've just created a ticket for that: https://issues.apache.org/jira/browse/SUREFIRE-1728 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184875.1504135901000.7916.1574893980197%40Atlassian.JIRA.
[JIRA] (JENKINS-60310) Content replace should be able to modify multiple files
Title: Message Title Mikhail T created an issue Jenkins / JENKINS-60310 Content replace should be able to modify multiple files Issue Type: Improvement Assignee: mo xun Components: content-replace-plugin Created: 2019-11-27 21:55 Priority: Minor Reporter: Mikhail T It is quite common, that the same replacements need to apply to multiple files. This can get tedious very quickly as one has to create a separate build step for each file. Unfortunately, trying to give the plugin a template does not work: **/*.vcxproj file not found Build step 'Content Replace' changed build result to FAILURE Build step 'Content Replace' marked build as failure Allowing it would be a great improvement. Add Comment
[JIRA] (JENKINS-60145) Show full sidebar link name on hover
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60145 Show full sidebar link name on hover Change By: Mark Waite This issue reflects the discussion on the comments for [ JENKINS- 59508https://issues.jenkins-ci.org/browse/JENKINS- 59508 ] . When the sidebar link names are too long, they are cropped as seen picture attached.!sidebar-cropped-link.png|thumbnail! The proposal is to show a tooltip when hovering over the image, using the HTML _title_ attribute: !sidebarlink-tooltip-example.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203008.1573579369000.7911.1574886720355%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten updated an issue Jenkins / JENKINS-60309 NPE when using with gitlab-plugin's statuses. Change By: ipleten Component/s: gitlab-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.7909.1574886360223%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten commented on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. Looks like NPE goes from gitlan-plugin in https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/util/CommitStatusUpdater.java#L185 It expect class to be an instance of "AbstractGitSCMSource.SCMRevisionImpl" but for MergeRequest it's a "ChangeRequestSCMRevision" in https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/master/src/main/java/io/jenkins/plugins/gitlabbranchsource/MergeRequestSCMRevision.java#L8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.7907.1574886360198%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor assigned an issue to Alex Taylor Jenkins / JENKINS-57430 Getting issue when using github Change By: Alex Taylor Assignee: Liam Newman Alex Taylor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.7896.1574885880819%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor updated JENKINS-57430 Jenkins / JENKINS-57430 Getting issue when using github Change By: Alex Taylor Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.7903.1574885881000%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor commented on JENKINS-57430 Re: Getting issue when using github This should be fixed by https://github.com/github-api/github-api/pull/622 for at least the CHECK_RUN event so it will stop this particular bug. There are many other unchecked events though that need to be added. That is a whole other problem Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.7892.1574885880712%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor started work on JENKINS-57430 Change By: Alex Taylor Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.7901.1574885880948%40Atlassian.JIRA.
[JIRA] (JENKINS-54538) Ability to save unmasked credentials to file
Title: Message Title Tomasz Fijarczyk closed an issue as Not A Defect Jenkins / JENKINS-54538 Ability to save unmasked credentials to file Change By: Tomasz Fijarczyk Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195310.1541675184000.7887.1574884800340%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title
Mark Waite edited a comment on JENKINS-60297
Re: Jenkins could not read from remote repository
The message from command line git is:{ { noformat} fatal: '///////.git' does not appear to be a git repository {noformat } } If you're accessing the remote git repository through https or ssh, that might indicate that the remote git repository is temporarily inaccessible on that remote server has some issue with its file system. In my case, I can generate that message when I use a a valid ssh private key credential to clone a repository which does not exist on a remote server which I host myself. My example looks like this:{noformat}mwaite@mark-pc2:~/git/jenkins/git-plugin$ git clone mwa...@git.markwaite.net:git/bare/jenkins/not-really-a-repository.gitCloning into 'not-really-a-repository'...fatal: 'git/bare/jenkins/not-really-a-repository.git' does not appear to be a git repositoryfatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}However, when I attempt to use a valid ssh private key to clone a non-existent repository from github.com, I don't see that exact message. I see:{noformat}mwaite@mark-pc2:~/git/jenkins/git-plugin$ git clone g...@github.com:MarkEWaite/not-really-a-repository.gitCloning into 'not-really-a-repository'...ERROR: Repository not found.fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}Based on that, I would guess that you're cloning a repository from a server that you're hosting. That internal server is temporarily unable to detect the repository, especially during times of high load (concurrent clones). You could test that theory by running multiple {{git clone}} commands on different machines at the same time.If you're accessing the remote git repository through file system access (for example through an NFS mount or a CIFS mount), that message might indicate that command line git was unable to read the directory it needed. It might also mean that it was unable to find a specific file or to acquire a lock on a specific file. If you're accessing a git repository through a remote file access protocol, you should reconsider that choice and use the remote protocols that are included with command line git (http/https and ssh).
Add Comment
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title
Mark Waite edited a comment on JENKINS-60297
Re: Jenkins could not read from remote repository
The message from command line git is:{noformat}fatal: '///////.git' does not appear to be a git repository{noformat}If you're accessing the remote git repository through https or ssh, that might indicate that the remote git repository is temporarily inaccessible on or that remote server has some issue with its file system. In my case, I can generate that message when I use a a valid ssh private key credential to clone a repository which does not exist on a remote server which I host myself. My example looks like this:{noformat}mwaite@mark-pc2:~/git/jenkins/git-plugin$ git clone mwa...@git.markwaite.net:git/bare/jenkins/not-really-a-repository.gitCloning into 'not-really-a-repository'...fatal: 'git/bare/jenkins/not-really-a-repository.git' does not appear to be a git repositoryfatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}However, when I attempt to use a valid ssh private key to clone a non-existent repository from github.com, I don't see that exact message. I see:{noformat}mwaite@mark-pc2:~/git/jenkins/git-plugin$ git clone g...@github.com:MarkEWaite/not-really-a-repository.gitCloning into 'not-really-a-repository'...ERROR: Repository not found.fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}Based on that, I would guess that you're cloning a repository from a server that you're hosting. That internal server is temporarily unable to detect the repository, especially during times of high load (concurrent clones). You could test that theory by running multiple {{git clone}} commands on different machines at the same time.If you're accessing the remote git repository through file system access (for example through an NFS mount or a CIFS mount), that message might indicate that command line git was unable to read the directory it needed. It might also mean that it was unable to find a specific file or to acquire a lock on a specific file. If you're accessing a git repository through a remote file access protocol, you should reconsider that choice and use the remote protocols that are included with command line git (http/https and ssh).
Add Comment
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Mark Waite updated JENKINS-60297 Jenkins / JENKINS-60297 Jenkins could not read from remote repository Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.7881.1574884740534%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60297 Jenkins could not read from remote repository Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.7879.1574884740509%40Atlassian.JIRA.
[JIRA] (JENKINS-54538) Ability to save unmasked credentials to file
Title: Message Title Tomasz Fijarczyk commented on JENKINS-54538 Re: Ability to save unmasked credentials to file Make sens, can't believe I missed the obvious Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195310.1541675184000.7882.1574884740546%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title
Mark Waite commented on JENKINS-60297
Re: Jenkins could not read from remote repository
The message from command line git is: {{ fatal: '///////.git' does not appear to be a git repository}} If you're accessing the remote git repository through https or ssh, that might indicate that the remote git repository is temporarily inaccessible on that remote server has some issue with its file system. In my case, I can generate that message when I use a a valid ssh private key credential to clone a repository which does not exist on a remote server which I host myself. My example looks like this:
mwaite@mark-pc2:~/git/jenkins/git-plugin$ git clone mwa...@git.markwaite.net:git/bare/jenkins/not-really-a-repository.git
Cloning into 'not-really-a-repository'...
fatal: 'git/bare/jenkins/not-really-a-repository.git' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
However, when I attempt to use a valid ssh private key to clone a non-existent repository from github.com, I don't see that exact message. I see:
mwaite@mark-pc2:~/git/jenkins/git-plugin$ git clone g...@github.com:MarkEWaite/not-really-a-repository.git
Cloning into 'not-really-a-repository'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Based on that, I would guess that you're cloning a repository from a server that you're hosting. That internal server is temporarily unable to detect the repository, especially during times of high load (concurrent clones). You could test that theory by running multiple git clone commands on different machines at the same time. If you're accessing the remote git repository through file system access (for example through an NFS mount or a CIFS mount), that message might indicate that command line git was unable to read the directory it needed. It might also mean that it was unable to find a specific file or to acquire a lock on a specific file. If you're accessing a git repository through a remote file access protocol, you should reconsider that choice and use the remote protocols that are included with command line git (http/https and ssh).
[JIRA] (JENKINS-20073) Add an action to allow moving credentials between credential domains
Title: Message Title Kalle Niemitalo commented on JENKINS-20073 Re: Add an action to allow moving credentials between credential domains AFAICT, this is already works; if you have multiple credential domains in the same credential store, then the UI lets you move a credential from one domain to another. Is there any reason why this issue should not be closed? However, it is not yet possible to move credentials from one project or folder to another. That feature request been filed separately as JENKINS-20075. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151593.1381922552000.7872.1574882580294%40Atlassian.JIRA.
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-59331
Re: withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Credentials Binding Plugin has done this ever since the certificate binding feature was added in [commit 7d789a8c590fd87cb9dd61c89c894a5df26a0605|https://github.com/jenkinsci/credentials-binding-plugin/commit/7d789a8c590fd87cb9dd61c89c894a5df26a0605] and merged in [PR#39|https://github.com/jenkinsci/credentials-binding-plugin/pull/39]. The commit message even mentions the assumption that the credential description matches the keystore alias name, but I don't think I have seen it documented anywhere else. When I edit the description of a certificate credential, the help text "An optional description to help tell similar credentials apart" certainly gives no hint of any such requirement.CertificateMultiBinding already calls {{credentials.getKeyStore()}}, so perhaps it could just enumerate the returned KeyStore and get the alias name from there, without needing changes in the Credentials Plugin. If the {{aliasVariable}} parameter is specified but the KeyStore actually contains more than one key, then CertificateMultiBinding could log a warning about that. If each certificate credential normally contains only one certificate and private key, then the keystore alias name is not really needed for selecting the correct certificate, and I think users are likely to choose short words like "cert" as keystore alias names. If the {{withCredentials}} step is then changed to store these to the {{aliasVariable}}, there may be a risk that Jenkins starts unnecessarily masking this word in unrelated output. Perhaps the keystore alias name should be exempt from this masking.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: "Null pointer exception" and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.Logs snapshot:{noformat}ov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener onCheckoutINFO: SCMListener: Checkoutsoftserve Checkoutsoftware » pipe-test-build -ipleten » MR-64-merge #5Nov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: Result: nullNov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: COMMIT: 2d46589fed77023cc5a4ac38422873408e5ce1cborg.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run") at org.gitlab4j.api.AbstractApi.validate(AbstractApi.java:593) at org.gitlab4j.api.AbstractApi.post(AbstractApi.java:264) at org.gitlab4j.api.CommitsApi.addCommitStatus(CommitsApi.java:452) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.sendNotifications(GitLabPipelineStatusNotifier.java:249) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.access$300(GitLabPipelineStatusNotifier.java:51) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener.onCheckout(GitLabPipelineStatusNotifier.java:373) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:140) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.lambda$doRetrieve$1(SCMSourceRetriever.java:154) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrySCMOperation(SCMSourceRetriever.java:104) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:153) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:93) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: "Null pointer exception" and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working. Logs snapshot:{noformat}ov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener onCheckoutINFO: SCMListener: Checkoutsoftserve » pipe-test-build-ipleten » MR-64-merge #5Nov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: Result: nullNov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: COMMIT: 2d46589fed77023cc5a4ac38422873408e5ce1cborg.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run") at org.gitlab4j.api.AbstractApi.validate(AbstractApi.java:593) at org.gitlab4j.api.AbstractApi.post(AbstractApi.java:264) at org.gitlab4j.api.CommitsApi.addCommitStatus(CommitsApi.java:452) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.sendNotifications(GitLabPipelineStatusNotifier.java:249) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.access$300(GitLabPipelineStatusNotifier.java:51) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener.onCheckout(GitLabPipelineStatusNotifier.java:373) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:140) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.lambda$doRetrieve$1(SCMSourceRetriever.java:154) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrySCMOperation(SCMSourceRetriever.java:104) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:153) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:93) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-59331
Re: withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Credentials Binding Plugin has done this ever since the certificate binding feature was added in [commit 7d789a8c590fd87cb9dd61c89c894a5df26a0605|https://github.com/jenkinsci/credentials-binding-plugin/commit/7d789a8c590fd87cb9dd61c89c894a5df26a0605] and merged in [PR#39|https://github.com/jenkinsci/credentials-binding-plugin/pull/39]. The commit message even mentions the assumption that the credential description matches the keystore alias name, but I don't think I have seen it documented anywhere else. When I edit the description of a certificate credential, the help text "An optional description to help tell similar credentials apart" certainly gives no hint of any such requirement.CertificateMultiBinding already calls {{credentials.getKeyStore()}}, so perhaps it could just enumerate the returned KeyStore and get the alias name from there, without needing changes in the Credentials Plugin. If the {{aliasVariable}} parameter is specified but the KeyStore actually contains more than one key, then CertificateMultiBinding could log a warning about that.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title Kalle Niemitalo commented on JENKINS-59331 Re: withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name Credentials Binding Plugin has done this ever since the certificate binding feature was added commit 7d789a8c590fd87cb9dd61c89c894a5df26a0605 and merged in PR#39. The commit message even mentions the assumption that the credential description matches the keystore alias name, but I don't think I have seen it documented anywhere else. When I edit the description of a certificate credential, the help text "An optional description to help tell similar credentials apart" certainly gives no hint of any such requirement. CertificateMultiBinding already calls credentials.getKeyStore(), so perhaps it could just enumerate the returned KeyStore and get the alias name from there, without needing changes in the Credentials Plugin. If the aliasVariable parameter is specified but the KeyStore actually contains more than one key, then CertificateMultiBinding could log a warning about that. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201882.1568291887000.7859.1574880720140%40Atlassian.JIRA.
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title Kalle Niemitalo updated an issue Jenkins / JENKINS-59331 withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name Change By: Kalle Niemitalo Summary: Empty 'Alias Variable' when using withCredentials certificate binding (aliasVariable: ) stores description of credential, not keystore alias name Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201882.1568291887000.7856.1574879940251%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: " Null pointer exception " and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten created an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Issue Type:
Bug
Assignee:
Parichay Barpanda
Components:
gitlab-branch-source-plugin
Created:
2019-11-27 18:26
Priority:
Minor
Reporter:
ipleten
We are using gitlab-plugin and evaluating gitlab-branch-source-plugin for our need. Pipeline is failing with: Null pointer exception and prior that failure in Jenkins maser log:
...
org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")
...
in pipeline we have something like that:
..
steps {
gitlabCommitStatus(STAGE_NAME) {
container('deploy') {
sh 'mvn deploy'
}
When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.
[JIRA] (JENKINS-60308) CompositeIoException is unhelpful for diagnostics
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-60308
CompositeIoException is unhelpful for diagnostics
Change By:
James Nord
The causes of a CompositeIoException are lost when the exception is rethrown as part of a chain, (ie it is a cause in another Throwable). This is because Throwable.printStackTrace() does not call printStackTrace on its causes but rather printEnclosedStackTrace to handle circular references and prevent a thread loop. This is exceptionally painful when upgrading to 2.204 for the most recent LTS as something in that chain causes tests to fail if the temporary JenkinsHome of a JenkinsRule Test can not be cleans.it results in failures like: {noformat}[2019-11-27T17:04:38.004Z] [ERROR] com.cloudbees.Blah.someTest Time elapsed: 7.157 s <<< ERROR![2019-11-27T17:04:38.004Z] java.io.IOException: Failed to clean up temp dirs[2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:96)[2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:84)[2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.JenkinsRule.after(JenkinsRule.java:511)[2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:614)[2019-11-27T17:04:38.004Z] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)[2019-11-27T17:04:38.004Z] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)[2019-11-27T17:04:38.004Z] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[2019-11-27T17:04:38.004Z] at java.lang.Thread.run(Thread.java:748)[2019-11-27T17:04:38.004Z] Caused by: jenkins.util.io.CompositeIOException: Unable to delete 'C:\e4909a8e\workspace\operations-center-context_PR-382\target\tmp\j h2709724025285257367'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.[2019-11-27T17:04:38.004Z] at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99)[2019-11-27T17:04:38.004Z] at hudson.Util.deleteRecursive(Util.java:293)[2019-11-27T17:04:38.004Z] at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1271)[2019-11-27T17:04:38.004Z] at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1267)[2019-11-27T17:04:38.004Z] at hudson.FilePath.act(FilePath.java:1075)[2019-11-27T17:04:38.004Z] at hudson.FilePath.act(FilePath.java:1058)[2019-11-27T17:04:38.004Z] at hudson.FilePath.deleteRecursive(FilePath.java:1265)[2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:91)[2019-11-27T17:04:38.004Z] ... 7 more{noformat} This is exceptionally painful on windows where you can not delete a directory if the same process has files open in it, and when the failure is on a CI system and the developers all have Linux/Mac then it becomes even harder. without knowing which file(s) could not be deleted you are effectively fishing. You can inspect the exception if you
[JIRA] (JENKINS-60308) CompositeIOException is unhelpful for diagnostics
Title: Message Title James Nord updated an issue Jenkins / JENKINS-60308 CompositeIOException is unhelpful for diagnostics Change By: James Nord Summary: CompositeIoException CompositeIOException is unhelpful for diagnostics Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203303.1574876686000.7850.1574876880273%40Atlassian.JIRA.
[JIRA] (JENKINS-60308) CompositeIoException is unhelpful for diagnostics
Title: Message Title James Nord created an issue Jenkins / JENKINS-60308 CompositeIoException is unhelpful for diagnostics Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-11-27 17:44 Priority: Major Reporter: James Nord The causes of a CompositeIoException are lost when the exception is rethrown as part of a chain, (ie it is a cause in another Throwable). This is because Throwable.printStackTrace() does not call printStackTrace on its causes but rather printEnclosedStackTrace to handle circular references and prevent a thread loop. This is exceptionally painful when upgrading to 2.204 for the most recent LTS as something in that chain causes tests to fail if the temporary JenkinsHome of a JenkinsRule Test can not be cleans. it results in failures like: [2019-11-27T17:04:38.004Z] [ERROR] com.cloudbees.Blah.someTest Time elapsed: 7.157 s <<< ERROR! [2019-11-27T17:04:38.004Z] java.io.IOException: Failed to clean up temp dirs [2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:96) [2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:84) [2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.JenkinsRule.after(JenkinsRule.java:511) [2019-11-27T17:04:38.004Z] at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:614) [2019-11-27T17:04:38.004Z] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) [2019-11-27T17:04:38.004Z] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) [2019-11-27T17:04:38.004Z] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [2019-11-27T17:04:38.004Z] at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-60169) Multi-line build log indication of Build Failure Analyzer plugin is not matching text
Title: Message Title David Simmons commented on JENKINS-60169 Re: Multi-line build log indication of Build Failure Analyzer plugin is not matching text I am experiencing the same thing. No matter how liberal the regex, my match is always a single line from the build log. It's as if the multiline switch doesn't do anything at all. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203123.157373099.7846.1574875500338%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Yann-Thomas Le Moigne created an issue Jenkins / JENKINS-60307 CreateItem with rest api impossible with some character Issue Type: Bug Assignee: Unassigned Attachments: resultCreateItemWithSpecialCharacter.PNG Components: core Created: 2019-11-27 17:21 Labels: api createItem Priority: Minor Reporter: Yann-Thomas Le Moigne When I would create a new job with the xml rest api route, and a description with special character as &, then jenkins server answer a 500 internal server error to my postman. If the description value contains any special character, then it's working correctly. My url : /createItem?name=yatho-test Header : content-type : application/xml Basic authent for the credentials Body : '1.1' encoding='UTF-8'?> "workflow-multibranch@2.21"> I am testing & and é and á ... "pipeline-maven@3.8.1"> "jenkins.mvn.DefaultSettingsProvider"/> "jenkins.mvn.DefaultGlobalSettingsProvider"/> false "pipeline-model-definition@1.3.9"> "docker-commons@1.15"/> "jenkins.branch.MultiBranchProjectViewHolder" plugin="branch-api@2.5.4"> "org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/> "cloudbees-folder@6.9"> false "jenkins.branch.MetadataActionFolderIcon" plugin="branch-api@2.5.4"> "org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
[JIRA] (JENKINS-60145) Show full sidebar link name on hover
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-60145 Show full sidebar link name on hover Change By: Baptiste Mathus Released As: (towards) 2.205 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203008.1573579369000.7836.1574873521042%40Atlassian.JIRA.
[JIRA] (JENKINS-59331) Empty 'Alias Variable' when using certificate binding
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-59331
Re: Empty 'Alias Variable' when using certificate binding
I see a similar result with Jenkins ver. 2.190.3, Credentials Binding Plugin 1.20, and Credentials Plugin 2.3.0. I defined a step like this in a declarative pipeline Jenkinsfile:{code}withCredentials([certificate(credentialsId: 'APK-signing',keystoreVariable: 'AndroidSigningKeyStore',passwordVariable: 'AndroidSigningStorePass',aliasVariable: 'AndroidSigningKeyAlias')]) {writeFile encoding: 'UTF-8', file: 'AndroidSigningKeyAlias.txt', text: env.AndroidSigningKeyAlias// actual signing not shown}{code}and, what was written to AndroidSigningKeyAlias.txt was not the "keystore alias name" documented in [https://jenkins.io/doc/pipeline/steps/credentials-binding/], but instead the description of the credential. The keystore alias name was actually the same as in the PKCS#12 file from which I had imported the credential to Jenkins. [CertificateMultiBinding#bind|https://github.com/jenkinsci/credentials-binding-plugin/blob/dfb2c2d560dbb52a771d16e9490a6455d3174388/src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/CertificateMultiBinding.java#L79-L80]:{code:java} if(aliasVariable!=null && !aliasVariable.isEmpty()) m.put(aliasVariable, credentials.getDescription());{code} I guess the original reporter had not added a description to the credential, and the alias variable was thus left empty.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-59331) Empty 'Alias Variable' when using certificate binding
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-59331
Re: Empty 'Alias Variable' when using certificate binding
I see a similar result with Jenkins ver. 2.190.3 and , Credentials Binding Plugin 1.20 , and Credentials Plugin 2 . 3.0. I defined a step like this in a declarative pipeline Jenkinsfile: {code :groovy }withCredentials([certificate(credentialsId: 'APK-signing',keystoreVariable: 'AndroidSigningKeyStore',passwordVariable: 'AndroidSigningStorePass',aliasVariable: 'AndroidSigningKeyAlias')]) {writeFile encoding: 'UTF-8', file: 'AndroidSigningKeyAlias.txt', text: env.AndroidSigningKeyAlias// actual signing not shown}{code} and, what was written to AndroidSigningKeyAlias.txt was not the "keystore alias name" documented in [https://jenkins.io/doc/pipeline/steps/credentials-binding/], but instead the description of the credential. The keystore alias name was actually the same as in the PKCS#12 file from which I had imported the credential to Jenkins.I guess the original reporter had not added a description to the credential, and the alias variable was thus left empty.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201882.1568291887000.7839.1574873521122%40Atlassian.JIRA.
[JIRA] (JENKINS-60306) LDAP login user needs read permissions
Title: Message Title Roberto Galicia created an issue Jenkins / JENKINS-60306 LDAP login user needs read permissions Issue Type: Bug Assignee: Unassigned Components: ldap-plugin Created: 2019-11-27 16:47 Environment: Red Hat Enterprise Linux Server 7.6 Jenkins 2.204 LDAP Plugin 1.21 Labels: jenkins plugin ldap Priority: Major Reporter: Roberto Galicia In our LDAP server the anonymus access is not allowed, so we need to authenticate with Manager DN and then search the login user attributes. When we "Test LDAP settings" we can see how the Lookup is successful: Lookup User lookup: successful User ID: username User Dn: CN=username,OU=people,OU=Collaborators,OU=Users,O=domain User Display Name: username LDAP Group membership: GLOBAL_GROUP LDAP Group lookup: successful (1 group) But the login failed: Login Authentication: failed for user "username" Lockout The user "username" will be unable to login with the supplied password. If this is your own account this would mean you would be locked out! Are you sure you want to save this configuration?
[JIRA] (JENKINS-59331) Empty 'Alias Variable' when using certificate binding
Title: Message Title
Kalle Niemitalo commented on JENKINS-59331
Re: Empty 'Alias Variable' when using certificate binding
I see a similar result with Jenkins ver. 2.190.3 and Credentials Binding Plugin 1.20. I defined a step like this in a declarative pipeline Jenkinsfile:
withCredentials([certificate(
credentialsId: 'APK-signing',
keystoreVariable: 'AndroidSigningKeyStore',
passwordVariable: 'AndroidSigningStorePass',
aliasVariable: 'AndroidSigningKeyAlias')]) {
writeFile encoding: 'UTF-8', file: 'AndroidSigningKeyAlias.txt', text: env.AndroidSigningKeyAlias
// actual signing not shown
}
and, what was written to AndroidSigningKeyAlias.txt was not the "keystore alias name" documented in https://jenkins.io/doc/pipeline/steps/credentials-binding/, but instead the description of the credential. The keystore alias name was actually the same as in the PKCS#12 file from which I had imported the credential to Jenkins. I guess the original reporter had not added a description to the credential, and the alias variable was thus left empty.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59966) Prometheus Plugin: Causes StackOverFlowerError
Title: Message Title Damien Coraboeuf commented on JENKINS-59966 Re: Prometheus Plugin: Causes StackOverFlowerError We have the same issue in my company: Jenkins LTS 2.190.1 Prometheus plugin 2.0.6 Stacktrace overflow as mentioned above. However, we do have a second Jenkins instance, with same version, and no issue there. So this must be somehow linked to some kind of setup. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202770.1572283306000.7829.1574872440348%40Atlassian.JIRA.
[JIRA] (JENKINS-54538) Ability to save unmasked credentials to file
Title: Message Title Kalle Niemitalo commented on JENKINS-54538 Re: Ability to save unmasked credentials to file https://jenkins.io/doc/pipeline/steps/credentials-binding/ says this is by design: "The masking could of course be trivially circumvented; anyone permitted to configure a job or define Pipeline steps is assumed to be trusted to use any credentials in scope however they like." Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195310.1541675184000.7826.1574872320123%40Atlassian.JIRA.
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Jenkins client in Keycloak using the ["Keycloak config" here . |https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " _ is missing the Overall/Read permission_ permission ".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. http:///whoAmI/ doesn't show any group memberships, but not sure if it should. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Daniel Beck commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy Yes, with Authorize Project/Matrix Auth. Something like https://plugins.jenkins.io/job-restrictions probably does that though. If you need further assistance, I recommend you ask on the Jenkins Users mailing list. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7819.1574869860518%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title
Ian Katz updated an issue
Jenkins / JENKINS-60305
Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Change By:
Ian Katz
I'm trying to connect Jenkins to my company's cloud-hosted Jira (e.g. [https://MYCOMPANY.atlassian.net/).|https://mycompany.atlassian.net/).] My account there is set up with google, so based on [JIRA Rest API authentication always returns 401 unauthorized|#M317050] I took the step of creating an API token from [https://id.atlassian.com/manage/api-tokens] Using this, I am able to successfully curl my Jira site:{quote} { { code} $ curl -D- -u "m...@mycompany.com:aUthT0K3n" -X GET -H "Content-Type: application/json" [ https://MYCOMPANY.atlassian.net/rest/api/2/issue/TST-123 |https://mycompany.atlassian.net/rest/api/2/issue/TST-123] {code } } HTTP/2 200[...snip...]{color:#172b4d} {color}{quote}Adding these credentials to Jenkins credentials manager was no problem. I specify them for the Jira plugin configuration too. But when I click "Validate Settings", I receive the following error:{quote}Failed to login to JIRA{quote}I can confirm that the proper credentials are being accessed, because when I visit [https://id.atlassian.com/manage/api-tokens] it says that the API token was used "A few seconds ago". I see this in my Jenkins logs:{quote}Failed to login to JIRA at [https://MYCOMPANY.atlassian.net/|https://mycompany.atlassian.net/] RestClientException{{ \ {statusCode=Optional.of(400), errorCollections=[ErrorCollection \ {status=400, errors={}, errorMessages=[The 'permissions' query parameter is required.]}]}}}{quote}I suspect that this is related to this deprecation warning:[https://community.developer.atlassian.com/t/announcement-changes-to-rest-api-2-mypermissions-get-my-permissions/21245]{quote}Previously, the resource would return all permissions defined on the Jira instance, now the list is limited to the keys provided in the {{permissions}} query parameter._Not_ sending the parameter is deprecated, and we are planning to start rejecting such requests starting from 1 February 2019.You can find more details here: [Change notice - Get my permissions resource now requires the permissions query parameter|https://developer.atlassian.com/cloud/jira/platform/change-notice-get-my-permissions-requires-permissions-query-parameter/] {quote} Is there something obvious that I'm missing or is this a bug in the plugin?
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title
Ian Katz updated an issue
Jenkins / JENKINS-60305
Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Change By:
Ian Katz
I'm trying to connect Jenkins to my company's cloud-hosted Jira (e.g. [https://MYCOMPANY.atlassian.net/).|https://mycompany.atlassian.net/).] My account there is set up with google, so based on [JIRA Rest API authentication always returns 401 unauthorized|#M317050] I took the step of creating an API token from [https://id.atlassian.com/manage/api-tokens] Using this, I am able to successfully curl my Jira site:{quote} {{ $ curl -D- -u "m...@mycompany.com:aUthT0K3n" -X GET -H "Content-Type: application/json" [https://MYCOMPANY.atlassian.net/rest/api/2/issue/TST-123|https://mycompany.atlassian.net/rest/api/2/issue/TST-123] }} HTTP/2 200[...snip...]{color:#172b4d} {color}{quote}Adding these credentials to Jenkins credentials manager was no problem. I specify them for the Jira plugin configuration too. But when I click "Validate Settings", I receive the following error:{quote}Failed to login to JIRA{quote}I can confirm that the proper credentials are being accessed, because when I visit [https://id.atlassian.com/manage/api-tokens] it says that the API token was used "A few seconds ago". I see this in my Jenkins logs:{quote} {{ Failed to login to JIRA at [https://MYCOMPANY.atlassian.net/|https://mycompany.atlassian.net/] RestClientException {{ \{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={}, errorMessages=[The 'permissions' query parameter is required.]}]}}}{quote}I suspect that this is related to this deprecation warning:[https://community.developer.atlassian.com/t/announcement-changes-to-rest-api-2-mypermissions-get-my-permissions/21245]{quote}Previously, the resource would return all permissions defined on the Jira instance, now the list is limited to the keys provided in the {{permissions}} query parameter._Not_ sending the parameter is deprecated, and we are planning to start rejecting such requests starting from 1 February 2019.You can find more details here: [Change notice - Get my permissions resource now requires the permissions query parameter|https://developer.atlassian.com/cloud/jira/platform/change-notice-get-my-permissions-requires-permissions-query-parameter/] {quote}
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title
Ian Katz updated an issue
Jenkins / JENKINS-60305
Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Change By:
Ian Katz
I'm trying to connect Jenkins to my company's cloud-hosted Jira (e.g. [https://MYCOMPANY.atlassian.net/).|https://mycompany.atlassian.net/).] My account there is set up with google, so based on [JIRA Rest API authentication always returns 401 unauthorized| [https://community.atlassian.com/t5/Jira-questions/JIRA-Rest-API-authentication-always-returns-401-unauthorized/qaq-p/187181 #M317050] ] I took the step of creating an API token from [https://id.atlassian.com/manage/api-tokens] Using this, I am able to successfully curl my Jira site:{quote}$ curl -D- -u "m...@mycompany.com:aUthT0K3n" -X GET -H "Content-Type: application/json" [https://MYCOMPANY.atlassian.net/rest/api/2/issue/TST-123|https://mycompany.atlassian.net/rest/api/2/issue/TST-123]HTTP/2 200[...snip...]{color:#172b4d} {color}{quote}Adding these credentials to Jenkins credentials manager was no problem. I specify them for the Jira plugin configuration too. But when I click "Validate Settings", I receive the following error:{quote}Failed to login to JIRA{quote}I can confirm that the proper credentials are being accessed, because when I visit [https://id.atlassian.com/manage/api-tokens] it says that the API token was used "A few seconds ago". I see this in my Jenkins logs:{quote}{{Failed to login to JIRA at [ https://MYCOMPANY.atlassian.net/ |https://mycompany.atlassian.net/] RestClientException\{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={}, errorMessages=[The 'permissions' query parameter is required.]}]}}} {quote}I suspect that this is related to this deprecation warning:[https://community.developer.atlassian.com/t/announcement-changes-to-rest-api-2-mypermissions-get-my-permissions/21245]{quote}Previously, the resource would return all permissions defined on the Jira instance, now the list is limited to the keys provided in the {{permissions}} query parameter._Not_ sending the parameter is deprecated, and we are planning to start rejecting such requests starting from 1 February 2019.You can find more details here: [ [ Change notice - Get my permissions resource now requires the permissions query parameter| | https://developer.atlassian.com/cloud/jira/platform/change-notice-get-my-permissions-requires-permissions-query-parameter/] [https://developer.atlassian.com/cloud/jira/platform/change-notice-get-my-permissions-requires-permissions-query-parameter/] []|https://developer.atlassian.com/cloud/jira/platform/change-notice-get-my-permissions-requires-permissions-query-parameter/] {quote}
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title Ian Katz created an issue Jenkins / JENKINS-60305 Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-11-27 15:31 Environment: Jenkins ver. 2.190.2 (official Docker image) Jira Plugin 3.0.11 Labels: jira 400 login atlassian Priority: Major Reporter: Ian Katz I'm trying to connect Jenkins to my company's cloud-hosted Jira (e.g. https://MYCOMPANY.atlassian.net/). My account there is set up with google, so based on JIRA Rest API authentication always returns 401 unauthorized I took the step of creating an API token from https://id.atlassian.com/manage/api-tokens Using this, I am able to successfully curl my Jira site: $ curl D -u "m...@mycompany.com:aUthT0K3n" -X GET -H "Content-Type: application/json" https://MYCOMPANY.atlassian.net/rest/api/2/issue/TST-123 HTTP/2 200 [...snip...] Adding these credentials to Jenkins credentials manager was no problem. I specify them for the Jira plugin configuration too. But when I click "Validate Settings", I receive the following error: Failed to login to
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Jenkins client in Keycloak using the ["Keycloak config" here . |https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Jenkins client in Keycloak using the ["Keycloak config" here.|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " _ is missing the Overall/Read permission permission_ ".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203298.1574859362000.7808.1574867940232%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth closed an issue as Not A Defect Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.7806.1574867820215%40Atlassian.JIRA.
