Folks: I'm an organizer of the Tahoe-LAFS project (http://tahoe-lafs.org ). The Nix project maintains a NixPkg of Tahoe-LAFS and a Hydra test builder for it:
http://hydra.nixos.org/job/nixpkgs/trunk/tahoelafs The Tahoe-LAFS developers also maintain a test builder for NixOS: http://tahoe-lafs.org/buildbot/builders/Ludo%20NixOS-amd64 (The buildslave is contributed to Tahoe-LAFS by Ludovic Courtès.) These two automated test systems are complementary -- both are needed! The builder operated by Nix developers lets them be sure that the latest release of Tahoe-LAFS, as patched by the Nix developers, integrates with the other Nix components that it depends on and that depend on it. The builder operated by Tahoe-LAFS developers lets them be sure that each successive patch that they commit doesn't break the current head of Tahoe-LAFS on Nix. We use this as part of our workflow: a platform is defined as a "Supported Platform" if we have a Buildbot for it and we can keep that buildbot green on every darcs commit. I'm writing to ask if you could link to the Tahoe-LAFS builders from the Nix Hydra builder and from the Nix package page. I've added a link to the Hydra builder from the Tahoe-LAFS buildbot page: http://tahoe-lafs.org/buildbot And I asked Ludovic to add a link to the Hydra builder from his particular buildslave's page: http://tahoe-lafs.org/buildbot/builders/Ludo%20NixOS-amd64 To link to the Tahoe-LAFS buildbot page, just link to: http://tahoe-lafs.org/buildbot Thanks! Regards, Zooko _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
