CI: Setup workflows to build all variants in the app (WPB-8644)
|
|
PR Submission Checklist for internal contributors
-
The PR Title
- [x] conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
- [x] contains a reference JIRA issue number like
SQPIT-764 - [x] answers the question: If merged, this PR will: ... ³
-
The PR Description
- [x] is free of optional paragraphs and you have filled the relevant parts to the best of your ability
What's new in this PR?
Description
Created 4 workflows to build apks from develop, prod, internal and main based on some events.
-
On each push/pull request into/against
developwe build:DevDebugandStagingRelease -
On each push/pull request into/against
prodwe build:ProdCompatRelease -
On each push/pull request into/against
mainwe build:BetaRelease -
On each push/pull request into/against
release/candidatewe build:InternalCompatandStagingCompat
Needs releases with:
- [ ] GitHub link to other pull request
- [ ] Wire's Github Workflow has automatically linked the PR to a JIRA issue
PR Post Merge Checklist for internal contributors
- [ ] If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.
References
- https://sparkbox.com/foundry/semantic_commit_messages
- https://github.com/wireapp/.github#usage
- E.g.
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.
Build 4800 failed.
Build 4825 failed.
Build 4863 failed.
Build 4869 failed.
Build 4924 failed.
Build 4934 failed.
Build 4939 failed.
@ohassine looks like you are rolling back kalium to a previous commitish.
This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
| develop | This PR |
|---|---|
| 323fad3c7ba910ccafaa3a279007d5ace1607e8c | dcd806b84178f1873df629a427a573a22bf027c9 |
Is this intentional?
Build 4951 failed.
Build 4957 failed.
Build 4960 failed.
Build 4963 failed.
Build 4966 failed.
Build 5020 failed.
After this is merged, we got to update the branch rules so we require ui-tests / ui-tests (29) and unit-tests / coverage for PRs, instead of ui-tests (29) and unit-tests that we currently do
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
No data about Duplication