openshift-cli-new-build man page

openshift cli new-build — Create a new build configuration

Synopsis

openshift cli new-build [Options]

Description

Create a new build by specifying source code

This command will try to create a build configuration for your application using images and code that has a public repository. It will lookup the images on the local Docker installation (if available), a Docker registry, or an image stream.

If you specify a source code URL, it will set up a build that takes your source code and converts it into an image that can run inside of a pod. Local source must be in a git repository that has a remote repository that the server can see.

Once the build configuration is created a new build will be automatically triggered. You can use 'openshift cli status' to check the progress.

Options

--allow-missing-images=false
If true, indicates that referenced Docker images that cannot be found locally or in a registry should still be used.
--allow-missing-imagestream-tags=false
If true, indicates that image stream tags that don't exist should still be used.
--binary=false
Instead of expecting a source URL, set the build to expect binary contents. Will disable triggers.
--build-secret=[]
Secret and destination to use as an input for the build.
--code=[]
Source code in the build configuration.
--context-dir=""
Context directory to be used for the build.
--docker-image=[]
Name of a Docker image to use as a builder.
-D, --dockerfile=""
Specify the contents of a Dockerfile to build directly, implies --strategy=docker. Pass '-' to read from STDIN.
--dry-run=false
If true, show the result of the operation without performing it.
-e, --env=[]
Specify key value pairs of environment variables to set into resulting image.
--image=[]
Name of an image stream to to use as a builder. (deprecated)
-i, --image-stream=[]
Name of an image stream to to use as a builder.
-l, --labels=""
Label to set in all generated resources.
--name=""
Set name to use for generated build artifacts.
--no-output=false
If true, the build output will not be pushed anywhere.
-o, --output=""
Output results as yaml or json instead of executing, or use name for succint output (resource/name).
--output-version=""
The preferred API versions of the output objects
--source-image=""
Specify an image to use as source for the build. You must also specify --source-image-path.
--source-image-path=""
Specify the file or directory to copy from the source image and its destination in the build directory. Format: [source]:[destination-dir].
--strategy=""
Specify the build strategy to use if you don't want to detect (docker|source).
--to=""
Push built images to this image stream tag (or Docker image repository if --to-docker is set).
--to-docker=false
Have the build output push to a Docker repository.

Options Inherited from Parent Commands

--api-version=""
DEPRECATED: The API version to use when talking to the server

--as=""
Username to impersonate for the operation.

--certificate-authority=""
Path to a cert. file for the certificate authority.

--client-certificate=""
Path to a client certificate file for TLS.

--client-key=""
Path to a client key file for TLS.

--cluster=""
The name of the kubeconfig cluster to use

--config=""
Path to the config file to use for CLI requests.

--context=""
The name of the kubeconfig context to use

--google-json-key=""
The Google Cloud Platform Service Account JSON Key to use for authentication.

--insecure-skip-tls-verify=false
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.

--log-flush-frequency=0
Maximum number of seconds between log flushes

--match-server-version=false
Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request.

--server=""
The address and port of the Kubernetes API server

--token=""
Bearer token for authentication to the API server.

--user=""
The name of the kubeconfig user to use

Example

# Create a build config based on the source code in the current git repository (with a public
# remote) and a Docker image
openshift cli new-build . --docker-image=repo/langimage

# Create a NodeJS build config based on the provided [image] [source code] combination
openshift cli new-build openshift/nodejs-010-centos7 https://github.com/openshift/nodejs-ex.git

# Create a build config from a remote repository using its beta2 branch
openshift cli new-build https://github.com/openshift/ruby-hello-world#beta2

# Create a build config using a Dockerfile specified as an argument
openshift cli new-build -D $'FROM centos:7\nRUN yum install -y httpd'

# Create a build config from a remote repository and add custom environment variables
openshift cli new-build https://github.com/openshift/ruby-hello-world RACK_ENV=development

# Create a build config from a remote repository and inject the npmrc into a build
openshift cli new-build https://github.com/openshift/ruby-hello-world --build-secret npmrc:.npmrc

# Create a build config that gets its input from a remote repository and another Docker image
openshift cli new-build https://github.com/openshift/ruby-hello-world --source-image=openshift/jenkins-1-centos7 --source-image-path=/var/lib/jenkins:tmp

See Also

openshift-cli(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

openshift-cli(1).

Openshift CLI User Manuals Openshift June 2016