Skip to content

🚀 Pre-release master -> staging_Bazinga2 #7667

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

Open
1 of 17 tasks
YuryHrytsuk opened this issue May 13, 2025 · 1 comment
Open
1 of 17 tasks

🚀 Pre-release master -> staging_Bazinga2 #7667

YuryHrytsuk opened this issue May 13, 2025 · 1 comment
Assignees
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Milestone

Comments

@YuryHrytsuk
Copy link
Contributor

YuryHrytsuk commented May 13, 2025

What kind of pre-release?

master branch

Sprint Name

Bazinga

Pre-release version

2

Commit SHA

TBD

Planned date

TBD

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

  • Weekly staging release

What Changed

No response

Devops check ⚠️ devops

0. This can be done entirely in portainer
1. Scale graylog-mongodb to 0 replica
2. Delete docker persistant volume of graylog-mongodb
3. Scale graylog-mongodb to 1 replica

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>
@YuryHrytsuk YuryHrytsuk added t:maintenance Some planned maintenance work release Preparation for pre-release/release labels May 13, 2025
@YuryHrytsuk YuryHrytsuk self-assigned this May 13, 2025
@matusdrobuliak66 matusdrobuliak66 added this to the Bazinga! milestone May 16, 2025
@matusdrobuliak66 matusdrobuliak66 changed the title 🚀 Pre-release master -> staging_PauwelKwak6 🚀 Pre-release master -> staging_Bazinga2 May 16, 2025
@matusdrobuliak66
Copy link
Collaborator

matusdrobuliak66 commented May 16, 2025

⚠️⚠️ Run DB script @matusdrobuliak66

After this commit #7677 is deployed, we should do this: https://github.com/ITISFoundation/private-issues/issues/85#issuecomment-2886608706

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Projects
None yet
Development

No branches or pull requests

2 participants