-
Notifications
You must be signed in to change notification settings - Fork 18
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
Consider adding build artifact support for CI or provide easy process for QA to build XPIs locally #58
Comments
Also, this was probably the more relevant piece: Note how we're copying over any generated *.xpi assets into the More details on the details at https://circleci.com/blog/build-artifacts/ and https://circleci.com/docs/2.0/artifacts/ (the latter uses the newer, preferred version 2 of the Circle API). |
Update: @jrbenny35 has kindly offered to help us with this. The current goal would be to automatically generate a build artifact (XPI) per commit via Circle CI that would be available in each open PR for QA to download and test. |
@pdehaan is this already happening here: https://github.com/mozilla/shield-studies-addon-template/blob/master/.circleci/config.yml#L51 ? |
Yeah, it looks like we might be... shield-studies-addon-template/.circleci/config.yml Lines 51 to 52 in af8ed48
Where we're calling
... and ./bin/xpi.sh appears to copy everything into aforementioned "./dist/" directory (whew!): shield-studies-addon-template/bin/xpi.sh Lines 31 to 36 in af8ed48
|
All that said, I have to find where to get the artifacts on Circle-CI. If I click the Circle-CI badge in the README, it seems to open a new tab with the badge image (not a link to the Circle-CI builds). And I don't seem to see the Circle-CI results on any PRs. Not sure if that is because I don't have write access to this repo, or something else... Although, if I manually navigate to Circle, I can see some artifacts in the latest build! https://circleci.com/gh/mozilla/shield-studies-addon-template/44#artifacts/containers/0 |
@biancadanforth Does peter's answer help a bit? I am still willing to help in anyway I can. |
@jrbenny35 Thanks for checking in. I know that we currently have a bash script to build the XPI in our local working directory, but I don't quite understand how we go from there to having it (or a URL like the page pdehaan linked above) made available in the GitHub PR itself? It sounds like from pdehaan that his method of finding that URL was pretty convoluted. Is there a way to include a link to the right URL for downloading the correct XPI in the PR itself automatically? |
Hmm, I know testpilot has a storybook bot that comments on the PR with a link to the PR deployed. Maybe we could find something like that. |
Closing since this was added with #73 |
If we can keep QA testing inside of GitHub and provide a single location where QA can find the latest build, that'd save us a lot of back and forth in Bugzilla/e-mail.
Option 1: Develop an easy process for QA to build the XPI from source
From Paul Oiegas of SoftVision:
Option 2: Add build artifact support for CI
From @pdehaan
The text was updated successfully, but these errors were encountered: