Skip to content

Jenkins Wrapper Public Testing

Background

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 we welcome testing by GitLab's wider community to help us improve on this first iteration.

Related Issues:

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.

  1. Get started by reviewing the Jenkinsfile Runner Container Builder's README file.
  2. 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.)
  3. 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.
  4. Install the Jenkinsfile Runner Container Builder. Please note there is no third-party binary to run or checkout.
  5. Generate container to house your Jenkins instance
  6. Run the Jenkinsfile in GitLab CI job
  7. Provide your feedback, notes, results (success, failure, suggestions) in discussion thread under the Comment created in Step 2 above.
  8. (optional) Use artifacts on GitLab
  9. (optional) Run multiple Jenkinsfiles

Other Documentation

Edited by 🤖 GitLab Bot 🤖