We had a conversation with Nicolas yesterday, and we agreed to discuss the 
the JCasC + Custom War Packager + Jenkinsfile Runner combination at the 
next JCasC meeting. Meeting date: Sep 12, 7AM UTC, Youtube link: 
https://www.youtube.com/watch?v=sxJxez8jsIw . We will also post the 
participant link in 
https://gitter.im/jenkinsci/configuration-as-code-plugin before the meeting 
starts.

BR, Oleg

P.S: Also, join our "Cloud Native Jenkins" talk <http://sched.co/F9NT> at 
DevOps World | Jenkins World, we will present an demo based on these tools.

On Thursday, September 6, 2018 at 3:46:41 PM UTC+2, James Rawlings wrote:
>
> We’ve been trying this out in Jenkins X and love it, great stuff!
>
> On 6 Sep 2018, at 14:12, Oleg Nenashev <[email protected] <javascript:>> 
> wrote:
>
> Hi all,
>
> During last weeks I have made some experiments w.r.t integrating 
> Jenkinsfile Runner and Configuration as Code.
> As a PoC, I have updated Custom War Packager 
> <https://github.com/jenkinsci/custom-war-packager> and added support of 
> Jenkinsfile Runner Docker image bundling there.
> You can find a demo here: 
> https://github.com/jenkinsci/custom-war-packager/tree/master/demo/jenkinsfile-runner
>
> Generally this PoC allows producing a Docker image, which includes 
> Jenkinsfile Runner, arbitrary Jenkins plugins, and also self-configuration 
> logic powered by JCasC or, if needed, System Groovy scripts. Everything i s 
> bundled statically hence there is no performance overhead for downloading 
> plugins when the Docker image starts. Then you can run this image in Docker 
> or Kubernetes by a single command
>
> So far it uses an old version of Jenkinsfile Runner, but my plan is 
> replace it by the stock version once it is finalized. For now it is just a 
> *proof 
> of concept*, but it may be interesting for some cases.
>
> Best regards,
> Oleg
>
>
> On Tuesday, May 1, 2018 at 6:29:02 PM UTC+2, Jesse Glick wrote:
>>
>> On Tue, May 1, 2018 at 10:42 AM, nicolas de loof 
>> <[email protected]> wrote: 
>> >> There is a gigantic long tail of Jenkins features (mostly plugins) 
>> >> which would not work in a Build Publisher-like environment 
>> > 
>> > Not sure what you have in mind (if you have a concrete sample this 
>> could 
>> > help). 
>>
>> The first thing that pops into my head is Throttle Concurrent Builds, 
>> but I think if you start going through randomly selected plugins you 
>> will find dozens if not hundreds of examples. 
>>
>> > what I'd like to achieve is to fully remove Jenkins Web UI and only 
>> > rely on Github commit status 
>> > for user interaction […]. So plugins 
>> > would only make sense 
>> > during the build, and any UI contributing plugin would just be 
>> excluded. 
>>
>> OK, this is definitely an interesting project, but I would consider it 
>> a novel CI system with a modest degree of Jenkins compatibility. 
>>
>> > echo "entering stage foo" > /var/run/jenkins.sock 
>>
>> Or I was just thinking some kind of magic string to stdout/stderr. I 
>> have seen some scripts using ANSI control characters, or the 
>> (freestyle-compatible) plugin I mentioned before lets you configure 
>> any regexp. 
>>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/49cc7f1c-ca41-4bd7-b0bf-639d1a1c803c%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/49cc7f1c-ca41-4bd7-b0bf-639d1a1c803c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e7c0c1cb-69a8-49c1-bae0-276b8cd1a71e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to