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
[chore]: Pipelines for CI/CD #889
Conversation
only deploy on the main repo Co-authored-by: Wesley de Groot <email@wesleydegroot.nl>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I love the thinking behind this.
Currently all our actions get triggered by
on-push
oron-pull-request
events and run in parallel. The problem with that is, that for example after pushing to themain
branch, if the tests were to fail, the pre-release would be deployed anyway.To mitigate this issue I implemented pipelines for both
on-push
events onmain
as well ason-pull-request
events.on-push
:SwiftLint
->Tests
->Deploy Pre-Release
on-pull-request
:SwiftLint
->Tests
Now if any job fails, no succeeding job will be run and the whole pipeline fails. Since we would not want to deploy a pre-release with a potential error.
Example
Update Dependencies
CodeEditTextView
to0.2.2