Add CI to build all the targets

[SergioGasquez]

Expanded the CI to build the project for all the targets using the Dockerfile generated for devcontainer support.

[ivmarkov]

Why this and not just cargo install cargo-generate?

[SergioGasquez]

I changed to the binary approach as it's way faster. If you think is better to do it with cargo install I am happy to undo this change

[ivmarkov]

I'm not sure why we are now installing cargo-generate that way?

[SergioGasquez]

I'm not sure why we are now installing cargo-generate that way?

It's only because it's faster, but I wouldn't mind using cargo install if you think is better

[SergioGasquez]

Installing cargo-generate from release binaries can also make the CI more "consistent" as it avoids some "external" errors on CI. Eg: Todays CI run failed because cargo install cargo-generate was failing

[ivmarkov]

@SergioGasquez Sorry for following up late, can you resolve the conflicts, then I'll merge?

[SergioGasquez]

@SergioGasquez Sorry for following up late, can you resolve the conflicts, then I'll merge?

Hello @ivmarkov, do not worry about the delays! Conflicts are now resolved. Thanks for all your dedication!

[ivmarkov]

@SergioGasquez I think we need to temporarily disable the PlatformIO based build, until we figure out what is wrong there.

[SergioGasquez]

@SergioGasquez I think we need to temporarily disable the PlatformIO based build, until we figure out what is wrong there.

I've commented those steps!

[ivmarkov]

@SergioGasquez BTW it still complains that the branch is unmergeable due to conflicts.
I think you need to rebase it on top of latest master first.

[SergioGasquez]

It now shows that it can be merged with no conflicts! :)

[ivmarkov]

It can be merged but it cannot be rebased. Anyway, ill not use rebase then.