mbed CLI 0.8 (EPR)

[screamerbg]

New:

• .lib do not allow named branches (only rev hashes) *.lib should not allow named branches #224
• mbed publish --message <msg> to allow mbed publish automation Run mbed publish without log message prompt #228
• Support multiple locations to requirements.txt (was deprecated in mbed-os Travis - targets addition mbed-os#409)
• Add -N/--artifact-name option to compile to match tools/build.py and tools/test.py options No artifact-name option when compiling static library #229
• Report 12 SHA revision hashes in output. Use full 40 SHA hash in .lib
• Bump minor version to 0.8

Fixes:

• Update toolchain settings to use MBED_ prefix (related to [Tools] Add MBED_ prefix to compilers environment variables mbed-os#2033)
• Deprecate mbed compile --tests in favour of mbed test --compile and general mbed test workflows Inconsistent commands in the cli #225

[bridadan]

I understand this change:

.lib do not allow named branches (only rev hashes)

But this may be a breaking change for a few of the Oulu test apps. The Oulu team needs to be made aware of this change before this gets merged to prevent merge blockages on ARMmbed/mbed-os.

cc @jupe

Ditto for deprecating mbed compile -tests

https://github.com/ARMmbed/mbed-os/blob/master/circle.yml#L4

These should be updated first before merging.

[screamerbg]

@bridadan Thanks for pointing these out. Happy to change circle.yml?

[bridadan]

Done: ARMmbed/mbed-os#413

I'm not sure if removing mbed compile --tests now is the right time. I think instead printing out a message when mbed compile --tests is invoked suggesting the alternative mbed test --compile might be a better path forward, at least for the next few releases. This will directly affect people's workflow and I think having a few releases with warnings makes sense before completely removing it.

[screamerbg]

@bridadan Not sure that we'd want partner engineers to use the compile --test when they could use much better workflow that is already provided by mbed test. In that sense deprecating these now makes more sense.

[bridadan]

You're right, we should be encouraging them to use mbed test instead of mbed compile --tests. But they won't know an alternative if we don't point them at it. That's why I'm saying we should print a warning saying they should use mbed test instead of removing it.

[sg-]

All partners have been shown how to use mbed test. If we have CI or internal devs using mbed compile --tests they should be using the supported workflow.