similar to other users I also have a quite large set of jobs that use the
(scripted, not declarative) Groovy pipelines. In my setup I have deliberately
chosen to:
- store all the Groovy scripts in SCM
- have a seperate dedicated repository for all my Groovy scripts;
alternative would be to store the JenkinsFile in the same repo as where the
test data is stored.
- use groovy 'load' to pull in generic utility code.
alternative is using shared libraries; I prefer local load since it allows me
to use SCM branches of my jenkins repository
I also started from historic Freestyle jobs. First thing I did is transform the
Freestyle job into one that calls a single script with parameters from a
repo.Then create a very simple pipeline job that call that very script. Then
slowly start taking more parts of the script into the groovy code.
For me doing it big-bang was a no-go. Have been hit by the Groovy diffs similar
to what @Giles also mentioned. Take small steps. Debugging Groovy
in Jenkins is extremely hard. Investigate the use of "Replay" !Once you have
the first job running, the rest will be much easier.good luck.
On Tuesday, June 2, 2020, 09:58:35 PM GMT+2, Giles <giles...@gmail.com>
wrote:
I wrote a large library file full of Groovy methods. I have a big stack of
Jenkinsfiles, similar to Randy Beckworth, although mine are generally named
"<purpose>/<environment>.Jenkinsfile" (as you can see, Jenkins isn't very
particular about naming). The Jenkinsfiles are generally very short, just long
enough to call one of the library methods with a set of parameters. We have
50-80 Jenkins jobs, and each of those has its own Jenkins file. The initial
set-up was tedious, but now that it's all in place it works very well. Not
sure if you could call a Python library, or if you'll end up using Groovy to
call Python scripts. My Groovy calls a lot of shell scripts - it's ugly, but
works surprisingly well so you can make that work if you have to.
I think there are plugins and/or programmatic methods of generating jobs to
avoid doing a lot of that tedious work yourself, but I also think you'd have to
be looking at a very big setup (thousands of jobs) before it would be worth the
investment of time to understand those plugins/methods.
Learning Jenkins' version of Groovy is a bit of a trip: it has a lot of its own
methods, and I've found some weird edge cases where Jenkins' Groovy doesn't
behave the same as standard Groovy. All that said - it's definitely been worth
the work.
On Monday, 1 June 2020 11:37:46 UTC-4, Al Silver wrote:
I've used Jenkins a little but not in the traditional method of CI/CD. I'm
using Jenkins as a Web UI to run individual python scripts for networking
devices... Users would log into Jenkins and then select any one of numerous
Freestyle projects (with parameters) to run (there could be 100 or more...).
The job executes a shell which runs a pytest script that logs into (via ssh)
multiple networking devices and performs some actions... pretty straightforward
and it works ok but has some limitations. With that said, I think I'll have
more flexibility and power building and maintaining these jobs as pipelines and
treating them as code. My question is I guess I would need to convert my
pipelines into Jenkinsfiles? However, most of the docs I read show a single
Jenkinsfile (named "Jenkinsfile") I would need one for each job (a 100 or so).
I must be missing something here or not understanding. Can someone point in
the right direction for what I'm trying to accomplish?
ThxAl
--
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/4cae1d19-a93d-49f5-8257-96912ea49279%40googlegroups.com.
--
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/776171713.2826360.1591268446434%40mail.yahoo.com.
