[JIRA] (JENKINS-55149) Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure Change By: Oliver Gondža Labels: lts-candidate newbie-friendly 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.196216.1544618674000.9719.1558595340367%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16750) Job console output does not refresh when job is done
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-16750 Job console output does not refresh when job is done Change By: Oliver Gondža Labels: lts-candidate 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.147577.1360573351000.9723.1558595400583%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56477) Selecting only compatible plugins when clicking "All" does not work
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-56477 Selecting only compatible plugins when clicking "All" does not work Change By: Oliver Gondža Labels: lts-candidate newbie-friendly 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.198077.1552039327000.9733.1558595400774%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57071) Cannot use Linux agent installer modules
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57071 Cannot use Linux agent installer modules Change By: Oliver Gondža Labels: lts-candidate 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.198814.1555466964000.9735.1558595460243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46515) Launcher will retry connections forever under some irrecoverable status
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status Change By: Oliver Gondža Labels: lts-candidate 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.184832.1503993829000.9738.1558595520162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57107 SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p) Change By: Oliver Gondža Labels: lts-candidate 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.198852.183944000.9742.1558596660260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-51004 slave.jar -loggingConfig argument not working as documented Change By: Oliver Gondža Labels: diagnostics lts-candidate 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.190230.1524671418000.9745.1558596720304%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57273) NodeListener.onCreated was called when Jenkins.addNode or Nodes.addNode actually replaced an existing node
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57273 NodeListener.onCreated was called when Jenkins.addNode or Nodes.addNode actually replaced an existing node Change By: Oliver Gondža Labels: lts-candidate 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.199039.1556718654000.9748.1558596780262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57594) email-ext: get culprits per repo
Title: Message Title Julien Errera updated an issue Jenkins / JENKINS-57594 email-ext: get culprits per repo Change By: Julien Errera Summary: email-ext: better libraries handling get culprits per repo 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.199518.1558509365000.9752.1558596900221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57412 Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Change By: Oliver Gondža Labels: LTS lts 2.176.1 - candidate fixed LTS regression 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.199218.1557561012000.9760.1558596960399%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site
Title: Message Title Owen Mehegan commented on JENKINS-47309 Re: Plugin || Confluence Publisher || Not working with confluence cloud site API deprecation notice here: https://blog.developer.atlassian.com/confluence-cloud-soap-api-migration/ 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.185734.1507283628000.9755.1558596960317%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Oliver Gondža Labels: lts 2.176.1 - candidate fixed 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.198858.1555612432000.9763.1558597140177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57607) Can't log in after plugin update
Title: Message Title Björn Olsson commented on JENKINS-57607 Re: Can't log in after plugin update Me too, I upgrade to 2.15, and i get the "invalid username or password" error message. downgrade to 2.14 and it works again. 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.199534.1558534736000.9767.1558597620203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57477 Cancelling a job results in "sendctrlc.x64...exe" stops working Change By: Oliver Gondža Labels: 2.176.1-rejected lts-candidate winp 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.196067.1544012607000.9772.1558597680481%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57477) Cancelling a job results in "sendctrlc.x64...exe" stops working
Title: Message Title Oliver Gondža commented on JENKINS-57477 Re: Cancelling a job results in "sendctrlc.x64...exe" stops working Postponing this to 1.176.2 as the fix is quite new and there appear to be an alternative fix. 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.196067.1544012607000.9795.1558597740693%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oliver Gondža Labels: 2.176.1-rejected detached-plugin docker lts-candidate plugin-manager 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.199434.155810265.9799.1558599300360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57627) Update the project description page
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57627 Update the project description page Issue Type: Task Assignee: Devin Nusbaum Components: promoted-builds-plugin Created: 2019-05-23 08:22 Priority: Minor Reporter: Prastik Gyawali 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.199557.1558599763000.9804.1558599780175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57627) Update the project description page
Title: Message Title Prastik Gyawali resolved as Fixed Jenkins / JENKINS-57627 Update the project description page Change By: Prastik Gyawali Status: Open Resolved Assignee: Devin Nusbaum Prastik Gyawali Resolution: Fixed 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.199557.1558599763000.9806.1558599840230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector-update-libs.hpi 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.199458.1558312268000.9808.1558599900102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector-local-passive-after-conn.hpi 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.199458.1558312268000.9812.1558599961864%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job updated libs, issue disconnect always as in 2.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.199458.1558312268000.9810.1558599961803%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57457) GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks Change By: Prastik Gyawali Labels: gsoc-2019 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.199317.1557843061000.9814.1558600380113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Labels: gsoc-2019 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.199320.1557845087000.9816.1558600500049%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) jenkins -jira integration
Title: Message Title Radek Antoniuk commented on JENKINS-57619 Re: jenkins -jira integration What certificate is used on the JIRA side? Can you connect directly to JIRA with curl via the command-line? 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.199547.1558546618000.9818.1558600620200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) jenkins -jira integration
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-57619
jenkins -jira integration
Change By:
Radek Antoniuk
{noformat} sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source) at java.security.cert.CertPathBuilder.build(Unknown Source)Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(Unknown Source) at sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at sun.security.validator.Validator.validate(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) at sun.security.ssl.Handshaker.processLoop(Unknown Source) at sun.security.ssl.Handshaker$1.run(Unknown Source) at sun.security.ssl.Handshaker$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Unknown Source) at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:284) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:352)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Unknown Source) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(Unknown Source) at sun.security.ssl.SSLEngineImpl.writeAppRecord(Unknown Source) at sun.security.ssl.SSLEngineImpl.wrap(Unknown Source) at javax.net.ssl.SSLEngine.wrap(Unknown Source) at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:266) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:306) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:508) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:120) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.Abstra
[JIRA] (JENKINS-57619) jenkins -jira integration
Title: Message Title Radek Antoniuk edited a comment on JENKINS-57619 Re: jenkins -jira integration What certificate is used on the JIRA side? Can you connect directly to JIRA with curl via the command-line? Also, please add details in the issue about JIRA and jenkins plugin versions. 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.199547.1558546618000.9822.1558600740122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) Unable to find valid certification path
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57619 Unable to find valid certification path Change By: Radek Antoniuk Summary: U\nable Unable to find valid certification path 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.199547.1558546618000.9826.1558600800266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) U\nable to find valid certification path
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57619 U\nable to find valid certification path Change By: Radek Antoniuk Summary: jenkins -jira integration U\nable to find valid certification path 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.199547.1558546618000.9824.1558600800242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34774) ClosedChannelException in log (excessive)
Title: Message Title Radek Antoniuk closed an issue as Fixed This should be fixed in jira-plugin 2.5.2. If not, please reopen with current logs from current Jenkins and jira-plugin, thanks! Jenkins / JENKINS-34774 ClosedChannelException in log (excessive) Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed 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.170424.1463073889000.9828.1558600980894%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57457) GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199317.1557843061000.9844.1558601520211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57597) Jenkins cannot be run as Windows Service: Error 1053
Title: Message Title Radoslaw Stepien closed an issue as Fixed Jenkins / JENKINS-57597 Jenkins cannot be run as Windows Service: Error 1053 Change By: Radoslaw Stepien Status: Open Closed Resolution: Fixed 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.199521.1558515469000.9845.1558601820184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57628) Global tool configuration - MAVEN_HOME issue
Title: Message Title Eduard Costoae created an issue Jenkins / JENKINS-57628 Global tool configuration - MAVEN_HOME issue Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-23 09:03 Priority: Minor Reporter: Eduard Costoae Hello, I have encountered an issue where although i set correct path(in my case /usr/local/maven) to my local maven installation(inside Global Tool Configuration tab) my build fails @ run time with the message "mvn: not found". Workaround to this was the creation of a symlink inside /usr/bin pointing to my mvn binary, this worked because /usr/bin was already present in the PATH variable of jenkins user. My setup: fresh install of Ubuntu 18.04 inside VirtualBox (up to date) Jenkins Version 2.164.3 Apache Maven Version 3.6.1 I hope this is not a duplicate issue, i searched for it but couldn't find any reported. Please let me know if you need any more information. Regards, Eduard. Add Comment
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199320.1557845087000.9847.1558602300065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57629) Login to some users isn't possible with AD plugin 2.15
Title: Message Title Yoav Miles created an issue Jenkins / JENKINS-57629 Login to some users isn't possible with AD plugin 2.15 Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: security-log.txt Components: active-directory-plugin Created: 2019-05-23 09:06 Environment: Jenkins LTS 2.164.3 active-directory-plugin 2.15 Priority: Minor Reporter: Yoav Miles This is a regression from version 2.14 - some users aren't able to login: the AD log states that the user logged in successfully, but the acegisecurity log throws a false AccountExpiredException. Unfortunately I haven't figured out on what logic a user was regarded as expired, otherwise I would've provided more information. Downgrading back to 2.14 eliminated the issue for all users that couldn't login. Add Comment
[JIRA] (JENKINS-57462) Upload the bio with an avatar in jenkins.io
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57462 Upload the bio with an avatar in jenkins.io Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199322.1557847038000.9853.1558602660078%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57627) Update the project description page
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57627 Update the project description page Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199557.1558599763000.9850.1558602360154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57457) GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199317.1557843061000.9849.1558602360142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199320.1557845087000.9854.1558603440101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Sprint: GSoC 2019. Community Bonding 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.199320.1557845087000.9855.1558603560052%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) How to mapping Custom Field key in JIRA trigger plugin
Title: Message Title Deakey Tan created an issue Jenkins / JENKINS-57630 How to mapping Custom Field key in JIRA trigger plugin Issue Type: Bug Assignee: Wisen Tanasa Attachments: image-2019-05-23-17-25-15-520.png, image-2019-05-23-17-25-55-827.png Components: jira-trigger-plugin Created: 2019-05-23 09:30 Environment: Jenkins 2.164.3 JIRA-trigger-plugin 1.0.0 Priority: Minor Reporter: Deakey Tan Hi team, I have used JIRA-trigger-plugin, it's a great job. I have some difficulties, I need to get some values from custom field, such as emailAddress. But when I mapping, it only show the key. I have try 10103.emailAddress, etc, not work. Could you help me to get this values? Many thanks Add Comment
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title zern king created an issue Jenkins / JENKINS-57631 No credentials found for id Issue Type: Bug Assignee: Unassigned Attachments: image-2019-05-23-17-17-27-088.png, image-2019-05-23-17-19-38-432.png Components: credentials-plugin Created: 2019-05-23 09:31 Environment: docker on linux jenkins: 2.164.3 Credentials Plugin:2.1.19 Labels: plugins credentials Priority: Critical Reporter: zern king use Role-Based Strategy. Create a Folder "test" create credentials in folder "test" Create a job within the folder use the credentials Run job but: ERROR: No credentials found for id "557f78f0-a2e0-4fae-a3ee-00cac16514f8" create credentials in system domain it's worked.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title zern king updated an issue Jenkins / JENKINS-57631 No credentials found for id Change By: zern king Attachment: image-2019-05-23-17-33-43-511.png 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.199561.1558603884000.9862.1558604040130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title zern king updated an issue Jenkins / JENKINS-57631 No credentials found for id Change By: zern king use Role-Based Strategy. * Create a Folder "test" * create credentials in folder "test" * Create a job within the folder use the credentials * Run jobbut: ERROR: No credentials found for id "557f78f0-a2e0-4fae-a3ee-00cac16514f8"create credentials in system domain it's worked.!image-2019-05-23-17-19-38-432.png!!image-2019-05-23-17- 21 33 - 23 43 - 218 511 .png!!image-2019-05-23-17-17-27-088.png! 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.199561.1558603884000.9863.1558604040176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57627) Update the project description page
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57627 Update the project description page Change By: Prastik Gyawali Labels: gsoc-2019 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.199557.1558599763000.9864.1558604280065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57632) StringIndexOutOfBoundsException on expandAttachmentsLink()
Title: Message Title Jonas Prapuolenis created an issue Jenkins / JENKINS-57632 StringIndexOutOfBoundsException on expandAttachmentsLink() Issue Type: Bug Assignee: Joe Hansche Attachments: image-2019-05-23-12-40-58-080.png Components: confluence-publisher-plugin Created: 2019-05-23 09:41 Environment: Jenkins ver. 2.138.1 Confluence Publisher 2.0.3 Atlassian Confluence 6.14.3 Priority: Blocker Reporter: Jonas Prapuolenis Uploading attachments is working fine on its own. Editing confluence page is working fine on its own. When trying to do both of these - editing confluence page fails with an exception: BUILD SUCCESSFUL in 5s 1 actionable task: 1 executed Build step 'Invoke Gradle script' changed build result to SUCCESS Archiving artifacts [confluence] Uploading attachments to Confluence page: https://confluence.xxx.com/display/YYY/ZZZ [confluence] Found 2 archived artifact(s) to upload to Confluence... [confluence] Uploading 2 file(s) to Confluence... [confluence] - Uploading file: X1_(9308).apk (application/octet-stream) [confluence]done: https://confluence.XXX.com/download/attachments/5571366/X1_%289308%29.apk?version=1&modificationDate=1558596764844&api=v2 [confluence] - Uploading file: X2_(9308).apk (application/octet-stream) [confluence]done: https://confluence.XXX.com/download/attachments/5571366/X2_%289308%29.apk?version=1&modificationDate=1558596765878&api=v2
[JIRA] (JENKINS-57633) Finalise the "Skeleton" design for the plugin
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57633 Finalise the "Skeleton" design for the plugin Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-23 09:42 Priority: Major Reporter: Prastik Gyawali 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.199563.1558604531000.9867.1558604580206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/
[JIRA] (JENKINS-57633) Finalise the "Skeleton" design for the plugin
Title: Message Title Prastik Gyawali started work on JENKINS-57633 Change By: Prastik Gyawali 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.199563.1558604531000.9868.1558604580249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57633) Finalise the "Skeleton" design for the plugin
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57633 Finalise the "Skeleton" design for the plugin Change By: Prastik Gyawali Labels: gsoc-2019 Sprint: GSoC 2019. Community Bonding 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.199563.1558604531000.9869.1558604640082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57632) StringIndexOutOfBoundsException on expandAttachmentsLink()
Title: Message Title Jonas Prapuolenis commented on JENKINS-57632 Re: StringIndexOutOfBoundsException on expandAttachmentsLink() Have not found a workaround, so blocked by this. 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.199562.1558604515000.9871.1558605360110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Issue Type: Epic Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-23 10:00 Labels: gsoc-2019 Priority: Major Reporter: Prastik Gyawali 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 jenkin
[JIRA] (JENKINS-56935) Multibranch pipeline orphaned item strategy can't be set to 0
Title: Message Title Carlos Juan Gómez Peñalver commented on JENKINS-56935 Re: Multibranch pipeline orphaned item strategy can't be set to 0 Kevin Phillips Looks like the solution is to leave both fields empty https://stackoverflow.com/questions/51734259/jenkins-multibranch-pipeline-wont-prune-deleted-branches Maybe 0 should be equivalent. Groovy DSL documentation for these fields says that the default value is "-1" https://jenkinsci.github.io/job-dsl-plugin/#path/javaposse.jobdsl.dsl.jobs.OrganizationFolderJob.orphanedItemStrategy-discardOldItems 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.198618.155473183.9874.1558605660170%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57635) Can not log in after upgrade to 2.15 from 2.14
Title: Message Title S imon created an issue Jenkins / JENKINS-57635 Can not log in after upgrade to 2.15 from 2.14 Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-05-23 10:06 Environment: Windows Server Labels: security Priority: Major Reporter: S imon After upgrading the active-directory from 2.14 to 2.15, I am unable to log in: the message is Username/Password wrong. Add Comment
[JIRA] (JENKINS-57636) Generate graphs/links when report not generated
Title: Message Title
Jakub Pawlinski created an issue
Jenkins / JENKINS-57636
Generate graphs/links when report not generated
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-05-23 10:11
Priority:
Minor
Reporter:
Jakub Pawlinski
I have a build that in some cases is avoided - logs are not produced. I would like to be able to compensate reports generation, so no matter if new results are collected, the graph and links are displayed. Currenly only a build that records issues is showing both of those. I tried to compensate it by generating report with empty issues collection but then the graph drops to 0 Example - every second build generates report:
pipeline {
agent any
stages {
stage ('recordIssues') {
when { _expression_ { env.BUILD_NUMBER.toBigInteger().mod( 2 ) == 0 } }
steps {
recordIssues(
tools: [
intel(pattern: "logs\\**\\*.*"),
]
)
}
}stage ('compensate') {
when { _expression_ { env.BUILD_NUMBER.toBigInteger().mod( 2 ) != 0 } }
steps {
echo "don't know how..."
}
}
}
}
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Prastik Gyawali Tasks to be completed during the first coding phase.1) Make all the Extensions,PromotionConditions,Implementations,etc pipeline compatible(by detaching them from the promoted-builds)2) Apply the parameterized-trigger concept to trigger the promotion job.3) Use the run-selector-plugin and/or copy-artifacts to know the triggering build.4) Test this job application.5) [New tasks to be updated or modified] 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.199564.1558605601000.9879.1558606500058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Prastik Gyawali Sprint: GSoC 2019. Coding Phase 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.199564.1558605601000.9881.1558606620596%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57637) Detach the existing extensions,implementations,conditions,etc and refactor them for pipeline compatibility.
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57637 Detach the existing extensions,implementations,conditions,etc and refactor them for pipeline compatibility. Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-23 10:16 Labels: gsoc-2019 Priority: Major Reporter: Prastik Gyawali 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 receivin
[JIRA] (JENKINS-57638) Custom named tools are not presenting with custom names/ids in report
Title: Message Title
Jakub Pawlinski created an issue
Jenkins / JENKINS-57638
Custom named tools are not presenting with custom names/ids in report
Issue Type:
Bug
Assignee:
Ulli Hafner
Attachments:
image-2019-05-23-11-18-01-535.png
Components:
warnings-ng-plugin
Created:
2019-05-23 10:18
Priority:
Minor
Reporter:
Jakub Pawlinski
Using custom named tools is not rendering properly in results page:
pipeline {
agent any
stages {
stage ('recordIssues') {
steps {
recordIssues(
aggregatingResults: true,
tools: [
intel(pattern: "logs\\**\\*.*"),
msBuild(id: 'A', name: 'A', pattern: 'logs\\A\\**\\*.*'),
msBuild(id: 'B', name: 'B', pattern: 'logs\\B\\**\\*.*')
]
)
}
}
}
}
renders like below (can't tell which is A and which is B):
[JIRA] (JENKINS-57639) InfluxDB Plugin Robot Framework "suite_result" data publication fails with org.influxdb.InfluxDBException$FieldTypeConflictException after update to 1.21
Title: Message Title
Atte Tanskanen created an issue
Jenkins / JENKINS-57639
InfluxDB Plugin Robot Framework "suite_result" data publication fails with org.influxdb.InfluxDBException$FieldTypeConflictException after update to 1.21
Issue Type:
Bug
Assignee:
Aleksi Simell
Components:
influxdb-plugin
Created:
2019-05-23 10:32
Environment:
Jenkins: 2.164.2 InfluxDB Plugin: 1.21 InfluxDB: 1.4.2
Priority:
Minor
Reporter:
Atte Tanskanen
InfluxDB plugin fails Robot Framework data publication for measurement "suite_result" in post-build action with below exception. Started happening in all jobs (freestyle and pipeline) after updating Jenkins from 2.107.3 to 2.164.2 and InfluxDB Plugin from 1.15 to 1.21. Data is being published from same jobs and to same InfluxDB target and database as before the update. This error fails an otherwise successful build in Jenkins.
[InfluxDB Plugin] Collecting data for publication in InfluxDB...
[InfluxDB Plugin] Robot Framework data found. Writing to InfluxDB...
[InfluxDB Plugin] Git ChangeLog data found. Writing to InfluxDB...
[InfluxDB Plugin] Publishing data to: Target{description=, url="" username=, database=}
ERROR: Build step failed with exception
org.influxdb.InfluxDBException$FieldTypeConflictException: partial write: field type conflict: input field "rf_critical_failed" on measurement "suite_result" is type integer, already exists as type float dropped=562
at org.influxdb.InfluxDBException.buildExceptionFromErrorMessage(InfluxDBException.java:144)
at org.influxdb.InfluxDBException.buildExceptionForErrorState(InfluxDBException.java:173)
a
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title
René Korthaus commented on JENKINS-50711
Re: plugin doesn't work with ssh link to git repo
We can reproduce this issue with the latest 0.9.10, too. For us it only happens when the Jenkins master is a Linux node whereas the slave is a Windows node. Here are the steps:
Create a new freestyle job:
Check "This project is parameterized"
Add Parameter "Git Parameter"
Name: BRANCH_SPECIFIER
Parameter Type: Branch or Tag
Default Value: origin/master
Check "Restrict where this project can be run"
Label _expression_:
Under Source Code Management, add a Git repo to check out
Repository URL:
Credentials:
Branch Specifier ${BRANCH_SPECIFIER}
Build the freestyle job using "Build with parameters"
Actual Result: Branches are listed fine, clicking "Build" checks out the branch and makes the job run successful
Build the freestyle job a second time using "Build with parameters"
Expected Result: Branches are listed, clicking "Build" checks out the branch and finishes the job successfully
Actual Result: The default branch "origin/master" and an error message are shown
The def
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title
René Korthaus edited a comment on JENKINS-50711
Re: plugin doesn't work with ssh link to git repo
We can reproduce this issue with the latest 0.9.10, too. For us it only happens when the Jenkins master is a Linux node whereas the slave is a Windows node. Here are the steps: * Create a new freestyle job: ** Check "This project is parameterized" ** Add Parameter "Git Parameter" *** Name: BRANCH_SPECIFIER *** Parameter Type: Branch or Tag *** Default Value: origin/master ** Check "Restrict where this project can be run" *** Label _expression_: ** Under Source Code Management, add a Git repo to check out *** Repository URL: *** Credentials: *** Branch Specifier ${BRANCH_SPECIFIER} * Build the freestyle job using "Build with parameters" ** Actual Result: Branches are listed fine, clicking "Build" checks out the branch and makes the job run successful * Build the freestyle job a second time using "Build with parameters" ** Expected Result: Branches are listed, clicking "Build" checks out the branch and finishes the job successfully ** Actual Result: The default branch "origin/master" and an error message are shown {code:java} {code} * The default value has been returned * An error occurred while download data * Command "git ls-remote -h git@URL:group/project.git" returned status code 128: * stdout: * stderr: /tmp/ssh7012935625751221498.sh: 6: /tmp/ssh7012935625751221498.sh: ssh: not found fatal: Could not read from remote repository. * Please make sure you have the correct access rights and the repository exists. * Please look at the Log * Please check the configuration {code} The problem is also reported in JENKINS-56558. It even points to the problematic code that causes 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...@g
[JIRA] (JENKINS-57294) Flexibel Publish Plugin
Title: Message Title Andreas Neumeier started work on JENKINS-57294 Change By: Andreas Neumeier 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.199060.1556747235000.9895.1558608360198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57635) Can not log in after upgrade to 2.15 from 2.14
Title: Message Title S imon updated an issue Jenkins / JENKINS-57635 Can not log in after upgrade to 2.15 from 2.14 Change By: S imon After upgrading the active-directory plugin from 2.14 to 2.15, I am unable to log in: the message is Username/Password wrong. 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.199565.155860597.9897.1558609020139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Daniel Stratton Attachment: debugLog.20190523.2055.txt 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.199458.1558312268000.9905.1558609080444%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57607) Can't log in after plugin update
Title: Message Title S imon commented on JENKINS-57607 Re: Can't log in after plugin update Just adding a me too! 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.199534.1558534736000.9900.1558609080277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Viacheslav Subotskyi commented on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin I had to switch to `sh` as well 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.195937.1543444084000.9911.1558612260397%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted updated JENKINS-50993 fixed in splunk-devops 1.7.1 Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Status: Open Fixed but Unreleased Resolution: Fixed 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.190218.1524652389000.9932.1558612921014%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted updated JENKINS-50993 Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Status: Fixed but Unreleased Resolved 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.190218.1524652389000.9934.1558612921052%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted closed an issue as Fixed Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted 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.190218.1524652389000.9938.1558612980364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57586) TaskListenerDecorator's close method is not called
Title: Message Title Ted commented on JENKINS-57586 Re: TaskListenerDecorator's close method is not called Oleg Nenashev is the behavior expected? 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.199504.1558458028000.9941.1558613160043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Vladislav Naumov commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed Seems to be fixed in 1.43 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.196789.1547639731000.9943.1558613760351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Oliver Gondža commented on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 Alright, it turned out the changes in 1.58 uncovered a conceptual problem in the plugin. I have just release 0.5 with the new unsafe signature reworked. https://github.com/jenkinsci/permissive-script-security-plugin/commit/7458ae4d1363a95d78fb8212460b4056f4b205ee 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.198922.1556125514000.9961.1558613941604%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57640) Support for Configuration as Code
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-57640 Support for Configuration as Code Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-05-23 12:18 Labels: jcasc-compatibility Priority: Minor Reporter: Jon Brohauge Being able to set the global properties using the CasC plugin would be fantastic. This allows for setting the properties programatically and having the values under source control. Add Comment
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Oliver Gondža updated JENKINS-57171 Jenkins / JENKINS-57171 Permissive script security plugin is broken after updating to script security 1.58 Change By: Oliver Gondža Status: Reopened Fixed but Unreleased Resolution: Fixed Released As: 0. 4 5 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.198922.1556125514000.9975.1558613941791%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57640) Support for Configuration as Code
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57640 Support for Configuration as Code Change By: Jon Brohauge Component/s: dependency-track-plugin Component/s: dependency-check-jenkins-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.199570.1558613883000.9988.155861490%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57641) Same stage appears multiple times if last pipeline includes multiple stage runs.
Title: Message Title Alfono Rodríguez Martín created an issue Jenkins / JENKINS-57641 Same stage appears multiple times if last pipeline includes multiple stage runs. Issue Type: Bug Assignee: ElectricFlow ElectricCloud Components: electricflow-plugin Created: 2019-05-23 12:32 Priority: Minor Reporter: Alfono Rodríguez Martín When creating a post build step in Jenkins to trigger a Flow Release, there is an option to select which stages to run. The bug will show the same stage multiple times if the last pipeline run included multiple stage runs. E.g., if UAT had been run three times: Select Stages to run: [ ] Dev [ ] UAT [ ] UAT [ ] UAT [ ] Pre-prod [ ] Prod Add Comment
[JIRA] (JENKINS-57608) complete final design doc
Title: Message Title Jack Shen updated JENKINS-57608 Design Doc for Working Hours Plugin Jenkins / JENKINS-57608 complete final design doc Change By: Jack Shen Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://docs.google.com/document/d/1SezLtQejur2ji-KUur3dC3TXK8ivxrttiwHYbTkA8Yk/edit# 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.199535.1558535093000.9994.1558615140238%40Atlassia
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57642 Wrong parameter type and squashing its content when trigger a job Issue Type: Bug Assignee: Scott Hebert Components: jms-messaging-plugin Created: 2019-05-23 12:47 Priority: Major Reporter: Pavel Janoušek I have a job triggered by CI Event (JMS Messaging provider). The job has a declared parameter CI_MESSAGE of type Multi-line String Parameter, according the config.xml of the job, the parameter is CI_MESSAGE When the job is triggered by this plugin, it very ofter puts the content of this parameter as a String, according the build.xml as: CI_MESSAGE ...content... although the definition in the same build.xml still says: CI_MESSAGE Very rare the parameter is correctly stored in build.xml as:
[JIRA] (JENKINS-46542) External way to set default parameter values for a pipeline job
Title: Message Title Kateryna Skok commented on JENKINS-46542 Re: External way to set default parameter values for a pipeline job I have the same problem as in the previous comment. How can I delete cached values? 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.184860.1504106931000.10005.1558615860782%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-57642
Wrong parameter type and squashing its content when trigger a job
Change By:
Pavel Janoušek
I have a job triggered by CI Event (JMS Messaging provider). The job has a declared parameter CI_MESSAGE of type Multi-line String Parameter, according the config.xml of the job, the parameter is{code:java} CI_MESSAGE {code}When the job is triggered by this plugin, it very ofter puts the content of this parameter as a String, according the build.xml as:{code:java} CI_MESSAGE ...content...{code}although the definition in the same build.xml still says:{code:java} CI_MESSAGE {code}Very rare the parameter is correctly stored in build.xml as:{code:java} CI_MESSAGE...content...{code} ans and the definition is the same as previous.UI is confused and String parameter has a far different rendering than Text parameter.It is related to the other weird state - when it put the content of the parameter as String, it separate each key=value pair to separate line, when it put the content of the parameter as Text, it squash all pairs to the one line as: Content from hudson.model.StringParameterValue:{code:java}build=aaaparam2=128url="">{code}Equal content from hudson.model.TextParameterValue:{code:java}build=aaaparam2=128url=foo{code}I don't know what is the source of CI_MESSAGE content, but it doesn't matter - the content type should be always TextParameter, not the other one (StringParameter).
Add Comment
[JIRA] (JENKINS-57635) Can not log in after upgrade to 2.15 from 2.14
Title: Message Title Don Benson commented on JENKINS-57635 Re: Can not log in after upgrade to 2.15 from 2.14 I had the same problem with my Jenkins installation. We are using Active Directory with automatic discovery of the domain (i.e. Custom Domain is not checked). For our authorization setting, we are using Project-based Matrix Authorization Strategy. In the error log, I found these new exceptions: 2019-05-21 21:07:27.092+ [id=126357] WARNING o.e.jetty.server.HttpChannel#handleException: /updateCenter/2019-05-21 21:07:27.092+ [id=126357] WARNING o.e.jetty.server.HttpChannel#handleException: /updateCenter/java.lang.NullPointerException at org.jenkinsci.plugins.matrixauth.AuthorizationContainer.hasPermission(AuthorizationContainer.java:162) at hudson.security.GlobalMatrixAuthorizationStrategy$AclImpl.hasPermission(GlobalMatrixAuthorizationStrategy.java:127) at hudson.security.SidACL._hasPermission(SidACL.java:70) at hudson.security.SidACL.hasPermission(SidACL.java:52) at hudson.security.ACL.checkPermission(ACL.java:72) at hudson.security.AccessControlled.checkPermission(AccessControlled.java:47) at jenkins.model.Jenkins.getTarget(Jenkins.java:4698) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:703) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:32) at hudson.init.impl.InstallUncaughtExceptionHandler$$Lambda$42/27557199.reportException(Unknown Source) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1700) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1667) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:505) at org.eclip
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Oliver Gondža edited a comment on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 Alright, it turned out the changes in 1.58 uncovered a conceptual problem in the plugin. I have just release 0.5 with the new unsafe signature detection reworked.https://github.com/jenkinsci/permissive-script-security-plugin/commit/7458ae4d1363a95d78fb8212460b4056f4b205ee 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.198922.1556125514000.10024.1558616221343%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Oliver Gondža updated JENKINS-57171 Jenkins / JENKINS-57171 Permissive script security plugin is broken after updating to script security 1.58 Change By: Oliver Gondža Status: Fixed but Unreleased Resolved 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.198922.1556125514000.10038.1558616221510%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57636) Generate graphs/links when report not generated
Title: Message Title Ulli Hafner commented on JENKINS-57636 Re: Generate graphs/links when report not generated Which links do you mean? The link on the job page or on the build page? 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.199566.1558606318000.10045.1558616280266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57608) complete final design doc
Title: Message Title Jack Shen updated JENKINS-57608 Jenkins / JENKINS-57608 complete final design doc Change By: Jack Shen Status: Fixed but Unreleased Resolved 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.199535.1558535093000.10053.1558616340462%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51874) Parameterized Remote Trigger does not use URL for Build Token Root Plugin
Title: Message Title Denis Shvedchenko commented on JENKINS-51874 Re: Parameterized Remote Trigger does not use URL for Build Token Root Plugin Hello, from stack trace it is obvious that root cause lays in https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java#L624 Executing side tries to understand whenever remote job supports parameters or not before constructing url that optionally uses Build Root Token, that performed in HttpHelper.buildTriggerUrl(...) May 23, 2019 1:02:09 PM org.jenkinsci.plugins.ParameterizedRemoteTrigger.utils.HttpHelper sendHTTPCall WARNING: Server returned 403 - Forbidden. User does not have enough permissions for this request: https://*/job /reference/job/provider/api/json?tree=actions[parameterDefinitions],property[parameterDefinitions],name,fullName,displayName,fullDisplayName,url - [HTTP/ 1.1 403 Forbidden] org.jenkinsci.plugins.ParameterizedRemoteTrigger.exceptions.ForbiddenException: Server returned 403 - Forbidden. User does not have enough permissions fo r this request: https:///job/reference/job/provider/api/json?tree=actions[parameterDefinitions],property[param eterDefinitions],name,fullName,displayName,fullDisplayName,url at org.jenkinsci.plugins.ParameterizedRemoteTrigger.utils.HttpHelper.sendHTTPCall(HttpHelper.java:474) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.utils.HttpHelper.tryCall(HttpHelper.java:571) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.utils.HttpHelper.tryGet(HttpHelper.java:591) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.doGet(RemoteBuildConfiguration.java:877) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.getRemoteJobMetadata(RemoteBuildConfiguration.java:1049) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.performTriggerAndGetQueueId(RemoteBuildConfiguration.java:624) <- at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:591) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:557) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Henjo van Rees commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) The LDAP was already enabled before the upgrade, still enabled after the upgrade from 2.150.1. So no, that did not fix it unfortunately. 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.197810.1550821517000.10101.1558617720935%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57643) Support for projectName + projectVersion instead of projectId upon sunchronized=true
Title: Message Title
Jon Brohauge created an issue
Jenkins / JENKINS-57643
Support for projectName + projectVersion instead of projectId upon sunchronized=true
Issue Type:
Improvement
Assignee:
Steve Springett
Components:
dependency-track-plugin
Created:
2019-05-23 13:24
Priority:
Minor
Reporter:
Jon Brohauge
Having the projectId obligatory when using this plugin while having synchronous: true, is an issue for automatically created pipelines. Most of the developers that are going to use this tool, know nothing of the projectId, but obviously knows their projectName and projectVersion. Since the plugin can communicate fine with a Dependency-Track server only using projectName and projectVersion for non-synchronous configuration, it should also be doable with a synchronous configuration. Executing the following pipeline step:
dependencyTrackPublisher projectId: "[projectId]", projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: true
works. Executing the following pipeline step:
dependencyTrackPublisher projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: true
does not work. Executing the following pipeline step:
[JIRA] (JENKINS-57643) Support for projectName + projectVersion instead of projectId upon synchronous:true
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57643 Support for projectName + projectVersion instead of projectId upon synchronous:true Change By: Jon Brohauge Summary: Support for projectName + projectVersion instead of projectId upon sunchronized= synchronous: true 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.199574.1558617849000.10105.1558618140121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57605) Use the "H2 API Plugin" to load H2
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-57605 Use the "H2 API Plugin" to load H2 Change By: Cyrille Le Clerc Component/s: database-h2-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.199531.1558531518000.10106.1558619820085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector-update-libs.hpi 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.199458.1558312268000.10110.1558620780246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector-restructure-relogon.hpi 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.199458.1558312268000.10108.1558620780221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job restructure relogon. Really strange place. 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.199458.1558312268000.10112.1558620780269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57644) Email-Ext does not send to users whose email address starts with '#'
Title: Message Title Steve Turner created an issue Jenkins / JENKINS-57644 Email-Ext does not send to users whose email address starts with '#' Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2019-05-23 14:15 Environment: Jenkins ver. 2.164.3 Email Extension Plugin ver. 2.66 Priority: Minor Reporter: Steve Turner I've noticed that the email-ext plugin will not send out notifications to emails beginning with a '#', even though the job console states that it is doing so. For example: Build step 'Execute shell' marked build as failure Discard old builds... Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Sending email to: #jenkinsad...@company.com Finished: FAILURE The email-ext plugin is fine if the email does not being with a '#'. Add Comment
[JIRA] (JENKINS-57645) Simple mapping instead of script
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-57645 Simple mapping instead of script Issue Type: Improvement Assignee: Dawid Malinowski Components: environment-script-plugin Created: 2019-05-23 14:16 Priority: Minor Reporter: Simon Richter I'd like to map matrix parameters to values used during the build because some tools disagree on the names of various things, e.g. "amd64" vs "x86_64" vs "Win64". Since the job might run on Linux or Windows, it is difficult to write a script that will always work. All I need is a simple table based mapping, so it might be nice to have a way to configure that instead of a script. e.g. mapping from $compiler;$version;$target to $cmake_generator, I could define msvc;2015;x86 -> "Visual Studio 2015 17" msvc;2015;amd64 -> "Visual Studio 2015 17 Win64" msvc;2015;arm64 -> "Visual Studio 2015 17 ARM64" and then subsequently use $cmake_generator as the generator argument for the CMake plugin. Being able to define multiple output values in the same line would also be nice in case I need more derived values (e.g. for installation paths). Add Comment
[JIRA] (JENKINS-57646) Pipeline "when" condition is evaluated on the node
Title: Message Title
Oren Shpigel created an issue
Jenkins / JENKINS-57646
Pipeline "when" condition is evaluated on the node
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
conditional-buildstep-plugin, pipeline
Created:
2019-05-23 14:19
Environment:
Jenkins ver. 2.164.3
Priority:
Minor
Reporter:
Oren Shpigel
For the following code:
pipeline {
agent any
stages {
stage('Test') {
agent { label 'nodes' }
steps {
sh ''' # code to run tests '''
}
}
stage('Deploy') {
when {
branch 'master'
}
agent { label 'specific-node' }
steps {
sh ''' # code to deploy '''
}
}
}
The "when" condition is being evaluated on 'specific-node' and causes a bottleneck, instead of being evaluated on the master, or on the node that ran the previous stage.
[JIRA] (JENKINS-57644) Email-Ext does not send to users whose email address starts with '#'
Title: Message Title
Steve Turner updated an issue
Jenkins / JENKINS-57644
Email-Ext does not send to users whose email address starts with '#'
Change By:
Steve Turner
I've noticed that the email-ext plugin will not send out notifications to emails beginning with a '#', even though the job console states that it is doing so. For example:{quote}Build step 'Execute shell' marked build as failureDiscard old builds...Email was triggered for: Failure - AnySending email for trigger: Failure - AnySending email to: #jenkinsad...@company.comFinished: FAILURE{quote}The email-ext plugin is fine if the email does not being begin with a '#'.
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.199575.1558620905000.10122.1558621260147%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title James Schlesselman commented on JENKINS-55813 Re: Improve AD/LDAP attribute analysis for locked accounts FYI . . I was not able to login after upgading to 2.15. I downgraded back to 2.14 and was able to login again. 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.197207.1548686882000.10124.1558621620148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57534) P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57534 P4_CHANGELIST entry in map returned by checkout step is sometimes wrong Change By: Karl Wirth Labels: P4_SUPPORT P4_B 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.199441.1558118694000.10132.1558621680432%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57534) P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Title: Message Title Karl Wirth commented on JENKINS-57534 Re: P4_CHANGELIST entry in map returned by checkout step is sometimes wrong Hi Stuart Rowe, That's create thank you very much. I'll make sure Dev know about 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.199441.1558118694000.10129.1558621680392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52697) Logstash plugin: support JCasC
Title: Message Title Jakub Bochenski commented on JENKINS-52697 Re: Logstash plugin: support JCasC I will try to do a release tomorrow 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.192583.1532331323000.10134.1558621740109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
