For this purpose I am using FileSystem SCM plugin to retrieve scripts
without committing + local Docker snapshot of the production instance. You
can find some info about my approach in these slides
Slides are a bit outdated, but the demo is more or less up to date:
Hopefully it helps,
четверг, 1 февраля 2018 г., 20:51:47 UTC+1 пользователь slide написал:
> If you look on the left side of the Jenkins area when looking at the job,
> there is an option called "Replay" that allows you to edit the scripts and
> rerun with the same setup. You can play with the scripts and stuff there
> and then grab the changes and check them in.
>> Sorry, I know this sounds extremely basic:
>> But how to you iteratively work on the build without actually checking in
>> the Jenkinsfile? I'd can work on a basic Pipeline project and edit/run/fix
>> Groovy syntax etc without an issue.
>> But for other projects, like the Multibranch Pipeline once it wants a
>> Jenkins file in the source tree as per the scan. (note: our source trees
>> are currently SVN).
>> So how do you work on the build without checking in the Jenkinsfile a
>> half a dozen times before you get the file right? This has me very confused.
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> To view this discussion on the web visit
>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.