Does this support testing trusted stuff at all (e.g., isTrusted in the infra pipeline library)? Or is this mainly for non-trusted components?
On Fri, Dec 14, 2018 at 10:15 AM Oleg Nenashev <[email protected]> wrote: > Hi all, > > Few weeks ago I have created a ci.jenkins.io-runner > <https://github.com/oleg-nenashev/ci.jenkins.io-runner> repository. This > repository is my reference implementation of the Jenkinsfile Runner > <https://github.com/jenkinsci/jenkinsfile-runner> & Custom WAR Packager > <https://github.com/jenkinsci/custom-war-packager> flow for creating > custom single-shot Jenkins masters with built-in self-configuration logic. > The flow is described here > <https://jenkins.io/blog/2018/09/12/speaker-blog-a-cloud-native-jenkins/#ephemeral-jenkins-masters-research> > and here <https://jenkins.io/blog/2018/10/16/custom-war-packager/>, and > it is used in Jenkins X Serverless > <https://github.com/jenkins-x/jenkins-x-serverless/>and in the JFR for > GitHub Actions prototype > <https://github.com/jonico/jenkinsfile-runner-github-actions> . > > As you may guess from the name, the repository tries to emulate the > ci.jenkins.io configuration so that the package can be used to develop > Jenkinsfiles and Jenkins Pipeline Library > <https://github.com/jenkins-infra/pipeline-library/> patches (e.g. for > *buildPlugin()*). > > So the repository can be used for several purposes: > > - Reference implementation of a tool for local Pipeline Development > (Pipeline Authhoring SIG in CC) > - Reference implementation of the CWP and JFR packaging flow > - Playground for Jenkinsfile Runner contributors who may want to > experiment with new features, e.g. Dependabot for autoupgrades ( > JENKINS-54834 <https://issues.jenkins-ci.org/browse/JENKINS-54834>) or > a Jenkinsfile Runner Test framework (JENKINS-54391 > <https://issues.jenkins-ci.org/browse/JENKINS-54391>) > - Development tool for Jenkins contributors working on Jenkins > Pipeline Library <https://github.com/jenkins-infra/pipeline-library/> > > Why do I ask about hosting? > > - For some cases like JFR Test Framework, it would be really great to > have an access to the CI instance like ci.jenkins.io > - I would be interested to prototype JEP-217: Experimental Jenkins > organization on DockerHub > <https://github.com/jenkinsci/jep/tree/master/jep/217> using this > repository > - It would be nice to get it officially hosted at the end of the day > > Would be great to get your feedback. > > Thanks in advance, > Oleg > > -- > 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/CAPfivLCYpoenZ6mcU6DhVgyTVKfMAv5Kwx6Qa_CLyNU1D61s3A%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCYpoenZ6mcU6DhVgyTVKfMAv5Kwx6Qa_CLyNU1D61s3A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Website: http://earl-of-code.com -- 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/CAPiUgVfuP-M5Vx%2BJHipegwyRjdUdPn9ZCpmSskgyUn-6oxjMVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
