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
You run these tests on each update to dev/stage/prod right? I remember you saying something like that
@jrbenny35 the tests are currently running only on stage. Dev hasn't been in scope so far. I'm also not dismissing the possibility to extend coverage for -dev as well, but when/if that happens, I'm more inclined to add a daily scheduled run rather than linking our runs with each addons-frontend and addons-server builds.
For prod, we are currently working on identifying which set of non-destructive tests should be run as a Sanity suite after the AMO push on Thursdays. In this case, it would be nice to have the possibility to trigger jobs based on addons-frontend/server tags. As far as I know, Ops are triggering prod tags manually from Jenkins, so I'm not sure if this is an impediment to what we are trying to achieve.
I think we can add a script to the addons-frontend repo to trigger a build here when there is a release tagged. This is a good example, https://discuss.circleci.com/t/trigger-repo-build-on-other-repo-update/23712/3
The text was updated successfully, but these errors were encountered: