+1
On Fri, 14 Dec 2018 at 11:59, Tracy Miranda wrote:
> Hi all,
>
> On behalf of CloudBees, I’d like to request the permission to use the
> following name that uses ‘Jenkins’ in it:
>
>- CloudBees Jenkins X Distribution
>
> This will be a name of a product distribution Jenkins X from
we solved this in Jenkins X through the use of Prow for handling webhooks &
orchestrating the serverless jenkins pod and then using kubernetes custom
resources to maintain state (pipeline activities, environments, teams,
releases etc)
https://jenkins-x.io/news/serverless-jenkins/
we then use an
sounds like a great idea! What kind of times would suit folks?
On 15 March 2018 at 22:35, Michael Neale wrote:
> Nice description!
>
> Given the disparate timezones of everyone involved, would it make sense to
> have a few office hour type things? (not sure if there is
Thanks for those kind words Kohsuke. More inline...
On Thursday, March 15, 2018 at 2:32:48 AM UTC, Kohsuke Kawaguchi wrote:
>
> Thanks James,
>
> This is an important and exciting JEP for me, because it sets the mission
> & scope for a new project “Jenkins X.”
> Starting from Jenkins 2, in
I've just submitted a draft of a new JEP:
https://github.com/jenkinsci/jep/pull/62
You can read the JEP in full here:
https://github.com/jstrachan/jep/blob/jx/jep/400/README.adoc
I hope this makes sense & some of you find it interesting. I'd love
feedback if anyone has any!
I'll try blog more
Hello folks!
I’m James Strachan. I’m a long time Jenkins user and OSS developer. (e.g. I
created Groovy, Apache Camel, dom4j, jaxen etc Though I’m going to keep
quiet about Jelly... ;). I’ve worked on a few Jenkins plugins over the
years but never much on the core of Jenkins.
So I’ve been
I've dipped my toe into the world of writing Jenkins Workflow Steps; so far
so good!
I've written a little hubot chat bot approval step as a kinda
facade/decorator of InputStep:
https://github.com/fabric8io/fabric8-jenkins-workflow-steps#hubotapprove
whats a bit smelly though is that the