Skip to content

Documented that multiple replicas are not supported by the orchestrat… #1245

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
merged 2 commits into from
Oct 31, 2025
Merged

Documented that multiple replicas are not supported by the orchestrat… #1245

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1f43ff1
Documented that multiple replicas are not supported by the orchestrat…
jafarre-bi Oct 30, 2025
6879170
Update change log
jafarre-bi Oct 30, 2025
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
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
## Unreleased

### Added

* Documented that multiple replicas are not supported by the orchestration pipeline ([#1245]https://github.com/opendevstack/ods-jenkins-shared-library/pull/1245)

### Changed
* Enforce SonarQube stage and make it safe to fail ([#1223]https://github.com/opendevstack/ods-jenkins-shared-library/pull/1223)
Expand Down
1 change: 1 addition & 0 deletions docs/modules/jenkins-shared-library/pages/orchestration-pipeline.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -360,3 +360,4 @@ When you author templates, you can also store the secrets in the param files GPG
- During export, the templates are parameterized automatically, but this is done using string search-and-replace and unwanted replacements might occur (this can be prevented by authoring the templates manually).
- By default, SonarQube scans (and reports) are only generated for the `master` branch of each component. As the orchestration pipeline automatically creates release branches for each version, no scans and reports are created on those. This can be changed by configuring `sonarQubeBranch: '*'`` in each component's `Jenkinsfile`, however keep in mind that quality trends etc. will be mixed up if you use the free version of SonarQube as that version does not have support for multiple branches.
- An existing QA-tag cannot be deployed again in PROD. This has been intentionally designed that way as any change to PROD needs its unique change ID, which results in a new tag.
- The orchestration pipeline does not support more than one replica per Deployment or DeploymentConfig. If you decide to set up more than one replica, do it at your own risk.