jenkinsci / jenkinsci/workflow-basic-steps-plugin
[JENKINS-48668] Add unstash option to continue on failure
- Vorherrschende Sprache
- Java
- Sterne
- 73
- Forks
- 129
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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
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.
Beitragsleitfaden
Rechercherichtung
Start by locating the unstash step implementation and its related tests in the workflow-basic-steps-plugin, then inspect how failures are reported in declarative pipelines. Done means an optional ignoreFailures setting preserves the current default behavior, permits continuation when enabled, and has coverage for successful and missing-stash cases.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- ci-cd, devops
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100