forked from argoproj/argo-rollouts
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
478 changed files
with
64,588 additions
and
32,813 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Workflows | ||
|
||
| Workflow | Description | | ||
|---------------------|-----------------------------------------------------------------| | ||
| changelog.yml | Updates changelog when a release is published | | ||
| codeql.yaml | CodeQL analysis | | ||
| docker-publish.yaml | Build container image for PR's & publish for push events | | ||
| image-reuse.yaml | Build, push, and Sign container images | | ||
| go.yaml | lint, build, codegen | | ||
| pr-title-check.yaml | Lint PR for semantic information | | ||
| init-release.yaml | Build manifests and version then create a PR for release branch | | ||
| release.yaml | Build images, cli-binaries, provenances, and post actions | | ||
|
||
|
||
# Reusable workflows | ||
|
||
## image-reuse.yaml | ||
|
||
- The resuable workflow can be used to publish or build images with multiple container registries(Quay,GHCR, dockerhub), and then sign them with cosign when an image is published. | ||
- A GO version `must` be specified e.g. 1.19 | ||
- The image name for each registry *must* contain the tag. Note: multiple tags are allowed for each registry using a CSV type. | ||
- Multiple platforms can be specified e.g. linux/amd64,linux/arm64 | ||
- Images are not published by default. A boolean value must be set to `true` to push images. | ||
- An optional target can be specified. | ||
|
||
| Inputs | Description | Type | Required | Defaults | | ||
|-------------------|-------------------------------------|-------------|----------|-----------------| | ||
| go-version | Version of Go to be used | string | true | none | | ||
| quay_image_name | Full image name and tag | CSV, string | false | none | | ||
| ghcr_image_name | Full image name and tag | CSV, string | false | none | | ||
| docker_image_name | Full image name and tag | CSV, string | false | none | | ||
| platforms | Platforms to build (linux/amd64) | CSV, string | false | linux/amd64 | | ||
| push | Whether to push image/s to registry | boolean | false | false | | ||
| target | Target build stage | string | false | none | | ||
|
||
| Outputs | Description | Type | | ||
|-------------|------------------------------------------|-------| | ||
|image-digest | Image digest of image container created | string| | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.