Deployment to the website #4126
Replies: 2 comments 2 replies
-
|
Good afternoon @FAJ-Munich - this is expected behavior during deployment, as our deployment utilizes a rolling no-downtime deployment. It is only expected to occur for a short time during the time a deployment is occurring. During the short deployment window, it is possible that some HTTP requests are responded to from an old instance with the previous commit, and some are responded to with the latest commit. This is expected behavior during deployments and not an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the explanation! Highly appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
You're welcome. Thank you for the report! |
Beta Was this translation helpful? Give feedback.
-
Maybe a superfluous question:
I experience that deployment to the website appears to be "jumping", i.e., on multiple re-loads in the browser the result is randomly chosen between an older version (without the latest commits) and the latest version (including the latest commits). I am not sure if there is a way around such behaviour: certainly, it matters the most when bug fixes for the code are deployed.
Beta Was this translation helpful? Give feedback.
All reactions