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.
On Thu, Feb 1, 2018 at 12:21 PM pisymbol <[email protected]> wrote: > 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. > > Thanks! > > -aps > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/e27f6539-f5ed-48bb-9971-2752ea52243a%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/e27f6539-f5ed-48bb-9971-2752ea52243a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeNVy0sxPr54yw-JiBVkmXGYks2YcKpXVyYYLXR4VphSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
