Title: Message Title
Marcelo Carlos edited a comment on JENKINS-43749
Re: Support multiple Jenkinsfiles from the same repository
Are there any plans to add/support this feature?Our scenario is fairly similar to the others. We have a monorepo where we store different projects. To better illustrate our scenario and why this is important to us, here is one simplified use-case:We have our repo (let's call it "monorepo"). In this repo we have several folders, such as: * toolOne (written in golang) * docker-images ** base ** imageTwoIdeally, we'd have three pipelines in the example above, one for `toolOne`, one for `docker-images/base` and one for `docker-images/imageTwo`.On top of that, an interesting additional use case is when we want to build `imageTwo`. That project contains a multi-stage Dockerfile which compiles part of the source code of `toolOne` and adds the compiled binary into the `imageTwo` image (that's one of the main reasons we choose the monorepo approach, this way we can easily and quickly handle cross-project/tools dependencies).At the moment, we've been setting all of that up using a single Jenkinsfile at the root of the repo and handling builds with *lots* of build parameters and conditionals, so we can run/skip stages according to the build we want to execute.We looked into the "Job DSL Plugin", but we'd rather avoid since we've been successfully using Jenkinsfile in several of other projects and it is great to the same format for all projects and repos.However, the scenario above is gradually becoming a blocker as the pipeline is growing too big due to all the conditionals and stages we had to define to work around the existing limitation of 1 Jenkinsfile per repo.So, back to the original question, are there any plans you could share about adding/supporting this feature?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
