[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Ulli Hafner commented on JENKINS-61293 Re: NPE from second recordIssues step Ok, fixed in upstream https://github.com/jenkinsci/analysis-model/pull/311. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.3267.1583222040215%40Atlassian.JIRA.
[JIRA] (JENKINS-60687) Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB
Title: Message Title Aleksi Simell updated JENKINS-60687 Jenkins / JENKINS-60687 Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB Change By: Aleksi Simell Status: Fixed but Unreleased Resolved Released As: 2.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203931.1578474488000.3263.1583220840642%40Atlassian.JIRA.
[JIRA] (JENKINS-60687) Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB
Title: Message Title Aleksi Simell closed an issue as Done Jenkins / JENKINS-60687 Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB Change By: Aleksi Simell Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203931.1578474488000.3265.1583220840770%40Atlassian.JIRA.
[JIRA] (JENKINS-60687) Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB
Title: Message Title Aleksi Simell updated JENKINS-60687 Jenkins / JENKINS-60687 Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB Change By: Aleksi Simell Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203931.1578474488000.3261.1583220840545%40Atlassian.JIRA.
[JIRA] (JENKINS-61304) EC2 Plugin terminates instances temporarily offline
Title: Message Title
Umberto Nicoletti created an issue
Jenkins / JENKINS-61304
EC2 Plugin terminates instances temporarily offline
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2020-03-03 07:18
Environment:
Jenkins 2.204.2 EC2 Plugin 1.49.1
Priority:
Minor
Reporter:
Umberto Nicoletti
The latest version of the plugin added code to catch instances that were started, and then failed to connect to Jenkins. Previously such instances would stay up forever incurring unnecessary costs. The code block that adds this functionality is: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java#L167-L185 Note hos whe termination branch is guarded by the clause `computer.isOffline()` which is unfortunately too broad. Looking up the definition of `computer.isOffline()` yields this code: {{ @Exported public boolean isOffline() {}} return temporarilyOffline || getChannel()==null; } This reveals that temporarilyOffline is considered too: as a result an instance that has sucessfully connected, but is, for example, under temporary maintenance will be abruptly terminated by the plugin. AFAICT there is no simple workaround, besides perhaps rewriting `if (computer.isOffline()){` to `if (computer.getChannel()==null){` I'll try to submit a patch asap
[JIRA] (JENKINS-61303) warnings-ng-plugin: Exception when creating relative paths
Title: Message Title Bernd Rausch created an issue Jenkins / JENKINS-61303 warnings-ng-plugin: Exception when creating relative paths Issue Type: Bug Assignee: Ulli Hafner Attachments: exception.txt Components: warnings-ng-plugin Created: 2020-03-03 07:16 Environment: Jenkins 2.222 Warnings Next Generation 8.0.0 Priority: Minor Reporter: Bernd Rausch Since the update to Warnings Next Generation 8.0.0, all C# projects in our environment fail because of the following exception: [MSBuild] -> found 147 issues (skipped 1481 duplicates)[MSBuild] -> found 147 issues (skipped 1481 duplicates)ERROR: Build step failed with exceptionjava.lang.IllegalArgumentException: 'other' has different root at sun.nio.fs.WindowsPath.relativize(WindowsPath.java:392) at The full stack trace is in the attachment. This seems to be a result of the following improvement: JENKINS-58538 JENKINS-57556 Replace absolute paths with relative paths for issues (#358) @uhafner Perhaps this jdk bug is also relevant: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6226081
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61293 NPE from second recordIssues step Thanks, that helped! now I can reproduce the bug. Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/415 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.3245.1583218920299%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title ethorsa commented on JENKINS-61253 Re: Remoting using WebSocket fails with "Handshake response not received" Exception Great, thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204820.1582797002000.3243.1583218380266%40Atlassian.JIRA.
[JIRA] (JENKINS-61297) Parameter to SQLScript from pipeline project using class SQLPlusRunnerBuilder
Title: Message Title Vinaypal Singh commented on JENKINS-61297 Re: Parameter to SQLScript from pipeline project using class SQLPlusRunnerBuilder Thanks For response. You mean to say from script type as File, we will call one normal scripts from inside we need to call our parameter based script, but i think it will not solve the purpose of passing parameters to sql scripts, how inner sql scripts will identify the parameters. Can you please elaborate more about your suggestion to solve this problem. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204874.1583175778000.3241.1583212500138%40Atlassian.JIRA.
[JIRA] (JENKINS-61183) Can't able save golbal config in jenkins after install Extension Plugin (V2.68)
Title: Message Title Alex Earl commented on JENKINS-61183 Re: Can't able save golbal config in jenkins after install Extension Plugin (V2.68) I am unable to reproduce this issue based on the information given. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204727.1582313426000.3237.1583211540203%40Atlassian.JIRA.
[JIRA] (JENKINS-61183) Can't able save golbal config in jenkins after install Extension Plugin (V2.68)
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-61183 Can't able save golbal config in jenkins after install Extension Plugin (V2.68) Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204727.1582313426000.3239.1583211540230%40Atlassian.JIRA.
[JIRA] (JENKINS-60984) Editable Email Notification not working for Trigger Failure.
Title: Message Title Alex Earl closed an issue as Duplicate Jenkins / JENKINS-60984 Editable Email Notification not working for Trigger Failure. Change By: Alex Earl Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204452.1580946416000.3234.1583210040430%40Atlassian.JIRA.
[JIRA] (JENKINS-61297) Parameter to SQLScript from pipeline project using class SQLPlusRunnerBuilder
Title: Message Title Fernando Boaglio commented on JENKINS-61297 Re: Parameter to SQLScript from pipeline project using class SQLPlusRunnerBuilder Sorry, there is no support for SQL*Plus parameters, maybe you can create manually a SQL script before calling it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204874.1583175778000.3202.1583206860555%40Atlassian.JIRA.
[JIRA] (JENKINS-37194) Allow Tokens via Token Macro plugin
Title: Message Title Andrew Sumner closed an issue as Won't Fix This issue has been hanging around for a long time and I'm unlikely to get to it. Jenkins / JENKINS-37194 Allow Tokens via Token Macro plugin Change By: Andrew Sumner Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this
[JIRA] (JENKINS-61299) breaking forward slash inserted in download with proget jenkins plugin
Title: Message Title Andrew Sumner commented on JENKINS-61299 Re: breaking forward slash inserted in download with proget jenkins plugin Which version of the plugin? I've just released version 1.4 so wondering if I made a breaking change - not that I should have changed anything in that area. It might take me a couple of days to get to the bottom of this - just moved and have yet to get development environment up and running again. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204879.1583187475000.3186.1583205300144%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Jesse Rittner commented on JENKINS-60764 Re: Allow configuration per folder rather than globally Chris Kilding I'm not terribly familiar with cross-account credentials, but I have some concerns. What specifically will stop a malicious developer from accessing the production secrets from their feature branch job and printing them out? Also, I noticed a comment that says "The secret name must be unique across all AWS accounts that Jenkins uses." We require that secret names be identical across the three accounts to maintain consistency. To clarify, we are not interested in pulling secrets from multiple accounts within a given multibranch pipeline. Rather, each pipeline should only have access to one of the three accounts. it sounds like your intended setup is that Jenkins will run in a shared AWS tools account Can you clarify what you mean by this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204025.1579015116000.3184.1583204520154%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Fred G commented on JENKINS-61294 Re: Jenkins node disconnects frequently because of that job fails. It's not clear why this issue was assigned to the build-node-column-plugin component, therefore reassigning to core and unassigning myself. Please also provide more context about the master and the build agent. Which OS? Java version? etc. Did this issue exist from the beginning? Did it appear suddenly? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204871.1583165063000.3152.1583196660142%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Fred G updated an issue Jenkins / JENKINS-61294 Jenkins node disconnects frequently because of that job fails. Change By: Fred G Component/s: core Component/s: build-node-column-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204871.1583165063000.3148.1583196480265%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Fred G assigned an issue to Unassigned Jenkins / JENKINS-61294 Jenkins node disconnects frequently because of that job fails. Change By: Fred G Assignee: Fred G Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204871.1583165063000.3150.1583196480299%40Atlassian.JIRA.
[JIRA] (JENKINS-61147) load build parameters during repository scan
Title: Message Title Brandon Fryslie edited a comment on JENKINS-61147 Re: load build parameters during repository scan This is not necessary if you are using the Job DSL plugin - (which you should be regardless) - . Instead of defining the parameters in your Jenkinsfile, put them in the .groovy file where your Job DSL is defined. Then the parameters are available on the initial run of the job.[https://jenkinsci.github.io/job-dsl-plugin/] EDIT: Apologies, I wasn't implying that this isn't a valid feature request. However, using the Job DSL allows you to achieve what you are asking, and it makes your life easier in the long run as well. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204677.1582120134000.3145.1583194980159%40Atlassian.JIRA.
[JIRA] (JENKINS-61302) Slave to Agent Renaming: Role Strategy Plugin Documentation
Title: Message Title Nigel Armstrong created an issue Jenkins / JENKINS-61302 Slave to Agent Renaming: Role Strategy Plugin Documentation Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2020-03-02 23:11 Priority: Minor Reporter: Nigel Armstrong Slave to agent renaming was done in Jenkins-43058 but the documentation has not been updated and still mentions project and slave Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-53763) Help texts overflow the browse screen
Title: Message Title Zbynek Konecny edited a comment on JENKINS-53763 Re: Help texts overflow the browse screen [~lianq] can you still reproduce this with latest Jenkins? Also you seem to be using some custom theme, maybe that's the problem? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194271.1537871763000.3135.158319138%40Atlassian.JIRA.
[JIRA] (JENKINS-53763) Help texts overflow the browse screen
Title: Message Title Zbynek Konecny commented on JENKINS-53763 Re: Help texts overflow the browse screen lian qiang can you still reproduce this with latest Jenkins? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194271.1537871763000.3133.1583189880141%40Atlassian.JIRA.
[JIRA] (JENKINS-61301) Rest API endpoint for user permissions
Title: Message Title Alexander Simbirtsev created an issue Jenkins / JENKINS-61301 Rest API endpoint for user permissions Issue Type: New Feature Assignee: Unassigned Components: core Created: 2020-03-02 22:24 Priority: Minor Reporter: Alexander Simbirtsev We need REST API endpoint to access the list of User permissions for all existing Jobs. Another way to implement this feature is to add permissions information to /user/[userId]/api/ endpoint. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-61299) breaking forward slash inserted in download with proget jenkins plugin
Title: Message Title Max Cascone updated an issue Jenkins / JENKINS-61299 breaking forward slash inserted in download with proget jenkins plugin Change By: Max Cascone Summary: breaking forward slash inserted in downloadprogetpackage download with proget jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204879.1583187475000.3119.1583187780198%40Atlassian.JIRA.
[JIRA] (JENKINS-61300) Search field size wrong after screen resize and for long texts
Title: Message Title Zbynek Konecny updated an issue Jenkins / JENKINS-61300 Search field size wrong after screen resize and for long texts Change By: Zbynek Konecny More detailed description in [https://github.com/jenkinsci/jenkins/pull/4522] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204880.1583187672000.3117.1583187780138%40Atlassian.JIRA.
[JIRA] (JENKINS-61300) Search field size wrong after screen resize and for long texts
Title: Message Title Zbynek Konecny created an issue Jenkins / JENKINS-61300 Search field size wrong after screen resize and for long texts Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-02 22:21 Priority: Minor Reporter: Zbynek Konecny Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-61299) breaking forward slash inserted in downloadprogetpackage jenkins plugin
Title: Message Title
Max Cascone updated an issue
Jenkins / JENKINS-61299
breaking forward slash inserted in downloadprogetpackage jenkins plugin
Change By:
Max Cascone
When using the download directive in the jenkins plugin, it inserts a forward slash at the start of the destination string, which breaks the download to a windows agent: {code:java} downloadProgetPackage downloadFolder: "${WORKSPACE}/${deployLocation}", downloadFormat: 'zip', feedName: 'PlatDev', groupName: "Relativity/${env.appName}/${BRANCH_NAME}", packageName: "${env.appName}", version: 'Latest' ${WORKSPACE} == pwd() == D:\ workspace\_5649 workspace_5649 -PS-jenkins-deploy-pipeline${deployLocation} == 'deploy' {code} *Result*: {code:java} [ProGet] Download package to /D:\ workspace\_5649 workspace_5649 -PS-jenkins-deploy-pipeline/deploy {code} has anyone seen this, resolved it?I am currently working around it by using the raw url download: {code:java} httpRequest outputFile: "${deployLocation}/${appName}.zip", responseHandle: 'NONE', url: 'http://proget.consilio.com/upack/PlatDev/download/Relativity/ProcessingSync/PLATDEV-5649-PS-jenkins-deploy-pipeline/ProcessingSync?latest=zip' {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61299) breaking forward slash inserted in downloadprogetpackage jenkins plugin
Title: Message Title
Max Cascone created an issue
Jenkins / JENKINS-61299
breaking forward slash inserted in downloadprogetpackage jenkins plugin
Issue Type:
Bug
Assignee:
Andrew Sumner
Components:
inedo-proget-plugin
Created:
2020-03-02 22:17
Environment:
Jenkins v2.204.2 on windows and linux
Priority:
Minor
Reporter:
Max Cascone
When using the download directive in the jenkins plugin, it inserts a forward slash at the start of the destination string, which breaks the download to a windows agent: downloadProgetPackage downloadFolder: "${WORKSPACE}/${deployLocation}", downloadFormat: 'zip', feedName: 'PlatDev', groupName: "Relativity/${env.appName}/${BRANCH_NAME}", packageName: "${env.appName}", version: 'Latest' ${WORKSPACE} == pwd() == D:\workspace_5649-PS-jenkins-deploy-pipeline ${deployLocation} == 'deploy' Result: [ProGet] Download package to /D:\workspace_5649-PS-jenkins-deploy-pipeline/deploy has anyone seen this, resolved it? I am currently working around it by using the raw url download: httpRequest outputFile: "${deployLocation}/${appName}.zip", responseHandle: 'NONE', url: 'http://proget.consilio.com/upack/PlatDev/download/Relativity/ProcessingSync/PLATDEV-5649-PS-jenkins-deploy-pipeline/ProcessingSync?latest=zip'
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Nick Jones commented on JENKINS-61293 Re: NPE from second recordIssues step Great suggestion, Ulli Hafner. I've attached the sanitized (structure-only) versions of those open-tasks*.xml files from the last successful build (using v7). I don't see anything with TreeString in it, but then the builds with v8 don't generate these files at all, so the only ones I can examine are the older v7 ones. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.3110.1583186340234%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-61293 NPE from second recordIssues step Change By: Nick Jones Attachment: open-tasks-new-issues.xml Attachment: open-tasks-outstanding-issues.xml Attachment: open-tasks-blames.xml Attachment: open-tasks-fixed-issues.xml Attachment: open-tasks-forensics.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Ulli Hafner commented on JENKINS-61295 Re: Illegal argument exception from warnings-ng plugin It is not yet released... I need to wrap that library in the Jenkins plugin but that needs some time until this lib has been pushed to maven central... (tomorrow) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204872.158316597.3104.1583185860139%40Atlassian.JIRA.
[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines
Title: Message Title Ulli Hafner commented on JENKINS-56699 Re: Provide formatter for messages that contain newlines I see, you are looking for an newbie issue that you can fix? Currently some parsers create multiline messages and descriptions (in plain text using newlines as separator). If these messages are shown in the UI, then the newlines are simply ignored since they have no meaning in HTML. So the fix would be to detect the newlines and show the information in a better way. Example: Set a breakpoint in https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/test/java/io/jenkins/plugins/analysis/warnings/StepsITest.java#L275 and open the Jenkins under test (you need to suspend the test thread only). This parser creates a 2 line message. It has newlines in the issue.message property but in the UI it is shown in a single line. It would make sense to either put everything into a * or to insert after each line. (The same is true for the description if I remember correctly). I'm not sure if such a change can be applied to all parsers or if we should have a property for parsers that already report messages or descriptions in HTML. But we can check this afterwards if the fix is working for some of the multi-line parsers... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Samuel Loretan commented on JENKINS-58249 Re: Perforce plugin: JCasC cannot export configuration David Rodriguez – not Paul, but P4BaseCredentials is an abstract base class, you probably want one of its concrete implementation instead (P4PasswordImpl or P4TicketImpl). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200312.1561709954000.3097.1583185200207%40Atlassian.JIRA.
[JIRA] (JENKINS-60857) Wildcard certificates rejected by Winstone after Jetty update
Title: Message Title Jesse Glick commented on JENKINS-60857 Re: Wildcard certificates rejected by Winstone after Jetty update This is known to be broken in 2.204.3. Either go back to 2.204.2, or wait for 2.204.4. Please do not comment further in JIRA or the pull request. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204231.1579860751000.3072.1583184720637%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title
Ulli Hafner edited a comment on JENKINS-61293
Re: NPE from second recordIssues step
Does one of the {{ [Jenkins-HOME]/jobs/[job]/builds/[number]/open-tasks-*xml }} files contain the text {{TreeString}}?Maybe you can send the xml tags from the 4 files from the build (from 7.x)? See https://superuser.com/questions/731760/how-to-delete-values-from-xml-in-notepad on how to remove the values. (Or use the regex {{>.*<}} and replace with {{><}} in an IDE.)Example I need:{code}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.3068.1583184660152%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title
Ulli Hafner commented on JENKINS-61293
Re: NPE from second recordIssues step
Does one of the {{ [Jenkins-HOME]/jobs/[job]/builds/[number]/open-tasks-*xml }} files contain the text TreeString? Maybe you can send the xml tags from the 4 files from the build (from 7.x)? See https://superuser.com/questions/731760/how-to-delete-values-from-xml-in-notepad on how to remove the values. (Or use the regex >.*< and replace with >< in an IDE.) Example I need:
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.3065.1583184600142%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Jesse Glick updated JENKINS-61197 Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Released As: 2.223 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204745.1582545957000.3062.1583184420438%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Jesse Glick Assignee: Oleg Nenashev Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204745.1582545957000.3060.1583184420409%40Atlassian.JIRA.
[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines
Title: Message Title Benjamin Cross edited a comment on JENKINS-56699 Re: Provide formatter for messages that contain newlines Sorry, I'm very newbie and want to ensure I am understanding the improvement you are asking for. I see the SourcePrinter has a render method. When the message is rendered it uses the Sanitizer. Are you asking for a new method to put that message into html for the createTitle method where each new line is considered a newbreak ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198337.1553335794000.3057.1583183880139%40Atlassian.JIRA.
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Christoph Fetzer commented on JENKINS-61295 Re: Illegal argument exception from warnings-ng plugin Great! This was fast. I'll try it tomorrow. Thanks so far! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204872.158316597.3054.1583183820199%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Ulli Hafner started work on JENKINS-61293 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.3051.1583183580230%40Atlassian.JIRA.
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61295 Illegal argument exception from warnings-ng plugin Change By: Ulli Hafner Released As: https://github.com/uhafner/codingstyle/releases/tag/codingstyle-1.0.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204872.158316597.3048.1583182980328%40Atlassian.JIRA.
[JIRA] (JENKINS-60857) Wildcard certificates rejected by Winstone after Jetty update
Title: Message Title
Steven Fransen commented on JENKINS-60857
Re: Wildcard certificates rejected by Winstone after Jetty update
I update my jenkins to LTS 2.204.3 and it would not even launch
$ cat failed-boot-attempts.txt Mon Mar 02 08:01:43 PST 2020 Mon Mar 02 08:08:07 PST 2020 Mon Mar 02 08:08:54 PST 2020 Mon Mar 02 08:35:52 PST 2020 Mon Mar 02 08:37:10 PST 2020 Mon Mar 02 08:40:31 PST 2020 Mon Mar 02 08:42:34 PST 2020 Mon Mar 02 08:44:01 PST 2020 Mon Mar 02 08:46:54 PST 2020 Mon Mar 02 08:47:53 PST 2020 Mon Mar 02 08:56:15 PST 2020 [08:58:31] root@mtjenkins01/var/lib/jenkins $ cat /var/log/jenkins/jenkins.log Running from: /usr/lib/jenkins/jenkins.war 2020-03-02 16:56:15.111+ [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMax is now deprecated 2020-03-02 16:56:15.127+ [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMaxIdle is now deprecated 2020-03-02 16:56:15.132+ [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @498ms to org.eclipse.jetty.util.log.JavaUtilLog 2020-03-02 16:56:15.179+ [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file 2020-03-02 16:56:15.207+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath 2020-03-02 16:56:15.412+ [id=1] INFO winstone.Logger#logInternal: Exclude Ciphers [^.*_(MD5|SHA|SHA1)$, ^TLS_RSA_.*$, ^SSL_.*$, ^.*_NULL_.*$, ^.*_anon_.*$] 2020-03-02 16:56:15.438+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.25.v20191220; built: 2019-12-20T17:00:00.294Z; git: a9729c7e7f33a459d2616a8f9e9ba8a90f432e95; jvm 1.8.0_222-b10 2020-03-02 16:56:15.645+ [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet 2020-03-02 16:56:15.679+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0 2020-03-02 16:56:15.679+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults 2020-03-02 16:56:15.681+ [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 66ms 2020-03-02 16:56:15.967+ [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/lib/jenkins found at: SystemProperties.getProperty("JENKINS_HOME") 2020-03-02 16:56:16.038+ [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@2a7ed1f{Jenkins v2.204.3,/,file:///var/cache/jenkins/war/,AVAILABLE}{/var/cache/jenkins/war} 2020-03-02 16:56:16.084+ [id=1] INFO o.e.j.util.ssl.SslContextFactory#load: x509=X509@463fd068(mtcoveritydb01,h=[],w=[]) for SslContextFactory@895e367[provider=null,keyStore=null,trustStore=null] 2020-03-02 16:56:16.084+ [id=1] INFO o.e.j.util.ssl.SslContextFactory#load: x509=X509@1b266842(starfieldclass2ca,h=[],w=[]) for SslContextFactory@895e367[provider=null,keyStore=null,trustStore=null] 2020-03-02 16:56:16.085+ [id=1] INFO o.e.j.util.ssl.SslContextFactory#load: x509=X509@7a3793c7(taiwangrca,h=[],w=[]) for SslContextFactory@895e367[provider=null,keyStore=null,trustStore=null] 2020-03-02 16:56:16.085+ [id=1] INFO o.e.j.util.ssl.SslContextFactory#load: x509=X509@42b3b079(itservices.def.com,h=[gaalpa2adssrv53.itservices.def.com, itservices.def.com, gaalpa2adssrv53, itservices, its-ad-ldap.it.xxx.com, its-ad-ldap.lrns.def.com, its-ad-ldap.cci.xxx.com],w=[]) for SslContextFactory@895e367[provider=null,keyStore=null,trustStore=null] 2020-03-02
[JIRA] (JENKINS-61298) BasicBranchBuildStrategies is not building tags anymore
Title: Message Title Scott Hubbard created an issue Jenkins / JENKINS-61298 BasicBranchBuildStrategies is not building tags anymore Issue Type: Bug Assignee: Unassigned Attachments: image-2020-03-02-13-51-28-142.png, Screen Shot 2020-03-02 at 1.48.41 PM.png Components: basic-branch-build-strategies-plugin Created: 2020-03-02 20:59 Environment: Jenkins 2.222, Basic Branch Build Strategies Plugin 1.3.2, GitHub Branch Source Plugin 2.6.0 Priority: Minor Reporter: Scott Hubbard I have a dozen or so Jenkins jobs that are configured to be built from GitHub tags. We have a GitHub Enterprise server on-prem that we use. It was all working fine up until a couple days ago. I have not made any config changes or upgrades to Jenkins around the time it stopped working (Jenkins was upgraded 19 days ago). In the Jenkins job, if I view "Multibranch Pipeline Events" I can see that the webhooks are triggered, but they are not built. [Mon Mar 02 19:49:59 GMT 2020] Received Push event for tag 0.3.5.8 in repository docker-images/echo-webserver CREATED event from 192.168.47.5 ⇒ https://jenkins.mycompany.com/github-webhook/ with timestamp Mon Mar 02 19:49:54 GMT 2020 19:50:01 Connecting to https://github.mycompany.com/api/v3 using jenkins/** (Jenkins service account) Examining docker-images/echo-webserver Checking branches... Getting remote
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Ivan Fernandez Calvo updated JENKINS-38779 Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.3019.1583182800758%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Ivan Fernandez Calvo updated JENKINS-38779 Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Ivan Fernandez Calvo Status: Closed Fixed but Unreleased Resolution: Fixed Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.3016.1583182800706%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-38779 Re: Group Attribute while setting up Saml SSO Deenadayalan Ramamoorthy please, do not change closed issues, it was resolved as incomplete and in that state should be Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.3013.1583182740243%40Atlassian.JIRA.
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Ulli Hafner commented on JENKINS-61295 Re: Illegal argument exception from warnings-ng plugin I see, seems that Windows does throw another exception if the relative path cannot be obtained... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204872.158316597.3009.1583182440213%40Atlassian.JIRA.
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Ulli Hafner started work on JENKINS-61295 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204872.158316597.3005.1583182380179%40Atlassian.JIRA.
[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines
Title: Message Title Benjamin Cross edited a comment on JENKINS-56699 Re: Provide formatter for messages that contain newlines Sorry, I'm very newbie and want to ensure I am understanding the improvement you are asking for. I see the SourcePrinter has a render method. When the message is rendered it uses the Sanitizer. Are you asking for a new method to put that message into html for the createTitle method where each new line is considered a new ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198337.1553335794000.3003.1583182200107%40Atlassian.JIRA.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title
David Rodriguez commented on JENKINS-58249
Re: Perforce plugin: JCasC cannot export configuration
Hi Paul, Would like to test this fix but I need to some help on how to configure the JCasC jenkins.yaml file for the P4 credential. Below is my attempt to add P4 credential to the jenkins.yaml file and restart jenkins. Getting stacktrace : java.lang.IllegalArgumentException: No com.cloudbees.plugins.credentials.Credentials implementation found for P4BaseCredentials"
// code placeholder
credentials:
system:
domainCredentials:
- credentials:
- basicSSHUserPrivateKey:
description: "Private key credentials for Jenkins GitLab user"
id: "gitlab-key"
privateKeySource:
directEntry:
privateKey: ${GITLAB_PRIVATE_KEY}
scope: GLOBAL
username: ${JENKINS_GITLAB_USER_NAME}
- P4BaseCredentials:
description: "Perforce password credential"
id: "p4-userpass"
p4port: "${PERFORCE_SERVER}:${PERFORCE_PORT}"
scope: GLOBAL
username: ${PERFORCE_USER_NAME}
password: ${PERFORCE_PASSWORD}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines
Title: Message Title Benjamin Cross commented on JENKINS-56699 Re: Provide formatter for messages that contain newlines Sorry, I'm very newbie and want to ensure I am understanding the improvement you are asking for. I see the SourcePrinter has a render method. When the message is rendered it uses the Sanitizer. Are you asking for a new method to put that message into html for the createTitle method? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198337.1553335794000.2995.1583182140354%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error Sorry, have been busy moving house so haven't had access. This plugin was specifically designed for universal packages and there are no plans at present to support nuget (however you're welcome to raise an issue with Inedo and if approved I would work on it). A quick google found this article which might give you some guidance. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.2993.1583181720096%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Nick Jones commented on JENKINS-61293 Re: NPE from second recordIssues step All I can see in the system log is this: 2020-03-02 20:37:38.094+ [id=11719] WARNING h.util.RobustReflectionConverter#doUnmarshal: Cannot convert type edu.hm.hafner.util.TreeString to type java.lang.String Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.2990.1583181600150%40Atlassian.JIRA.
[JIRA] (JENKINS-59832) Multiple inheritFrom templates ignored in declarative pipeline
Title: Message Title Andrey Cherkashin commented on JENKINS-59832 Re: Multiple inheritFrom templates ignored in declarative pipeline Thomas Ramé I ended up making a single large pod template and inherit that one instead of having neat composable templates. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202567.1571344897000.2984.1583181000136%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Nick Jones commented on JENKINS-61293 Re: NPE from second recordIssues step The job name and source code files do disclose some proprietary information so I would have to produce sanitized versions in order to be able to send them to you or post them here. Are there questions I could answer about the files (e.g., their structure) without sending the files themselves? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.2981.1583180760198%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Michael Tupitsyn edited a comment on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams Is there any way we can expedite the PR merge? The workaround with configure block works, but it introduces performance implication (with configure block, DSL plugin re-formats config XML with every run and restores some optional element elements and attributes). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.2973.1583178180289%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Michael Tupitsyn commented on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams Is there any way we can expedite the PR merge? The workaround with configure block works, but it introduces performance implication (with configure block, DSL plugin re-formats config XML with every run and restores some optional element and attributes). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.2964.1583178060409%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Deenadayalan Ramamoorthy updated JENKINS-38779 Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Deenadayalan Ramamoorthy Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.2960.1583177760335%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Deenadayalan Ramamoorthy updated JENKINS-38779 Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Deenadayalan Ramamoorthy Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.2948.1583177702106%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Deenadayalan Ramamoorthy stopped work on JENKINS-38779 Change By: Deenadayalan Ramamoorthy Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.2952.1583177702172%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Deenadayalan Ramamoorthy updated JENKINS-38779 Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Deenadayalan Ramamoorthy Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.2956.1583177702237%40Atlassian.JIRA.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Deenadayalan Ramamoorthy updated JENKINS-38779 Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Deenadayalan Ramamoorthy Resolution: Incomplete Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175179.1475746431000.2944.1583177640416%40Atlassian.JIRA.
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated JENKINS-38608 Released in git plugin 4.2.0 March 1, 2020 Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174799.1475161307000.2932.1583175781779%40Atlassian.JIRA.
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174799.1475161307000.2939.1583175781966%40Atlassian.JIRA.
[JIRA] (JENKINS-57660) Git plugin stack trace saving job with invalid refspec
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-57660 Git plugin stack trace saving job with invalid refspec Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199593.1558700538000.2925.1583175781590%40Atlassian.JIRA.
[JIRA] (JENKINS-57660) Git plugin stack trace saving job with invalid refspec
Title: Message Title Mark Waite updated JENKINS-57660 Released in git plugin 4.2.0 March 1, 2020 Jenkins / JENKINS-57660 Git plugin stack trace saving job with invalid refspec Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199593.1558700538000.2923.1583175781556%40Atlassian.JIRA.
[JIRA] (JENKINS-61297) Parameter to SQLScript from pipeline project using class SQLPlusRunnerBuilder
Title: Message Title
Vinaypal Singh created an issue
Jenkins / JENKINS-61297
Parameter to SQLScript from pipeline project using class SQLPlusRunnerBuilder
Issue Type:
Task
Assignee:
Fernando Boaglio
Components:
sqlplus-script-runner-plugin
Created:
2020-03-02 19:02
Environment:
Linux
Priority:
Major
Reporter:
Vinaypal Singh
HI Team, I have created 2 String parameter that is SCHEMA_OWNER & SCHEMA_ROLE within Pipeline project and trying to run parameter based sql script(grant_role.sql) with script type as file and passing params as given below. {stage('SQLRunner_DB02'){ step([ $class: 'SQLPlusRunnerBuilder', credentialsId:'BASE_OWNER', instance:'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(Host=127.0.0.1)(Port=1521))(CONNECT_DATA=(SID=ORC:L)))', scriptType:'file', script: 'grant_role.sql ${SCHEMA_OWNER} ${SCHEMA_ROLE}', scriptContent:'', customOracleHome:'/usr/lib/oracle/19.5/client64']) Output::: [DB_Test] $ /usr/lib/oracle/19.5/client64/bin/sqlplus -L BASE_OWNER/BASE_OWNER@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(Host=127.0.0.1)(Port=1521))(CONNECT_DATA=(SID=ORCL))) "@/var/lib/jenkins/workspace/DB_Test/grant_role.sql EST_OWNER TEST_ROLE" SQL*Plus: Release 19.0.0.0.0 - Production on Mon Mar 2 12:04:33 2020 Version 19.5.0.0.0 Copyright (c) 1982, 2019, Oracle. All rights reserved. Last Successful login time: Mon Mar 02 2020 12:04:33 -05:00 Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SP2-0310: unable to open file "/var/lib/jenkins/workspace/DB_Test/grant_role.sql TEST_OWNER TEST_ROLE" Please suggest a way to overcome this problem
[JIRA] (JENKINS-59828) Support the creation of GitSCMFileSystem for tags
Title: Message Title Mark Waite closed an issue as Fixed Released in git plugin 4.2.0 March 1, 2020 Jenkins / JENKINS-59828 Support the creation of GitSCMFileSystem for tags Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202563.1571333622000.2913.1583175720585%40Atlassian.JIRA.
[JIRA] (JENKINS-48625) Several git repo browser URL formats are not checked or documented
Title: Message Title Mark Waite updated JENKINS-48625 Released in git plugin 4.2.0 March 1, 2020 Jenkins / JENKINS-48625 Several git repo browser URL formats are not checked or documented Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-48625) Several git repo browser URL formats are not checked or documented
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-48625 Several git repo browser URL formats are not checked or documented Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187279.1513683224000.2921.1583175721627%40Atlassian.JIRA.
[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"
Title: Message Title Mark Waite updated JENKINS-61065 Released in git plugin 4.2.0 March 1, 2020 as an option to disable multi-build selection. Jenkins / JENKINS-61065 Git plugin: infinite build trigger by "SCM change" Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204548.1581498096000.2915.1583175720701%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite closed an issue as Fixed Release in git client plugin 3.2.0 March 1, 2020. Jenkins / JENKINS-57205 Null pointer exception in JGit pre-build merge Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.2906.1583175660668%40Atlassian.JIRA.
[JIRA] (JENKINS-46360) Unable to run jobs in parallel
Title: Message Title Felipe Almeida updated JENKINS-46360 Jenkins / JENKINS-46360 Unable to run jobs in parallel Change By: Felipe Almeida Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184623.1503438843000.2903.1583173800933%40Atlassian.JIRA.
[JIRA] (JENKINS-46360) Unable to run jobs in parallel
Title: Message Title Felipe Almeida updated JENKINS-46360 PR Merged Jenkins / JENKINS-46360 Unable to run jobs in parallel Change By: Felipe Almeida Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/awslabs/aws-codepipeline-plugin-for-jenkins/releases/tag/aws-codepipeline-0.40 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You
[JIRA] (JENKINS-60048) Forensics date relative to build date
Title: Message Title Ulli Hafner updated JENKINS-60048 Jenkins / JENKINS-60048 Forensics date relative to build date Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202877.1572908734000.2879.1583173141718%40Atlassian.JIRA.
[JIRA] (JENKINS-57638) Custom ids/names not shown in origin when aggregating the report
Title: Message Title Ulli Hafner updated JENKINS-57638 Jenkins / JENKINS-57638 Custom ids/names not shown in origin when aggregating the report Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199568.1558606728000.2894.1583173141929%40Atlassian.JIRA.
[JIRA] (JENKINS-59601) Add parser for JUnit test results
Title: Message Title Ulli Hafner updated JENKINS-59601 Jenkins / JENKINS-59601 Add parser for JUnit test results Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/analysis-model/releases/tag/analysis-model- 8.0.0 -beta5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202242.1569916653000.2892.1583173141907%40Atlassian.JIRA.
[JIRA] (JENKINS-60417) Print log if post processing has been skipped
Title: Message Title Ulli Hafner updated JENKINS-60417 Jenkins / JENKINS-60417 Print log if post processing has been skipped Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203478.1575970934000.2884.1583173141799%40Atlassian.JIRA.
[JIRA] (JENKINS-60973) Use relative paths in remote API
Title: Message Title Ulli Hafner updated JENKINS-60973 Jenkins / JENKINS-60973 Use relative paths in remote API Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204441.1580897215000.2888.1583173141852%40Atlassian.JIRA.
[JIRA] (JENKINS-60148) Result log is modified after attaching the action.
Title: Message Title Ulli Hafner updated JENKINS-60148 Jenkins / JENKINS-60148 Result log is modified after attaching the action. Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203012.1573594621000.2880.1583173141730%40Atlassian.JIRA.
[JIRA] (JENKINS-59617) Create unit test for IconLabelProvider
Title: Message Title Ulli Hafner updated JENKINS-59617 Jenkins / JENKINS-59617 Create unit test for IconLabelProvider Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202258.1569961463000.2871.1583173141615%40Atlassian.JIRA.
[JIRA] (JENKINS-58538) Support for relative paths in folder view
Title: Message Title Ulli Hafner updated JENKINS-58538 Jenkins / JENKINS-58538 Support for relative paths in folder view Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200687.1563409751000.2874.1583173141664%40Atlassian.JIRA.
[JIRA] (JENKINS-57556) Path should be stored relative to workspace
Title: Message Title Ulli Hafner updated JENKINS-57556 Jenkins / JENKINS-57556 Path should be stored relative to workspace Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199467.1558350085000.2886.1583173141823%40Atlassian.JIRA.
[JIRA] (JENKINS-61190) recordIssues with referenceBuildId parameter creates exception Invalid parameter "referenceBuildId"
Title: Message Title Ulli Hafner updated JENKINS-61190 Jenkins / JENKINS-61190 recordIssues with referenceBuildId parameter creates exception Invalid parameter "referenceBuildId" Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 -beta Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204735.158244805.2896.1583173141951%40Atlassian.JIRA.
[JIRA] (JENKINS-60154) Link to Results not clickable when Groovy Parser ID includes Spaces
Title: Message Title Ulli Hafner updated JENKINS-60154 Jenkins / JENKINS-60154 Link to Results not clickable when Groovy Parser ID includes Spaces Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203020.1573635088000.2882.1583173141768%40Atlassian.JIRA.
[JIRA] (JENKINS-60014) Show date for blame of a line
Title: Message Title Ulli Hafner updated JENKINS-60014 Jenkins / JENKINS-60014 Show date for blame of a line Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202836.157260248.2890.1583173141887%40Atlassian.JIRA.
[JIRA] (JENKINS-57401) Show path for files
Title: Message Title Ulli Hafner updated JENKINS-57401 Jenkins / JENKINS-57401 Show path for files Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199185.1557486222000.2876.1583173141687%40Atlassian.JIRA.
[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines
Title: Message Title Ulli Hafner commented on JENKINS-56699 Re: Provide formatter for messages that contain newlines Hmm, I don't think that this has been fixed yet. Or what do you think? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198337.1553335794000.2869.1583173080099%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Ulli Hafner commented on JENKINS-61293 Re: NPE from second recordIssues step Since you have this error you should not upgrade to 8.0 in the production environment. But do you see anything in the system log of Jenkins? (Security violation during serialization or something similar?) Are the tasks you have in your staging environment confidential? Or would it be possible to attach (or send me the files [Jenkins-HOME]/jobs/[job]/builds/[number]/open-tasks-*xml via private Email)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204870.1583163778000.2866.1583172780170%40Atlassian.JIRA.
[JIRA] (JENKINS-61296) Milestone step should allow to optionally define build result
Title: Message Title
Sebastian Häni updated an issue
Jenkins / JENKINS-61296
Milestone step should allow to optionally define build result
Change By:
Sebastian Häni
The {{milestone}} step cancels older builds with result {{NOT_BUILT}}.It should be possible to optionally override this behavior and set it to something else, e.g. {{ABORTED}}.Use case:I want to cancel older PR builds by using this code:{code:java}def buildNumber = env.BUILD_NUMBER as intif (buildNumber > 1) { // aborting previous builds by passing superseding their milestone milestone(buildNumber - 1)}// creating milestone for current buildmilestone(buildNumber){code}This works as expected, older builds are cancelled with result {{NOT_BUILT}}. Now I am using the Bitbucket Branch Source Plugin to automatically report the build status to Bitbucket. In that plugin, the status {{NOT_BUILT}} gets mapped to {{SUCCESS}} in Bitbucket. If I have a Merge Check to prevent merging of the PR, I now have a situation that the build result is {{SUCCESS}} even though it never ran.So I want to be able to customize the cancelled build's result by overriding it in the milestone step. The new parameter is optional, and if not overriden, the behavior should be exactly as it was before. Proposed API:{code}milestone(, < surpassed superseded build's result>){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61296) Milestone step should allow to optionally define build result
Title: Message Title
Sebastian Häni updated an issue
Jenkins / JENKINS-61296
Milestone step should allow to optionally define build result
Change By:
Sebastian Häni
The {{milestone}} step cancels older builds with result {{NOT_BUILT}}.It should be possible to optionally override this behavior and set it to something else, e.g. {{ABORTED}}.Use case:I want to cancel older PR builds by using this code:{code:java}def buildNumber = env.BUILD_NUMBER as intif (buildNumber > 1) { // aborting previous builds by passing their milestone milestone(buildNumber - 1)}// creating milestone for current buildmilestone(buildNumber){code}This works as expected, older builds are cancelled with result {{NOT_BUILT}}. Now I am using the Bitbucket Branch Source Plugin to automatically report the build status to Bitbucket. In that plugin, the status {{NOT_BUILT}} gets mapped to {{SUCCESS}} in Bitbucket. If I have a Merge Check to prevent merging of the PR, I now have a situation that the build result is {{SUCCESS}} even though it never ran.So I want to be able to customize the cancelled build's result by overriding it in the milestone step. The new parameter is optional, and if not overriden, the behavior should be exactly as it was before.Proposed API:{code}milestone(, ){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt edited a comment on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 [~jglick] just tested a bunch combinations, results below.https+websockets * jdk-11 server - the CLI/agent to hang (jdk-8 and jdk-11 agent). * jdk-8 server - the CLI/agent connect as expected (jdk-8 and jdk-11 agent)http+websockets * all combinations of server / CLI/agent jdk work as expected.TLDR - _only_ *jdk-11* server w/*HTTPS* port SERVER_URL hangs (client jdk doesn't matter in this case). To get a self-signed cert that google chrome likes, while using docker for mac, and being limited to the 1 server url is a bit tricky.!image-2020-03-02-09-30-13-234.png!When I can I'll try and extract out the simplest setup to reproduce the behavior. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204765.1582603216000.2850.1583170380204%40Atlassian.JIRA.
[JIRA] (JENKINS-61296) Milestone step should allow to optionally define build result
Title: Message Title
Sebastian Häni created an issue
Jenkins / JENKINS-61296
Milestone step should allow to optionally define build result
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-multibranch-plugin
Created:
2020-03-02 17:31
Labels:
multi-branch milestone
Priority:
Minor
Reporter:
Sebastian Häni
The milestone step cancels older builds with result NOT_BUILT. It should be possible to optionally override this behavior and set it to something else, e.g. ABORTED. Use case: I want to cancel older PR builds by using this code:
def buildNumber = env.BUILD_NUMBER as int
if (buildNumber > 1) {
// aborting previous builds by passing their milestone
milestone(buildNumber - 1)
}
// creating milestone for current build
milestone(buildNumber)
This works as expected, older builds are cancelled with result NOT_BUILT. Now I am using the Bitbucket Branch Source Plugin to automatically report the build status to Bitbucket. In that plugin, the status NOT_BUILT gets mapped to SUCCESS in Bitbucket. If I have a Merge Check to prevent merging of the PR, I now have a situation that the build result is SUCCESS even though it never ran. So I want to be able to customize the cancelled build's result by overriding it in the milestone step. The new parameter is optional, and if not overriden, the behavior should be exactly as it was before.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Jesse Glick just tested a bunch combinations, results below. https+websockets jdk-11 server - the CLI/agent to hang (jdk-8 and jdk-11 agent). jdk-8 server - the CLI/agent connect as expected (jdk-8 and jdk-11 agent) http+websockets all combinations of server / CLI/agent jdk work as expected. TLDR - only jdk-11 server w/HTTPS port SERVER_URL hangs (client jdk doesn't matter in this case). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204765.1582603216000.2845.1583170080180%40Atlassian.JIRA.
[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines
Title: Message Title Benjamin Cross commented on JENKINS-56699 Re: Provide formatter for messages that contain newlines So then can this issue be closed? What HTML tags should be added? Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198337.1553335794000.2841.1583169960206%40Atlassian.JIRA.
[JIRA] (JENKINS-61293) NPE from second recordIssues step
Title: Message Title Nick Jones commented on JENKINS-61293 Re: NPE from second recordIssues step Ah, no. Going back to the reference build for the last successful run of the taskScanner, I get the Angry Jenkins "Oops" page with the same stack trace: java.lang.NullPointerException at edu.hm.hafner.analysis.Report.addAll(Report.java:166) at edu.hm.hafner.analysis.Report.copyIssuesAndProperties(Report.java:639) at edu.hm.hafner.analysis.Report.addAll(Report.java:186) at io.jenkins.plugins.analysis.core.model.AnalysisResult.getIssues(AnalysisResult.java:413) at io.jenkins.plugins.analysis.core.model.IssuesDetail.(IssuesDetail.java:173) at io.jenkins.plugins.analysis.core.model.ResultAction.getTarget(ResultAction.java:315) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:703) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) etc. Should I roll back to a pre-8.0 release and see how these various pages behave? Or is it useful for me to keep this on 8.0? (This is our Staging Jenkins system, so it's not impacting users yet.) Add Comment
[JIRA] (JENKINS-61240) Adding License file to GitHub repo
Title: Message Title Dennis Gu started work on JENKINS-61240 Change By: Dennis Gu Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204797.1582729235000.2833.1583168820253%40Atlassian.JIRA.
[JIRA] (JENKINS-61240) Adding License file to GitHub repo
Title: Message Title Dennis Gu updated an issue Jenkins / JENKINS-61240 Adding License file to GitHub repo Change By: Dennis Gu Adding MIT license file to Veracode scan plugin repo Remove old Veracode License content Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204797.1582729235000.2834.1583168820283%40Atlassian.JIRA.
