[jitsi-dev] migrating debian repositories (new ci machine for devs)


#1

Hey devs and Ingo,

I'm almost done with the new ci machine. I've created a package
named jitsi-archive-keyring which installs the new stable debian repo and
its public key. These days I will start making all jitsi-meet related
packages depending on it and will push one version in the current repo and
will disable their job on the old machine and enable the job on the new
machine (where I will remove that dependency as this key and list
installation is currently not part of any project except the desktop
client).

The deb package jitsi-archive-keyring is already pushed to current stable
and nightly repos.

This way a last package will go to the old repo, and new package will go to
the new one. The testing and stable will be empty, as these will be filled
automatically for jitsi-meet related packages.

We will setup the jobs on the new machine so we can have the release plan
for the desktop. Job that will move the new stable to the new place
(promote the build from unstable as it is currently available as a job).
Any suggestions are welcome.
The key is also available here and in the keyservers:
https://download.jitsi.org/jitsi-key.gpg.key
The new repos will be in the form of:
deb https://download.jitsi.org stable/
deb https://download.jitsi.org testing/
deb https://download.jitsi.org unstable/

Regards
damencho


#2

Hi all,

Everything is moved to the new machine and the repos are migrated.
I've edited some of the pages to reflect the changes. Still haven't
updated those for the stable repo.
The stable repo is empty, will update it with latest meet.jit.si
versions, and will update the pages once we push and a new jitsi
desktop client release.
I think we should switch off linux bin package and generic installer,
they are using izpack and bin is embedding java 1.6. I think, nobody
is testing/using them so it is ok to stop them, WDYT?

Regards
damencho

ยทยทยท

On Mon, Jun 27, 2016 at 8:35 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hey devs and Ingo,

I'm almost done with the new ci machine. I've created a package named
jitsi-archive-keyring which installs the new stable debian repo and its
public key. These days I will start making all jitsi-meet related packages
depending on it and will push one version in the current repo and will
disable their job on the old machine and enable the job on the new machine
(where I will remove that dependency as this key and list installation is
currently not part of any project except the desktop client).

The deb package jitsi-archive-keyring is already pushed to current stable
and nightly repos.

This way a last package will go to the old repo, and new package will go to
the new one. The testing and stable will be empty, as these will be filled
automatically for jitsi-meet related packages.

We will setup the jobs on the new machine so we can have the release plan
for the desktop. Job that will move the new stable to the new place (promote
the build from unstable as it is currently available as a job).
Any suggestions are welcome.
The key is also available here and in the keyservers:
https://download.jitsi.org/jitsi-key.gpg.key
The new repos will be in the form of:
deb https://download.jitsi.org stable/
deb https://download.jitsi.org testing/
deb https://download.jitsi.org unstable/

Regards
damencho