md380tools icon indicating copy to clipboard operation
md380tools copied to clipboard

Have automated builds using github releases

Open hsmade opened this issue 9 years ago • 12 comments

It would be nice if we could have automated builds for the firmware that get uploaded to the github releases page.

https://docs.travis-ci.com/user/deployment/releases

hsmade avatar Sep 12 '16 19:09 hsmade

Rudy builds every hour, if there are new commits. What I am proposing different because:

  • it will build directly after the tag/commit (to be decided)
  • it will deliver the artifact (the bin file(s)) to the github releases page, so it's all on the same place. https://github.com/travisgoodspeed/md380tools/releases

hsmade avatar Sep 13 '16 09:09 hsmade

Can github releases be precompiled, or are they only the source code of tagged releases?

travisgoodspeed avatar Sep 14 '16 08:09 travisgoodspeed

Issue #290 was caused by PD0ZRY's sorting of firmware versions, which put S13.020 ahead of the others even though it won't boot on most radios.

We really need a properly organized download page to prevent future confusion.

travisgoodspeed avatar Sep 14 '16 08:09 travisgoodspeed

here is an example: https://github.com/roelandjansen/md380tools/releases

Yes, releases can contain binaries, that is their purpose actually. What I do on my own pipelines is tag my master with a version number (https://semver.org) and publish that.

hsmade avatar Sep 14 '16 09:09 hsmade

"We really need a properly organized download page to prevent future confusion."

This is exactly the reason why I proposed this, actually :)

hsmade avatar Sep 14 '16 09:09 hsmade

Okay, we'll enable these builds and start scheduling toward a release candidate.

Cheers, 6A/KK4VCZ

travisgoodspeed avatar Sep 14 '16 09:09 travisgoodspeed

We have a working scenario where jenkins builds direct after I push and the release is then on my page. It's a merge of aeickho, hsmade, sijskes and travis. For hsmade and sijskes things get cherry picked sometimes or specific branches picked instead of master.

roelandjansen avatar Sep 14 '16 09:09 roelandjansen

Nothing new as of yet?

I assume fw build 3FFA38F is last one.

ghost avatar Oct 13 '16 16:10 ghost

the last builds are integrated at

https://github.com/roelandjansen/md380tools/releases

and the last stable at this moment is

https://github.com/roelandjansen/md380tools/releases/tag/e762fc9

There is internalwork going on at this moment and not published yet.

roelandjansen avatar Oct 14 '16 07:10 roelandjansen

For more information on what we are doing check https://github.com/travisgoodspeed/md380tools/blob/master/ContinuousIntegration.md

CoMPaTech avatar Oct 14 '16 08:10 CoMPaTech

What is being done with travisgoodspeed/md380tools/releases?

No tags/builds been setup yet. Only Roelandjansens commits are built to master on his github with hourly pre/latest releases

ghost avatar Oct 16 '16 13:10 ghost

Correct. The ci/cd onlt runs on that one

roelandjansen avatar Oct 16 '16 14:10 roelandjansen