Patch: Two stage build for CI

Patch: Two stage build for CI

[Anand Tamariya]

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

Hi,
Many a times it's easier to check results from CI for either compile or
test failure. Hence, I've broken the build into two stages.

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index f4e08d59dd..45db1b8d9d 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -35,8 +35,16 @@ before_script:
   - DEBIAN_FRONTEND=noninteractive apt install --no-install-recommends -y
-qq -o=Dpkg::Use-Pty=0 libc-dev gcc g++ make autoconf automake
libncurses-dev gnutls-dev git

 stages:
+  - build
   - test

+compile:
+  stage: build
+  script:
+    - ./autogen.sh autoconf
+    - ./configure --without-makeinfo
+    - make
+
 test-all:
   # This tests also file monitor libraries inotify and inotifywatch.
   stage: test

[-- Attachment #2: Type: text/html, Size: 881 bytes --]

Re: Patch: Two stage build for CI

[Michael Albinus]

Anand Tamariya <atamariya@gmail.com> writes:

> Hi,

Hi Anand,

> Many a times it's easier to check results from CI for either compile
> or test failure. Hence, I've broken the build into two stages.

Thanks for this. In general, I agree with you. However, your patch has
some problems:

- It takes even more time after a change, because the compilation is
  not extracted from the tests, but it runs additionally. Better would
  be, to reuse compilation artifacts in the test stage, instead of
  compilation again.

- Consequently, we would need for every test stage entry a corresponding
  build stage entry. And it would also be great, if the compilation
  related to test-filenotify-gio could reuse artifacts from the
  compilation related to test-all.

- You call only "make", not "make bootstrap".

- There are no only: and except: clauses. For example, if somebody just
  changes etc/NEWS, we don't need to run any CI.

Best regards, Michael.