Skip to content

Add Travis CI for supported targets #12

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

Merged
merged 1 commit into from
Dec 11, 2020

Conversation

LDong-Arm
Copy link
Contributor

@LDong-Arm LDong-Arm commented Dec 8, 2020

This is based on https://github.com/ARMmbed/mbed-os-example-blinky/blob/development/.travis.yml but uses Mbed CLI 1.0 instead of CMake.

List of targets:

  • ARM_MUSCA_S1
  • ARM_MUSCA_S1_NS (identical to ARM_MUSCA_S1 for backward compatibility)
  • ARM_MUSCA_B1
  • ARM_MUSCA_B1_NS (identical to ARM_MUSCA_B1)
  • K64F
  • K66F
  • NUCLEO_F429ZI
  • FVP_MPS2_M0
  • FVP_MPS2_M0P
  • FVP_MPS2_M3
  • FVP_MPS2_M4
  • FVP_MPS2_M7
  • GD32_F450ZI

Note: CYTFM_064B0S2_4343W is excluded for now due to Python failure of Cypress signing tool during Post-Build. This happens to any Mbed application for this target, I've created ARMmbed/mbed-os#14022.

@LDong-Arm
Copy link
Contributor Author

LDong-Arm commented Dec 8, 2020

The list of items being built is here: https://github.com/ARMmbed/mbed-os-example-psa/pull/12/checks
Once I've got some review, I can remove develop builds and only keep debug and release builds as @jainvikas8 suggested to me. Apart from that, do we want to build all these targets?
Update: Done.

@LDong-Arm LDong-Arm force-pushed the add_travis branch 4 times, most recently from 596fec6 to e216469 Compare December 10, 2020 12:31
Copy link
Contributor Author

@LDong-Arm LDong-Arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jainvikas8 Thanks for the review, I'll fix them.

@evedon
Copy link
Contributor

evedon commented Dec 10, 2020

Once I've got some review, I can remove develop builds and only keep debug and release builds as @jainvikas8 suggested to me.
I agree that we need release builds but I would use develop (default) instead of debug.

Apart from that, do we want to build all these targets?
I will follow up on the list of targets and confirm. For now, let's have all supported targets.

@LDong-Arm
Copy link
Contributor Author

Apart from that, do we want to build all these targets?
I will follow up on the list of targets and confirm. For now, let's have all supported targets.

Yea this is a concern. The CI run currently takes quite a long term.

@jainvikas8 jainvikas8 changed the title Add Travis CI for all supported targets & all profiles Add Travis CI for supported targets Dec 10, 2020
Copy link

@jainvikas8 jainvikas8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok to merge, if CI passes.

@evedon
Copy link
Contributor

evedon commented Dec 11, 2020

@LDong-Arm The script is still using release and debug profiles instead of release and develop.

Targets covered (based on PSA service availability in Mbed OS
targets.json):
 * ARM_MUSCA_S1
 * ARM_MUSCA_B1
 * K64F
 * K66F
 * NUCLEO_F429ZI
 * FVP_MPS2_M0
 * FVP_MPS2_M0P
 * FVP_MPS2_M3
 * FVP_MPS2_M4
 * FVP_MPS2_M7
 * GD32_F450ZI

Profiles covered: release and develop.

Note: CYTFM_064B0S2_4343W is excluded until an issue with its
Post-Build script is fixed.
@LDong-Arm
Copy link
Contributor Author

@evedon Missed it, updated

@evedon evedon merged commit 42bab1d into ARMmbed:development Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants