Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger circleci jobs based on addons-frontend tags #31

Open
b4handjr opened this issue Nov 30, 2020 · 3 comments
Open

Trigger circleci jobs based on addons-frontend tags #31

b4handjr opened this issue Nov 30, 2020 · 3 comments

Comments

@b4handjr
Copy link
Collaborator

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

@AlexandraMoga
Copy link
Contributor

@jrbenny35 do we still need this now with the integration tests being removed from addons-frontend?

@b4handjr
Copy link
Collaborator Author

b4handjr commented Feb 3, 2021

@jrbenny35 do we still need this now with the integration tests being removed from addons-frontend?

You run these tests on each update to dev/stage/prod right? I remember you saying something like that

@AlexandraMoga
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants