[JIRA] (JENKINS-58469) Not able to generate the coverage report with jenkins jacoco plugin 1.0.19 and jacoco 0.7.4
Title: Message Title Satya yamanuri commented on JENKINS-58469 Re: Not able to generate the coverage report with jenkins jacoco plugin 1.0.19 and jacoco 0.7.4 Team any suggestion on this we have to use the 1.0.19 version plugin in Jenkins and this plug in supports only jacococ version 0.7.4. Ans using 0.7.4 we are getting the following excception. Unable to read execution data file C:\p4\nemo\ce\sw\4.0\team\services\CoreServices\build\jacoco\testDebugUnitTest.exec Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200603.1562936172000.10156.1563168240045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58485) Do not serialize ConcurrentHashMap$KeySetView
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-58485 Do not serialize ConcurrentHashMap$KeySetView Issue Type: Improvement Assignee: Abhyudaya Sharma Components: folder-auth-plugin, role-strategy-plugin Created: 2019-07-15 05:20 Labels: gsoc-2019 Priority: Minor Reporter: Abhyudaya Sharma The Folder-auth plugin uses ConcurrentHashMap's KeySetView as internal data structures and has whitelisted it for serialization through XStream. Remove the white-list entry for `ConcurrentHashMap$KeySetView` and serialize a simpler data structure to the config. This issue follows directly from Jesse Glick's comments on https://github.com/jenkinsci/role-strategy-plugin/pull/89 . Add Comment
[JIRA] (JENKINS-58460) Add Gitter chat for Folder Auth Plugin
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58460 Add Gitter chat for Folder Auth Plugin Change By: Abhyudaya Sharma Labels: gsoc-2019 Sprint: GSoC - Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200594.1562917146000.10153.1563167340193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55933) Create a sample configuration to test slowdown
Title: Message Title Abhyudaya Sharma resolved as Fixed Jenkins / JENKINS-55933 Create a sample configuration to test slowdown Change By: Abhyudaya Sharma Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/role-strategy-plugin/releases/tag/role-strategy-2.11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197342.1549211393000.10150.1563167220433%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56777) Chrome opens, but nothing happens (Selenium)
Title: Message Title Nayan Gogoi commented on JENKINS-56777 Re: Chrome opens, but nothing happens (Selenium) Hi All, I am also facing the same problem in Jenkins ver. 2.163 ,Chrome Version-73 with Windows7 and Java 8 I am able to execute my project from eclipse by while trying with Jenkins I am getting the below message - [INFO] Surefire report directory: C:\Program Files (x86)\Jenkins\workspace\TestMaven\target\surefire-reports --- T E S T S --- Running com.testtalks.karatedemo.MavenProjectSelenium.AppTest Configuring TestNG with: org.apache.maven.surefire.testng.conf.TestNG652Configurator@470e2030 775 [main] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 73.0.3683.68 (since Google Chrome 73 is installed in your machine) 797 [main] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as C:\Windows\system32\config\systemprofile\.m2\repository\webdriver\chromedriver\win32\73.0.3683.68\chromedriver.exe Starting ChromeDriver 73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72) on port 1668 Only local connections are allowed. Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code. [1563166834.026][SEVERE]: Timed out receiving message from renderer: 600.000 Exception while taking screenshotnull Tests run: 4, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 603.531 sec <<< FAILURE! login(com.testtalks.karatedemo.MavenProjectSelenium.AppTest) Time elapsed: 602.667 sec <<< FAILURE! org.openqa.selenium.SessionNotCreatedException: session not created from timeout: Timed out receiving message from renderer: 600.000 (Session info: chrome=73.0.3683.86) (Driver info: chromedriver=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 600.86 seconds Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z' System info: host: 'MCNJY01', ip: '192.168.56.1', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_131' Driver info: driver.version: ChromeDriver at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214) at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166) at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53) at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91) at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$24(ProtocolHandshake.java:359) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) Can anyone help, please. Thanks, Nayan
[JIRA] (JENKINS-57415) [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period
Title: Message Title Abhyudaya Sharma closed an issue as Done Jenkins / JENKINS-57415 [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period Change By: Abhyudaya Sharma Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199221.1557584264000.10142.1563166980470%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58203) [GSoC] Role Strategy Plugin Performance Improvements: Phase 2
Title: Message Title Abhyudaya Sharma closed an issue as Duplicate Jenkins / JENKINS-58203 [GSoC] Role Strategy Plugin Performance Improvements: Phase 2 Change By: Abhyudaya Sharma Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200259.1561529852000.10140.1563166980427%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58459) Add User documentation to Folder Auth README
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58459 Add User documentation to Folder Auth README Change By: Abhyudaya Sharma Labels: gsoc-2019 Sprint: GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200593.1562916638000.10138.1563166920211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58293) Introduce folder based authorization
Title: Message Title Abhyudaya Sharma updated JENKINS-58293 Jenkins / JENKINS-58293 Introduce folder based authorization Change By: Abhyudaya Sharma Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200358.1562038388000.10135.1563166800221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58293) Introduce folder based authorization
Title: Message Title Abhyudaya Sharma commented on JENKINS-58293 Re: Introduce folder based authorization The pull request above was closed and the code for the new AuthorizationStrategy was moved to a separate repository. Please see https://github.com/jenkinsci/folder-auth-plugin/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200358.1562038388000.10133.1563166740122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58399) Avoid finding implying permission for every `hasPermissio()` call
Title: Message Title Abhyudaya Sharma updated JENKINS-58399 Jenkins / JENKINS-58399 Avoid finding implying permission for every `hasPermissio()` call Change By: Abhyudaya Sharma Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/role-strategy-plugin/releases/tag/role-strategy-2.13 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200524.1562663702000.10129.1563166620326%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58399) Avoid finding implying permission for every `hasPermission()` call
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58399 Avoid finding implying permission for every `hasPermission()` call Change By: Abhyudaya Sharma Summary: Avoid finding implying permission for every ` hasPermissio hasPermission ()` call Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200524.1562663702000.10131.1563166620362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58227) Role Strategy: JCasC export fails for dangerous permissions
Title: Message Title Abhyudaya Sharma commented on JENKINS-58227 Re: Role Strategy: JCasC export fails for dangerous permissions See: https://github.com/jenkinsci/role-strategy-plugin/pull/91 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200287.1561587934000.10127.1563166560121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58458) Add CI for Java 11 to the Folder Auth Plugin
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58458 Add CI for Java 11 to the Folder Auth Plugin Change By: Abhyudaya Sharma Labels: gsoc-2019 Sprint: GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200592.1562916335000.10124.1563166500258%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58458) Add CI for Java 11 to the Folder Auth Plugin
Title: Message Title Abhyudaya Sharma resolved as Done See https://github.com/jenkinsci/folder-auth-plugin/pull/1 Jenkins / JENKINS-58458 Add CI for Java 11 to the Folder Auth Plugin Change By: Abhyudaya Sharma Status: Open Resolved Resolution: Done Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/untagged-59fd23271a0b210c8d21 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-58461) Configure the Release Drafter for Folder Auth
Title: Message Title Abhyudaya Sharma resolved as Done Release drafter had drafted the first release. See https://github.com/jenkinsci/folder-auth-plugin/releases/tag/untagged-59fd23271a0b210c8d21 Jenkins / JENKINS-58461 Configure the Release Drafter for Folder Auth Change By: Abhyudaya Sharma Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200595.1562917198000.10118.1563166380536%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58461) Configure the Release Drafter for Folder Auth
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58461 Configure the Release Drafter for Folder Auth Change By: Abhyudaya Sharma Labels: gsoc-2019 Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/untagged-59fd23271a0b210c8d21 Sprint: GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200595.1562917198000.10115.1563166380485%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58484) Using claim plugin in scripted pipeline
Title: Message Title
Abhijith Komarla created an issue
Jenkins / JENKINS-58484
Using claim plugin in scripted pipeline
Issue Type:
Bug
Assignee:
Arnaud TAMAILLON
Components:
claim-plugin
Created:
2019-07-15 03:39
Priority:
Minor
Reporter:
Abhijith Komarla
hi team, I am new to Jenkins and I am trying to use Claims plugin to allow users to claim a build failure in a scripted pipeline. Please let me know how I can do it. I understand in declarative pipeline i can use something like below. {{step([$class: 'ClaimPublisher']) }} Jenkins version 2.121.2 Build Failure Analyzer 1.20.0 Claim plugin version 2.15 Also if you can let me know how I can find this information myself that will be more helpful.
Add Comment
[JIRA] (JENKINS-42609) Plugin should expose overview of it's env vars on an overview page
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-42609 Plugin should expose overview of it's env vars on an overview page Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179547.1489052534000.10110.1563149160257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58483) Jenkins 2.185 won't connect to SSH agents
Title: Message Title
Jens Adam updated an issue
Jenkins / JENKINS-58483
Jenkins 2.185 won't connect to SSH agents
Change By:
Jens Adam
{quote}ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.java.lang.IllegalArgumentException: Unknown server host key algorithm 'ssh-ed25519' at com.trilead.ssh2.transport.KexManager.checkServerHostkeyAlgorithmsList(KexManager.java:316) at com.trilead.ssh2.Connection.setServerHostKeyAlgorithms(Connection.java:1289) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/14/19 22:07:00] Launch failed - cleaning up connection[07/14/19 22:07:00] [SSH] Connection closed.{quote}Plugins were updated three days ago and a restart of 2.184 went fine.Now I just updated to 2.185 and got the quoted "Unknown server host key algorithm 'ssh-ed25519'" messages with all agents (Linux and MacOS) offline.Probably something related to the recent 'trilead' changes? Workaround: Downgrade to previous version ('apt install jenkins=2.184').
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58483) Jenkins 2.185 won't connect to SSH agents
Title: Message Title Jens Adam created an issue Jenkins / JENKINS-58483 Jenkins 2.185 won't connect to SSH agents Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-14 22:29 Environment: Jenkins 2.185, Ubuntu 16.04, OpenJDK 1.8.0, latest plugins (ssh-slaves 1.30) Priority: Major Reporter: Jens Adam ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.java.lang.IllegalArgumentException: Unknown server host key algorithm 'ssh-ed25519' at com.trilead.ssh2.transport.KexManager.checkServerHostkeyAlgorithmsList(KexManager.java:316) at com.trilead.ssh2.Connection.setServerHostKeyAlgorithms(Connection.java:1289) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/14/19 22:07:00] Launch failed - cleaning up connection[07/14/19 22:07:00] [SSH] Connection closed. Plugins were updated three days ago and a restart of 2.184 went fine. Now I just updated to 2.185 and got the quoted "Unknown server host key algorithm 'ssh-ed25519'" messages with all agents (Linux and MacOS) offline. Probably something related to the recent 'trilead' changes?
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57312
Re: Provide tokens for new and fixed warnings
I think, the best way would be to add a parameter to the existing token. This is simpler to implement and would reuse an already existing concept.We basically need a new parameter of type {{String}} that will be converted to an enum similar to {{QualityGateType}}. In this enum we should have a function object that handles the correct property to report. Then we can provide all different values just with one enum. So rather then using the hard coded getter {{action.getResult().getTotalSize();}} we need to use {{enumInstance.getActualSizeMethodReference().apply( deltaReport analysisResult );}}. The only problem is available properties are available in the delta report that is currently not persisted interface {{AnalysisBuildResult}} . I need to check what would be So the best way to implement it enum would probably look like:{code}public enum IssueTokenType {/** Total number of issues .*/TOTAL(AnalysisBuildResult::getTotalSize),/** Total number of issues (severity Error). */TOTAL_ERROR(r -> r.getTotalSizeOf(Severity.ERROR)),/** Number of new issues. */NEW(AnalysisBuildResult::getTotalSize),/** Number of new issues (severity Error). */NEW_ERROR(r -> r.getNewSizeOf(Severity.ERROR)),/** Number of fixed issues. */FIXED(AnalysisBuildResult::getFixedSize), }{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.10105.1563136080222%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57232) Configuration as code support for audit-trail plugin
Title: Message Title Pierre Beitz started work on JENKINS-57232 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198992.1556571471000.10101.1563131940351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero commented on JENKINS-58382 Re: Build is stuck due to blocked thread PR https://github.com/openshift/jenkins-sync-plugin/pull/317 is up for addressing the deadlock After it merges, I'll cherry pick it into https://github.com/jenkinsci/openshift-sync-plugin and cut a new version of the plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200506.1562597218000.10099.1563131160149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero started work on JENKINS-58382 Change By: Gabe Montero Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200506.1562597218000.10097.1563131100222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title Ulli Hafner commented on JENKINS-57312 Re: Provide tokens for new and fixed warnings I think, the best way would be to add a parameter to the existing token. This is simpler to implement and would reuse an already existing concept. We basically need a new parameter of type String that will be converted to an enum similar to QualityGateType. In this enum we should have a function object that handles the correct property to report. Then we can provide all different values just with one enum. So rather then using the hard coded getter action.getResult().getTotalSize(); we need to use enumInstance.getActualSizeMethodReference().apply(deltaReport);. The only problem is the delta report that is currently not persisted. I need to check what would be the best way to implement it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.10094.1563130800180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title Ulli Hafner assigned an issue to Sladyn Nunes Jenkins / JENKINS-57312 Provide tokens for new and fixed warnings Change By: Ulli Hafner Assignee: Ulli Hafner Sladyn Nunes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.10090.1563129960202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-42882 GitSCMFile::content() doesn't handle symlinks Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179887.1489758548000.10087.1563106920589%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45902) do not delete workspace silently while invoking git url: https://mygitrepo in pipeline
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-45902 do not delete workspace silently while invoking git url: https://mygitrepo in pipeline Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184122.1501583185000.10078.1563106620383%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45352) Multi-scm unable to checkout git repo after git-plugin update from 3.3.0->3.3.1 with outdated slave.jar
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-45352 Multi-scm unable to checkout git repo after git-plugin update from 3.3.0->3.3.1 with outdated slave.jar Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183503.1499418227000.10080.1563106620411%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40607) Fix Findbugs errors
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-40607 Fix Findbugs errors Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177294.148233515.10074.1563106560333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45007) git-plugin GitSCM does not support ssh credentials when using checkout in a Jenkinsfile
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-45007 git-plugin GitSCM does not support ssh credentials when using checkout in a Jenkinsfile Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183094.1497976385000.10071.1563106440378%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45007) git-plugin GitSCM does not support ssh credentials when using checkout in a Jenkinsfile
Title: Message Title
Mark Waite commented on JENKINS-45007
Re: git-plugin GitSCM does not support ssh credentials when using checkout in a Jenkinsfile
The example in the description has the same problem as the example on stackoverflow. Instead of creating a single entry for userremoteConfig with a value for URL and a value for credentialsID inside that entry, it creates two entries for userremoteConfig, one with URL and one with credentialsID. Don't do this:
userRemoteConfigs: [
[url: "${gitUrl}" ],
[credentialsId:'----']
Instead, do this:
userRemoteConfigs: [
[url: "${gitUrl}" ,
credentialsId:'----']
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183094.1497976385000.10069.1563106440339%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-49786 Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188735.1519794403000.10061.1563106080433%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19063) Failed to instantiate class BuildChooser from stapler-class:hudson.tasks.Maven
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-19063 Failed to instantiate class BuildChooser from stapler-class:hudson.tasks.Maven Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150510.137570815.10066.1563106080511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43761) checkout scm does not detect last commit
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-43761 checkout scm does not detect last commit Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181177.1492778592000.10057.1563106020303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43878) Pipeline shallow git clone takes longer than non-shallow clone
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-43878 Pipeline shallow git clone takes longer than non-shallow clone Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181406.149324275.10054.1563105900300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33202) Enhance Git Plugin LocalBranch to better support Maven release builds
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-33202 Enhance Git Plugin LocalBranch to better support Maven release builds Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168580.145667289.10049.1563105840662%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32948) ["git" step] Add "WipeWorkspace" option to simplify release jobs
Title: Message Title Mark Waite closed an issue as Won't Do Jenkins / JENKINS-32948 ["git" step] Add "WipeWorkspace" option to simplify release jobs Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168166.1455542086000.10052.1563105840711%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50158) Git plugin class LocalBranch needs to be serializable
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-50158 Git plugin class LocalBranch needs to be serializable Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189162.1520951676000.10043.1563105780872%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58435) Latest update fails with No Artifactory server configured for null; Duplicate upload server in config
Title: Message Title Catalin Mocanu edited a comment on JENKINS-58435 Re: Latest update fails with No Artifactory server configured for null; Duplicate upload server in config Also I can confirm the same problem tried with Jenkins artifactory plugin versions: 3.3. 2 , 3 . 176 3 .1 , 3 . 3.0, 3.2.4 and I receive same error. Can this problem be fixed asap? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200564.1562821412000.10041.1563100680233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58435) Latest update fails with No Artifactory server configured for null; Duplicate upload server in config
Title: Message Title Catalin Mocanu commented on JENKINS-58435 Re: Latest update fails with No Artifactory server configured for null; Duplicate upload server in config I can confirm the same problem with Jenkins 2.176.1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200564.1562821412000.10038.1563100500150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58432) Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL)
Title: Message Title Ariel M closed an issue as Cannot Reproduce Jenkins / JENKINS-58432 Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL) Change By: Ariel M Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200561.1562782481000.10034.1563091380403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Some builds disappeared in jenkins history (also not exists in disk)
Title: Message Title Ariel M closed an issue as Not A Defect Jenkins / JENKINS-58179 Some builds disappeared in jenkins history (also not exists in disk) Change By: Ariel M Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200230.1561449713000.10032.1563091380347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
