Oc new-app: Difference between revisions
| Line 22: | Line 22: | ||
When new-app is executed, OpenShift tries to do the following: | When new-app is executed, OpenShift tries to do the following: | ||
1. Create a [[OpenShift Concepts#Build_Configuration|build configuration]] and build the source | 1. Create a [[OpenShift Concepts#Build_Configuration|build configuration]] and build the source into a new version of the application. | ||
2. | 2. As result of [[OpenShift Concepts#Build_Configuration|build configuration]] configuration execution, a new container image based on the [[OpenShift Concepts#Image_Stream|image stream]] compatible with the source code is created. | ||
Revision as of 07:32, 21 November 2017
Internal
Overview
A tool that generates an appropriate JSON configuration so OpenShift can build an image based on it. The configuration represents resources of an application, maintained inside a project.
For more details on projects and applications, see Projects and Applications.
The command is a shortcut to configure a project with common resources for a standard development workflow. Source code, images and templates are specified at this stage. The command looks for images on the new local Docker installation, if available, in the Docker registry and the OpenShift image stream.
If new-app finds a Dockerfile in the repository, it uses the "docker" build strategy. Otherwise it uses the "source" strategy. The strategy can be explicitly set with --strategy option.
It can also be used to instantiate a stored template:
oc new-app --template=example-template --param=USERNAME=somevalue
When new-app is executed, OpenShift tries to do the following:
1. Create a build configuration and build the source into a new version of the application.
2. As result of build configuration configuration execution, a new container image based on the image stream compatible with the source code is created.