[Jenkins-infra] Proposal: open the flood gates for all Plugins' Pipelines on ci.jenkins.io

Arnaud Héritier aheritier at gmail.com
Fri Jun 16 19:12:10 UTC 2017

Go go go
Eat your own ...

Le ven. 16 juin 2017 à 20:54, R. Tyler Croy <tyler at monkeypox.org> a écrit :

> Last year we started allowing plugin developers use of new shiney elastic
> compute capacity on ci.jenkins.io provided by our friends at Microsoft.
> Today I
> would like to proposal that we open the flood gates, and add "*-plugin" to
> our
> GitHub Organization Folder here: https://ci.jenkins.io/job/Plugins/
> What's changed:
>   * In the realm of Pipeline administrative manageability, practically
> nothing
>     unfortunately. We are still unable to globally prevent runaway
> Pipelines.
>     We are still unable to limit capabilities of Pipelines, disallowing
>     specific steps, or label/node assignments.
>   * The shared library (https://github.com/jenkins-infra/pipeline-library),
> and
>     its `buildPlugin()` method has been working fantastically. Practically
>     every Jenkinsfile I see is simply: buildPlugin()
>   * The "file an INFRA ticket" approach has been working, but is still
> manual
>     work, and as everybody knows: automated is better than manual.
>   * We haven't been spending enough money on Azure. I'm only half-joking
> here,
>     Microsoft has been tremendously gracious, and we're no where close to
> using
>     our annual budget :)
>   * Speaking of budget, stephenc's done a lot of great work to help Jenkins
>     (more specifically the scm-api and github-branch-source plugins)
> handle the
>     GitHub rate limits. While we sometimes exhaust our hourly limit, the
>     behavior of the github-branch-source now gives me great confidence that
>     requires will not be disrupted/discarded, but merely delayed.
> I think the risk is low, Pipeline has matured quite a bit since I first
> discussed this topic with the dev community. I also think that the more
> contributors who are using Pipeline as a user (editing a Jenkinsfile), the
> more
> likely plugin contributors are going to want to have a stellar experience
> in
> Pipeline for their plugin, so win-win :)
> If this seems reasonable to folks, I'll discuss a couple last-minute items
> with
> olblak and we can light up ci.jenkins.io with 1300+ plugins :D
> Cheers
> - R. Tyler Croy
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>      xmpp: rtyler at jabber.org
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
> --
> 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+unsubscribe at googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/20170616185430.ggedoq27zymb6kg2%40blackberry.coupleofllamas.com
> .
> For more options, visit https://groups.google.com/d/optout.
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20170616/ef12577e/attachment.html>

More information about the Jenkins-infra mailing list