-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
ci: update actions and images #24039
Conversation
FLASH Analysispx4_fmu-v5x
px4_fmu-v6x
Updated: 2024-12-04T17:39:40 |
4bfe36e
to
258080d
Compare
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
0b28622
to
f7630d4
Compare
affa6e2
to
5268a89
Compare
5ab2531
to
dbe8ca5
Compare
1df7e85
to
e467171
Compare
d36d194
to
6b8c2f8
Compare
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.
hey @dagar can you take a look? i think its ready for review
@@ -25,28 +25,27 @@ jobs: | |||
"NO_NINJA_BUILD=1 px4_fmu-v5_default", | |||
"NO_NINJA_BUILD=1 px4_sitl_default", | |||
"px4_sitl_allyes", | |||
"airframe_metadata", |
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.
I removed airframe_metadata
& parameters_metadata
from this workflow, they are also being built by the "Build all targets" workflow. I don't see a point in building again here.
- name: auto-commit any changes to change indication | ||
uses: stefanzweifel/git-auto-commit-action@v4 | ||
with: | ||
commit_message: '[AUTO COMMIT] update change indication' | ||
file_pattern: 'src/modules/ekf2/test/change_indication/*.csv' |
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.
check ekf files only
commit_message: | | ||
'[AUTO COMMIT] update change indication' | ||
|
||
See .github/workflopws/ekf_update_change_indicator.yml for more details |
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.
I found a few of these commits in the codebase, they are hard to follow, adding this comment will help someone point to the source
- uses: actions/checkout@v1 | ||
with: | ||
token: ${{ secrets.ACCESS_TOKEN }} | ||
- name: Install Node v20.18.0 |
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.
Installing node directly on the container for this test.
Why? the install emscripten is giving me tons of issues when running with the docker-run
package
- name: Install Node v20.18.0 | ||
uses: actions/setup-node@v4 | ||
with: | ||
node-version: 20.18.0 |
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.
This is the version required by the emscripten dependency
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
Updates some actions to run build steps in container instead of the whole workflow.
6b8c2f8
to
8190241
Compare
Thank you @mrpollo ! 🙏 |
Problem
GitHub deprecated older versions of the cache, and checkout actions which are now using an updated version of node which isnt' available on the older PX4 container images
Solution
Updated cache, and checkout deps to latest where possible, and switched to the newer px4-dev container image with the updated base operating system environment