Move to a monorepo (jungle + bscpkgs) #149

New Issue

rarias · 2025-07-22T16:37:44+02:00

rarias commented

2025-07-22 16:37:44 +02:00

Merge bscpkgs+jungle into a single git repository at jungle, so we have just one overlay for packages and the nixos configuration for the machines in the same place.

There are some problems with the current design of two repositories, one for packages (bscpkgs) and another for configuration (jungle):

As we update bscpkgs, we need to create a corresponding commit in jungle to pick the changes.
We need two additional overlays, one for machine agnostic packages (bscpkgs) and then another for the jungle cluster. This causes packages directly build from bscpkgs to be unable to run at jungle due to MPI being always broken and extra rebuilds.
No need to evaluate the configuration of a machine to pick the resulting package set. We can directly inject the "merged" package overlay into nixpkgs so generate a general package set, so we can use simply jungle#foo from any machine.
git diff will also show changes between packages which may be helpful when identifying causes of problems.

We should keep the git history, but that can be done with a merge commit.

Merge bscpkgs+jungle into a single git repository at jungle, so we have just one overlay for packages and the nixos configuration for the machines in the same place. There are some problems with the current design of two repositories, one for packages (bscpkgs) and another for configuration (jungle): - As we update bscpkgs, we need to create a corresponding commit in jungle to pick the changes. - We need two additional overlays, one for machine agnostic packages (bscpkgs) and then another for the jungle cluster. This causes packages directly build from bscpkgs to be unable to run at jungle due to MPI being always broken and extra rebuilds. - No need to evaluate the configuration of a machine to pick the resulting package set. We can directly inject the "merged" package overlay into nixpkgs so generate a general package set, so we can use simply jungle#foo from any machine. - `git diff` will also show changes between packages which may be helpful when identifying causes of problems. We should keep the git history, but that can be done with a merge commit.

rarias self-assigned this 2025-07-22 16:37:49 +02:00

rarias added the

nix

label 2025-07-22 16:37:53 +02:00

rarias added a new dependency 2025-10-01 16:04:45 +02:00

#171 Move big blobs outside repository

rarias commented

2025-10-10 12:21:45 +02:00

Fixed in #189

Fixed in https://jungle.bsc.es/git/rarias/jungle/pulls/189

rarias closed this issue

2025-10-10 12:21:51 +02:00