This is an old thread I have a solution that worked for me so I thought I'd
share. I am no Jenkins expert so I don't know if this is some kind of
horrible hack, but basically the idea is to ignore the scm object provided
by the multi-branch pipeline and setup your own.
I use this for a multi-p
Hi i have the same issue in jenkins pipeline, I have multiple projects in
one repo. Is this issue got solved, if solved please post the sample link
so that it will be helpful. Thanks in advance.
On Monday, November 14, 2016 at 4:48:06 PM UTC+5:30, Sverre Moe wrote:
>
> I need some help brainsto
Multibranch pipelines are really only suitable for single-project
multi-branch repos. The farest I got with a multi-project setup was using
the Jenkins Repo Plugin (for the Google Repo Tool), but this would reverse
the use case you're looking for: It pings all subprojects / subrepos and
kicks o
I try to keep 1 Jenkins file per folder into the delevery system and it was
a pain in the end. I simplify things by moving the Jenkinsfile into a sub
repos (we are using Mercurial). So I keep my Jenkinsfile revision outside
the main branch and our repos only point to the proper Jenkinsfile sub
I need some help brainstorming a solution for multiproject repositories.
Pipeline building a repository that contains several delivery projects.
The root of the repository contains several delivery projects.
- delivery-project
- delivery1
- CMakeList.txt
- delivery-project-delivery1.spec
