[Jenkins-infra] Deleting libzfs4j Pipeline from ci.jenkins.io

Kohsuke Kawaguchi kk at kohsuke.org
Tue Nov 28 17:19:59 UTC 2017

Ack. This library really only plays a minor role in Jenkins anyway.

On Mon, Nov 27, 2017 at 2:48 PM R. Tyler Croy <tyler at monkeypox.org> wrote:

> (resending because I fat-fingered the CC before).
> While working on INFRA-1356 today I discovered that a Pipeline for a
> non-Jenkins owned project was added a whiles back to the Libraries folder
> (https://github.com/kohsuke/libzfs4j)
> I deleted the Pipeline since we do not build personal or other
> organizations
> projects in our build and test infrastructure. This library looks like it
> sits
> in the netherworld between Jenkins and the rest of the Java-ecosystem. It
> reminds me of a similar discussion I had with oleg-nenashev and recampbell
> about some Jenkins-related libraries which were in the Jenkins solar
> system but
> not really part of the project.
> To spare a big discussion, the gist of guidance I gave at the time was
> that if
> it's not part of the Jenkins project, then it doesn't get to utilize our
> infrastructure. Tbe basic logic of this aside, there are also contractual
> reasons to abide by this rule based on our infra agreement with Microsoft.
> If it makes sense, however, to migrate this into the jenkinsci GitHub
> organization, it will automatically have its Pipeline slurped up by the
> GitHub
> Org Folder on ci.jenkins.io.
> 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
> ------------------------------------------------------
Kohsuke Kawaguchi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171128/00065419/attachment.html>

More information about the Jenkins-infra mailing list