Trigger multiple pipelines for one commit

[opendevstack]

Trigger multiple pipelines for one commit

[rattermeyer]

Hmm. Not conviced yet. Wouldn't be another option to create a "Master" Jenkinsfile in a multi-module build and call the other Jenkinsfile, like proposed here: https://stackoverflow.com/questions/44766324/invoke-a-remote-jenkins-file-from-another-jenkinsfile.
You would not get a seperate pipeline for each module, but if you have a multi-module project, I would expect that the different modules are released and deployed together. In this case, I would like to have a single pipeline for the project and only optimize build times as you have described.

[michaelsauter]

@rattermeyer Nice find, did not know this is possible.

I am not convinced however that one would want to deploy the modules together. There are many who favour a monorepo over many repos, but that does not mean that you build a monolith (everything deployed at the same time) necessarily. Therfore I think it could make sense to have a different pipeline.

That said, I I'll think a bit more about your proposal. Also, we can wait until we have a few use cases and then decide on the best solution for this.

[rattermeyer]

Monorepo <> Multi-module project. If we talk about a monorepo, then your idea makes sense. But a monorepo should /can contain independent projects. But a multi-module build tends to have the same version for all components.

[michaelsauter]

@rattermeyer Ah yes, I was thinking more in terms of monorepo than multi-module, but still took multi-module as an example without knowing too much about it. I just used it as an example since ODS is setup for multiple repos and I wanted to avoid the repo-style discussion in this PR. If multi-module projects tend to be deployed together, then what you wrote makes more sense for them.

[michaelsauter]

As this came up in a slightly different discussion again, the solution has evolved slightly (@sino92 thanks for the hint!):

Instead of allowing to specify multiple jenkinsfiles in one webhook, we just add a feature to specify one jenkinsfile. Doing so:

• Allows users to put the Jenkinsfile somewhere else than in the root dir
• Allows users to create multiple webhooks, firing for potentially different events, to many Jenkinsfiles, each of which can determine if they want to run or not.

I think this is a great solution, giving a lot of flexibility and very straight-forward to implement.

[stitakis]

@michaelsauter idea sounds good to me but not sure if I understood it correctly... the proposed change would allow users to specify in a webhook the path and name of the Jenkinsfile, which ev. will be located not in root dir, to be triggered by Jenkins, right?

[michaelsauter]

@stitakis Yes, it would allow users to configure https://github.com/opendevstack/ods-core/blob/master/jenkins/webhook-proxy/pipeline.json#L31 by using a GET param in the webhook URL.

[michaelsauter]

I'll close this as using jenkinsfilePath and component params in the webhook URL allow to have more than one webhook per repo, and therefore the ability to trigger more than one pipeline.

Also opendevstack/ods-jenkins-shared-library#147 gives authors the building blocks to easily build their own deployment stages.