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_EnchantedOdyssey3 #5620

Closed
11 of 14 tasks
YuryHrytsuk opened this issue Apr 5, 2024 · 3 comments
Closed
11 of 14 tasks

🚀 Pre-release master -> staging_EnchantedOdyssey3 #5620

YuryHrytsuk opened this issue Apr 5, 2024 · 3 comments
Assignees
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work

Comments

@YuryHrytsuk
Copy link
Contributor

YuryHrytsuk commented Apr 5, 2024

What kind of pre-release?

master branch

Sprint Name

EnchantedOdyssey

Pre-release version

3

Commit SHA

4e5aae010f89e0b053a47c2e05dd56a7c632249e

Did the commit CI suceeded?

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": "2024-04-10T11:41:00.000Z", "end": "2024-04-10T12:41:00.000Z", "reason": "Release EnchantedOdyssey3"}
  • 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 Apr 5, 2024
@mrnicegyu11
Copy link
Member

Ops-Environments Changelog:

Changelog:
- Refactor/open postgres on osparc public (#647)
- Try to fix GAIA docker-in-docker failure
- ♻️Change: Switch to `docker stack config` (#613)
- Some refactoring (#644)
- Revert "Director v2 avoid ops node (#633)" (#634)
- Director v2 avoid ops node (#633)
- Handle docker-in-docker situations and docker secrets handling in gitlab Ci runners

@mrnicegyu11
Copy link
Member

done

@mrnicegyu11
Copy link
Member

next staging release issue: #5649

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

3 participants