jenkinsci/jenkinsfile-runner

Deploy a CD flow for the Windows Vanilla images

Open

#212 opened on Oct 24, 2019

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Java (291 forks)batch import
chorehelp wanted

Repository metrics

Stars
 (1,090 stars)
PR merge metrics
 (Avg merge 47d 2h) (3 merged PRs in 30d)

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

Research direction
Explore setting up a continuous delivery pipeline for Windows Vanilla Docker images, possibly using GitHub Actions or Jenkins with Windows agents, and push to the jenkins4eval DockerHub organization. Investigate alternatives since ci.jenkins.io is unstable.
Tech stack
dockerjava
Domain
devopsinfrastructureci cd
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
DockerJenkinsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40