Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

[Oleg Nenashev]

Hi all,

Few weeks ago I have created a ci.jenkins.io-runner repository. This repository is my reference implementation of the Jenkinsfile Runner & Custom WAR Packager flow for creating custom single-shot Jenkins masters with built-in self-configuration logic. The flow is described here and here, and it is used in Jenkins X Serverless and in the JFR for GitHub Actions prototype .

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 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) or a Jenkinsfile Runner Test framework (JENKINS-54391)
  
• Development tool for Jenkins contributors working on Jenkins 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 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

[Slide]

Does this support testing trusted stuff at all (e.g., isTrusted in the infra pipeline library)? Or is this mainly for non-trusted components?

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCYpoenZ6mcU6DhVgyTVKfMAv5Kwx6Qa_CLyNU1D61s3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Website: http://earl-of-code.com

[Oleg Nenashev]

For infra.isTrusted() it will return false, but it may be possible to override it in JCasC if needed.

Generally ci.jenkins.io-runner has a number of limitations: https://github.com/oleg-nenashev/ci.jenkins.io-runner#limitations (e.g. DinD or Windows support), so I would not expect it to work for all cases.  oleg-nenashev/demo-jenkins-config-as-code can be used for a better replication of the ci.jenkins.io environment, but I have never tested packaging or Docker publishing flows there.

BR, Oleg

You received this message because you are subscribed to the Google Groups "Jenkins Pipeline Authoring SIG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-pipeline-auth...@googlegroups.com.
To post to this group, send email to jenkins-pipelin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-pipeline-authoring-sig/CAPiUgVfuP-M5Vx%2BJHipegwyRjdUdPn9ZCpmSskgyUn-6oxjMVg%40mail.gmail.com.