When a .tarball-version file containing the version string is present,
it is taken for granted that the source tarball is present.  This
allows to lift the requirement on a Git checkout to use the source
tarball.  This makes it easy and cheap to sync this tarball and
accompanying .tarball-version file across different Jenkins agents to
distribute the packaging jobs, bring the total build time from about 1
h 40 to 40 minutes.

* Makefile (TARBALL_VERSION): New variable.  When defined, do not do
not invoke Git to derive the version string, simply use it.
[RELEASE_TARBALL_FILENAME]: Do not compute prerequisites when
TARBALL_VERSION is defined; assume the tarball is present.
* .gitignore: Ignore .tarball-version.
* Jenkinsfile: (Generate release tarball): Generate a .tarball-version
file, and stash it along the release tarball.  Explicit this should
run on a 'guix' agent.
(Build packages): Forward to any 'linux-builder' agent, clean the
workspace, unstash and extract the tarball and build.

GitLab: jami-packaging#98
Change-Id: I13088b75c9ccd5166662a84b7c5f8d4e8b7b65da

Previously, the only way to ensure a clean release tarball was to
start from scratch, fetching all the contrib sources from the
network (> 1 GiB).  This change leverages the new 'list-tarballs'
targets of the contrib build system to allow reusing the relevant
tarballs from the cache when available, which translates to faster
builds.

It also constructs the pristine source release archive via
git-archive, which guards against including unwanted files.  Since
only the required tarballs are included in the source archive, its
size is reduced from 1.4 GiB to 72 MiB.

GitLab: jami-packaging#55
Change-Id: I4993b269f3b97f6a4b6b8592aa8b5f4eb5448943

Also add packages to .dockerignore, as this output directory can grow
to multiple GiBs.

Change-Id: I17b8b0a6d7be535d888232952c346b45c3224eb1

This hack is no longer necessary.  The Jenkins nodes are running Docker 19.

Change-Id: I8e41e1295a49ebe48b2fca9fa6c91158f49f16c9

Andreas Traczyk authored 4 years ago and Sébastien Blin committed 4 years ago

Replaces the ring-client-windows submodule with jami-client-qt and
adjusts make-ring.py and helper scripts to support both the gtk and
qt client builds for GNU/Linux.

Gitlab: #581
Change-Id: I55c0272cb354c9fa96f3541b6e5a8b7b271f14ba

Fredy Pulido authored 5 years ago and Sébastien Blin committed 5 years ago

Adds:
* Debian 9 armhf
* Debian 9 arm64
* Debian 10 armhf
* Debian 10 arm64
* Raspbian 10 armhf
* The One Click Install (oci) version for all this items

This commit also fix the --generate option in the generated makefile by
scripts/make-packaging-target.py and remove the --architecture option
there because was not used at any part of the script.

Because our builder docker can not docker build with ARM we implemented
a workaround called dirty qemu-static is documented and we have a issue
to sovle it.

The pipeline for packaging-deploy-gnulinux-generic got changed to add
the support for the ARM architecture but the OCI build is not enabled
because the build including the oci takes long (5 hours or plus).

Warning: require companion changes in daemon (topic debian-arm)
to ensure the right compilation flags

Change-Id: I905bbd4660824670d7de836129886f3d7f1dc83b

We can ignore the .docker-image-* files created by
Makefile.packaging.

Change-Id: I14f08efd51f1440749c210708f600a7f3729e065
Reviewed-by: Stepan Salenikovich <stepan.salenikovich@savoirfairelinux.com>

Change-Id: I42f69660cef7b0e004b11a8ab0035721b0a2efe9
Tuleap: #872

This new scripts creates a local repository and deploys it with rsync.
It will be used by Jenkins to deploy packages to dl.ring.cx.

Change-Id: Ib1d9526e88fa15b053ae234f05839e86a3ce263a
Tuleap: #872

This moves the official Debian packaging into ring-project. Jenkins
should now be able to run packaging jobs and publish packages. It
should also make it easy to add a `verify` check on Jenkins to test
packaging patches.

This will make it much easier to work on packaging issues because the
build environment is now reproductible on any machine.

The patch adds Makefile targets to create packages such as:
 - package-all
 - package-<DISTRO>

Builds are all done inside Docker containers and it is possible to
build many at a time with the `package-all` target.

To debug a build, use `package-<DISTRO>-interactive` to obtain a shell
inside a container, ready to launch a build.

Tuleap: #781
Change-Id: Id87a74a6c412ffc5bf82b9562639ce5a9424b06a

This new documentation can be built using `make docs`. It should be
built automatically via a hook on github and published on
https://ring.readthedocs.org.

This allows for much better formatting and is more pleasant to browse
for new contributors. It is possible to build the docs using the
Makefile at the root of the repository.

Change-Id: I664d4662b76c525f2a67eac6266bada3e94aa835
Tuleap: #595

Begin merging all helper scripts into one. Support for other distros
is to be added in the future.

Tuleap: #451
Change-Id: I8ab09502a58ce6a6ccf154be2cf51af401759365