Automate testing and building of deb package using GitHub Actions #63
Conversation
| - name: Install dependencies | ||
| run: | | ||
| sudo apt-get update | ||
| sudo apt-get install -y ruby ruby-dev rubygems build-essential gnupg python-gpg libgpgme-dev swig |
There was a problem hiding this comment.
What do we need the swig package for?
There was a problem hiding this comment.
It seems that the gpg Python dependency needs it: https://github.com/DrauzJu/zeyple/commit/1344e64f7d5a4815e7ff61b71be6b8109293d45b/checks?check_suite_id=262393072#step:4:328
|
This looks great! Thank you for setting that up. And I'm glad to see this in the build output:
I can't wait to drop support for Python 2 :D |
|
Thanks for merging! I think you need to register here to enable GitHub Actions in the repository: https://github.com/features/actions |
|
Thanks @DrauzJu! It's now live at https://github.com/infertux/zeyple/actions 😄 |
Aims to close #1
With this PR, a GitHub Actions Workflow is introduced, which is triggered on every push to the master branch. It sets up the environment (Ubuntu 18.04), runs the tests, builds a deb-package and uploads it. A demo of a successful run including the produced deb-package can be found here.
As a next step, a test matrix could be introduced to test gpg and gpgme. Furthermore, it should be automatically tested if the generated deb-pacakge can be installed successfully.