[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [ [ a few solutions floating around| |#60316968]] [https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968] [ ] |#60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [ [ a few solutions floading floating around| |#60316968]] [https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968 ] []| #60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [a few solutions floating floading around|[https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968#60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline. In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are a few solutions floating around that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa). That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Francesco Pretto commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I don't know if this precisely answer the original issue here but I achieved to have multiple Jenkinsfile in the same repository/branch with the current feature set, I explained the procedure in this StackOverflow answer. The main idea is having separate Build and CSM projects configured in Jenkins, with the former that can be a simple Freestyle project with a polling on a repository and the latter a pipeline with a trigger on the CSM project. The trickier part was to add to add the skipDefaultCheckout directive in the Build pipeline, which is strange since I expected "Lightweight checkout" flag in the pipeline project to actually disable the checkout itself. Is this intended? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.3306.1582193042147%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title victor paul edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository [~fajran] Is is it possible to share the code removing your firms references? Seems this has been the issue with Jenkins since years and there is not a stable solution. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.6256.1581381964975%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title victor paul commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Fajran Rusadi Is is possible to share the code removing your firms references? Seems this has been the issue with Jenkins since years and there is not a stable solution. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.6005.1581381481770%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Francesco Pretto edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I'm relatively new to Jenkins but for me the reason this feature can't just be straightforwardly implemented in Jenkins is that it lack lacks a concept of a first-citizen SCM resource, meaning that SCM repositories can be configured in jobs but they are not treated as shareable resources themselves. If repositories could be configured as shareable resources (with no build steps configurable in them) and job could be configured to source on these resources (instead of configuring a separate git/svn connection for each job) it would be easier to implement a single queue of jobs to trigger for SCM changes on a single repository and it would be easier to filter which pipeline to trigger in case Job1 is configured with Jenkinsfile1 and Job2 is configured with JenkinsFile2. The single queue and the filter can probably be implemented with [scripting|https://stackoverflow.com/a/51237488/213871] but to have UI support and more declarative approach in the upstream pipelines (as opposed to imperatively select which job to trigger in the downstream SCM projects) something like what I am suggesting could be needed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Francesco Pretto commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I'm relatively new to Jenkins but for me the reason this feature can't just be straightforwardly implemented in Jenkins is that it lack a concept of a first-citizen SCM resource, meaning that SCM repositories can be configured in jobs but they are not treated as shareable resources themselves. If repositories could be configured as shareable resources (with no build steps configurable in them) and job could be configured to source on these resources (instead of configuring a separate git/svn connection for each job) it would be easier to implement a single queue of jobs to trigger for SCM changes on a single repository and it would be easier to filter which pipeline to trigger in case Job1 is configured with Jenkinsfile1 and Job2 is configured with JenkinsFile2. The single queue and the filter can probably be implemented with scripting but to have UI support and more declarative approach in the upstream pipelines (as opposed to imperatively select which job to trigger in the downstream SCM projects) something like what I am suggesting could be needed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.2430.1575766562090%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Fajran Rusadi commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Tzach Yarimi to clarify, we had different multibranch pipeline job for different component. So what service does is create a new multibranch pipeline job when it detects a new component added to the repository. The new job will be configured to use the Jenkinsfile specific of that new component. If the job already exists, it will check if the branch is already registered otherwise it will update the job config to add a new branch and start the scanning process to make the branch job available. Once the branch job is available, the service will trigger the build of that. Unfortunately I could not share the code. 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.1842.1562250242164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Tzach Yarimi commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Fajran Rusadi is your service creating jobs inside the multibranch folders? Can you please share some code for doing that? 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.986.1562164202165%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jon-Paul Sullivan commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository When creating multiple jobs off the same GitHub repository, I found we required this plugin to get sane PR checking: https://plugins.jenkins.io/github-scm-trait-notification-context Default behaviour can play havoc with CI pipelines. 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.12924.1561980962001%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Fajran Rusadi commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository What I ended up doing to support our monorepo approach was the following Create separate (multibranch pipeline) Jenkins job for every individual components in the monorepo All Jenkins jobs will use the same repository URL but each has its own path to Jenkinsfile. This way each component can have its own distinct build pipeline I disabled the build triggering function in Jenkins and instead create an additional service to handle build trigger The build trigger service also manages the Jenkins jobs. Whenever it detects a new component, it will create the corresponding Jenkins job automatically, with the correct configuration 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.12823.1561980782576%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
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
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Marcelo Carlos commented 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 imageTwo Ideally, 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 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
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Aleksei Pushnov commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository This feature would allow to ease up configuration on many environments. 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.10557.1561638062094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Mikhail Naletov commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Cool feature. I really need the same. 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.15230.1559141520030%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Mikhail Naletov commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Cool feature. I really need the same. 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.15132.1559141471509%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title nikhil kanotra commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Hi Any update on this bug ... for mono-repositories in micro-services, this is very common scenario, where there are multiple jenkins files for multiple folder (microservice). github org webhook doesnt support thisand creating branch for each and every microservice is not feasible please fix this on priority if possible 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.1216.1557746343477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Antti Turpeinen commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Just noticed that JENKINS-50328 bug is related to this issue. If that bug would be fixed then we could create multiple multi-branch pipeline projects using same git repository but with different Jenkinsfile? 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 stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jens Beyer commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Mark Wright: Indeed we have the problem that githooks trigger all builds, and this is some kind of issue, but not too big for us (rarely leads to intermediate build errors because the projects depend on each other). We thought about solutions once the issue would become bigger, like cancelling builds if their upstream builds are still in queue, or lockable resources) but at the moment we believe only the separation of the subprojects into own repositories would probably help in the long run. Except: If Git polling would honour sparse checkouts (maybe as additional option, since I can imagine this being quite expensive), this would not be necessary at all. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Mark Wright commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Jens Beyer in your example, do you use githooks to trigger builds? If so, how do you prevent changes from one of your sub-projects from triggering building of another? E.g how do you prevent a change under /project-app from building /project2-app? Or do you just build them all? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
