jenkinsci/jenkinsfile-runner

Deploy a CD flow for the Windows Vanilla images

Open

#212 opened on Oct 24, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (1,090 stars) (291 forks)batch import
chorehelp wanted

Description

After https://github.com/jenkinsci/jenkinsfile-runner/pull/206 by @slide we still need to setup a delivery flow for these images so that they can be actually used from the jenkins4eval DockerHub organization.

ci.jenkins.io Does not seem to be stable enough ATM, we might need alternate solution.

Contributor guide

Tech stack
docker
Domain
devopsci cd
Issue type
devops
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
DockerCI/CD pipeline knowledgeWindows image building
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the existing PR #206 for the base Windows Vanilla images. Design a continuous delivery pipeline to automatically build and push these images to the jenkins4eval DockerHub organization. Consider using Azure Pipelines or a Jenkins instance with Windows agents as an alternative to ci.jenkins.io. Investigate the current state of ci.jenkins.io and propose a robust solution. Check the repository's existing CI configuration for guidance.