Continuous Integration artifacts are now built only once a day (nightly builds) and include Gtk+ versions

* The CI tests are unchanged. The workflow file has been renamed to ci.yml, though.
* Nightly builds are described by nightly.yml and are built at 4:13.
* Nightly Ubuntu package builds now include the Gtk+ 3 packages.

1 files changed, 0 insertions, 107 deletions

diff --git a/.github/workflows/continuous-integration.yml b/.github/workflows/continuous-integration.yml
deleted file mode 100644
index cbe7837..0000000
--- a/.github/workflows/continuous-integration.yml
+++ /dev/null
@@ -1,107 +0,0 @@
-name: Continuous Integration
-
-on:
-  push:
-    branches: [ master ]
-  pull_request:
-    branches: [ master ]
-
-jobs:
-  build-and-test:
-    strategy:
-      matrix:
-        os: [ubuntu-18.04, ubuntu-20.04]
-        compiler: ['CC=gcc CXX=g++', 'CC=clang CXX=clang++']
-        interface: [ncurses, gtk]
-
-    # NOTE: The virtual environments already contain both GCC and Clang
-    runs-on: ${{ matrix.os }}
-
-    steps:
-
-    - name: Recursive Git Clone
-      uses: actions/checkout@v2
-      with:
-        submodules: recursive
-
-    - name: Update Repositories
-      run: sudo apt-get update
-    - name: Install Build Dependencies
-      run: >
-        sudo apt-get install -y
-        build-essential
-        autoconf automake libtool
-        libglib2.0-dev libncurses-dev libgtk-3-dev gob2 xvfb
-        groff doxygen
-
-    - name: Configure Build
-      run: |
-        autoreconf -i
-        ./configure --with-interface=${{ matrix.interface }} --enable-html-manual ${{ matrix.compiler }}
-
-    # NOTE: xvfb-run emulates an XServer and is required when building
-    # Gtk versions (since SciTECO calls itself during the build).
-    - name: make
-      run: xvfb-run -a make
-    - name: make install
-      run: sudo xvfb-run -a make install
-    - name: Run Test Suite
-      run: xvfb-run -a make check
-    - name: Build Developer Documentation
-      run: cd doc && make devdoc
-    # FIXME: Will try to perform an out-of-tree build which will not
-    # work without manual intervention due to Scintilla.
-#   - name: make distcheck
-#     run: xvfb-run -a make distcheck
-    - name: Build Source Tarball
-      run: make dist
-
-  # This is a separate job since we don't need to build Debian packages
-  # using Clang and there is no need to run "make all".
-  debian-packages:
-    strategy:
-      matrix:
-        os: [ubuntu-18.04, ubuntu-20.04]
-
-    runs-on: ${{ matrix.os }}
-
-    steps:
-
-    - name: Recursive Git Clone
-      uses: actions/checkout@v2
-      with:
-        submodules: recursive
-
-    - name: Update Repositories
-      run: sudo apt-get update
-    - name: Install Build Dependencies
-      run: >
-        sudo apt-get install -y
-        devscripts build-essential lintian debhelper
-        autoconf automake libtool
-        libglib2.0-dev libncurses-dev
-        groff-base
-
-    # NOTE: We need to configure the build directory only to generate distribute.mk.
-    - name: Configure Build
-      run: |
-        autoreconf -i
-        ./configure
-
-    # NOTE: Packages are left in debian-temp/.
-    - name: Build Debian Package
-      run: ./distribute.mk debian-binary
-    # FIXME: For doing Windows builds, we need a few manually built packages
-    # (PDCurses, Glib...).
-    # Perhaps they can be uploaded to Sourceforge and simply downloaded here.
-    # Alternatively, we could manually prepare a Docker container image or
-    # even build them from scratch here.
-#   - name: Build Windows Bundle
-#     run: ./distribute.mk mingw-binary
-
-    # NOTE: There is no way to prevent Github zipping the artifact.
-    - name: Archive Debian Package (ncurses)
-      uses: actions/upload-artifact@v2
-      with:
-        name: ${{ matrix.os }} package (ncurses)
-        path: debian-temp/*.deb