-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Proposal: Deploy packs using StackStorm instead of CircleCI #29
Comments
Yes, there are problems with the missing locking and synchronization for the index file when building many packs in parallel which could be improved. However it's important the way how StackStorm-Exchange was built, open, transparent and self-sufficient based on free CircleCI and requiring no additional infrastructure. Additionally, |
Talking about the Deployment and index synchronization issue for StackStorm-Exchange, Here is how to do that: Minimize the Exchange index conflict
Make deployment operations idempotent
This way we can minize the StackStorm-Exchange pack deployment issues up to state when human interruption is almost not needed. Some of those steps are already in-place in the current CircleCI Deployment, so this should be fairly simple change and a quick win. |
Alternative conflict-free approach: deploy isolated per-pack index update
^^ This will require more work comparing to previous enhancement, but this approach removes the possibility of index conflict at all. So there are plenty of options making things simple, working and self-sufficient, instead of relying on external StackStorm or lock-control instance. |
We have moved Exchange CI to GHA away from CircleCI, so I think we can close this. |
Good call, agreed 💯 |
Sometimes we have to update the CircleCI configurations for all Exchange packs, and this is very tedious since our scripts have to wait for the
deploy
step of the CircleCI run for each pack to finish before merging the next PR or branch and kicking off another CircleCI run.Some examples of where this is required:
apt update
to bust the apt cache for thedeploy
steprequests
versionThe text was updated successfully, but these errors were encountered: