During Sora Card release 3.4.0 we did faced with several problems which appears to block uploading build to QA team and App store connect.
CI machine run out of free memory space. It happens periodically, as always at the most inopportune time. It requires asking devops to clean up the space manually. Automation on CI can help to fix it.
Also good to have coordinations in between Sora releases and Dev ops CI maintenance, to avoid blocking testing/releasing and waisting time on problem investigation.
Test fails on CI if dev stand is down and blocks uploading build to App store, which is reasonable to reduce release time (final QA testing can be processed in parallel with Apple review) Quick fix is to turn off testing phase on CI (not a good practice) Potential fix is to add preDev stand to test new «bakend» releases before breaking down dev stands for all ather teams.
2bogd
commented
1 year ago
During Sora Card release 3.4.0 we did faced with several problems which appears to block uploading build to QA team and App store connect.
CI machine run out of free memory space. It happens periodically, as always at the most inopportune time. It requires asking devops to clean up the space manually. Automation on CI can help to fix it.
Also good to have coordinations in between Sora releases and Dev ops CI maintenance, to avoid blocking testing/releasing and waisting time on problem investigation.
Test fails on CI if dev stand is down and blocks uploading build to App store, which is reasonable to reduce release time (final QA testing can be processed in parallel with Apple review) Quick fix is to turn off testing phase on CI (not a good practice) Potential fix is to add preDev stand to test new «bakend» releases before breaking down dev stands for all ather teams.
There were problems with builds from 61 up to 85 https://jenkins.soramitsu.co.jp/job/sora/job/sora-ios/view/tags/job/3.4.0/61/console https://jenkins.soramitsu.co.jp/job/sora/job/sora-ios/view/tags/job/3.4.0/85/