This looks straightforward to me. I think the answer is C - Declarative Pipelines are restartable by default, and the preserveStashes() option is needed to preserve data. I'll double-check the other options, but I'm feeling good about this one.
I'm a bit confused by the wording of the question. It seems like there might be some tricky details around the different scenarios for restarting Declarative Pipelines. I'll need to make sure I understand the distinctions before answering.
Okay, let me think this through. I know Declarative Pipelines are designed to be restartable, but the question is asking about the specific conditions for that. I'll need to carefully read through the options to make sure I understand the nuances.
Hmm, this is a tricky one. I'm not entirely sure about the differences between restarting after a Jenkins failure versus a transient outage. I'll need to review the details on that.
I'm pretty confident about this one. I think the answer is C - all Declarative Pipelines are restartable by default, and the preserveStashes() option is needed to preserve data from the original run.
Option A seems the most accurate. Declarative Pipelines can be restarted with the same inputs, and data from the original run is available if the preserveStashes() option is used.
Ming
5 months agoGracia
5 months agoUlysses
5 months agoRhea
6 months agoCandida
6 months agoCarrol
6 months agoGerry
6 months agoDiane
7 months agoEladia
7 months agoDonte
7 months agoClemencia
7 months agoMee
7 months agoRebecka
8 months agoDortha
8 months agoAnnamae
9 months agoLuisa
8 months agoReyes
10 months agoYasuko
10 months agoJohnson
10 months agoChristoper
10 months agoDoyle
11 months agoGlenna
9 months agoFelicidad
9 months agoRoslyn
10 months agoJohnson
11 months ago