You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2024. It is now read-only.
Hi,
we are using StaticCMS with Astro site hosted on gitlab where we setup circleci CI site rebuild and deploy to our www server. This all works fine until we make and publish several changes made across different collections which trigger multiple commits to gitlab resulting in multiple ci pipelines building and publishing the site. There might be a race condition when a newer deployment would be overwritten by an older one in cases when an older CI job building the site finishes last.
To prevent this, would you consider a new feature which would batch cms changes to one commit so that all changes are published at once instead of in multiple commits?
Thanks,
Libor
The text was updated successfully, but these errors were encountered:
Hi,
we are using StaticCMS with Astro site hosted on gitlab where we setup circleci CI site rebuild and deploy to our www server. This all works fine until we make and publish several changes made across different collections which trigger multiple commits to gitlab resulting in multiple ci pipelines building and publishing the site. There might be a race condition when a newer deployment would be overwritten by an older one in cases when an older CI job building the site finishes last.
To prevent this, would you consider a new feature which would batch cms changes to one commit so that all changes are published at once instead of in multiple commits?
Thanks,
Libor
The text was updated successfully, but these errors were encountered: