-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
The Elasticsearch compatibility job should run as a Github workflow rather than on Jenkins.
It can be found here: https://ci.optimize.camunda.cloud/view/all/job/elasticsearch_compatibility/
ATs:
- The Elasticsearch compatibility job is no longer run on Jenkins
- The Elasticsearch compatibility job runs as a scheduled Github workflow
This is the controller panel for Smart Panels app
[OPT-7512] Migrate Elasticsearch compatibility job from Jenkins to GHA
Description |
Original:
The Event Based Process Import Performance job job should run as a Github workflow rather than on Jenkins.
It can be found here: [https://ci.optimize.camunda.cloud/view/all/job/event-import-performance/] *ATs:* * The engine compatibility job is no longer run on Jenkins * The engine compatibility job runs as a scheduled Github workflow |
New:
The Elasticsearch compatibility job should run as a Github workflow rather than on Jenkins.
It can be found here: [https://ci.optimize.camunda.cloud/view/all/job/elasticsearch_compatibility/] *ATs:* * The Elasticsearch compatibility job is no longer run on Jenkins * The Elasticsearch compatibility job runs as a scheduled Github workflow |
This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10125. Please use this link for any future references and continue any discussion there.