nixpkgs/pkgs/applications/version-management/gitlab/gitlab-workhorse/default.nix

{ stdenv, fetchFromGitLab, git, buildGoModule }:

buildGoModule rec {
  pname = "gitlab-workhorse";

  version = "8.58.0";

  src = fetchFromGitLab {
    owner = "gitlab-org";
    repo = "gitlab-workhorse";
    rev = "v${version}";
    sha256 = "1642vxxqnpccjzfls3vz4l62kvksk6irwv1dhjcxv1cppbr9hz80";
  };

  vendorSha256 = "0vkw12w7vr0g4hf4f0im79y7l36d3ah01n1vl7siy94si47g8ir5";
  buildInputs = [ git ];
  buildFlagsArray = "-ldflags=-X main.Version=${version}";
  doCheck = false;

  meta = with stdenv.lib; {
    homepage = "http://www.gitlab.com/";
    platforms = platforms.linux;
    maintainers = with maintainers; [ fpletz globin talyz ];
    license = licenses.mit;
  };
}
gitlab-workhorse: use buildGoModule 2020-11-26 12:41:37 +00:00			`{ stdenv, fetchFromGitLab, git, buildGoModule }:`
gitlab-workhorse: 6.1.1 -> 7.0.0 2018-10-23 10:23:29 +00:00
gitlab-workhorse: use buildGoModule 2020-11-26 12:41:37 +00:00			`buildGoModule rec {`
treewide: name -> pname (easy cases) (#66585) treewide replacement of stdenv.mkDerivation rec { name = "-${version}"; version = ""; to pname 2019-08-15 12:41:18 +00:00			`pname = "gitlab-workhorse";`
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way all Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598. 2016-01-30 13:47:04 +00:00
gitlab: 13.6.1 -> 13.7.1 (#107558) 2020-12-26 21:06:22 +00:00			`version = "8.58.0";`
gitlab-workhorse: 4.2.0 -> 6.0.0 2018-09-21 07:31:30 +00:00
gitlab-workhorse: rename srcs attribute to src 2018-11-23 13:47:18 +00:00			`src = fetchFromGitLab {`
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way all Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598. 2016-01-30 13:47:04 +00:00			`owner = "gitlab-org";`
			`repo = "gitlab-workhorse";`
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795. 2016-08-03 16:49:18 +00:00			`rev = "v${version}";`
gitlab: 13.6.1 -> 13.7.1 (#107558) 2020-12-26 21:06:22 +00:00			`sha256 = "1642vxxqnpccjzfls3vz4l62kvksk6irwv1dhjcxv1cppbr9hz80";`
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way all Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598. 2016-01-30 13:47:04 +00:00			`};`

gitlab: 13.6.1 -> 13.7.1 (#107558) 2020-12-26 21:06:22 +00:00			`vendorSha256 = "0vkw12w7vr0g4hf4f0im79y7l36d3ah01n1vl7siy94si47g8ir5";`
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work 2019-10-01 13:38:22 +00:00			`buildInputs = [ git ];`
gitlab: 12.3.5 -> 12.4.0 - gitlab-shell no longer requires ruby for anything else than the install script, so the bundlerEnv stuff could be dropped - gitlab-shell and gitlab-workhorse now report their versions correctly 2019-10-23 20:47:24 +00:00			`buildFlagsArray = "-ldflags=-X main.Version=${version}";`
gitlab-workhorse: use buildGoModule 2020-11-26 12:41:37 +00:00			`doCheck = false;`
treewide: Add lots of platforms to packages with no meta Build-tested on x86_64 Linux and on Darwin. 2016-08-02 16:06:29 +00:00
gitlab: 8.11.2 -> 8.12.1 2016-09-27 13:49:21 +00:00			`meta = with stdenv.lib; {`
treewide: Per RFC45, remove all unquoted URLs 2020-04-01 01:11:51 +00:00			`homepage = "http://www.gitlab.com/";`
gitlab: Don't build any gitlab component outside linux For some reason hydra seems to have issues downloading the gitlab-workhorse source on macOS. Since we don't build the rails app for macOS, the other components seem a bit useless there, so we limit them to linux for now. 2019-10-09 13:45:12 +00:00			`platforms = platforms.linux;`
gitlab: Add myself to list of maintainers 2019-10-08 14:37:01 +00:00			`maintainers = with maintainers; [ fpletz globin talyz ];`
gitlab: 8.11.2 -> 8.12.1 2016-09-27 13:49:21 +00:00			`license = licenses.mit;`
treewide: Add lots of platforms to packages with no meta Build-tested on x86_64 Linux and on Darwin. 2016-08-02 16:06:29 +00:00			`};`
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way all Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598. 2016-01-30 13:47:04 +00:00			`}`