seismic-dms-service merge requestshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests2022-04-12T12:05:24Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/360cherry pick "fixing gcp helm deploy" into release/0.142022-04-12T12:05:24ZDavid Diederichd.diederich@opengroup.orgcherry pick "fixing gcp helm deploy" into release/0.14Original MR: !358Original MR: !358David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1047Cherry-pick 'fix: split batchclient delete request into multiple' into releas...2023-12-20T12:19:09ZRashaad GrayCherry-pick 'fix: split batchclient delete request into multiple' into release/0.25**Original MR**: !1045
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporat...**Original MR**: !1045
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.M22 - Release 0.25Rashaad GrayRashaad Grayhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/807Cherry-pick 'fix: use without impersonation-token-context temp workaround' in...2023-07-18T07:38:42ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'fix: use without impersonation-token-context temp workaround' into release/0.22**Original MR**: !795
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !795
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/pipelines/new?ref=cherry-pick-for-795)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1051Cherry-pick GC fix2023-12-27T08:49:46ZYan Sushchynski (EPAM)Cherry-pick GC fix## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [x] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [x] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
Fix GC pipeline with building imageM22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/645Cherry-pick 'GC fix: use full image name for redis' into release/0.192023-02-16T18:46:13ZChad LeongCherry-pick 'GC fix: use full image name for redis' into release/0.19**Original MR**: !632
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !632
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/pipelines/new?ref=cherry-pick-for-632)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1056cherry pick: hide bulk delete and compute size tests under the feature flags2024-01-09T12:26:11ZDaniel Perezcherry pick: hide bulk delete and compute size tests under the feature flags## Type of change
- [X] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [X] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [X] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [X] Yes
## Have you set the target Milestone?
- [ ] No
- [X] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
> Disabled bulk delete and compute size
> **Original MR**: !1055M22 - Release 0.25Diego MolteniDaniel PerezDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/576Cherry Pick M12 changes2023-01-04T20:46:19ZPrakash SivakumarCherry Pick M12 changesCherry Pick M12 to M14 as part of MEDS releaseCherry Pick M12 to M14 as part of MEDS releaseM14 - Release 0.17Prakash SivakumarPrakash Sivakumarhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/702Cherrypick/m14 to m162023-04-21T17:27:34ZMahsa HanifiCherrypick/m14 to m16## Type of change
- [ ] Bug Fix
- [x] Feature
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] GC...## Type of change
- [ ] Bug Fix
- [x] Feature
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [X] Yes
## Updates description?
> Merged changes from M14 to M16 branchMahsa HanifiMahsa Hanifihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/710Cherrypick/m14 to m16 file master2023-04-28T18:08:38ZMahsa HanifiCherrypick/m14 to m16 file master## Type of change
- [ ] Bug Fix
- [X] Feature
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] GC...## Type of change
- [ ] Bug Fix
- [X] Feature
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [X] Yes
## Have you set the Milestone?
- [X] No
- [ ] Yes
## Updates description?
This is the upgrade work from M14 to M16 all the changes are cherry-picked from M14Mahsa HanifiMahsa Hanifihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/489Cherry pick: Merge branch 'fix_Anthos_logger_minio' into 'release/0.16'2022-12-09T13:49:22ZChad LeongCherry pick: Merge branch 'fix_Anthos_logger_minio' into 'release/0.16'fix: Anthos logger, MinIO list objects, and search Datasets by gtags
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!467
(cherry picked from commit 6253eb78dfe2240529e65214e8815...fix: Anthos logger, MinIO list objects, and search Datasets by gtags
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!467
(cherry picked from commit 6253eb78dfe2240529e65214e881539dd48627ea)
c802dabf fix: Anthos logger and Minio
e3d5324d fix: linters
6cabc36d fix: search tags
9eb8031c Merge branch 'master' of...M13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/484Cherry pick: Merge branch 'slb/dm3/force-subproject-key' into 'master'2022-08-17T08:32:45ZChad LeongCherry pick: Merge branch 'slb/dm3/force-subproject-key' into 'master'fix: (azure) forcing usage old key model when using a single partition model db in azure comsos
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!479
(cherry picked from commit 1e...fix: (azure) forcing usage old key model when using a single partition model db in azure comsos
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!479
(cherry picked from commit 1e7082a0e4207f518daec9d08f4a4d5ba1f86cba)
dd2623eb fix: forcing usage old key in azure old dbM13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/480Cherry pick: Merge branch 'slb/dm3/force-subproject-key' into 'master'2022-08-16T16:44:13ZDiego MolteniCherry pick: Merge branch 'slb/dm3/force-subproject-key' into 'master'fix: (azure) forcing usage old key model when using a single partition model db in azure comsos
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!479
(cherry picked from commit 1e...fix: (azure) forcing usage old key model when using a single partition model db in azure comsos
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!479
(cherry picked from commit 1e7082a0e4207f518daec9d08f4a4d5ba1f86cba)
dd2623eb fix: forcing usage old key in azure old dbM12 - Release 0.15Diego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/487Cherry pick: Merge branch 'slb/dperez50/fix-azure-pipeline' into 'master'2022-08-16T16:23:44ZDaniel PerezCherry pick: Merge branch 'slb/dperez50/fix-azure-pipeline' into 'master'Slb/dperez50/fix azure pipeline
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!464
(cherry picked from commit 365dea4f76bdd18b1c63092adf6e943e9029204d)
77b8379f ci: updating c...Slb/dperez50/fix azure pipeline
See merge request osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service!464
(cherry picked from commit 365dea4f76bdd18b1c63092adf6e943e9029204d)
77b8379f ci: updating conditions and logic
f6fe8799 ci: updating conditions and logic
d8f5669a ci: updating conditions and logic
2378d45f ci: updating conditions and logic
d69672c9 ci: updating conditions and logic
b2f42f57 ci: updating conditions and logic
17c9e24e ci: updating conditions and logic
5948c6e7 ci: updating conditions and logicM12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/909Cherry-pick: Merge branch 'update-seismic-gc' into 'release/0.23'2023-09-26T15:57:20ZAliaksandr Ramanovich (EPAM)Cherry-pick: Merge branch 'update-seismic-gc' into 'release/0.23'Original MR: !907
## Type of change
* [ ] Bug Fix
* [ ] Feature
* [ ] Pipeline
* [ ] Test
* [ ] Documentation
## Does this introduce a change in the core logic?
* [ ] No
* [ ] Yes
## Does this introduce a change in the cloud provide...Original MR: !907
## Type of change
* [ ] Bug Fix
* [ ] Feature
* [ ] Pipeline
* [ ] Test
* [ ] Documentation
## Does this introduce a change in the core logic?
* [ ] No
* [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
* [ ] AWS
* [ ] Anthos
* [ ] Azure
* [ ] GCP
* [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
* [ ] No
* [x] Yes
## Have you set the target Milestone?
* [ ] No
* [x] Yes
## Have you set the no-detached-pipeline label?
* [ ] No
* [x] Yes
## Updates description?
> Cherry-pick MR 907 to release/0.23 branch
>
> This MR contains only GC specific changes in deployment processM20 - Release 0.23Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/660Cherry-pick: Merge cherry-pick 0978566a9f6107f0ed9acbf05139a9b32b9b40282023-03-10T08:45:13ZDiego MolteniCherry-pick: Merge cherry-pick 0978566a9f6107f0ed9acbf05139a9b32b9b4028Original merge https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/634Original merge https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/634M16 - Release 0.19Diego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/880cherry pick MR 861 to m16 file master branch2023-10-18T12:57:57Zshivani karipecherry pick MR 861 to m16 file master branch## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ * ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ * ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation,...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ * ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ * ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ * ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ * ] Yes
## Have you set the target Milestone?
- [ ] No
- [ * ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ * ] Yes
## Updates description?
> Update this part with a description of your changes
- This merge request addresses the problem of failing unit tests in the file metadata.
- It adjusts the "allow failure" setting to false, enhancing performance and preparing for potential challenges if the pipeline fails in the future.
- added helm charts and modified pipeline configuration to fix the pipeline issues
parent MR link: [861](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/861)shivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/875cherry pick MR 861 to m16 master branch2023-08-25T02:17:32Zshivani karipecherry pick MR 861 to m16 master branch## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ * ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ * ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation,...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ * ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ * ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ * ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ * ] Yes
## Have you set the target Milestone?
- [ ] No
- [ * ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ * ] Yes
## Updates description?
> Update this part with a description of your changes
- This merge request addresses the problem of failing unit tests in the file metadata.
- It adjusts the "allow failure" setting to false, enhancing performance and preparing for potential challenges if the pipeline fails in the future.
parent MR link: [861](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/861)shivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1042Cherry-pick '[MSCOSDU-1907] fix sdms azure publish' into release/0.252023-12-16T09:49:51ZDavid Diederichd.diederich@opengroup.orgCherry-pick '[MSCOSDU-1907] fix sdms azure publish' into release/0.25**Original MR**: !1033
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporat...**Original MR**: !1033
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/pipelines/new?ref=cherry-pick-for-1033)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1043Cherry-pick 'test: compute size E2E tests' into release/0.252023-12-18T17:45:37ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'test: compute size E2E tests' into release/0.25**Original MR**: !1038
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporat...**Original MR**: !1038
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/pipelines/new?ref=cherry-pick-for-1038)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/673chore: consume segysdk-python 0.0.171315 and openzgy 0.2.969.2023-03-28T11:38:41ZIvan Medeiros Monteirochore: consume segysdk-python 0.0.171315 and openzgy 0.2.969.Consume segysdk-python 0.0.171315 and openzgy 0.2.969.Consume segysdk-python 0.0.171315 and openzgy 0.2.969.M17 - Release 0.20Ivan Medeiros MonteiroIvan Medeiros Monteiro