Hi Sorin. 

Short answer: No, I don't think the aim is to be incompatible at all with 
local developer builds. 

If you have a build script that uses make, then it is perfectly fine to use 
it, even as is. There is nothing wrong with a Jenkinsfile which is just 
delegating to a shell script or make. 

As you mentioned you have stages in your build already, then if possible 
you can break them up as suggested in another post, via "stage" statements 
which then contain the calls to the specific steps. This aids visualisation 
as it breaks things up, but it is still calling your scripts to do the 
actual work. Of course this may not be practical in your case, which is 
fine, but makes it harder to show visually at the moment. 



On Friday, August 19, 2016 at 9:20:02 PM UTC+10, Sorin Ionuț Sbârnea wrote:
>
> I do like Jenkins pipelines and the fact that now we can control Jenkins 
> jobs via an inside repository file. I also love the looks of the upcoming 
> Blue Ocean interface and I can't wait to see it as default interface.
>
> Now, the reality is that there is a serious problem which seems to be 
> ignored by the Jenkins development team: 
>
> By implementing Jenkins pipelines you lose the ability to execute a build 
> job outside jenkins. 
>
> Due to this our current pipelines are mostly just one execution of 'make', 
> so we can't really benefit from having the execution steps splitted and 
> nicely-displayed by Jenkins.
>
> Like most users we do have multi-stage bash/make scripts that are building 
> the product.
>
> Is there a way to implement Jenkins pipelines and still be able to run 
> local builds? What is you take on this?
>

-- 
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/0d8d6102-59ea-4510-8b0f-83421a794160%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to