Automated extension builds #32
Merged
Conversation
|
Added packaging and signing of the chrome build too. Current it is just signed with the CI key, but I think this should be fine for betas. |
1836775
into
ghostery:develop
1 check passed
1 check passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Automated build of the extension on Jenkins. Contains a Dockerfile in-which we can build the extension and a Jenkinfile to describe the build steps.
The build is done using
moab makezip, which builds and packages the extension for all platforms. With the firefox build, we can also make a signed xpi for the Cliqz browser.Next steps: make signed builds for other browsers. We may be able to add linux compatibility to moab for this.