[JIRA] (JENKINS-55771) Assign variable from shell output using declarative pipeline

[bryce.schober@gmail.com (JIRA)]

Bryce Schober created an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline-build-step-plugin, pipeline-stage-step-plugin Created: 2019-01-24 23:57 Environment: LTS 2.150.2 Priority: Minor Reporter: Bryce Schober Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[bryce.schober@gmail.com (JIRA)]

Bryce Schober updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Bryce Schober Currently, we can capture the output of a shell step inside of a {{script{}}} block, but have no way to do that in clean declarative pipeline syntax. For example, [this post on StackOverflow|https://stackoverflow.com/a/38783622] must instead

Add Comment

[bryce.schober@gmail.com (JIRA)]

Bryce Schober updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Bryce Schober Component/s: workflow-durable-task-step-plugin Component/s: pipeline-build-step-plugin Component/s: pipeline-stage-step-plugin

Add Comment

[bryce.schober@gmail.com (JIRA)]

Bryce Schober updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Bryce Schober

Currently, we can capture the output of a shell step inside of a {{script{}}} block, but have no way to do that in clean declarative pipeline syntax. For example, [this post on StackOverflow|https://stackoverflow.com/a/38783622] must instead be: {code:groovy} // Git committer email script {   GIT_COMMIT_EMAIL = sh (     script: 'git --no-pager show -s --format=\'%ae\'',     returnStdout: true   ).trim() } echo "Git committer email: ${GIT_COMMIT_EMAIL}" {code}

Add Comment

[bryce.schober@gmail.com (JIRA)]

Bryce Schober updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Bryce Schober Component/s: pipeline

Add Comment

[bryce.schober@gmail.com (JIRA)]

Bryce Schober updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Bryce Schober

Currently, we can capture the output of a shell step inside of a {{script { }} } block, but have no way to do that in clean declarative pipeline syntax. For example, [this post on StackOverflow|https://stackoverflow.com/a/38783622] must instead be: {code:groovy} // Git committer email script {   GIT_COMMIT_EMAIL = sh (     script: 'git --no-pager show -s --format=\'%ae\'',     returnStdout: true   ).trim() } echo "Git committer email: ${GIT_COMMIT_EMAIL}" {code}

It also doesn't work to wrap it in a declarative {{environment}} block, though that may perhaps be a reasonable place to extend the syntax.

Add Comment

[bryce.schober@gmail.com (JIRA)]

Bryce Schober assigned an issue to Devin Nusbaum

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Bryce Schober Assignee: Devin Nusbaum

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Devin Nusbaum Component/s: pipeline-model-definition-plugin Component/s: pipeline Component/s: workflow-durable-task-step-plugin

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum updated an issue

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Devin Nusbaum Labels: pipeline

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum assigned an issue to Unassigned

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Devin Nusbaum Assignee: Devin Nusbaum

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-55771

Re: Assign variable from shell output using declarative pipeline There might be an existing issue to track this kind of thing already, but IIUC it is somewhat by design (CC @abayer). In your example at least you could move your echo into the script you run, but perhaps that is not your real use case.

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum edited a comment on JENKINS-55771

Re: Assign variable from shell output using declarative pipeline

There might be an existing issue to track this kind of thing already, but IIUC it is somewhat by design (CC @ [~ abayer ] ). In your example at least you could move your echo into the script you run, but perhaps that is not your real use case.

Add Comment

[andrew.bayer@gmail.com (JIRA)]

Andrew Bayer resolved as Duplicate

Yeah, this is one aspect of JENKINS-44376.

Jenkins / JENKINS-55771

Assign variable from shell output using declarative pipeline

Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate

Add Comment

[bitwiseman@gmail.com (JIRA)]

Liam Newman closed an issue as Duplicate

Bulk closing resolved issues.

Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline

Change By: Liam Newman Status: Resolved Closed

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)