[JIRA] (JENKINS-60638) Example on "Releasing a project" is incorrect
Title: Message Title Arjun Gopisetty started work on JENKINS-60638 Change By: Arjun Gopisetty Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203875.1578171274000.2271.1578200580320%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Example on "Releasing a project" is incorrect
Title: Message Title Arjun Gopisetty updated JENKINS-60638 Jenkins / JENKINS-60638 Example on "Releasing a project" is incorrect Change By: Arjun Gopisetty Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203875.1578171274000.2272.1578200580401%40Atlassian.JIRA.
[JIRA] (JENKINS-60362) Gerrit Behaviours not executed
Title: Message Title Luca Domenico Milanesio resolved as Fixed Jenkins / JENKINS-60362 Gerrit Behaviours not executed Change By: Luca Domenico Milanesio Status: Open Resolved Resolution: Fixed Released As: 0.4.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203384.1575450858000.2270.1578190080414%40Atlassian.JIRA.
[JIRA] (JENKINS-60362) Gerrit Behaviours not executed
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60362 Re: Gerrit Behaviours not executed This is caused by the same code issue of JENKINS-60383 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203384.1575450858000.2268.1578190080336%40Atlassian.JIRA.
[JIRA] (JENKINS-60383) Remote nodes unable to checkout code
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60383 Re: Remote nodes unable to checkout code Thanks again Will Wagner for reporting and fixing the problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203433.1575577992000.2265.1578190020427%40Atlassian.JIRA.
[JIRA] (JENKINS-60383) Remote nodes unable to checkout code
Title: Message Title Luca Domenico Milanesio resolved as Fixed Jenkins / JENKINS-60383 Remote nodes unable to checkout code Change By: Luca Domenico Milanesio Status: In Progress Resolved Resolution: Fixed Released As: 0.4.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203433.1575577992000.2263.1578190020385%40Atlassian.JIRA.
[JIRA] (JENKINS-60383) Remote nodes unable to checkout code
Title: Message Title Luca Domenico Milanesio started work on JENKINS-60383 Change By: Luca Domenico Milanesio Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203433.1575577992000.2259.1578189960301%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Let me know how this works for you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2257.1578186180127%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Adding reactive parameters turned out to be a LOT harder than I anticipated, so I've taken a different tack and used the [active choices plugin|https://plugins.jenkins.io/uno-choice.] I've documented this in the attached word document. You can either store the groovy code using the [scriptler|https://plugins.jenkins.io/scriptler []|https://plugins.jenkins.io/uno-choice].] plugin, or directly in the job with the active choice plugin. Select Application and Release.docx Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2255.1578186120286%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner updated an issue Jenkins / JENKINS-60613 Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Change By: Andrew Sumner Attachment: Select Application and Release.docx Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2253.1578185940159%40Atlassian.JIRA.
[JIRA] (JENKINS-60639) Display report link on tasks panel or build summary
Title: Message Title Damian Szczepanik updated an issue Jenkins / JENKINS-60639 Display report link on tasks panel or build summary Change By: Damian Szczepanik Summary: Display report plugin link on tasks panel or build summary Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203876.1578177992000.2251.1578178020193%40Atlassian.JIRA.
[JIRA] (JENKINS-60639) Display report plugin on tasks panel or build summary
Title: Message Title Damian Szczepanik created an issue Jenkins / JENKINS-60639 Display report plugin on tasks panel or build summary Issue Type: Task Assignee: Unassigned Attachments: classic.png Components: blueocean-plugin Created: 2020-01-04 22:46 Priority: Minor Reporter: Damian Szczepanik For the cucumber-reports plugin and the request which has been reported I'd like to add link/icon to the blue ocean which allows to open report which is generated by my plugin for every build. For the classic view attached screenshot presents how this is implemented now. Is it possible if so, share guide or reference commit or even plugin which handles such link. Add Comment
[JIRA] (JENKINS-60449) Optional extensions can blow up Jenkins
Title: Message Title Jesse Glick updated JENKINS-60449 Jenkins / JENKINS-60449 Optional extensions can blow up Jenkins Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed Released As: 2.212 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203527.1576086424000.2248.1578177900258%40Atlassian.JIRA.
[JIRA] (JENKINS-60449) Optional extensions can blow up Jenkins
Title: Message Title Jesse Glick assigned an issue to Vincent Latombe Jenkins / JENKINS-60449 Optional extensions can blow up Jenkins Change By: Jesse Glick Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203527.1576086424000.2245.1578177840231%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Example on "Releasing a project" is incorrect
Title: Message Title
Arjun Gopisetty updated an issue
Jenkins / JENKINS-60638
Example on "Releasing a project" is incorrect
Change By:
Arjun Gopisetty
The [Releasing a project?|[https://jenkinsci.github.io/jira-steps-plugin/getting-started/examples/release_project/]] example code contains the following lines:{code:java}def transitionInput = [transition: [name: 'Close']]jiraTransitionIssue idOrKey: issueKey, input: transitionInput{code} However, this is not valid for the Jira API endpoint: [https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post.|https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post] The *IssueTransition* parameter only takes the ID of the issue transition. The documentation needs to be fixed to rectify this mistake corrected so the function call works .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are
[JIRA] (JENKINS-60624) Repo not maintained anymore?
Title: Message Title Callum Pember commented on JENKINS-60624 Re: Repo not maintained anymore? Hi Rik, Thanks for checking out the PR and the amazingly fast turnaround! I've just built master and tested the changes. It's working perfectly. Thanks again! Callum Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203857.1578001388000.2242.1578173281127%40Atlassian.JIRA.
[JIRA] (JENKINS-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title Ryan Campbell commented on JENKINS-53158 Re: Pipelines leak OneOffExecutors when triggered on a temporary offline master Seems like behavior similar to JENKINS-57304 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193168.1534849944000.2237.1578172200180%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Example on "Releasing a project" is incorrect
Title: Message Title
Arjun Gopisetty updated an issue
Jenkins / JENKINS-60638
Example on "Releasing a project" is incorrect
Change By:
Arjun Gopisetty
The [Releasing a project?|[https://jenkinsci.github.io/jira-steps-plugin/getting-started/examples/release_project/]] example code contains the following lines: {code:java}def transitionInput = [transition: [name: 'Close']]jiraTransitionIssue idOrKey: issueKey, input: transitionInput{code} However, this is not valid for the Jira API endpoint: [https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post.|https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post] The ` * IssueTransition ` * parameter only takes the ID of the issue transition. The documentation needs to be fixed to rectify this mistake.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-60638) Example on "Releasing a project" is incorrect
Title: Message Title
Arjun Gopisetty updated an issue
Jenkins / JENKINS-60638
Example on "Releasing a project" is incorrect
Change By:
Arjun Gopisetty
The [Releasing a project?|[https://jenkinsci.github.io/jira-steps-plugin/getting-started/examples/release_project/]] example code contains the following lines: ``` {code:java} def transitionInput = [transition: [name: 'Close']] jiraTransitionIssue idOrKey: issueKey, input: transitionInput {code} ``` However, this is not valid for the Jira API endpoint: [https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post.|https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post] The `IssueTransition` parameter only takes the ID of the issue transition. The documentation needs to be fixed to rectify this mistake.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-60638) Example on "Releasing a project" is incorrect
Title: Message Title Arjun Gopisetty created an issue Jenkins / JENKINS-60638 Example on "Releasing a project" is incorrect Issue Type: Bug Assignee: Arjun Gopisetty Components: jira-steps-plugin Created: 2020-01-04 20:54 Priority: Minor Reporter: Arjun Gopisetty The [Releasing a project?|https://jenkinsci.github.io/jira-steps-plugin/getting-started/examples/release_project/] example code contains the following lines: ``` def transitionInput = [transition: [name: 'Close']] jiraTransitionIssue idOrKey: issueKey, input: transitionInput ``` However, this is not valid for the Jira API endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post. The `IssueTransition` parameter only takes the ID of the issue transition. The documentation needs to be fixed to rectify this mistake. Add Comment
[JIRA] (JENKINS-55164) Add support for declarative pipeline env var population
Title: Message Title Rik Turnbull closed an issue as Won't Fix Closing as I believe declarative pipelines work the same as scripted pipelines. Jenkins / JENKINS-55164 Add support for declarative pipeline env var population Change By: Rik Turnbull Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view
[JIRA] (JENKINS-60624) Repo not maintained anymore?
Title: Message Title Rik Turnbull commented on JENKINS-60624 Re: Repo not maintained anymore? Hi Callum, yes still here but just lacking the time to get in the headspace for this plugin. Luckily, New Year is quiet.. So, I had a look at your PR - and thanks for submitting, it has helped me understand a bit more about what's going on with the authentication. It seems that as the AWS authentication always happens on the Jenkins master, where the plugin runs, then it can only ever use creds supplied in the credentials stores or the local Jenkins master AWS configuration (env vars, .aws files, IAM roles). I did notice that the build job and pipeline environment variables are passed to the plugin though (via initialEnvironment), so rather than add a lot of new properties (as per your PR) I just modified the code to check this environment for the AWS_* environment variables. I then used the logic you had to determine the credentials provider. Changes here: https://github.com/jenkinsci/aws-parameter-store-plugin/commit/1a824f82d9ea9526b7eb6ff3f2cfdff2d22260be This should work for your requirements - if possible, can you check a custom build from this master branch? If not, I'll risk it and publish a new version. Cheers! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title Mark Waite edited a comment on JENKINS-50401 Re: Checkout resolution misbehaves with local branch and forward slashes [~mramonleon] I don't remember why I marked this as fixed but not released without linking a pull request or providing some other comment to justify that change. Neither this bug nor either of the linked bugs are mentioned in the [git plugin 4.0.0 changelog| [ https://github.com/jenkinsci/git-plugin/releases/tag/git-4.0.0] ] or in the [git client plugin 3.0.0 changelog| [ https://github.com/jenkinsci/git-client-plugin/releases/tag/git-client-3.0.0 |https://github.com/jenkinsci/git-plugin/releases/tag/git-4.0.0 ] ] . I've corrected my mistake and placed it back into 'OPEN' state. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189455.1522069171000.2228.1578153600341%40Atlassian.JIRA.
[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title Mark Waite commented on JENKINS-50401 Re: Checkout resolution misbehaves with local branch and forward slashes Ramon Leon I don't remember why I marked this as fixed but not released without linking a pull request or providing some other comment to justify that change. Neither this bug nor either of the linked bugs are mentioned in the [git plugin 4.0.0 changelog|https://github.com/jenkinsci/git-plugin/releases/tag/git-4.0.0] or in the [git client plugin 3.0.0 changelog|https://github.com/jenkinsci/git-client-plugin/releases/tag/git-client-3.0.0]. I've corrected my mistake and placed it back into 'OPEN' state. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189455.1522069171000..1578153480162%40Atlassian.JIRA.
[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title Mark Waite updated JENKINS-50401 Jenkins / JENKINS-50401 Checkout resolution misbehaves with local branch and forward slashes Change By: Mark Waite Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189455.1522069171000.2216.1578153180635%40Atlassian.JIRA.
[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title Mark Waite updated JENKINS-50401 Jenkins / JENKINS-50401 Checkout resolution misbehaves with local branch and forward slashes Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189455.1522069171000.2218.1578153180675%40Atlassian.JIRA.
[JIRA] (JENKINS-60625) Dashboard rendering blocked on UpdateSite.getJSONObject
Title: Message Title Jesse Glick updated JENKINS-60625 Jenkins / JENKINS-60625 Dashboard rendering blocked on UpdateSite.getJSONObject Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.212 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203858.1578003601000.2212.1578147780121%40Atlassian.JIRA.
