jx create codeship
jx create codeship
Creates a build on Codeship to create/update JX clusters
Synopsis
Creates a build on Codeship to create/update JX clusters
jx create codeship [flags]
Examples
jx create codeship
# to specify the org and service account via flags
jx create codeship -o org --gke-service-account <path>
Options
--advanced-mode Advanced install options. This will prompt for advanced install options
--azure-acr-subscription string The Azure subscription under which the specified docker-registry is located
--buildpack string The name of the build pack to use for the Team
--cleanup-temp-files Cleans up any temporary values.yaml used by helm install [default true] (default true)
--cloud-environment-repo string Cloud Environments Git repo (default "https://github.com/jenkins-x/cloud-environments")
--cloud-provider string The cloud provider (currently gke only) - cannot be used in conjunction with --cluster
--cloudbees-auth string Auth used when setting up a letter/tenant cluster, format: 'username:password'
--cloudbees-domain string When setting up a letter/tenant cluster, this creates a tenant cluster on the cloudbees domain which is retrieved via the required URL
-c, --cluster stringArray Name and Kubernetes provider (currently gke only) of clusters to be created in the form --cluster foo=gke
--cluster-name string The name of a single cluster to create - cannot be used in conjunction with --cluster
--codeship-organisation string The Codeship organisation to use, this will not be stored anywhere
--codeship-password string The password to login to Codeship with, this will not be stored anywhere
--codeship-username string The username to login to Codeship with, this will not be stored anywhere
--config-file string Configuration file used for installation
--default-admin-password string the default admin password to access Jenkins, Kubernetes Dashboard, ChartMuseum and Nexus
--default-admin-username string the default admin username to access Jenkins, Kubernetes Dashboard, ChartMuseum and Nexus (default "admin")
--default-environment-prefix string Default environment repo prefix, your Git repos will be of the form 'environment-$prefix-$envName'
--docker-registry string The Docker Registry host or host:port which is used when tagging and pushing images. If not specified it defaults to the internal registry unless there is a better provider default (e.g. ECR on AWS/EKS)
--docker-registry-org string The Docker Registry organiation/user to create images inside. On GCP this is typically your Google Project ID.
--domain string Domain to expose ingress endpoints. Example: jenkinsx.io
--draft-client-only Only install draft client
--environment-git-owner string The Git provider organisation to create the environment Git repositories in
--exposecontroller-pathmode path The ExposeController path mode for how services should be exposed as URLs. Defaults to using subnets. Use a value of path to use relative paths within the domain host such as when using AWS ELB host names
--exposecontroller-urltemplate string The ExposeController urltemplate for how services should be exposed as URLs. Defaults to being empty, which in turn defaults to "{{.Service}}.{{.Namespace}}.{{.Domain}}".
--exposer string Used to describe which strategy exposecontroller should use to access applications (default "Ingress")
--external-dns Installs external-dns into the cluster. ExternalDNS manages service DNS records for your cluster, providing you've setup your domain record
--external-ip string The external IP used to access ingress endpoints from outside the Kubernetes cluster. For bare metal on premise clusters this is often the IP of the Kubernetes master. For cloud installations this is often the external IP of the ingress LoadBalancer.
-f, --fork-git-repo string The Git repository used as the fork when creating new Organisation Git repos (default "https://github.com/jenkins-x/default-organisation.git")
--git-api-token string The Git API token to use for creating new Git repositories
--git-email string The email to use for any git commits (default "codeship@jenkins-x.io")
--git-provider-kind string Kind of Git server. If not specified, kind of server will be autodetected from Git provider URL. Possible values: bitbucketcloud, bitbucketserver, gitea, gitlab, github, fakegit
--git-provider-url string The Git server URL to create new Git repositories inside (default "https://github.com")
--git-public Create new Git repositories as public
--git-user string The name to use for any git commits (default "Codeship")
--git-username string The Git username to use for creating new Git repositories
--gitops Creates a git repository for the Dev environment to manage the installation, configuration, upgrade and addition of Apps in Jenkins X all via GitOps
--gke-disk-size string Size in GB for node VM boot disks. Defaults to 100GB (default "100")
--gke-enable-autorepair Sets autorepair feature for a cluster's default node-pool(s) (default true)
--gke-enable-autoupgrade Sets autoupgrade feature for a cluster's default node-pool(s)
--gke-machine-type string The type of machine to use for nodes
--gke-max-num-nodes string The maximum number of nodes to be created in each of the cluster's zones
--gke-min-num-nodes string The minimum number of nodes to be created in each of the cluster's zones
--gke-preemptible Use preemptible VMs in the node-pool
--gke-project-id string Google Project ID to create cluster in
--gke-service-account string The GKE service account to use
--gke-use-enhanced-apis Enable enhanced APIs to utilise Container Registry & Cloud Build
--gke-use-enhanced-scopes Use enhanced Oauth scopes for access to GCS/GCR
--gke-zone string The compute zone (e.g. us-central1-a) for the cluster
--global-tiller Whether or not to use a cluster global tiller (default true)
--helm-client-only Only install helm client
--helm-tls Whether to use TLS with helm
--helm3 Use helm3 to install Jenkins X which does not use Tiller
-h, --help help for codeship
--ignore-terraform-warnings Ignore any warnings about the Terraform plan being potentially destructive
--ingress-class string Used to set the ingress.class annotation in exposecontroller created ingress
--ingress-cluster-role string The cluster role for the Ingress controller (default "cluster-admin")
--ingress-deployment string The name of the Ingress controller Deployment (default "jxing-nginx-ingress-controller")
--ingress-namespace string The namespace for the Ingress controller (default "kube-system")
--ingress-service string The name of the Ingress controller Service (default "jxing-nginx-ingress-controller")
--install-dependencies Enables automatic dependencies installation when required
--install-only Force the install command to fail if there is already an installation. Otherwise lets update the installation
--jx-environment string The cluster name to install jx inside (default "dev")
--kaniko Use Kaniko for building docker images
--keep-exposecontroller-job Prevents Helm deleting the exposecontroller Job and Pod after running. Useful for debugging exposecontroller logs but you will need to manually delete the job if you update an environment
--knative-build Note this option is deprecated now in favour of tekton. If specified this will keep using the old knative build with Prow instead of the strategic tekton
--local-cloud-environment Ignores default cloud-environment-repo and uses current directory
--local-helm-repo-name string The name of the helm repository for the installed ChartMuseum (default "releases")
--local-organisation-repository string Rather than cloning from a remote Git server, the local directory to use for the organisational folder
--long-term-storage Enable the Long Term Storage option to save logs and other assets into a GCS bucket (supported only for GKE)
--lts-bucket string The bucket to use for Long Term Storage. If the bucket doesn't exist, an attempt will be made to create it, otherwise random naming will be used
-n, --name string The name of the service account to create
--namespace string The namespace the Jenkins X platform should be installed into (default "jx")
--ng Use the Next Generation Jenkins X features like Prow, Tekton, No Tiller, Vault, Dev GitOps
--no-active-cluster Tells JX there's isn't currently an active cluster, so we cannot use it for configuration
--no-brew Disables brew package manager on MacOS when installing binary dependencies
--no-default-environments Disables the creation of the default Staging and Production environments
--no-gitops-env-apply When using GitOps to create the source code for the development environment and installation, don't run 'jx step env apply' to perform the install
--no-gitops-env-repo When using GitOps to create the source code for the development environment this flag disables the creation of a git repository for the source code
--no-gitops-env-setup When using GitOps to install the development environment this flag skips the post-install setup
--no-gitops-vault When using GitOps to create the source code for the development environment this flag disables the creation of a vault
--no-tiller Whether to disable the use of tiller with helm. If disabled we use 'helm template' to generate the YAML from helm charts then we use 'kubectl apply' to install it to avoid using tiller completely. (default true)
--on-premise If installing on an on premise cluster then lets default the 'external-ip' to be the Kubernetes master IP address
-o, --organisation-name string The organisation name that will be used as the Git repo containing cluster details, the repo will be organisation-<org name>
-p, --project string The GCP project to create the service account in
--prow Enable Prow to implement Serverless Jenkins and support ChatOps on Pull Requests
--recreate-existing-draft-repos Delete existing helm repos used by Jenkins X under ~/draft/packs
--register-local-helmrepo Registers the Jenkins X ChartMuseum registry with your helm client [default false]
--remote-environments Indicates you intend Staging and Production environments to run in remote clusters. See https://jenkins-x.io/getting-started/multi-cluster/
--remote-tiller If enabled and we are using tiller for helm then run tiller remotely in the kubernetes cluster. Otherwise we run the tiller process locally. (default true)
--skip-auth-secrets-merge Skips merging the secrets from local files with the secrets from Kubernetes cluster
--skip-cluster-role Don't enable cluster admin role for user
--skip-ingress Skips the installation of ingress controller. Note that a ingress controller must already be installed into the cluster in order for the installation to succeed
--skip-installation Provision cluster(s) only, don't install Jenkins X into it
--skip-login Skip Google auth if already logged in via gcloud auth
--skip-setup-tiller Don't setup the Helm Tiller service - lets use whatever tiller is already setup for us.
--skip-terraform-apply Skip applying the generated Terraform plans
--static-jenkins Install a static Jenkins master to use as the pipeline engine. Note this functionality is deprecated in favour of running serverless Tekton builds
--tekton Enables the Tekton pipeline engine (which used to be called knative build pipeline) along with Prow to provide Serverless Jenkins. Otherwise we default to use Knative Build if you enable Prow
--tiller-cluster-role string The cluster role for Helm's tiller (default "cluster-admin")
--tiller-namespace string The namespace for the Tiller when using a global tiller (default "kube-system")
--timeout string The number of seconds to wait for the helm install to complete (default "6000")
--urltemplate string For ingress; exposers can set the urltemplate to expose
--user-cluster-role string The cluster role for the current user to be able to administer helm (default "cluster-admin")
--username string The Kubernetes username used to initialise helm. Usually your email address for your Kubernetes account
--vault Sets up a Hashicorp Vault for storing secrets during installation (supported only for GKE)
--vault-bucket-recreate If the vault bucket already exists delete it then create it empty (default true)
--version string The specific platform version to install
--versions-ref string Jenkins X versions Git repository reference (tag, branch, sha etc)
--versions-repo string Jenkins X versions Git repo (default "https://github.com/jenkins-x/jenkins-x-versions.git")
Options inherited from parent commands
-b, --batch-mode Runs in batch mode without prompting for user input (default true)
--verbose Enables verbose output
SEE ALSO
- jx create - Create a new resource