@kquick this is cool, thank you.

I am confused about this PR. Isn’t this functionality already in hyda?

@nomeata Not as far as I could tell... do you know of a URL that provides this?

Oh, I see, this is output paths, not declared built artifacts like

Nevermind then.

I tried this PR but I get the following:

When requesting the latest-outpath URL:

https://my.hydra.com//job/my-project/my-jobset/my-job/latest-outpath

it redirects me to:

https://my.hydra.com//nix/store/n3zsgkc28nw1b8bddinww50d9bb55kcp-my-output

which leads to a 404 because I guess hydra doesn't know how to serve /nix/store/... paths.

Do I need to setup something extra to serve /nix/store/... paths?

Yes, thanks for the reminder on this, Bas.

I'm using services.httpd to proxy for hydra on the same machine as well as provide paths for haddock docs and hoogle services generated by hydra (and thus this patch to allow serving of the "latest"). To allow the above redirection, I have the following clause:

services.httpd = {
    servedDirs = [
        { dir = "/nix/store";
          urlPath = "/nix/store/";
        };
    ];
    ...
};

Although it should be possible to serve the file directly via hydra, I'm not sure that's a good idea because it essentially bypasses a lot of the controls that a webserver proxy can provide.