-
Notifications
You must be signed in to change notification settings - Fork 40
Introduce QNX CI job #121
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
Introduce QNX CI job #121
Conversation
4841d8b to
0a32c05
Compare
| # Workflow configuration for S-CORE CI - Bazel Build & Test communication module for target platforms | ||
| # This workflow runs Bazel build and test for QNX when triggered by specific pull request events. | ||
|
|
||
| name: Bazel Build & Test communication module (target-platforms) |
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.
should this use reusable QNX8 workflow from https://github.com/eclipse-score/cicd-workflows ?
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.
Unfortunately I can't use the upstream workflows for various reasons.
Though, I want to upstream fixes to cicd-workflows to slowly lift this restriction.
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.
You mean you will create PRs to reusable workflows?
d89b623 to
02bbc19
Compare
For our current matrix builds we are inerested in the outcome of every branch independent of the other branches.
Build fails because the rust toolchain is not hermetic.
02bbc19 to
e1e32be
Compare
5a86dd4 to
2b83664
Compare
c040741 to
a6a5948
Compare
execute tests and store artifacts
We do not want to duplicate the logic of the workflows. Since we have the logic except for coverage reports already as part of other workflows we reduce this workflow to only create a coverage report. All the other workflows we enable to also be triggered by a release creation.
a6a5948 to
0f532ee
Compare
No description provided.