Skip to content

docs: fix typo and rename build job in CI/CD scoring guide #336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mathieu-benoit merged 1 commit into from
Oct 8, 2026
Merged

docs: fix typo and rename build job in CI/CD scoring guide #336

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/How to/score-cicd-pipelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ The first job in the workflow builds and tags the image locally with a semantic

```yaml
jobs:
build:
build-and-test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
Expand Down Expand Up @@ -174,7 +174,7 @@ This workflow can now test, push, and deploy a Score application. However, there

### Maintaining `score-k8s` state

CI Workflows typically start with a clean slate every time they execute. No state is stored on disk between runs. However, `score-k8s` _does_ store unique data, random seeds, and non-hermetic attributes in a `.score-k8s/state.yaml` file. For best results, this file should be restored before running `score-k8s` generate. For background on what's stored in this file, see [Local state]({{< relref "/docs/score-implementation/local-state" >}}).
CI Workflows typically start with a clean state every time they execute. No state is stored on disk between runs. However, `score-k8s` _does_ store unique data, random seeds, and non-hermetic attributes in a `.score-k8s/state.yaml` file. For best results, this file should be restored before running `score-k8s generate`. For background on what's stored in this file, see [Local state]({{< relref "/docs/score-implementation/local-state" >}}).

In this example, the file is stored as a secret in the target Kubernetes cluster. First, it's downloaded before running init or generate:

Expand Down
Loading