Feature: tag builds as stable after the releasetest is successful

[laurentsimon]

Is it feasible to tag builds/container images as stable after they have successfully run the releasetest integration tests?

@azeemsgoogle WDUT?

[azeemsgoogle]

Yes, that's what we do today already. A successful run of releasetest automatically tags the associated container images as :stable. Did you mean this or something else?

[laurentsimon]

ok, interesting. I pushed some commits on Monday and did not see that commit tagged as "stable". I need to double check then

[azeemshaikh38]

You are right. Looks like the recent releastest did not successfully transfer to BQ for the past few days, hence did not get marked :stable. Looking at the logs seems like a secondary rate limit issue, specifically the "Search" API which has much lower rate limits.

[azeemshaikh38]

So I think I figured out what's going on. After #1886 lot of repositories were failing for 2 reasons:

• Vulnerabilities check was erroring out on empty repositories which is not the right behavior. 🐛 Do not fail on empty repositories #1914 should fix that.
• BUG: Failures in Branch-Protection during release testing #1320 is continuing to cause failures like before.

IMO, we should fix #1320 to fix the failing releasetests before making a new release. @naveensrinivasan @laurentsimon wdyt?

[laurentsimon]

@asraa do you have cycles to fix #1320?

[azeemshaikh38]

@asraa do you have cycles to fix #1320?

I believe @naveensrinivasan plan's to work on this issue?

[laurentsimon]

Thanks @naveensrinivasan !