-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Steps to reproduce
- Make change in engine project that will cause failure in engine-IT stage if not considered
- Create a PR and trigger main CE pipeline
Observed
- engine-IT stage pull engine artifact from nexus and causes failing tests
Expected
- subsequent stages of Assembly unstash the created artifacts of it and doesn't fail
Acceptance Criteria (Required on creation):
Stashes are resolved correctly for the same pipeline as well as downstream pipeline.
Hints (Optional):
- Issue reproduced here: https://ci-pipeline.cambpm.camunda.cloud/job/7.16/job/cambpm-ce/job/cambpm-main/job/PR-1426/8/
- The unstashing should be performed in case of:
- downstream build
- standalone main CE/EE build
This is the controller panel for Smart Panels app
[Bug] In pipeline, stashes are not considered in the same pipeline
-
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Steps to reproduce
- Make change in engine project that will cause failure in engine-IT stage if not considered
- Create a PR and trigger main CE pipeline
Observed
- engine-IT stage pull engine artifact from nexus and causes failing tests
Expected
- subsequent stages of Assembly unstash the created artifacts of it and doesn't fail
Acceptance Criteria (Required on creation):
Stashes are resolved correctly for the same pipeline as well as downstream pipeline.
Hints (Optional):
- Issue reproduced here: https://ci-pipeline.cambpm.camunda.cloud/job/7.16/job/cambpm-ce/job/cambpm-main/job/PR-1426/8/
- The unstashing should be performed in case of:
- downstream build
- standalone main CE/EE build
This is the controller panel for Smart Panels app
-
Nikola Koevski
-
-
Yana Vasileva
- Votes:
-
0 Vote for this issue
- Watchers:
-
0 Start watching this issue
- Created:
- Updated:
- Resolved: