WARNING: Jenkins X version 2.x is unmaintained. Do not use it.
Please refer to the v3 documentation for the latest supported version.
If you already have some source code you wish to import into Jenkins X then you can use the jx import command. e.g.
cd my-cool-app jx import
Import will perform the following actions (prompting you along the way):
- add your source code into a git repository if it isn’t already
- create a remote git repository on a git service, such as GitHub
- push your code to the remote git service
- add any required files to your project if they do not exist:
Dockerfileto build your application as a docker image
pipeline.ymlto implement the CI / CD pipeline
- helm chart to run your application inside Kubernetes
- register a webhook on the remote git repository to your teams Jenkins
- trigger the first pipeline
config.jsonfile at the root of your project, or else it will be interpreted as kaniko configuration file, and can lead to a permission error when jx will try to push the builded project image to the docker registry.
Avoiding docker + helm
If you are importing a repository that does not create a docker image you can use the
--no-draft command line argument which will not use Draft to default the Dockerfile and helm chart.
Importing via URL
If you wish to import a project which is already in a remote git repository then you can use the
jx import --url https://github.com/jenkins-x/spring-boot-web-example.git
Importing GitHub projects
If you wish to import projects from a github organisation you can use:
jx import --github --org myname
You will be prompted for the repositories you wish to import. Use the cursor keys and space bar to select/deselect the repositories to import.
If you wish to default all repositories to be imported (then deselect any you don’t want add
jx import --github --org myname --all
To filter the list you can add a
jx import --github --org myname --all --filter foo
When importing projects into Jenkins X we use git branch patterns to determine which branch names are automatically setup for CI/CD.
Typically that may default to something like
master|PR-.*|feature.*. That means that the
master branch, any branch starting with
feature will be scanned to look for a
pipeline.yml to setup the CI/CD pipelines.
If you use another branch name than
master such as
develop or whatever you can change this pattern to be whatever you you like via the
--branches argument whenever you run jx import or jx create quickstart.
jx import --branches "develop|PR-.*|feature.*"
You may wish to set this to just
.* to work with all branches,.
jx import --branches ".*"
Configuring your teams branch patterns
Usually a team uses the same naming conventions for branches so you may wish to configure the branch patterns at a team level so that they will be used by default if anyone in your team runs jx import or jx create quickstart.
These settings are stored in the Environment Custom Resource in Kubernetes.
To set the branch patterns for your team jx create branchpattern command.
jx create branchpattern "develop|PR-.*|feature.*"
You can then view the current branch patterns for your team via the jx get branchpattern command:
jx get branchpattern
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.