That

On Saturday, April 29, 2017 at 4:46:32 PM UTC-7, Mark Waite wrote:
>
>
>
> On Saturday, April 29, 2017 at 3:06:32 PM UTC-6, Kaido Kert wrote:
>>
>> Hi, 
>>
>> I've been using Freestyle multibranch project option for a long time to 
>> run multi-branch builds. However, it officially say's its deprecated now.
>> However, we do not have the freedom to stuff Jenkinsfile into all 
>> repositories/branches we want to build, and never will.
>>
>>
> If you aren't able to place a Jenkinsfile into the repositories / branches 
> that you want to build, you might create a new (independent) repository 
> which has one branch per repository and branch that you will build.  In 
> each of the branches of that repository, you can add the Jenkinsfile and 
> have it perform the checkout of the repository / branch that you're not 
> able to change.  That allows you to have a repository with a branch per 
> build (which is what multi-branch pipeline wants), and you can place a 
> Jenkinsfile at the root of each branch to control what it is building.
>
> That creates a "builders" repository where you control the Jenkinsfile, 
> and that Jenkinsfile references the repositories and branches being built.
>
> I used that technique to "test drive" a pipeline configuration for a 
> component that wasn't ready to use Jenkins.  The official source repository 
> didn't know that I was test driving, and I was able to make rapid progress 
> without complaints about my Jenkins experiments.
>
> Mark Waite
>


 That would definitely solve the problem, i've done similar hooks to build 
CMake build trees for projects not intended to be built with it, etc.
However, it's a bit of a large overhead to just get 4-5 lines of minimal 
Jenkinsfile code to actually kick off the build, and especially when you 
are just tooling around and testing.

I've just actually gone through full Jenkins update to latest, and updated 
all plugins too, and now there is a new option, 'Default Jenkinsfile' which 
does seem to do what i need.

-kert

-- 
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/9238c114-0c44-4392-9e81-abdba3e783ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to