OC-CREATE-BUILD(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸŽ€ OC CREATE(1) πŸŽ€

ok so this is a page from the Openshift CLI User Manuals (yes, the whole manual, bestie β€” we're just doing one lil command out of it) and it's giving "June 2016 but make it eternal." Sit down, grab a boba, we're learning oc create build. πŸ’…


✨ NAME ✨

oc create build β€” literally just creating a new build. That's the whole vibe.


✨ SYNOPSIS ✨

oc create build [OPTIONS]

🌸 DESCRIPTION 🌸

So like. You're creating a new build. That's it, that's the tweet.

But for context, since we're being thorough: builds create container images from source code or Dockerfiles. A build can pull source code from Git, or it can accept a Dockerfile that pulls the source content. Two paths, one iconic destiny. πŸ¦‹


πŸ’– OPTIONS πŸ’–

okay this is the long part, but stay with me, every single flag matters:

  • --allow-missing-template-keys=true β€” if true, ignore any errors in templates when a field or map key is missing from the template. Heads up: this only applies to golang and jsonpath output formats.
  • --build-loglevel=0 β€” sets the log level for builds. Range is 0-10, and 0 is the default. πŸ—£οΈ
  • --context-dir="" β€” a relative path within the repository to use as the root of the build.
  • --dockerfile-contents="" β€” the actual contents of a Dockerfile to build.
  • --dockerfile-path="" β€” the relative path within the repository context where the Dockerfile lives.
  • --dry-run="none" β€” must be "none", "server", or "client". If it's the client strategy, only print the object that would be sent, without sending it. If it's the server strategy, submit the server-side request without persisting the resource. (Look at you being all responsible, not committing. 🫢)
  • --env=[] β€” add environment variables to the build strategy.
  • --from-image="" β€” a container image pull spec to use as the basis for the image build.
  • --image-optimization-policy="" β€” controls whether individual layers are created. Your options are SkipLayers, SkipLayersAndWarn, or None.
  • -o, --output="" β€” output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). Pick your fighter. ✨
  • --save-config=false β€” if true, the configuration of the current object will be saved in its annotation. Otherwise the annotation stays unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. Future-you says thank you.
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format.
  • --source-git="" β€” a URL or Git spec link to a Git repository.
  • --source-revision="" β€” a commit, branch, or tag within the source repository.
  • --strategy="" β€” the build strategy to use: Docker, Source, or Custom. Can be defaulted by other arguments, so don't stress too hard.
  • --template="" β€” template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
  • --to-image="" β€” a location to push the output image to.
  • --to-image-stream="" β€” an image stream tag to push the output image to. Accepts [NAMESPACE/]STREAM:TAG.

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these are the ones you didn't ask for but got anyway, like a goodie bag:

  • --as="" β€” username to impersonate for the operation. User could be a regular user or a service account in a namespace.
  • --as-group=[] β€” group to impersonate for the operation. This flag can be repeated to specify multiple groups.
  • --as-uid="" β€” UID to impersonate for the operation.
  • --as-user-extra=[] β€” user extras to impersonate for the operation. This flag can be repeated to specify multiple values for the same key.
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. (yes that path is real, we don't make the rules 😭)
  • --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.
  • --context="" β€” the name of the kubeconfig context to use.
  • --disable-compression=false β€” if true, opt-out of response compression for all requests to the server.
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure. ⚠️ like, actually read that one twice, bestie.
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests.
  • --kuberc="" β€” path to the kuberc file to use for preferences. This can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off.
  • --match-server-version=false β€” require server version to match client version.
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request.
  • --profile="none" β€” name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex).
  • --profile-output="profile.pprof" β€” name of the file to write the profile to.
  • --request-timeout="0" β€” the length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.
  • -s, --server="" β€” the address and port of the Kubernetes API server.
  • --tls-server-name="" β€” server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used.
  • --token="" β€” bearer token for authentication to the API server.
  • --user="" β€” the name of the kubeconfig user to use.
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code.

πŸ”₯ EXAMPLE πŸ”₯

the moment you've all been waiting for:

# Create a new build
oc create build myapp

ate. no crumbs. πŸ‘‘


🌈 SEE ALSO 🌈

oc-create(1), β€” go read that one too, iykyk.


πŸ’œ HISTORY πŸ’œ

June 2016, Ported from the Kubernetes man-doc generator. an elder. a legend. we respect her.


aaaand that's the page!! πŸ“ this whole thing came to you courtesy of Openshift and the Openshift CLI User Manuals, dated June 2016 β€” mwah, drink water, and go create a build bestie πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from