Hello Jérôme, thanks a lot for your response. Jérôme Godbout (2020/08/11 16:00 +0000): > Hi, > this is my point of view only,but using a single script (that you put > into your repos make it easier to perform the build, I put my pipeline > script into a separated folder). But you need to make sure your script > is verbose enough to see where it has fail if anything goes wrong, > sinlent and without output long script will be hard to understand > where it has an issue with it.
Indeed. Generally speaking, we activate the e and x shell options to have command displayed and scripts stop on the first error. [...] > I for one, use 3+ repos. > 1- The source code repos > 2- The pipeline and build script repos (this can evolve aside form the > source, so my build method can change and be applied to older source version, > I use branch/tag when backward compatibility is broken or a specific version > is needed for a particualr source branch) > 3- My common groovy, scripts tooling between my repos > 4- (optional) my unit tests are aside and can be run on multiple > versions That's a very interesting workflow, thanks! So you add all these repositories to your jobs and then they are run each time one of those repositories is updated, right? How do things work on slaves? Is each repos cloned in its own directory in the workspace directory? > Hope this can help you decide or plan you build architecture. It helps a lot! Thanks! Sébastien. -- 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/20200814152915.GA143147%40om.localdomain.
