moilanik
5c9df73a66
CI Feature / Load example-gitea-env.conf to pipeline env (push) Successful in 34s
acc-tests Cucumber test report
CI Feature / Cucumber tests (push) Failing after 45s
unit-tests Bats test report
CI Feature / Bats tests (push) Successful in 1m36s
CI Feature / Report Summary (push) Successful in 5s
45 lines
1.8 KiB
Gherkin
45 lines
1.8 KiB
Gherkin
Feature: GitOps update
|
|
As a GitOps repository
|
|
I want to update version references and report results back 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 — caller commit gets failure status
|
|
Given insufficient environment variables are provided for the GitOps update
|
|
When the GitOps update script runs
|
|
Then the caller commit shows a failure status with the missing variable name
|
|
And the script exits with error
|
|
|
|
@mock
|
|
Scenario: GitOps job fails — caller commit gets failure status
|
|
Given the GitOps repository clone will fail
|
|
When the GitOps update script runs
|
|
Then the caller commit shows a failure status
|
|
And the script exits with error
|
|
|
|
@mock
|
|
Scenario: Everything succeeds — caller and GitOps get success
|
|
Given a valid GitOps update dispatch
|
|
When the GitOps update script runs
|
|
Then the script exits successfully
|
|
And the caller commit shows a success status with a link to the GitOps commit
|
|
And the GitOps repo commit shows a success status with a link to the caller
|
|
|
|
@mock
|
|
Scenario: GitOps push fails — both repos get 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 caller commit shows a failure status
|
|
And the GitOps repo commit shows a failure status linking to the caller
|
|
|
|
@mock
|
|
Scenario: GitOps update succeeds — this repo commit status links to caller
|
|
Given a valid GitOps update dispatch
|
|
When the GitOps update script runs
|
|
Then the GitOps repo commit shows a source context status linking to the caller commit
|