niko
bc6bb78973
CI Git-Pages Main / Load git-pages.gitea-env.conf to pipeline env (push) Successful in 34s
CI Main / Check existing artifact (push) Successful in 22s
CI Git-Pages Main / Build & Push Helm chart (push) Successful in 48s
CI Main / Bats tests (push) Successful in 1m34s
acc-tests Cucumber test report
CI Main / Cucumber tests (push) Successful in 1m45s
CI Main / Load example-gitea-env.conf to pipeline env (push) Successful in 34s
CI Git-Pages Main / Check existing artifact (push) Successful in 21s
ci-helm-build-push Helm push 0.1.5
unit-tests Bats test report
CI Git-Pages Main / Update chart to the cluster (push) Failing after 0s
ci-docker-build-push Docker push 0.2.25
CI Git-Pages Main / Report Summary (push) Successful in 7s
CI Main / Build & Push Docker (push) Successful in 44s
CI Main / GitOps (push) Failing after 22s
CI Main / Move provider version tag (push) Has been skipped
CI Main / Report Summary (push) Successful in 6s
Co-authored-by: moilanik <niko.moilanen@tietoevry.com> Reviewed-on: #37
43 lines
1.6 KiB
Gherkin
43 lines
1.6 KiB
Gherkin
Feature: GitOps update
|
|
As a GitOps repository
|
|
I want to update version references and report results to the caller
|
|
So that the deployment chain is traceable from source to GitOps commit
|
|
|
|
Background:
|
|
Given a project repository exists in Gitea
|
|
And a commit has been pushed to the repository
|
|
|
|
@mock
|
|
Scenario: Not enough env vars — script fails, no status set
|
|
Given insufficient environment variables are provided for the GitOps update
|
|
When the GitOps update script runs
|
|
Then the script exits with error
|
|
|
|
@mock
|
|
Scenario: GitOps job fails — no status set (SHA not yet known)
|
|
Given the GitOps repository clone will fail
|
|
When the GitOps update script runs
|
|
Then the script exits with error
|
|
|
|
@mock
|
|
Scenario: Everything succeeds — GitOps repo gets success status with link to caller
|
|
Given a valid GitOps update dispatch
|
|
When the GitOps update script runs
|
|
Then the script exits successfully
|
|
And the GitOps repo commit shows a success status with a link to the caller commit
|
|
|
|
@mock
|
|
Scenario: GitOps push fails — GitOps repo gets failure status
|
|
Given the GitOps repo push will fail after the version is committed
|
|
When the GitOps update script runs
|
|
Then the script exits with error
|
|
And the GitOps repo commit shows a failure status linking to the caller commit
|
|
|
|
@mock
|
|
Scenario: No changes — GitOps repo gets "no change" status
|
|
Given the version file already has the target version
|
|
When the GitOps update script runs
|
|
Then the script exits successfully
|
|
And the GitOps repo commit shows a "no change" status
|
|
And no Git commit or push was performed
|