Jenkins Wrapper solution validation
What's this issue all about? (Background and context)
To help support a customer's long-term efforts to migrate from Jenkins to GitLab CI/CD, we want to offer a limited purpose interim solution in a Jenkins wrapper.
For this purpose, we created a CLI tool to automate the creation of a container for a customer’s Jenkins installation, with the intent that the container serves as a runtime Jenkins environment to run a Jenkins file inside a CI pipeline as a single CI job.
This tool is in beta and now we are set to test it out in order to improve on this first iteration.
Related Issues:
- Wrapper for Jenkins execution inside of GitLab MVC
- CLI tool for building Jenkins execution container from existing server
Other Documentation:
- Migrating from Jenkins (for general awareness, not for testing in this issue)
What are the overarching goals for the research?
Find out how useful the current implementation of the Jenkins wrapper is and what is exactly needed in order to make it a lovable product feature.
Hypothesis
Users are able easily run their Jenkins file inside a CI pipeline without hiccups.
Goals
Understand how the MVC impacts users' process of migrating from Jenkins to GitLab CI.
Objectives
Identify any hurdles users face while running their existing Jenkins jobs in GitLab CI pipelines.
What persona, persona segment, or customer type experiences the problem most acutely?
What business decisions will be made based on this information?
TBD
What, if any, relevant prior research already exists?
Who will be leading the research?
What timescales do you have in mind for the research?
TBD
Relevant links (script, prototype, notes, etc.)
Beta Testing Instructions
Please follow the steps below for your testing and ask questions or report issues via Comments in this issue. All comments are welcome to help us improve the current beta version of the tool.
- Get started by reviewing the Jenkinsfile Runner Container Builder's README file.
- Please describes your system and Jenkins version in a Comment on this issue to confirm your instance satisfies the Requirements and Limitations. (Further discussion/findings from your testing can be added under this Comment as noted in Step 7 below.)
- Setup your project. This is an optional step if you do not already have a project in GitLab OR you wish to isolate this testing to a new project to avoid impacting existing projects.
- Install the Jenkinsfile Runner Container Builder. Please note there is no third-party binary to run or checkout.
- Generate container to house your Jenkins instance
- Run the Jenkinsfile in GitLab CI job
- Note your results (success, failure, suggestions) in discussion thread under the Comment created in Step 2 above.
- (optional) Use artifacts on GitLab
- (optional) Run multiple Jenkinsfiles
Other Documentation
Link to discussion guide.
- Migrating from Jenkins (for general awareness, not for testing in this issue)