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
But, if nothing has changed in the add-on (i.e. no code, not the shared BG images), this is wasteful. Would be handy to tweak the deployment to just download and re-use an existing signed XPI from AMO. (We do this on Test Pilot, as an example.)
The text was updated successfully, but these errors were encountered:
The only thing this issue prevents is continual automatic deployments to dev on commits to master. That would be nice to have, though I might say that having automatic master branch builds of the add-on signed could be seen as a negative by AMO folks.
Currently, all deployments of the site via the development branch attempt to sign the add-on build. This will fail if the add-on version hasn't been changed.
But, if nothing has changed in the add-on (i.e. no code, not the shared BG images), this is wasteful. Would be handy to tweak the deployment to just download and re-use an existing signed XPI from AMO. (We do this on Test Pilot, as an example.)
The text was updated successfully, but these errors were encountered: