Version: 0.7

kore create build

kore create build#

Creates an automated container build in kore

Synopsis#

Allows you to automate the container build process via kore. Builds are executed within a team clusters and the resulting images are automatically pushed into the team registries. Kore will then handle the required setup to ensure the image is available to docker pull from any of the team clusters.

Note: at present the feature is beta and it's scope is limited to ECR and EKS clusters.

kore create build [flags]

Examples#

# Create a build from git repository - it will walk you through the required settings
$ kore create build kore
# Change the build context for docker build - i.e. the files in Dockerfile are relative
# to another directory.
$ kore create build kore --build-path /ui
# The git repository is private and requires access.
$ kore create secret gitlab-token gitlab-token
โœ— Please enter the gitlab personal access token : *******
# When creating the build we would use
$ kore create build kore --secret gitlab-token
# The same can be done for github. Note at the moment the feature is beta and we
# support adding personal access tokens for gitlab and github.
# You can create robot token to run the builds via
$ kore create build token <name> (for non team administrators)

Options#

--build-path string absolute path inside the code for docker build path
-c, --cluster string cluster you want the automated build to run
--dockerfile string location of the dockerfile in repository
--dry-run shows the resource but does not apply or create (defaults: false)
-h, --help help for build
--image string the name of the resulting container image
--non-interactive indicates if we should interactively prompt
--registry string registry to push the container build to
--repo string url for the git repository (e.g. git://github.com/appvia/kore.git
--secret string if the repository is private contains the credentials to clone

Options inherited from parent commands#

--debug indicates we should use debug / trace logging (defaults: false)
--force is used to force an operation to happen (defaults: false)
--no-wait indicates if we should wait for resources to provision
-o, --output string the output format of the resource (json,yaml,table,template) (default "table")
--profile string allows you to explicitly set the selected profile
--show-headers indicates we should display headers on table out (default true)
-t, --team string the team you are operating within
--verbose enables verbose logging for debugging purposes (defaults: false)

SEE ALSO#