Re: External Artifact Storage

+1 -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit

External Artifact Storage

Hi there, With the goal to make Jenkins more "cloud-friendly" or "cloud-native" I have created a JEP draft to enable the storage of artifacts outside the Jenkins home, ready for review https://github.com/carlossg/jep/tree/jep-submission/jep/ TL;DR Adding an ArtifactManager implementation

Upcoming JEP for usage of Incrementals repository

After IEP-9¹ there was a need for an actual system for producing and consuming these quasi-release “incremental” artifacts from Jenkins projects (typically based on Maven). This is just a heads-up that I am working on a preparing a JEP, probably for the 3xx “Essentials” series; and a reference

Re: [Even:Jenkins World EU 2018] CFP Closes this Sunday

Hi All, A friendly reminder that Jenkins World EU CFP will be closing this Sunday, 15 April. https://jenkinsworld2018cfp.hubb.me/Home/Index?ReturnUrl=%2fHome%2fDashboard Thnx, alyssa On Thu, Mar 15, 2018 at 3:04 PM, Alyssa Tong wrote: > Hello, > > A few updates to

Re: TODO-Plugin guidance

On Thu, Apr 12, 2018 at 7:57 AM, Ronald Petty wrote: > The > global.jelly is not generated, so there was no Configure screen for the > plugin. Yes, that was removed from the `Builder` archetype, as it was using an old idiom that does not generalize well and is no longer

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

On Thu, Apr 12, 2018 at 5:13 AM, Robert Sandell wrote: > Yes declarative has both of these in a way via the when directive's branch > and changeset conditions. If I've interpreted forBranch and forChangesIn > correctly `forChangesIn` sounded to me like something

Re: TODO-Plugin guidance

Thanks for the information. I did find part of the issue for me. The global.jelly is not generated, so there was no Configure screen for the plugin. There was an option (which I didn't check first time) for the job, but not the plugin. Adding global.jelly, repackage, it then worked like it

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

Yes declarative has both of these in a way via the when directive's branch and changeset conditions. If I've interpreted forBranch and forChangesIn correctly :) https://jenkins.io/doc/book/pipeline/syntax/#when /B 2018-04-11 23:39 GMT+02:00 Jesse Glick : > Declarative

Re: [DISCUSS] Change Jenkins default logging format

As I have already said many times, I fully support this initiative. Tomcat has done this move a while ago and it was a great success. Cyrille On Wednesday, April 4, 2018 at 3:18:00 PM UTC+2, Baptiste Mathus wrote: > > Hello everyone, > > Having worked on more things related to Jenkins logging

Re: [GSoC 2018] - Preliminary announcement

Hi, I want to be a mentor. I cannot access this link. Is there any new link? On Tuesday, December 19, 2017 at 4:32:42 PM UTC+5:30, Oleg Nenashev wrote: > > Hi, > > I suggest discussing the ideas in a Google Doc. > Wiki is fine, but it is complicated to handle the feedback there. > I have

Re: jep-200 issue

Thanks a lot Jesse. We will consider all these things when upgrading . Kind Regards, Eugen On Wed, Apr 11, 2018 at 7:51 PM, Jesse Glick wrote: > On Wed, Apr 11, 2018 at 10:54 AM, Eugen Horovitz > wrote: > > The rule violations :