Hi all,

I am currently working on Jenkinsfile Runner
<https://github.com/jenkinsci/jenkinsfile-runner> and finalizing the key
feature requests towards the 1.0 release. One of the common use-cases is
having community-provided images which would support common pipelines, e.g.
building Java projects with Maven (issue #344
<https://github.com/jenkinsci/jenkinsfile-runner/issues/344>). We already
have similar images for inbound agents (jenkinsci/jnlp-agents
<https://github.com/jenkinsci/jnlp-agents>). Jenkins X 1.x also included
multiple images for Jenkinsfile Runner in jenkins-x/jenkins-x-serverless
<https://github.com/jenkins-x/jenkins-x-serverless>.

I have created a first image for Maven/JDK8 in
oleg-nenashev/jenkinsfile-runner-image-packs
<https://github.com/oleg-nenashev/jenkinsfile-runner-image-packs>. It is
based on ci.jenkins.io-runner, but without Jenkins-specific magic. Would
appreciate feedback and contributions. A few questions to others:

   - *Hosting.* I would like to move this repository to the jenkinsci
   GitHub organization so that the repo could be accessible to users and
   contributors there. Would othersbe fine with that?
   - *Terminology*. I currently use the "Image Pack" terminology. Similar
   repositories use "Buildpacks" in Jenkins X and K8s, "Convenience Images"
   from CircleCI. I do not want to use "buildpacks" to avoid
   possible confusion with https://buildpacks.io/ . If anyone has ideas
   about better naming, would appreciate them.

Any other feedback will be also appreciated.

Thanks for your time,
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/CAPfivLAa5pC8rMBwLPM8LHtWzUC_y1W2R6O1p1CFwJC9HM8RHQ%40mail.gmail.com.

Reply via email to