As far as I know, “Jenkinsfile” is just a naming convention. I have multiple Jenkins files:
JenkinsFile.Parallel.groovy
JenkinsFile.Parallel.Snapshot.groovy
JenkinsFile.PatchWeekend-VmManager.groovy
I also add the .groovy extension so that editors can do syntax highlighting.
Randy
--
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-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/64f8998b-67f2-48ba-a0fa-6cdbdd4113ab%40googlegroups.com.
Nearly the same here:
When I run, I can checkout the proper jenkinsfile (branch, version) from the repos #2. It will checkout his needed version of the toolings repos #1. Then it will checkout the related source code and start building/testing, etc.
This split the way we do the build from the source code, the source code is totally agnostic of the build system. I can have different build script for different system. I can versionize my tools to get the same results every times. The slave doesn’t need anything installed, so the Jenkins only need the required plugins and credentials and tons of scripts approvals upon install.
From: 'monger_39' via Jenkins Users <jenkins...@googlegroups.com>
Sent: June 4, 2020 7:01 AM
To: Jenkins Users <jenkins...@googlegroups.com>
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/776171713.2826360.1591268446434%40mail.yahoo.com.
|