You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cleanup IP addresses in production ( please add here a link to relevant case )
Tests assessment: e2e testing check 🧪
AWS staging:
random vtk study dispatcher failing (insufficient resources)
random parallel portal links failing (insufficient resources)
DALCO staging:
ti-plan failing always
Test assessment: targeted-testing 🔍️
EI: no showstopper found. I went through all the PRs and mainly tested the UI changes. Small things I found have been reported in the PRs. fyi @matusdrobuliak66
Test assessment: user-testing 🧐
No response
Summary 📝
Prepare release link
make release-prod version=1.52.0 git_sha=f987bbc5631df4d3751d04438d08e772b10c7bc9
AWS stagging pending services problem is back:
As in the AWS staging, we are on the edge with used resources this behavior can sometimes happen, and the trigger of this is usually e2e tests where we run many services in parallel (which do not have enough resources, mainly the ones that needs GPU).
Release version
1.52.0
Commit SHA
f987bbc
Previous pre-release
https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_Mithril6
Did the commit CI suceeded?
Motivation
Changes
staging_Mithril5
v1.51.2
] #4049 by @GitHKFull Changelog: staging_Mithril4...staging_Mithril5
Release Issue: #4054
staging_Mithril6
Shared with
filter in Dashboard #4050 by @odeimaizservice_latest
cache table #4056 by @pcrespovFull Changelog: staging_Mithril5...staging_Mithril6
Release Issue: #4058
Devops check 👷
Tests assessment: e2e testing check 🧪
AWS staging:
DALCO staging:
Test assessment: targeted-testing 🔍️
EI: no showstopper found. I went through all the PRs and mainly tested the UI changes. Small things I found have been reported in the PRs. fyi @matusdrobuliak66
Test assessment: user-testing 🧐
No response
Summary 📝
{"start": "2023-04-06T15:00:00.000Z", "end": "2023-04-06T17:00:00.000Z", "reason": "Release v1.52.0"}
Releasing 🚀
The text was updated successfully, but these errors were encountered: