Skip to content
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

🚀 Pre-release master -> staging_MartinKippenberger2 #6435

Closed
2 of 16 tasks
YuryHrytsuk opened this issue Sep 24, 2024 · 2 comments
Closed
2 of 16 tasks

🚀 Pre-release master -> staging_MartinKippenberger2 #6435

YuryHrytsuk opened this issue Sep 24, 2024 · 2 comments
Assignees
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work

Comments

@YuryHrytsuk
Copy link
Contributor

YuryHrytsuk commented Sep 24, 2024

What kind of pre-release?

master branch

Sprint Name

MartinKippenberger

Pre-release version

2

Commit SHA

d38a6c361545fae272c49266a89f806a3b8719ea

Planned date

October 4, 2024

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

  • Weekly staging release

What Changed

Devops check ⚠️ devops

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 Sep 24, 2024
@YuryHrytsuk YuryHrytsuk added this to the MartinKippenberger milestone Sep 24, 2024
@YuryHrytsuk
Copy link
Contributor Author

Do not close until all Devops check ⚠️ devops are done

@YuryHrytsuk
Copy link
Contributor Author

Do not close until all Devops check ⚠️ devops are done

Done

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