cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/pkgs/applications/version-management/gitlab/gitlab-workhorse/default.nix

27 lines
672 B
Nix
Raw Normal View History

treewide: remove stdenv where not needed
2021-01-25 09:26:54 +01:00
{ lib, fetchFromGitLab, git, buildGoModule }:
gitlab-workhorse: 6.1.1 -> 7.0.0
2018-10-23 12:23:29 +02:00
gitlab-workhorse: use buildGoModule
2020-11-26 13:41:37 +01:00
buildGoModule rec {
treewide: name -> pname (easy cases) (#66585) treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
2019-08-15 14:41:18 +02: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 14:47:04 +01:00
gitlab: 13.7.1 -> 13.7.4 (#108720)
2021-01-29 21:13:59 +01:00
version = "8.58.2";
gitlab-workhorse: 4.2.0 -> 6.0.0
2018-09-21 09:31:30 +02:00
gitlab-workhorse: rename srcs attribute to src
2018-11-23 14:47:18 +01: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 14:47:04 +01:00
owner = "gitlab-org";
repo = "gitlab-workhorse";
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 18:49:18 +02:00
rev = "v${version}";
gitlab: 13.7.1 -> 13.7.4 (#108720)
2021-01-29 21:13:59 +01:00
sha256 = "1ks8rla6hm618dxhr41x1ckzk3jxv0f7vl2547f7f1fl3zqna1zp";
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 14:47:04 +01:00
};
gitlab: 13.6.1 -> 13.7.1 (#107558)
2020-12-26 22:06:22 +01: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 15:38:22 +02: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 22:47:24 +02:00
buildFlagsArray = "-ldflags=-X main.Version=${version}";
gitlab-workhorse: use buildGoModule
2020-11-26 13:41:37 +01: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 18:06:29 +02:00
treewide: with stdenv.lib; in meta -> with lib; Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2021-01-11 08:54:33 +01:00
meta = with lib; {
treewide: Per RFC45, remove all unquoted URLs
2020-04-01 03:11:51 +02: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 15:45:12 +02:00
platforms = platforms.linux;
gitlab: Add myself to list of maintainers
2019-10-08 16:37:01 +02:00
maintainers = with maintainers; [ fpletz globin talyz ];
gitlab: 8.11.2 -> 8.12.1
2016-09-27 15:49:21 +02: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 18:06:29 +02: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 14:47:04 +01:00
}
Reference in a new issue Copy permalink