-
Notifications
You must be signed in to change notification settings - Fork 7.6k
ci: Miscellaneous improvements #6132
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
Conversation
4e569a2
to
e154907
Compare
it is not necessary that the target mcu equals the third part of FQBN. This in our case currently is true, but if we want to test agains different boards (we will in near future) then scripts will not be able to tell what is the actual MCU and decide to skip the test. |
How would this look like? |
first part is "manufacturer"m, second is "core" and third is the board. manufacturer and core come from the path of installation: |
Signed-off-by: Abdelatif Guettouche <[email protected]>
Signed-off-by: Abdelatif Guettouche <[email protected]>
…fork or not. This allows forks to run workflows with their own code. Signed-off-by: Abdelatif Guettouche <[email protected]>
Okay, thanks. If the boards we want to test against are Espressif's, we can still extract the chip name from the board's, but other manufacturers won't necessary follow the same naming conventions (and I think we also have few special cases). |
770b954
to
84b85e1
Compare
Signed-off-by: Abdelatif Guettouche <[email protected]>
Signed-off-by: Abdelatif Guettouche <[email protected]>
Signed-off-by: Abdelatif Guettouche <[email protected]>
workflow_dispatch
to be able to trigger the workflow manually.