For more detail check out how to use jx boot.
How do I upgrade boot?
If anything ever goes wrong (e.g. your cluster, namespace or tekton gets deleted), you can always re-run jx boot on your laptop to restore your cluster.
How do I add more resources?
Add more resources (e.g.
Ingress, ConfigMap, Secret) to your development environment by adding YAML files to the boot
How do I add new Environments?
Add a new
Environment resource to the
env/templates folder for each new environment you want tto create. We’ve only added
dev, staging, production currently.
From your running cluster you can always grab the staging
Environment resource via the following (where XXX is the name of the staging repository returned via
kubectl get sr):
kubectl get env staging -oyaml > env/templates/myenv.yaml kubectl get sr XXX -oyaml > env/templates/myenv-sr.yaml
then modify the YAML to suit, changing the names of the resources to avoid clashing with your staging repository.
How to to manage SourceRepository resources?
See how to update your boot configuration with the latest SourceRepository resources
How do I map SourceRepository to a custom Scheduler
You need to map your
SourceRepository to a
Scheduler via either specifying
--scheduler when you
jx create quickstart / jx import your repository or modifying the
spec.scheduler.name in your development git repository or specifying a different default scheduler on the
dev environment.spec.teamSettings.defaultScheduler.name then the next time the prow configuration is generated (on
jx create quickstart / jx import / jx boot it’ll update the prow config to use your scheduler
How do I add more charts to Jenkins X?
It depends on which namespace you want the charts to be installed.
If its in the development environment (the
jx namespace by default) then
env/requirements.yaml is where to add the chart and for a chart
foo you can add
env/foo/values.yaml to configure it. (or
env/foo/values.tmpl.yaml if you want to use some templating of the
Though if you want our chart to be in another namespace then we use the convention of adding a folder in the
system directory in the boot configuration (e.g. like we do for ingress, cert manager, velero, service mesh etc). So make a new folder in
system and add the
jx step helm apply step in the pipeline in
jenkins-x.yml like we do for
How do I disable the ingress controller?
If you already have your own ingress controller and do not want
jx boot to install another one you can just delete the
install-nginx-controller step in your dev environment git repository. e.g. remove this step from the
jenkins-x.yml in your dev environment git repository
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.