Nikos Mavrogiannopoulos <[email protected]> writes: > This has the advantage of using gnutls' CI servers. For that I attach > the file needed to be present to enable using these servers.
Sounds useful! Can you explain very briefly how that's organized, what's done at your servers, and what's done by gitlab? We should try to avoid "service-as-a-software-substitute"? Is it easy to add additional configurations? On my wishlist would be x86-64 --disable-assembler, mini-gmp configs, ARM configs, and some big-endian config (not sure what big-endian archs still are relevant and available, possibly mips?). > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > new file mode 100644 > index 0000000..816cf74 > --- /dev/null > +++ b/.gitlab-ci.yml > @@ -0,0 +1,16 @@ > +Build and Check (x86-64): Is there any way to get a comment into this file, pointing to relevant documentation? I guess the "tags" are used to select what each build machine does? > + script: > + - git submodule update --init && autoreconf -fvi && ./.bootstrap is nettle's advertised method to generate files needed pre-configure. So I think it's better to use that than autoreconf. Why submodule, is nettle used as a submodule of gnutls, or is it some magic for the continuous integration system? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
