Hi, sorry, I probably should have described it more precise... I do in fact have my pipeline set up the way you suggested it: There's a stage for the build (on different platforms, potentially in parallel), there's a stage for the tests (again on different platforms) and there is a deployment stage that copies the relevant files to a file server if the previous stages did end successfully.
However, the complete product consists of a few dozen shared objects and executables, several documentation files to go with them and of course the installer packages. So I have a total of about 300 jenkins projects configured on our build server. These are currently either matrix or freestyle projects - but even though I made an effort to centralize as many parts of the projects as possible, the whole setup is not as flexible as I'd like it to be as changes/improvements to the build scripts are time-consuming to apply to so many projects, which is why I'd gladly switch to scripted pipelines. But of course I wouldn't want to e.g. have one of the documentation builders to overwrite a pdf file while it is being packaged into an installer by one of the installer builders. So the synchronization mechanism that the two aforementioned options offer on the freestyle projects are as far as I can see an essential feature for the setup I am maintaining. That's why I am looking for a way to get the same feature on a pipeline... -- 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/27651ae7-40fd-4307-ac81-0a7e5106d4c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
