🚀 Pre-release master -> staging_ThisIsSparta1

[matusdrobuliak66]

What kind of pre-release?

master branch

Sprint Name

ThisIsSparta

Pre-release version

1

Commit SHA

744ff06

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

• weekly release

What Changed

• 🎨Improving computational clusters cli monitoring tool #5204 by @sanderegg
• 🐛Clusters-keeper: calling >100 times for the same new cluster now returns cached information #5201 by @sanderegg
• 🔒️ Maintenance: Fixes issues detected by code scanning #5207 by @pcrespov
• 🎨 reroute dynamic service stop via dynamic-scheduler #5192 by @GitHK
• 🔒️⬆️ Maintenance: GHSA-v8gr-m533-ghj9 #5211 by @pcrespov
• 🐛 FrontEnd: Fixed misleading cursor for deleting study #5213 by @jsaq007
• 🐛 Fixes registration in multiple products via invitations #5055 by @pcrespov
• ✨E2E: add playwright sleepers test in CI #5177 by @sanderegg
• ✨Computational backend: add helpful tracing log #5218 by @sanderegg

Devops check ⚠️ devops

• Add changes (if any) and release tags in https://github.com/ITISFoundation/osparc-ops-environments/tags
• Add changes (if any) and release tags in osparc-ops-deployment-configuration (staging.osparc.io & osparc-staging.speag.com)
• ...

e2e testing check 🧪

No response

Summary 📝

• make release-staging name=<sprint_name> version=<version> git_sha=<commit_sha>
  • https://github.com/ITISFoundation/osparc-simcore/releases/new?prerelease=1&target=<commit_sha>&tag=staging_<sprint_name><version>&title=Staging%20<sprint_name><version>
• Draft pre-release
• Announce (add redis key maintenance in every concerned deployment)

  {"start": "2023-02-01T12:30:00.000Z", "end": "2023-02-01T13:00:00.000Z", "reason": "Release ResistanceIsFutile9 "}

• Announce release in Mattermost

  :loud_sound:  Maintenance scheduled for **NAMED_DAY DD. MM from START_TIME - END_TIME**.
  =========================================================================
  
  @all Be aware that you will automatically be logged out and your projects stopped and saved during the maintenance time. Affected:
  *   [https://staging.osparc.io](https://staging.osparc.io/)
  *   [https://https://staging.s4l-lite.io/](https://https://staging.s4l-lite.io//)
  
  and on premises:
  *   [https://osparc-staging.speag.com](https://osparc-staging.speag.com/)
  *   [https://tip-staging.speag.com](https://tip-staging.speag.com/)
  *   [https://s4l-staging.speag.com](https://s4l-staging.speag.com/)
  *   [https://s4l-lite-staging.speag.com](https://s4l-lite-staging.speag.com/)
  
  
  Reason: Scheduled staging-release of STAGING_NAME_AND_VERSION.
  
  Thanks for your understanding and sorry for the inconveniences,
  
  Your friendly oSparc Team
  
  

Releasing

• Release (release draft)
• Check Release CI
• Check hanging sidecars. Helper command to run in director-v2 CLI simcore-service-director-v2 close-and-save-service <uuid>
• Check deployed
  • aws deploy
  • dalco deploy
• Delete announcement
• Check e2e runs
• Announce

https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_<sprint_name><version>

[matusdrobuliak66]

Incident report: https://git.speag.com/oSparc/osparc-infra/-/issues/41

[matusdrobuliak66]

in sim4life.io manually changed buffer machines to 2