Release automation

[dvorka]

Automate and simplify the release process as much as possible.

Release distros and source:

• plan
  • [ ] define order of distributions build which is safe and robust (build & test before anything uploaded): build > run all tests > tarbal > ...
  • [ ] automation script to print (and test) prerequisites like running VMs
  • [ ] study GH Actions: can it build tarball? Can it build .deb? Can it build .rpm? Can it build .dmg?
  • [ ] document (somewhere) MindForger nightly / continuous builds which I currently have for Windows: describe how users can get to these builds (section / link on project homepage to section in documentation where location of distros will be described)
• release @ Ubuntu
  • [ ] create release directory (script parameter overrides variable)
  • [ ] initiate https://ci.appveyor.com/project/dvorka/mindforger/build/artifacts build from master
  • [ ] run all distro-*.* scripts
  • [ ] download Appveyor Win installer artifact
  • [ ] list all distributions and status
  • [ ] update Debian PPA (build PPA and upload new version)
• tarball @ Ubuntu
  • [ ] distro-tarball.sh ... clean tarball build (machine w/ all prerequisites installed)
    • [ ] arg: release directory
    • [ ] clean clone (master)
    • [ ] build directory
    • [ ] dependencies build
    • [ ] tarball archive directory > release directory
    • [ ] purge: command*.json, qmake stashes, deps/MITIE, ...
    • [ ] automation: AppVeyor artifact OR TravisCI artifact
• .deb @ Ubuntu (maintain revision sequence)
  • [ ] distro-deb.sh ... clean .deb build (machine w/ all prerequisites installed)
    • [ ] arg: release directory
    • [ ] clean clone (master)
    • [ ] build directory
    • [ ] dependencies build
    • [ ] tarball archive directory > release directory
• .rpm @ Fedora (maintain revision sequence)
  • [ ] distro-rpm.sh ... clean .rpm build (machine w/ all prerequisites installed)
    • [ ] Fedora VM up and running as prerequisite
    • [ ] OPTIONAL: build on Fedora to ensure ldd and ability to build
    • [ ] scp distro-rpm.sh
    • [ ] scp deb.sh
    • [ ] ssh to VM and run distro-rpm.sh
      • [ ] alien
    • [ ] download rpm > release directory
• [x] .installer @ Windows
  • [x] AppVeyor > release directory

Artifacts (stored in local machine archive directory):

• .exe
  • [x] AppVeyor > wget > release-x.x.x/
• tarball.tgz
  • [ ] mindforger/build/tarball/make-tarball.sh > release-x.x.x/
  • [ ] TODO TravisCI upload 2 GH releases
• .deb
  • [ ] ssh Debian VM > build .deb > scp ...@debianvm release-x.x.x/
  • [ ] TODO TravisCI upload 2 GH releases
• .rpm
  • [ ] scp release-x.x.x/mindforger-x-x-x.deb ...@fedoravm > build > alien > scp @fedoravm release-x.x.x/
• macOs
  • [ ] ... TODO: find VM hosting

Resources:

• examples of macOS builds on Travis CI:
  • https://github.com/martinrotter/rssguard
  • https://github.com/martinrotter/textosaurus
  • https://transfer.sh/ https://files.fm upload services
  • macOS build discussion @ reddit
• https://www.appveyor.com/docs/macos-images-software/
• https://forum.freecadweb.org/viewtopic.php?t=19738

[dvorka]

• build/release-automation/build-all-distros.sh
• before scripts starts do verification and sanity checks
  • directories exists
  • branches are OK
  • VMs are accessible
  • URLs valid
• produce result-report.md ~ prints summary what was build/downloaded/... and resulting state

[martinrotter]

@dvorka See update Travis logic in my rssguard repo, I switched to bintray deployment and it is very easy to setup on AppVeyor/Travis.

https://github.com/martinrotter/rssguard/blob/master/.travis.yml

[mlncn]

I think it will, but to confirm, completing this issue will address this problem:

Err:23 http://ppa.launchpad.net/ultradvorka/productivity/ubuntu focal Release 404 Not Found [IP: 91.189.95.83 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/ultradvorka/productivity/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default.

?

Thanks!

[martinrotter]

Btw, I migrated to Github Actions, with separate release which is automagically updated to contain latest development binaries.

[dvorka]

@martinrotter :+1: you were right - I just migrated to GitHub Actions as well and I was able to pretty quickly get .dmg, unit tests and tarball build working.