[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"
Title: Message Title Thorsten Scherler commented on JENKINS-54333 Re: Projects are triggered twice by "build with parameters" I pushed a branch https://github.com/jenkinsci/jenkins/compare/master...scherler:JENKINS-54333?expand=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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Thorsten Scherler commented on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen I created a branch for testing reasons https://github.com/jenkinsci/jenkins/compare/master...scherler:JENKINS-54333?expand=1 can someone who is able to reproduce the bug test with that in 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33458) Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Max Wahler commented on JENKINS-33458 Re: Make Sidebar-Link Plugin Compatible With Pipeline Are there any updates to this issue? I'd love to see sidebar links back in Jenkins! Our use case is that a build generates data that is sent to Metabase which generates charts to query and visualize the test results. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48839) Junit plugin reporting Fixed when apparently the previous run did not fail
Title: Message Title wayne wang commented on JENKINS-48839 Re: Junit plugin reporting Fixed when apparently the previous run did not fail We observed similar issue, See below snapshot. Buid #718 got "Regression" and said "Failed 1 times in the last 30 runs. Flakiness: 3%, Stability: 96%". The following builds (since build #719) passed. But they said "(No known failures. Flakiness 0%, Stability 100%)". This should be incorrect. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54507) pipeline_data is not pushing to influxdb
Title: Message Title Aleksi Simell closed an issue as Duplicate Closing ticket as duplicate. Continue discussion in https://issues.jenkins-ci.org/browse/JENKINS-53360. Jenkins / JENKINS-54507 pipeline_data is not pushing to influxdb Change By: Aleksi Simell Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48839) Junit plugin reporting Fixed when apparently the previous run did not fail
Title: Message Title wayne wang updated an issue Jenkins / JENKINS-48839 Junit plugin reporting Fixed when apparently the previous run did not fail Change By: wayne wang Attachment: JUnitPlugin.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54414) NullPointerException when packaging IPA
Title: Message Title Kazuhide Takahashi edited a comment on JENKINS-54414 Re: NullPointerException when packaging IPA [~welkiner]Fixed a bug that abnormally ends when there is no file in the buildPlatform directory when dSYMs is archived.There is a snapshot of the plug-in that fixed in the following places, so will you try it with this?If this is not a problem I will try to merge it with the next(2.0.10?) release.https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fxcode-plugin/detail/PR- 98 99 /1/artifacts 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54113) NullPointerException in XcodeProjectParser.listXcodeSchemes
Title: Message Title Kazuhide Takahashi commented on JENKINS-54113 Re: NullPointerException in XcodeProjectParser.listXcodeSchemes David Hedbor I'm fixed a bug that failed parsing in some Xcode projects and incomplete processing due to malfunction of Xcode project parser. There is a snapshot of the plug-in which modified the following URL, so I am glad that you can try it. https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fxcode-plugin/detail/PR-99/1/artifacts 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54507) pipeline_data is not pushing to influxdb
Title: Message Title Mohamed Nazeer Mohamed Ibrahim commented on JENKINS-54507 Re: pipeline_data is not pushing to influxdb Thanks for replying Yes https://issues.jenkins-ci.org/browse/JENKINS-53360 this kind of solution for pipeline data. Is there any possibility to get it done in near future. And also we referred the below link for the data collection by influxdb plugin. https://sap.github.io/jenkins-library/steps/influxWriteData/ According to this page we could not get the step data and pipeline data by default. Do we need to do any configuration changes. Thanks 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54535) Expose build parameters in RunWrapper
Title: Message Title Craig Ringer commented on JENKINS-54535 Re: Expose build parameters in RunWrapper PR https://github.com/jenkinsci/workflow-support-plugin/pull/81 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54535) Expose build parameters in RunWrapper
Title: Message Title Craig Ringer created an issue Jenkins / JENKINS-54535 Expose build parameters in RunWrapper Issue Type: Patch Assignee: Unassigned Components: workflow-support-plugin Created: 2018-11-08 04:34 Priority: Minor Reporter: Craig Ringer RunWrapper doesn't offer any way to access a run's build parameters. To address that, this patch adds new getBuildParameters() and getBuildParametersAsStrings() methods to RunWrapper. The former getBuildParameters method returns a parameter-type specific Object. It auto-wraps run parameters in a RunWrapper, returns string and boolean parameters as their base type, and otherwise returns whatever the parameter value is. Parameters marked sensitive are returned as their ParameterValue object with no unwrapping. This means scripts can't interact with all parameter types without extra approvals, but they can get the true parameter values and work with the common ones. The getBuildParametersAsStrings() method instead returns stringified forms of the parameters. These may be less useful for script logic, e.g. when a run name is returned instead of a RunWrapper. But it's much easier to use and more useful for diagnostic output and reporting to the user. Add Comment
[JIRA] (JENKINS-54534) SSH failing when HTTP proxy is in use
Title: Message Title
Alex Harvey updated an issue
Jenkins / JENKINS-54534
SSH failing when HTTP proxy is in use
Change By:
Alex Harvey
When using Jenkins behind an HTTP proxy, the EC2 launcher also tries to route traffic through the proxy.h3. To reproduceConfigure an HTTP proxy in Manage Jenkins > Manage Plugins > AdvancedSet a Server and Port for an HTTP Proxy.Then configure the EC2 plugin and try to launch a slave.h3. What I expectThe HTTP proxy, which is there for jobs that need to connect by HTTP to the Internet [ref|https://wiki.jenkins.io/display/JENKINS/JenkinsBehindProxy], should be ignored, because the EC2 plugin is not trying to open an HTTP connection, nor is it normally trying to send traffic to the Internet.h3. What actually happensAn error message is might be seen in the slave instance launch log like:{code}INFO: Failed to connect via ssh: HTTP Proxy Error (403 Forbidden){code} Eventually, the slave will fail to launch. h3. More infoIt looks like this issue was introduced in JENKINS-18855 in [this|https://github.com/jenkinsci/ec2-plugin/commit/e1f37936a18dc3e6a371009c3a6a2ac7d5512c2c] commit. Commit message notes, "It uses HTTP proxy defined in Plugin configuration. SOCKS proxy is not supported".This issue was reported again e.g. in JENKINS-30041 and a workaround was proposed, namely adding no_proxy=10.x.x.x. This issue was then closed, however, and the workaround there might work sometimes but not always.A better solution would be to add a SOCKS proxy feature for the EC2 plugin rather than inheriting proxy settings from Jenkins.
Add Comment
[JIRA] (JENKINS-54534) SSH failing when HTTP proxy is in use
Title: Message Title
Alex Harvey updated an issue
Jenkins / JENKINS-54534
SSH failing when HTTP proxy is in use
Change By:
Alex Harvey
When using Jenkins behind an HTTP proxy, the EC2 launcher also tries to route traffic through the proxy.h3. To reproduceConfigure an HTTP proxy in Manage Jenkins > Manage Plugins > AdvancedSet a Server and Port for an HTTP Proxy.Then configure the EC2 plugin and try to launch a slave.h3. What I expectThe HTTP proxy, which is there for jobs that need to connect by HTTP to the Internet [ref|https://wiki.jenkins.io/display/JENKINS/JenkinsBehindProxy], should be ignored, because the EC2 plugin is not trying to open an HTTP connection, nor is it normally trying to send traffic to the Internet.h3. What actually happensAn error message is seen in the slave instance launch log like:{code}INFO: Failed to connect via ssh: HTTP Proxy Error (403 Forbidden){code}h3. More infoIt looks like this issue was introduced in JENKINS-18855 in [this|https://github.com/jenkinsci/ec2-plugin/commit/e1f37936a18dc3e6a371009c3a6a2ac7d5512c2c] commit. Commit message notes, "It uses HTTP proxy defined in Plugin configuration. SOCKS proxy is not supported".This issue was reported again e.g. in JENKINS-30041 and a workaround was proposed, namely adding no_proxy=10.x.x.x. This workaround issue was then closed , however, and the workaround there might work sometimes but not always.A better solution presumably would be to add a SOCKS proxy feature for the EC2 plugin rather than inheriting proxy settings from Jenkins.
Add Comment
[JIRA] (JENKINS-54534) SSH failing when HTTP proxy is in use
Title: Message Title
Alex Harvey updated an issue
Jenkins / JENKINS-54534
SSH failing when HTTP proxy is in use
Change By:
Alex Harvey
When using Jenkins behind an HTTP proxy, the EC2 launcher also tries to route traffic through the proxy.h3. To reproduceConfigure an HTTP proxy in Manage Jenkins > Manage Plugins > AdvancedSet a Server and Port for an HTTP Proxy.Then configure the EC2 plugin and try to launch a slave.h3. What I expectThe HTTP proxy, which is there for jobs that need to connect by HTTP to the Internet [ref|https://wiki.jenkins.io/display/JENKINS/JenkinsBehindProxy], should be ignored, because the EC2 plugin is not trying to open an HTTP connection, nor is it normally trying to send traffic to the Internet.h3. What actually happensAn error message is seen in the slave instance launch log like:{code}INFO: Failed to connect via ssh: HTTP Proxy Error (403 Forbidden){code} h3. More info It looks like this issue was introduced in JENKINS-18855 in [this|https://github.com/jenkinsci/ec2-plugin/commit/e1f37936a18dc3e6a371009c3a6a2ac7d5512c2c] commit. Commit message notes, "It uses HTTP proxy defined in Plugin configuration. SOCKS proxy is not supported".This issue was reported again e.g. in JENKINS-30041 and a workaround was proposed, namely adding no_proxy=10.x.x.x. This workaround, however, might work sometimes but not always.A better solution presumably would be to add a SOCKS proxy feature for the EC2 plugin rather than inheriting proxy settings from Jenkins.
Add Comment
This message was sent by
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title shao dong commented on JENKINS-54529 Re: CAN NOT get build number with jenkins API Another question is how to get the current build name. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54534) SSH failing when HTTP proxy is in use
Title: Message Title
Alex Harvey updated an issue
Jenkins / JENKINS-54534
SSH failing when HTTP proxy is in use
Change By:
Alex Harvey
h3. Summary When using Jenkins behind an HTTP proxy, the EC2 launcher also tries to route traffic through the proxy.h3. To reproduceConfigure an HTTP proxy in Manage Jenkins > Manage Plugins > AdvancedSet a Server and Port for an HTTP Proxy.Then configure the EC2 plugin and try to launch a slave.h3. What I expectThe HTTP proxy, which is there for jobs that need to connect by HTTP to the Internet [ref|https://wiki.jenkins.io/display/JENKINS/JenkinsBehindProxy], should be ignored, because the EC2 plugin is not trying to open an HTTP connection, nor is it normally trying to send traffic to the Internet.h3. What actually happensAn error message is seen in the slave instance launch log like:{code}INFO: Failed to connect via ssh: HTTP Proxy Error (403 Forbidden){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54534) SSH failing when HTTP proxy is in use
Title: Message Title Alex Harvey created an issue Jenkins / JENKINS-54534 SSH failing when HTTP proxy is in use Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-11-08 03:59 Priority: Minor Reporter: Alex Harvey Summary When using Jenkins behind an HTTP proxy, the EC2 launcher also tries to route traffic through the proxy. To reproduce Configure an HTTP proxy in Manage Jenkins > Manage Plugins > Advanced Set a Server and Port for an HTTP Proxy. Then configure the EC2 plugin and try to launch a slave. What I expect The HTTP proxy, which is there for jobs that need to connect by HTTP to the Internet ref, should be ignored, because the EC2 plugin is not trying to open an HTTP connection, nor is it normally trying to send traffic to the Internet. What actually happens An error message is seen in the slave instance launch log like: INFO: Failed to connect via ssh: HTTP Proxy Error (403 Forbidden)
[JIRA] (JENKINS-54533) Polling is not working with Poll mail box trigger plugin even it is finding the mail
Title: Message Title Amar Nadh created an issue Jenkins / JENKINS-54533 Polling is not working with Poll mail box trigger plugin even it is finding the mail Issue Type: Task Assignee: Nick Grealy Components: poll-mailbox-trigger-plugin Created: 2018-11-08 03:50 Environment: Jenkins-2.121.3 Poll mail box trigger plugin-1.026 Labels: plugin Priority: Critical Reporter: Amar Nadh Jenkins is able to find the mail, but polling is not getting started or sometimes it is running very late.. Note: I didn't update Jenkins version/Plugin version. I tried restarting also but didn't work. Please see below: Connecting to the mailbox... Found properties: [attachments:IGNORE] [folder:INBOX] host:[1...@gmail.com [mail.debug:false] [mail.debug.auth:false]
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title shao dong commented on JENKINS-54529 Re: CAN NOT get build number with jenkins API At the same time, I found that the contents of the two were inconsistent. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54532) Document how to get parameters from a Run
Title: Message Title Craig Ringer commented on JENKINS-54532 Re: Document how to get parameters from a Run Pull https://github.com/jenkinsci/jenkins/pull/3724 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54532) Document how to get parameters from a Run
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-54532
Document how to get parameters from a Run
Change By:
Craig Ringer
It's very hard for someone new to Jenkins' internal structure (perhaps a Pipeline script author) to figure out how to get build parameters, environment variables, etc from a{{ Run }} .Address this with a documentation change that directs the reader to the {{ Actionable }} {{ superclass's getAction(Class) , }} and {{ getAllActions() }} methods, and to {{ ParametersAction }} as an example.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54532) Document how to get parameters from a Run
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-54532
Document how to get parameters from a Run
Change By:
Craig Ringer
It's very hard for someone new to Jenkins' internal structure (perhaps a Pipeline script author) to figure out how to get build parameters, environment variables, etc from a {{Run}}.Address this with a documentation change that directs the reader to the {{Actionable}} {{ superclass's {{ getAction(Class)}} and {{getAllActions() }} methods, and to {{ParametersAction}} as an example.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54532) Document how to get parameters from a Run
Title: Message Title Craig Ringer created an issue Jenkins / JENKINS-54532 Document how to get parameters from a Run Issue Type: Patch Assignee: Unassigned Components: core Created: 2018-11-08 02:59 Priority: Minor Reporter: Craig Ringer It's very hard for someone new to Jenkins' internal structure (perhaps a Pipeline script author) to figure out how to get build parameters, environment variables, etc from a Run. Address this with a documentation change that directs the reader to the Actionable superclass's getAction(Class), getAllActions() methods, and to ParametersAction as an example. Add Comment
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile That one could be solved with a simple s/getLogFile/getLogText/ I think. I can look at having WorkflowRun avoid creating multiple temp files like 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54531) Document that buildVariables is the child environment, not parameters
Title: Message Title Craig Ringer commented on JENKINS-54531 Re: Document that buildVariables is the child environment, not parameters Pull request 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54531) Document that buildVariables is the child environment, not parameters
Title: Message Title Craig Ringer edited a comment on JENKINS-54531 Re: Document that buildVariables is the child environment, not parameters Pull request : https://github.com/jenkinsci/workflow-support-plugin/pull/80 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54531) Document that buildVariables is the child environment, not parameters
Title: Message Title Craig Ringer updated an issue Jenkins / JENKINS-54531 Document that buildVariables is the child environment, not parameters Change By: Craig Ringer I found the description of RunWrapper.getBuildVariables a bit incomplete/confusing:> buildVariables>> for a non-Pipeline downstream build, offers access to a map of defined build variables; for a > Pipeline downstream build, any variables set globally on envso I suggest changing it, appending:> Child Pipeline jobs can use this to report additional information to the parent job by setting environment variables in env . Build Note that build parameters are not shown in buildVariables. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54531) Document that buildVariables is the child environment, not parameters
Title: Message Title Craig Ringer created an issue Jenkins / JENKINS-54531 Document that buildVariables is the child environment, not parameters Issue Type: Patch Assignee: Unassigned Components: workflow-support-plugin Created: 2018-11-08 02:31 Priority: Minor Reporter: Craig Ringer I found the description of RunWrapper.getBuildVariables a bit incomplete/confusing: > buildVariables > > for a non-Pipeline downstream build, offers access to a map of defined build variables; for a >Pipeline downstream build, any variables set globally on env so I suggest changing it, appending: > Child jobs can use this to report additional information to the parent job by setting environment variables. Build parameters are not shown in buildVariables. Add Comment
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title runze xia updated an issue Jenkins / JENKINS-54512 can not change workspace in k8s pipeline Change By: runze xia Summary: can not change workspace in piepline k8s pipeline 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title runze xia updated an issue Jenkins / JENKINS-54512 can not change workspace in k8s pipeline Change By: runze xia Component/s: kubernetes-plugin Component/s: core 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title runze xia commented on JENKINS-54512 Re: can not change workspace in k8s pipeline I found the problem, I can switch to any directory under `/home/jenkins`, but I can't switch to other directories outside. Is it because the user who runs the jenkins master? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54530) Upgrade mavenMinimalVersion from 3.1.0 to at least 3.5.0 (later is better)
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-54530 Upgrade mavenMinimalVersion from 3.1.0 to at least 3.5.0 (later is better) Issue Type: Task Assignee: Olivier Lamy Components: maven-plugin Created: 2018-11-08 02:19 Priority: Minor Reporter: Olivier Lamy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title runze xia commented on JENKINS-54529 Re: CAN NOT get build number with jenkins API The items in the queue are constantly changing. Maybe the items in the queue have already been consumed? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title runze xia commented on JENKINS-54529 Re: CAN NOT get build number with jenkins API I think you will assign the wrong module to the issue. Maybe this is a core issue? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title runze xia updated an issue Jenkins / JENKINS-54529 CAN NOT get build number with jenkins API Change By: runze xia Component/s: core Component/s: queue-cleanup-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title
shao dong updated an issue
Jenkins / JENKINS-54529
CAN NOT get build number with jenkins API
Change By:
shao dong
when i build a jenkins jobthenopen [/queue/item/1484/api/json|http://xxx.com/queue/item/1484/api/json] in chrome have can return "executable":{ "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "/job/ops-svn-update/213/" }but open[/queue/item/1484/api/json|http://xxx.com/queue/item/1484/api/json] with PHP API curl, NOT return"executable":{ "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "/job/ops-svn-update/213/" } version:[Jenkins ver. 2.138.1|https://jenkins.io/]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title
shao dong updated an issue
Jenkins / JENKINS-54529
CAN NOT get build number with jenkins API
Change By:
shao dong
when i build one a jenkins jobthenopen [/queue/item/1484/api/json|http://xxx.com/queue/item/1484/api/json] in chrome have return "executable":{ "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "/job/ops-svn-update/213/" }but open[/queue/item/1484/api/json|http://xxx.com/queue/item/1484/api/json] with PHP API curl, NOT return"executable":{ "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "/job/ops-svn-update/213/" } version:[Jenkins ver. 2.138.1|https://jenkins.io/]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title shao dong updated an issue Jenkins / JENKINS-54529 CAN NOT get build number with jenkins API Change By: shao dong Priority: Minor Critical 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title
shao dong updated an issue
Jenkins / JENKINS-54529
CAN NOT get build number with jenkins API
Change By:
shao dong
when i build one jobthenopen [ /queue/item/1484/api/json| http://xxx.com/queue/item/1484/api/json] in chrome have return "executable":{ "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": " http: / /xxx.com/ job/ops-svn-update/213/" }but open [ /queue/item/1484/api/json| http://xxx.com/queue/item/1484/api/json] with PHP API curl, NOT return"executable":{ "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": " http: / /xxx.com/ job/ops-svn-update/213/" } version:[Jenkins ver. 2.138.1|https://jenkins.io/]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title
shao dong updated an issue
Jenkins / JENKINS-54529
CAN NOT get build number with jenkins API
Change By:
shao dong
when i build one job then open [ http://xxx.com/queue/item/1484/api/json ] in chrome have return "executable": { { "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "http://xxx.com/job/ops-svn-update/213/" }but open [http://xxx.com/queue/item/1484/api/json] with PHP API curl, NOT return"executable": { { "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "http://xxx.com/job/ops-svn-update/213/" } version:[Jenkins ver. 2.138.1|https://jenkins.io/]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title
shao dong created an issue
Jenkins / JENKINS-54529
CAN NOT get build number with jenkins API
Issue Type:
Bug
Assignee:
runze xia
Components:
queue-cleanup-plugin
Created:
2018-11-08 02:00
Priority:
Minor
Reporter:
shao dong
when i build one job open http://xxx.com/queue/item/1484/api/json in chrome have return "executable": { "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "http://xxx.com/job/ops-svn-update/213/" } but open http://xxx.com/queue/item/1484/api/json with PHP API curl, NOT return "executable": { "_class": "hudson.model.FreeStyleBuild", "number": 213, "url": "http://xxx.com/job/ops-svn-update/213/" } version:Jenkins ver. 2.138.1
Add Comment
[JIRA] (JENKINS-54528) Gitlab Enterprise 11 API v3 group no longer supported
Title: Message Title
John Zheng created an issue
Jenkins / JENKINS-54528
Gitlab Enterprise 11 API v3 group no longer supported
Issue Type:
Bug
Assignee:
Mohamed El Habib
Components:
gitlab-oauth-plugin
Created:
2018-11-08 01:29
Priority:
Critical
Reporter:
John Zheng
/api/v3/groups for Jenkins Enterprise 11 return {"error":"API V3 is no longer supported. Use API V4 instead."} Tried to enter api link manually in the configuration page then login page api in the code shows /api/v4/api/v3/groups Any way to force use API V4? Also found that /api/v3/user still works for Gitlab Enterprise 11. /api/v4/user and /api/v4/groups both works find in Gitlab Enterprise 11. Thanks
Add Comment
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Nick Jones commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Sure enough, uninstalling the linenumbers-plugin and rerunning my problematic build generated just 1 "deprecated*.log" file, and I have only one "Avoid calling getLogFile" error in the logs, which comes from hudson.plugins.warnings.WarningsPublisher.parseConsoleLog. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54113) NullPointerException in XcodeProjectParser.listXcodeSchemes
Title: Message Title Kazuhide Takahashi started work on JENKINS-54113 Change By: Kazuhide Takahashi 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Nick Jones commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile I've added the linenumbers-plugin here, as it too has this issue now that workflow-job 2.26 is released. In my case, it seems to generate hundreds to thousands of copies of the original log file, all named with "deprecated" (e.g., deprecated5973622952721928030.log). I haven't figured out what causes the particular quantity of these files (I've seen over 6000 created by a single build), but it seems perhaps related to how the build was executed – triggering a build directly generates 1, but triggering a build from another build (in my case, a Pipeline build that spawns a number of builds to do a regression test) generates hundreds to thousands of copies. These all coincide with log messages in the Jenkins log like: java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at org.jenkinsci.plugins.linenumbers.LineNumbersAnnotator.annotate(LineNumbersAnnotator.java:54) at hudson.console.ConsoleAnnotator$1Aggregator.annotate(ConsoleAnnotator.java:114) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:145) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) Given the impact to the master node to store this number of files (6000 files = 14GB for a single build, in my case), and unless I know it's something other than this bug that causes it, I'd think it makes sense to raise to Major (if not Blocker), if the affected plugins don't have their own issues tracking this problem. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Nick Jones Component/s: linenumbers-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54281) Test Result Trend is broken
Title: Message Title Nikolas Falco commented on JENKINS-54281 Re: Test Result Trend is broken Could you post the generated report? In my PC I do not have cmake installed and I would not install all cmake stack to perform the test. Keep in mind that the image is generated by the junit-plugin and not from the xunit-plugin. xunit just converto cpp test report into junit report. Could you also post the URl of the broken image? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54504) Performance issue with promoted builds and Git branch parameter
Title: Message Title Josh Schreuder commented on JENKINS-54504 Re: Performance issue with promoted builds and Git branch parameter Boguslaw Klimas thank you! Setting a default value helped massively. We were indeed using TOP with no default value. After setting a default value the job pages now load very quickly. I am not well versed in Java, so I'm not sure I can provide a PR myself. I will try to take a look at a permanent fix if I have some time. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7242) confusing error when report directory is empty
Title: Message Title yamini k reopened an issue Jenkins / JENKINS-7242 confusing error when report directory is empty Change By: yamini k Resolution: Incomplete Status: Resolved Reopened 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7242) confusing error when report directory is empty
Title: Message Title yamini k commented on JENKINS-7242 Re: confusing error when report directory is empty Hello, I am facing this issue now, I see the error : [htmlpublisher] Archiving HTML reports... [htmlpublisher] Archiving at BUILD level C:\Users\216591\Jenkins\workspace\mob-android-test\Reports to /var/lib/jenkins/jobs/mob-android-test/builds/175/htmlreports/Report ERROR: Directory 'C:\Users\216591\Jenkins\workspace\mob-android-test\Reports' exists but failed copying to '/var/lib/jenkins/jobs/mob-android-test/builds/175/htmlreports/Report'. ERROR: This is especially strange since your build otherwise succeeded. Build step 'Publish HTML reports' changed build result to FAILURE Finished: FAILURE I see my Reports directory in my workspace is empty, May I know how to get this resolved? Thank you. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54527) Delivery Pipeline plugin - "Enable Start of new build" - "Build Now" button should get replaced with "Build with parameters" if pipeline has parameteres
Title: Message Title asas asas created an issue Jenkins / JENKINS-54527 Delivery Pipeline plugin - "Enable Start of new build" - "Build Now" button should get replaced with "Build with parameters" if pipeline has parameteres Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2018-11-07 22:50 Priority: Minor Reporter: asas asas We are using Delivery Pipeline plugin to view our pipeline. There is one option in Delivery Pipeline "Enable Start of new build" , As shown above if we click on Build Now then we get below error. Its been observed that "Build Now" option doesn't work with pipeline having parameters. Can we implement fix to detect if pipeline has parameters then option should be "Build With Parameters" instead of Build now. Add Comment
[JIRA] (JENKINS-54525) java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title Patrick Darragh updated JENKINS-54525 duplicate ticket. i forgot the version number. Jenkins / JENKINS-54525 java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) Change By: Patrick Darragh 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54526) jira version 2.150 java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title Patrick Darragh created an issue Jenkins / JENKINS-54526 jira version 2.150 java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 2018-11-07 22:07 Environment: jira version 2.150 Labels: plugin CVSRoot Priority: Minor Reporter: Patrick Darragh version Jenkins ver. 2.150 A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at
[JIRA] (JENKINS-54127) Add new option to pipeline - sshagent
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54127 Add new option to pipeline - sshagent Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: pipeline 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Boguslaw Klimas commented on JENKINS-54171 Re: Git parameter branch selector becomes slow after a period of time Hi Andrei Brajnicov You can do Thread dump (http://YOUR_JENKINS_HOST/threadDump) during page are loaded, maybe you can get some interesting information. Good example is in this issue JENKINS-54504 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-54333 Projects are triggered twice by "build with parameters" Change By: Thorsten Scherler Attachment: diff.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"
Title: Message Title Thorsten Scherler commented on JENKINS-54333 Re: Projects are triggered twice by "build with parameters" I can reproduce it and tried different things but it seems to be IE and YUI in combination. diff.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54525) java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title Patrick Darragh created an issue Jenkins / JENKINS-54525 java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 2018-11-07 21:34 Priority: Minor Reporter: Patrick Darragh A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:717) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:778) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:474) at
[JIRA] (JENKINS-54504) Performance issue with promoted builds and Git branch parameter
Title: Message Title Boguslaw Klimas edited a comment on JENKINS-54504 Re: Performance issue with promoted builds and Git branch parameter Hi,If you haven't set 'Default Value' and you have 'Selected Value' set as TOP, during invoke method getDefaultParameterValue by PromotionProcess.getDefaultParameterValuesAsEnvVarsplugin invoke git command look on [github| [ https://github.com/jenkinsci/git-parameter-plugin/blob/8fbc25e3f8e3b83cbba75abe8cc25fccabb8077d/src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java#L139-L163]. ] Perhaps the solution to this issue will be setting a 'Default Value' in git-parameter 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54504) Performance issue with promoted builds and Git branch parameter
Title: Message Title Boguslaw Klimas commented on JENKINS-54504 Re: Performance issue with promoted builds and Git branch parameter Hi, If you haven't set 'Default Value' and you have 'Selected Value' set as TOP, during invoke method getDefaultParameterValue by PromotionProcess.getDefaultParameterValuesAsEnvVars plugin invoke git command look on github Perhaps the solution to this issue will be setting a 'Default Value' in git-parameter 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54376) needs documentation
Title: Message Title Tomas Salazar commented on JENKINS-54376 Re: needs documentation https://plugins.jenkins.io/nvm-wrapper 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54524) Improper Encoding of Sync Status
Title: Message Title Tim Foster created an issue Jenkins / JENKINS-54524 Improper Encoding of Sync Status Issue Type: Bug Assignee: Craig Rodrigues Components: scm-sync-configuration-plugin Created: 2018-11-07 20:56 Environment: When SCM-Sync has failed to sync properly, and is showing the page footer prompting to "Click here" to clear the logs of failures. Jenkins 2.150 All browsers Priority: Minor Reporter: Tim Foster All the HTML tags within the lowest layer of were HTML encoded, so rather than being interpreted as tags, they were interpreted as plain text. This broke the link to clear the log. Add Comment
[JIRA] (JENKINS-54325) Support multiple SimplePageDecorators for login and signup page footers
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54325 Support multiple SimplePageDecorators for login and signup page footers Change By: Matt Sicker Summary: Support multiple SimplePageDecorators for login and signup page footers 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54325) Support multiple SimplePageDecorators for login and signup page footers
Title: Message Title
Matt Sicker updated an issue
Jenkins / JENKINS-54325
Support multiple SimplePageDecorators for login and signup page footers
Change By:
Matt Sicker
In {{login.jelly}}, this uses {{SimplePageDecorator}} instead of the typical {{PageDecorator}} used on most other pages. The latter decorator supports registering multiple instances so that they can all be included in various pages. The former, however, only uses the first instance found. By doing this, plugins cannot override the default login page decorations without needlessly copying code from Jenkins Core to emulate it.What I'd like is for the login page to list out all registered decorators for the footer in order rather than just the first one.This also applies to the {{signup.jelly}} 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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54523) Ability to stop an UNSTABLE declarative pipeline
Title: Message Title Jon B created an issue Jenkins / JENKINS-54523 Ability to stop an UNSTABLE declarative pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-11-07 20:38 Priority: Minor Reporter: Jon B I have a pipeline with with many steps. If my unit tests fail, I want to mark the pipeline as UNSTABLE and then to stop the pipeline. I am using Declarative style. I cannot figure out how to stop the pipeline from continuing. If I use error(), the pipeline does stop but it also gets marked as failed. Am I missing something? Can a pipeline be BOTH marked as UNSTABLE and also stop progress? Add Comment
[JIRA] (JENKINS-48344) Log files generated by Jenkins pipeline scripts are bloated
Title: Message Title Jesse Glick commented on JENKINS-48344 Re: Log files generated by Jenkins pipeline scripts are bloated Nick Jones no, with the global setting enabled the timestamps step/option does nothing besides print a warning that it is doing nothing. Your issue is some instance of JENKINS-54128, with the exact cause visible by checking the stack trace in your system log. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53771) Include vSphere Cloud in Cloud Statistics report
Title: Message Title pjdarton commented on JENKINS-53771 Re: Include vSphere Cloud in Cloud Statistics report The repo to fork from (and submit PRs to) is .../jenkinsci/vsphere-cloud-plugin "mvn install" will build it. "mvn hpi:run" will run a local Jenkins with just that plugin. I don't have any magic documentation myself (it is a bit of a "learning curve"), but I've found the two commands above fairly useful. Also, if you make a PR, the jenkinsci infrastructure should auto-build it for you, and you can download the .hpi file from it if you wish. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51698) Failed to check out svn ....svn: E200030: FULL
Title: Message Title Harald Villinger commented on JENKINS-51698 Re: Failed to check out svn svn: E200030: FULL The line org.tmatesoft.svn.core.SVNException: svn: E200030: FULL seems to indicate some basic SVN problems. Did you check disk space, permissions? What version of SVN do you use? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53771) Include vSphere Cloud in Cloud Statistics report
Title: Message Title Nick Jones commented on JENKINS-53771 Re: Include vSphere Cloud in Cloud Statistics report I'd be happy to look into a PR although am not set up to build the plugin, and lacking instructions at https://github.com/medianick/vsphere-cloud-plugin am not sure how to get started (I have the JDK and Maven and can clone the repo but beyond that am stuck). The generic instructions at https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial are not enough help. Would you be able to give me some direction there? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48344) Log files generated by Jenkins pipeline scripts are bloated
Title: Message Title
Nick Jones edited a comment on JENKINS-48344
Re: Log files generated by Jenkins pipeline scripts are bloated
Running the custom Timestamper plugin build in [~jglick]'s previous comment, on our test Jenkins instance, with a {{timestamps}} block in a Scripted Pipeline job but with the global "Enabled for all Pipeline builds" checkbox checked, I'm seeing 6681 "deprecated*.log" files -- each the same size as the "log" file (2328MB) -- created on our master node by a _single build_, all within a few minutes of each other. This is consuming 14GB+ of space for this one build, which would be catastrophic for disk space if we applied the same updates to our production Jenkins instance (where there are hundreds of jobs building hundreds of times per day). This {{timestamps}} block is still in place because our production Jenkins system hasn't had its plugins changed, and uses the same Jenkinsfile for this particular job, and with the hundreds of jobs we have in place, coordinating the removal of a {{timestamps}} block in GitHub across all these Jenkinsfiles with the upgrade of the Timestamper (and/or other plugins) would be exceptionally difficult. I'm assuming (perhaps wrongly) that these "deprecated" files are being generated by some interaction between this block and the newer plugin(s) in this system, but perhaps it's something else.Is the only way forward to remove all the {{timestamps}} blocks or options from all our Jenkinsfiles first, then upgrading these plugins? Or is something else going on?
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48344) Log files generated by Jenkins pipeline scripts are bloated
Title: Message Title Nick Jones commented on JENKINS-48344 Re: Log files generated by Jenkins pipeline scripts are bloated Running the custom Timestamper plugin build in Jesse Glick's previous comment, on our test Jenkins instance, with a timestamps block in a Scripted Pipeline job but with the global "Enabled for all Pipeline builds" checkbox checked, I'm seeing 6681 "deprecated*.log" files – each the same size as the "log" file (2328MB) – created by a single build, all within a few minutes of each other. This is consuming 14GB+ of space for this one build, which would be catastrophic for disk space if we applied the same updates to our production Jenkins instance (where there are hundreds of jobs building hundreds of times per day). This timestamps block is still in place because our production Jenkins system hasn't had its plugins changed, and uses the same Jenkinsfile for this particular job, and with the hundreds of jobs we have in place, coordinating the removal of a timestamps block in GitHub across all these Jenkinsfiles with the upgrade of the Timestamper (and/or other plugins) would be exceptionally difficult. I'm assuming (perhaps wrongly) that these "deprecated" files are being generated by some interaction between this block and the newer plugin(s) in this system, but perhaps it's something else. Is the only way forward to remove all the timestamps blocks or options from all our Jenkinsfiles first, then upgrading these plugins? Or is something else going on? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54213) MAC OS linked clone
Title: Message Title babak khoueinia commented on JENKINS-54213 Re: MAC OS linked clone Thank you pjdarton. I actually tried adding the VM to the list of known hosts on jenkins master: https://support.cloudbees.com/hc/en-us/articles/11573552-Host-Key-Verification-for-SSH-Agents And tried all the combinations but still no luck. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54522) Host JDK Tool Plugin download failing
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-54522 Host JDK Tool Plugin download failing Change By: Devin Nusbaum Assignee: Devin Nusbaum 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54522) Host JDK Tool Plugin download failing
Title: Message Title Devin Nusbaum commented on JENKINS-54522 Re: Host JDK Tool Plugin download failing Brendan Holmes Those URLs come straight from the crawler (You can see them listed here https://updates.jenkins.io/updates/hudson.tools.JDKInstaller.json), so you'd need to update this file so that it produces the right links for JDK 10 (maybe as simple as fixing the initial landing page for JDK 10?). If you want to take that on, I am happy to review your work, but I do not expect to be able to work on this myself anytime soon. If the "Install from java.sun.com" method is currently broken, how are people using the official JDK with Jenkins? See this comment in JENKINS-54305 for recommended ways to use a specific JDK. "Install from java.sun.com" should be considered deprecated and I would not use 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title Keith Zantow commented on JENKINS-41488 Re: Pipeline view automatically scrolls down I'd also note: JENKINS-41088 is a slightly different ask, but could fairly well be accommodated by implementing this. I'll add that after using the tool for a while, I also find myself less interested in following along a particular stage than seeing the graph to click around. At one point, long ago, I did some work to "fix" this behavior somewhat, but it didn't disable following by default. Perhaps I can resurrect the pertinent parts of that if I get some time. Or perhaps a simple button to follow/not follow that's saved in browser storage or something similar would suffice; not sure the right UX for it – suggestions welcome. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title Keith Zantow edited a comment on JENKINS-41488 Re: Pipeline view automatically scrolls down I'd also note: JENKINS-41088 is a slightly different ask, but could fairly well somewhat be accommodated by implementing this. I'll add that after using the tool for a while, I also find myself less interested in following along a particular stage than seeing the graph to click around. At one point, long ago, I did some work to "fix" this behavior somewhat, but it didn't disable following by default. Perhaps I can resurrect the pertinent parts of that if I get some time. Or perhaps a simple button to follow/not follow that's saved in browser storage or something similar would suffice; not sure the right UX for it -- suggestions welcome. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled
Title: Message Title Keith Yates commented on JENKINS-53539 Re: org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled This continues to occur. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title oskar stenman reopened an issue This is definitely not resolved, or handled by the referenced issue. Some builds we run ends up launching 15 parallel tasks (building AMI's for AWS environment), and i want to look at one of these. The pipeline view's _javascript_ makes it very very hard to select which one of those parallel tasks I want to watch as it's scrolling down to the bottom every few seconds, so i basically have to wait until everything is done (half an hour) before i can even select the right build and see what happened IN THE BEGINNING of this build to figure out what's wrong. Next, if i manage to pick the correct parallel build it somehow still manages to switch the console output to the output of another build if that one's finished before the one i'm currently watching.. To be honest, this autoscrolling behavior is useless for most of our scenarios as we run a lot of stuff in parallel. It might be ok to autoscroll-down if the user is already on the bottom of the page and you add more text, but don't mess with where my scrollbar is on the page otherwise. If i want to place it on the middle of the page to investigate something, let me do that. Currently the behaviour prohibits this as it's impossible to do anything but watch the last few lines as long as a build with a lot of text output is running. Either disable autoscrolling completely or only make it apply whenever a user has scrolled down to bottom. Jenkins / JENKINS-41488 Pipeline view automatically scrolls down Change By: oskar stenman Resolution: Duplicate Status: Closed Reopened Add Comment
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Brendan Holmes commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free JDK10 is still available, but the plugin now has the wrong URL for it. Per the issue I've just opened, first part of the URL should be: http://download.oracle.com/otn instead of: http://download.oracle.com/otn-pub Can we get this corrected? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54522) Host JDK Tool Plugin download failing
Title: Message Title Brendan Holmes created an issue Jenkins / JENKINS-54522 Host JDK Tool Plugin download failing Issue Type: Bug Assignee: Devin Nusbaum Attachments: Untitled.png Components: jdk-tool-plugin Created: 2018-11-07 18:16 Priority: Major Reporter: Brendan Holmes I'm on jdk-tool:1.1 and Jenkins 2.138.2. I've configured JDK10 in Global Tools per the attached screenshot. When running a job that uses it, I get: Installing JDK jdk-10.0.2-oth-JPR Downloading JDK from http://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.io.IOException: Failed to request https://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz?AuthParam=1541612216_106847a9a60b4e512bb6e81d31a78d22 exit code=404 I believe these URLs should be: http://download.oracle.com/otn instead of: http://download.oracle.com/otn-pub I've tried using other installer methods such as Extract *.zip/*.tar.gz and also the Custom Tool plugin instead, but these lack the authentication-handling needed to download JDK from Oracle. If the "Install from java.sun.com" method is currently broken, how are people using the official JDK with Jenkins? Doesn't seem to be a public docker image for it. Is everyone using openjdk instead? Or maintaining their own jdk docker images?
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Jesse Glick commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox JENKINS-54233 was recently reported, though I cannot reproduce it and it does not seem to have anything to do with clicking buttons (though it does look like a _javascript_ issue). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) Gcc parser does not resolve absolute paths
Title: Message Title Ulli Hafner commented on JENKINS-54035 Re: Gcc parser does not resolve absolute paths If it is possible, please also attach one of your console log files, then I just can see if I can fix it without setting up a C project. (Or send it via mail if it contains sensible data.) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) Gcc parser does not resolve absolute paths
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-54035 Gcc parser does not resolve absolute paths Change By: Ulli Hafner Summary: can't exclude everything under a given dir Gcc parser does not resolve absolute paths Component/s: analysis-model Component/s: warnings-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54233) Pipeline Script textarea missing
Title: Message Title Jesse Glick commented on JENKINS-54233 Re: Pipeline Script textarea missing If this started in 2.148 then theoretically the change by Thorsten Scherler for JENKINS-53462 could be responsible. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47881) Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Title: Message Title Andrew Bayer updated JENKINS-47881 Jenkins / JENKINS-47881 Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive Change By: Andrew Bayer Status: Reopened Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-50754 "ERROR: Could not find credentials matching (rolename)" when using AWS role Change By: Andrew Bayer Component/s: docker-commons-plugin Component/s: pipeline-model-definition-plugin Assignee: Andrew Bayer 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54519) Onelogin Groups Parameter pass as one value instead of a List
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54519 Re: Onelogin Groups Parameter pass as one value instead of a List by the way this is the correct way to send groups ``` developer browser ``` your integration is doing this that it is completely wrong ``` developer,browser ``` 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50907) customWorkspace setting of agent directive does not support EXECUTOR_NUMBER
Title: Message Title Andrew Bayer commented on JENKINS-50907 Re: customWorkspace setting of agent directive does not support EXECUTOR_NUMBER The problem here is that we generate the custom workspace string before we're actually on the agent. I'm not sure how we can work around that at this point - I'll think on 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54519) Onelogin Groups Parameter pass as one value instead of a List
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-54519 Onelogin Groups Parameter pass as one value instead of a List Change By: Ivan Fernandez Calvo Issue Type: Bug New Feature 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54519) Onelogin Groups Parameter pass as one value instead of a List
Title: Message Title Ivan Fernandez Calvo closed an issue as Won't Do Jenkins / JENKINS-54519 Onelogin Groups Parameter pass as one value instead of a List Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Won't Do 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54519) Onelogin Groups Parameter pass as one value instead of a List
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54519 Re: Onelogin Groups Parameter pass as one value instead of a List it is not a standard method to pass groups, indeed is a workaround, I ask to this in the past, I do not want to support weird, not standard behaviors see this PR for more info https://github.com/jenkinsci/saml-plugin/pull/34 Check it your IdP can integrate with your LDAP/AD in a way that returns a list, I know that OneLogin works with the plugins, so it should be possible, contact with OneLogin support. if after all, you want to make it, It can be done implementing a securityListener like this https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/user/LoginDetailsProperty.java#L128-L168 , it should replace the authorities with a list instead of an element, but this should be done in another plugin not here is not SAML standard. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43386) Not sending mail to user with permission to view
Title: Message Title Matt Drees commented on JENKINS-43386 Re: Not sending mail to user with permission to view We've run into this too. We're using the " Github Authentication Plugin" and the "GitHub Committer Authorization Strategy". I noticed it appears that email addresses owned by admins (as defined by users listed in the GitHub Authorization Settings->Admin User Names field) are not filtered out. Non-admin jenkins user's email addresses are filtered out with the "Not sending mail to user u...@cru.org with no permission to view" message. So this leads me to hypothesize there's a bug in either the github plugin, or how it is used by other components for authorization decisions. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52439) newContainerPerStage does not provide a clean container
Title: Message Title Andrew Bayer resolved as Not A Defect Jenkins / JENKINS-52439 newContainerPerStage does not provide a clean container Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Klaus Schniedergers commented on JENKINS-45719 Re: Description for a pipeline run is not compatible and cannot be disabled Adding this to the startup options worked to disable display of descriptions for runs in BlueOcean (haven't tried in recent versions): -Dblueocean.feature.run.description.enabled=false 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53151) withContext not working as expected in combination with consoleLogFilter
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-53151 withContext not working as expected in combination with consoleLogFilter Change By: Andrew Bayer Component/s: workflow-basic-steps-plugin Component/s: pipeline Component/s: pipeline-model-definition-plugin Assignee: Andrew Bayer 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53473) Support implicit checkout behavior override
Title: Message Title Andrew Bayer updated JENKINS-53473 Jenkins / JENKINS-53473 Support implicit checkout behavior override Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53711) Pipeline customWorkspace not obeyed in docker agent when reuseNode is true
Title: Message Title Andrew Bayer updated JENKINS-53711 Jenkins / JENKINS-53711 Pipeline customWorkspace not obeyed in docker agent when reuseNode is true Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54190) All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Title: Message Title Andrew Bayer resolved as Won't Fix Jenkins / JENKINS-54190 All of the parallel stages with a regression post trigger will trigger if one of the stages fail. Change By: Andrew Bayer Status: Open Resolved Resolution: Won't 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54190) All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Title: Message Title Andrew Bayer commented on JENKINS-54190 Re: All of the parallel stages with a regression post trigger will trigger if one of the stages fail. Yes - regression and fixed can only look at the whole build's status, so are really only useful for post at the end of the build. Sorry. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47881) Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Title: Message Title Koen Bruyninckx commented on JENKINS-47881 Re: Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive Hi Andrew, sorry I missed your previous post, I did it indeed similar to your proposal, and it works thx! 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. For more options, visit https://groups.google.com/d/optout.
