humanitec/Build and Push to Humanitec

Builds a container image from a Dockerfile and then pushes it to the Humanitec registry and notifies the platform.

Trust Signals

name	description	required	default
humanitec-token	API Token provided when you add your ci pipline in the Humanitec platform.	yes	—
organization	The name of the organization that the image will be built for.	yes	—
image-name	The name you want to refer to the image to in the Humanitec Platform.	no	""
existing-image	Use an existing image instead of building an image. The image name needs to include a tag or digest.	no	""
tag	Use tag when you want to bring your own tag.	no	—
ref	Use ref when you want to bring your own ref instead of the GitHub action supplied ref.	no	—
auto-tag	Use auto-tag when you want to push tags/release by their git name.	no	—
dockerfile	The same as "context".	no	—
context	Build context path. Defaults to the root of repository.	no	.
file	Name of the Dockerfile, defaults to `$context/Dockerfile`.	no	—
additional-docker-arguments	Additional arguments for docker (e.g.,build arguments). Defaults to empty.	no	—
humanitec-registry	Allows the default humanitec registry to be overidden for testing.	no	registry.humanitec.io
humanitec-api	Allows the default humanitec api to be overidden for testing.	no	api.humanitec.io
external-registry-url	Push the image to an external container registry. This registry does not need to be [registered with Humanitec](https://docs.humanitec.com/guides/connect-ci-setup/container-registries) and authentication needs to be done by the explicitly (e.g. using workload identity).	no	""

name	description
image	The full name of the image that was built and pushed.