Skip to main content

Builds

This section covers building, packaging, and publishing application artifacts on the Ybor Platform. Whether you're creating new applications or migrating existing ones, your CI/CD pipelines need to produce container images and manage releases in a way that integrates with the platform's deployment model.

The Build Model​

Applications on the Ybor Platform follow a three-workflow pattern:

  1. Build — Automatically triggered on every push or pull request. Compiles code, runs tests, builds container images, and publishes artifacts. On merges to main, automatically cuts a patch version.

  2. Cut Tag — Manually triggered to create minor or major version releases. Bumps the version, creates a Git tag, publishes artifacts, and creates a GitHub release.

  3. Promote — Manually triggered to promote a release to staging or production. Updates the platform manifests to deploy a specific version to the target environment.

This pattern ensures consistent versioning, traceable releases, and controlled deployments across environments.

Reusable Actions​

The platform provides p6m-actions — a collection of GitHub Actions for specific tasks (setup, build, publish, etc.). You can use these directly, fork them for customization, or build your own pipelines that produce compatible artifacts.

Prerequisites​

Before setting up build pipelines, ensure you have:

  • GitHub repository access with Actions enabled
  • Artifactory credentials configured as repository secrets (ARTIFACTORY_USERNAME, ARTIFACTORY_IDENTITY_TOKEN)
  • Platform dispatch token for promotion workflows (UPDATE_MANIFEST_TOKEN)
  • Repository variables for registry configuration (ARTIFACTORY_HOSTNAME, ARTIFACTORY_PROJECT)
Managed by Ybor

The secrets and variables listed above are provisioned by the Ybor platform during onboarding. If builds are failing due to missing credentials, contact your Admin or DevOps team to verify the configuration.

See Artifact Management for credential setup.

In This Section​