Describe the issue
Our release steps have the release engineer run scalability tests and CI will pass as green but no results are published to scalability repo.
@sugat009 discovered this for the 5.3.1 patch release:
Heads up: scalability results have not published since 5.2.0-beta.1
While cutting 5.3.1 I ran the scalability action on the 5.3.1-beta.1 tag and it went green, but no results folder showed up in medic/scalability-results. Digging in, the newest folder there is 5.2.0-beta.1 from June 25, and the whole 5.3 line is missing (no 5.3.0-beta.1, no 5.3.0, no 5.3.1-beta.1).
The workflow passes because it only launches the EC2 test instances. The results push from the EC2 side looks like it stopped after 5.2.0. Not blocking 5.3.1 probably!
Describe the improvement you'd like
Ensure CI fails when results don't publish to external repo. Ensure when CI is green, reports are published
Describe alternatives you've considered
none really, we need to archive these.
Describe the issue
Our release steps have the release engineer run scalability tests and CI will pass as green but no results are published to scalability repo.
@sugat009 discovered this for the
5.3.1patch release:Describe the improvement you'd like
Ensure CI fails when results don't publish to external repo. Ensure when CI is green, reports are published
Describe alternatives you've considered
none really, we need to archive these.