Reproducible builds

Explore what is still missing.

Any help is appreciated

Note: not urgent

reference https://git.jami.net/savoirfairelinux/ring-project/issues/613

Thx I didn't found it, little typo in the title

changed title from Reproductible builds to Reproducible builds

added to epic &1 (closed)

I think we could just launch the same job twice and check if the packages we got are the same (it supposed to be because is an automated process) after that we could see what's next

As reference the definition: https://reproducible-builds.org/docs/definition/

It looks that out of the box Jenkins can not rebuild but we could install this plugin:

https://wiki.jenkins.io/display/JENKINS/Rebuild+Plugin

@sblin can I install it or does I require authorization from anyone?

added CI / CD label

Hmm just retrigger the build, this will generate new binaries?

A priori, if it remember the input values yes, if not we will have to dig in.

retrigger is used to redo the exact same build

mentioned in issue #76 (closed)

For one thing, at least the Qt client build captures the build date. The date would need to be set to something static, epoch 1 for example. But my opinion is that capturing the source revision that got used as input is more pertinent (what we already have as the RELEASE_VERSION variable in the packaging (ring-project repo) Makefile).

closed

added packaging label