Skip to content

Commit

Permalink
[CLOUDCIFEAT1-130] Avoid non atomic updates (#248)
Browse files Browse the repository at this point in the history
Up to now each and every change was "commited" directly. Now we apply several changes to the memory representation of a pipeline run and "commit" these changes together. With that there is no (short) period of time where the pipeline run is inconsistent.

There are also a lot of other changes more the less related (e.g. affecting error handling)

Co-authored-by: Matthias Rinck <[email protected]>
  • Loading branch information
marcusholl and rinckm authored Aug 17, 2021
1 parent bcab41f commit 870a180
Show file tree
Hide file tree
Showing 13 changed files with 548 additions and 393 deletions.
17 changes: 17 additions & 0 deletions changelog.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -51,12 +51,29 @@
- version: NEXT
date: TBD
changes:

- type: bug
impact: minor
title: Avoid non atomic status updates
description: |-
Without this change the state might be upated e.g. to a final state
without setting a corresponding result. The result is provided a short period
of time later with an other update. In the meantime we have an invalid state.
With this change we apply both changes to the memory representation of a
pipeline run and send the update only once. With this approach there is no
short period of time with an invalid state
warning: |-
needs to be validated carefully since this is a bigger refactoring
pullRequestNumber: 248
jiraIssueNumber: CLOUDCIFEAT1-130

- type: bug
impact: patch
title: Fix deletion bug #241
description: |-
When a pipeline run was deleted the state and the result were not updated in some edge cases. This is fixed now.
pullRequestNumber: 250

- version: "0.12.1"
date: 2021-07-28
changes:
Expand Down
4 changes: 2 additions & 2 deletions charts/steward/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ type: application

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: 0.12.2-dev
version: 0.13.0-dev

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
appVersion: 0.12.2-dev
appVersion: 0.13.0-dev
4 changes: 4 additions & 0 deletions pkg/apis/steward/v1alpha1/constants.go
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,10 @@ const (
// faces an intermittent error during running phase.
EventReasonRunningFailed = "RunningFailed"

// EventReasonCleaningFailed is the reason for a event occuring when the run controller
// faces an intermittent error during cleanup phase.
EventReasonCleaningFailed = "CleaningFailed"

// EventReasonLoadPipelineRunsConfigFailed is the reason for an event occuring when the
// loading of the pipeline runs configuration fails.
EventReasonLoadPipelineRunsConfigFailed = "LoadPipelineRunsConfigFailed"
Expand Down
75 changes: 40 additions & 35 deletions pkg/k8s/mocks/mocks.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading

0 comments on commit 870a180

Please sign in to comment.