jenkinsci / jenkinsci/workflow-basic-steps-plugin

[JENKINS-48668] Add unstash option to continue on failure

Open
#451 0 comments 0 reactions 0 assignees View on GitHub
component:workflow-basic-steps-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
73
Forks
129
PR merge metrics
No merged PRs in 30d

Description

The following applies only to the declarative pipeline.

For the moment, there is only the name option for the unstash step.

I would like to have an extra option for the unstash step like ignoreFailures=false|true, by default on false to be backward compatible.

This extra option helps a lot when testing or using when conditionals on the pipeline stages, as there might be a stage before the unstash that actually does the stash, but the code in the step after the unstash can fallback to defaults if it cannot find the unstashed file.

It would be okay if, for example, the whole build can be made unstable if the unstash fails.

For the moment there is no way to continue it in the declarative pipeline (as the try/catch) is not supported.

---
Originally reported by ader1990, imported from: Add unstash option to continue on failure


  • status: Open
  • priority: Major
  • component(s): workflow-basic-steps-plugin
  • resolution: Unresolved
  • votes: 4
  • watchers: 3
  • imported: 20251215-220547

Raw content of original issue

The following applies only to the declarative pipeline.

For the moment, there is only the name option for the unstash step.

I would like to have an extra option for the unstash step like ignoreFailures=false|true, by default on false to be backward compatible.

This extra option helps a lot when testing or using when conditionals on the pipeline stages, as there might be a stage before the unstash that actually does the stash, but the code in the step after the unstash can fallback to defaults if it cannot find the unstashed file.

It would be okay if, for example, the whole build can be made unstable if the unstash fails.

For the moment there is no way to continue it in the declarative pipeline (as the try/catch) is not supported.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.