Open clemensutschig opened 1 year ago
@metmajer, fyi ..
While fixing this - I took a pretty hard look at the codebase - and propose two things on top of this fix
ods-service
and not just ods
/code componentsnon-ods
components, which decreases complexityI also found some interesting behaviour on unirest / getAsFile -> where the directory must exist - and the only way to make this happen is vie jenkins means (steps.dir)
Fix(es):
DEBUG: Verifiying image of container 'plain' ...
[Pipeline] echo
DEBUG: Container 'plain' is using defined image 'sha256:2ad8c81dc786477d5a84685eb5cba7db7ccb257dd3a010d712b58462443c616d'.
[Pipeline] echo
Resurrection of previous build for 'plain' possible.
[Pipeline] echo
DEBUG: Data from previous Jenkins build:
[resurrectedBuild:test2/41, deployments:[plain:[podName:plain-3-cdnn2, ... dev/plain@sha256:2ad8c81dc786477d5a84685eb5cba7db7ccb257dd3a010d712b58462443c616d]]]]
[Pipeline] echo
DEBUG: [plain-resurrect-data] (took 19607 ms)
Commits (are not happening anymore on untouched code):
vs a rebuild of repos (so forceRebuild
):
Describe the bug The release manager allows to configure "allowPartialRebuild" - which is especially helpful for large projects where only one component is changed, and only that one should be rebuild
To Reproduce
ods
components - add both to RM and build (in WIP)allowPartialRebuild
in metadata.yml -> trueExpected behavior only the changed component gets rebuild, the other stays as is - and gets resurrected
Affected version (please complete the following information):
Log Output (ensure to remove any confidential information like tokens, project names, etc.
Note the
oc -n null
- which makes this break