Thank you! I did look at the version and while I cannot remember exactly what it is, I seem to recall it's due for an update. Think I'll keep pipeline because there is talk about making all our processes as integrated as possible. Your answer is so well written and easy to understand - thank you again. Alison
On Saturday, October 21, 2017 at 7:14:31 PM UTC-4, Robert Hales wrote: > > You are probably talking freestyle vs. pipeline jobs. Pipeline are the > groovy scripted ones. > > Really, the pipeline jobs SHOULD only be doing some simple logic and > running the a build script (such as an ant build.xml). The pipeline code is > a newer way to do it, and is a much more flexible way to chain different > jobs. i.e. you can pull code from a repo, build it, test it, and deploy it, > all in one job, all written as code that can be kept in version control. > > If the jobs are doing something very simple like just running and ant > build.xml, then you should be able to easily rebuild those into a freestyle > job. If they have used the pipeline code to actually perform the build, you > would have to write and and build script. > > As to the question of aborting the jobs... What version of Jenkins do you > have? Depending on what the pipeline scripts are doing, there were some > bugs that caused different problems with aborting in earlier versions. It > may be that you just need to upgrade your Jenkins to a newer version, or > upgrade some plugins. . From my experience, the upgrades are easy. > > Scripted pipeline jobs are usually better for all but the most simple of > jobs, but if you don't want to invest the time to learn how to write and > maintain them, and all your jobs are simple enough, freestyle might be the > way to go. > > On Saturday, October 21, 2017 at 6:19:44 AM UTC-6, ABostonGal ABostonGal > wrote: >> >> 1. Two types of architecture exist on a Jenkins build server I inherited: >> pipeline builds (building from groovy files) and jobs building from just a >> build xml file. I find the pipeline builds very difficult to abort: I have >> to take multiple steps starting from clicking on a red x in the Executor >> panel for the job through to clicking on two links in the console. The jobs >> that run from a build xml are easy: click once on the red x in the Executor >> panel, and I'm done. >> >> Is there a easier way to stop the pipeline builds? >> >> 2. Can I change the pipeline builds back to the architecture that just >> uses the build xml files? >> >> >> -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b8034887-a8e4-4894-87e1-c7de33a253ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
