-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Chaos processes produce lots of version numbers #123
Comments
🤡 But then again, it's chaos tests, so maybe this is a deliberate attempt to over time flood the state with BPMN versions 🤡 |
Looks for me like a bug |
Might be related to duplicate processes here https://github.com/zeebe-io/zeebe-cluster-testbench/tree/main/processes and here https://github.com/zeebe-io/zeebe-chaos/tree/master/chaos-model |
I guess I can delete the ones in testbench, because this here is the SSOT? |
We still need to deploy the process models from zbchaos to testbench, possible first step in the docker image. |
600: Remove chaos files r=Zelldon a=pihme This PR removes the chaos files. Most of the files have already been moved to chaos test. However, some files are duplicated which leads to confusion and possibly to unintended outcomes: zeebe-io/zeebe-chaos#123 With the upcoming changes (i.e. Deepthi implementing another test) this repo will be slimmed down to only provide the bare testbench, which is then extensible by independently deployed tests (chaos tests, the Deepthi test). `@Zelldon` Happy to discuss this direction of travel with you, if you have any objections. This is not set in stone. Since you were off this week, I didn't yet have a chance to align. This PR was created under the assumption that you agree to this approach. `@Zelldon` I checked whether all the stuff I removed here is available in chaos-test. This seems true for the BPMN models and the deployment descriptors. However, I didn't immediately find any scripts to actually deploy the chaos workers. So this logic might have to be moved, or we just drop the last commit for a time being. Co-authored-by: pihme <[email protected]>
Some of the chaos experiment processes produce a new versions whenever they are deployed or executed:
The 100 seems to be a cap in Operate dashboard. The actual version number is 246. Most likely the processes are generated and use ramdom element IDs each time
The text was updated successfully, but these errors were encountered: