Feature #2435

Investigate GitHub action system.

Added by pospelov 6 months ago. Updated 3 months ago.

Status:ResolvedStart date:06 Apr 2020
Priority:HighDue date:
Assignee:ganeva% Done:


Target version:-


Currently, our continuous integration relies on two systems:

  • Buildbot for nightly and developer's builds
  • Appveyor/Travis for pull requests.

Following problems exist for the moment:

  • Buildbot is not visible from outside.
  • Buildbot is abandoned (obsolete version, no config for Randolf, no checks for the green lights).
  • Buildbot's Windows builds are broken.
  • Buildbot's macOS builds are based on MacMini and extremely slow, libraries are outdated.
  • GitHub continuous integration is very slow (but still very useful).
  • No automatic release procedure. All installers are built manually and manually uploaded to the apps server.

Since our group doesn't have resources (manpower and initiative) to resolve this situation properly and keep it steady in the long run, one possible solution could be to stick completely to the free and hosted services.

Within this item, investigate the GitHub action system and provide an answer to the following questions:

  • Is it possible to replace Travis with GitHub action for both, Mac OS and Linux.
  • Is it possible to replace Appveyor with GitHub actions for Windows builds.
  • What would be the performance with respect to Travis/Appveyor.
  • Is it possible to provide two configurations: one to run on the pull request, another to run on release procedure.


#1 Updated by ganeva 5 months ago

  • Assignee set to ganeva

#2 Updated by pospelov 4 months ago

  • Status changed from Sprint to Backlog
  • Target version deleted (Sprint 43)

#3 Updated by wuttke 3 months ago

  • Status changed from Backlog to Sprint

#4 Updated by wuttke 3 months ago

  • Status changed from Sprint to Resolved

Since 1.17, CI runs under GH Actions.

Also available in: Atom PDF