jenkinsci/jenkinsfile-runner

Add support of routing STDIN from files in the --cli mode

Open

#225 opened on Nov 6, 2019

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Java (291 forks)batch import
enhancementgood first issue

Repository metrics

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

Description

It is a follow-up to https://github.com/jenkinsci/jenkinsfile-runner/pull/207 by @xxyy . Currently the Jenkins CLI works well in the interactive mode, but only few commands there actually make sense. We could extend the feature by supporting passing STDIN via a file so that we could get commands like create-job operational inside jenkinsfile runner.

Suggested syntax:

> create-job foo <config.xml
> build foo

Later it can be extended by a create-job flavor which takes Jenkinsfile as an argument, instead XML

Contributor guide

Research direction
Investigate the current STDIN handling in the CLI mode and the references to PR #207. Identify where file input parsing would be added in the command processing flow.
Tech stack
java
Domain
backendcli
Issue type
Feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaJenkins CLI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60