GitLab Development Kit merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests2014-10-17T09:23:39Zhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/24Feature openldap2014-10-17T09:23:39Zusername-removed-10238Feature openldapThis introduces an openLDAP instance with two databases. Just alter the base and you faked an other database instance.This introduces an openLDAP instance with two databases. Just alter the base and you faked an other database instance.username-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/25Open ldap in readme2014-10-20T12:30:16ZSid SijbrandijOpen ldap in readmeSid SijbrandijSid Sijbrandijhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/26Compile openldap2014-10-20T16:57:22Zusername-removed-5302Compile openldapusername-removed-444username-removed-444https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/27Vagrantfile warning2014-11-27T17:47:52ZSid SijbrandijVagrantfile warningusername-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/28Added explanation how to run the tests2014-12-01T09:03:41Zusername-removed-1164jeroenvanbaarsen@gmail.comAdded explanation how to run the tests**What does this MR do?**
It explains how to run the tests, since `rspec .` will just break everything!
**What issues does it fix?**
#27**What does this MR do?**
It explains how to run the tests, since `rspec .` will just break everything!
**What issues does it fix?**
#27https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/29[wip] Gitlab ci support2015-01-08T10:36:49Zusername-removed-1164jeroenvanbaarsen@gmail.com[wip] Gitlab ci supportThis is the wip PR for GitLab CI support in the Development Kit.
After this is merged you get the following extra's:
1. Running `make` also install GitLab ci in `gitlab-ci` subdirectory
2. Running `make update` also updates GitLab...This is the wip PR for GitLab CI support in the Development Kit.
After this is merged you get the following extra's:
1. Running `make` also install GitLab ci in `gitlab-ci` subdirectory
2. Running `make update` also updates GitLab ci
3. Running `make update-gitlab-ci` updates only GitLab ci
4. Running `make gitlab-ci-clean` will remove GitLab ci from your system
5. GitLab and GitLab CI both use the same postgresql database that can be start from the root with `foreman start`
6. You can run GitLab and GitLab ci next to each other since GitLab ci is running on port 5000.
7. Out of the box GitLab ci is configured to run with GitLab from this GDK
There is a big change I forgot something important, please let me know so I can fix it :)
Depends on: https://gitlab.com/gitlab-org/gitlab-ci/merge_requests/16https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/30Pre install list2014-12-16T09:45:45Zusername-removed-55219Pre install list@sytses Made the pre-install list specifications more obvious@sytses Made the pre-install list specifications more obvioushttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/31Dev docs in gdk2016-09-21T19:35:56ZSid SijbrandijDev docs in gdkAlso see https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/1331Also see https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/1331username-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/32Feature/29 cent os readme fix2015-01-23T09:37:06Zusername-removed-31083Feature/29 cent os readme fixI encountered problems running spinach tests on CentOS. I found out a git version *in*-compatable with Gitlab tests is the only binary available for centOS. I documented in the Readme my installation setup for CentOS, and also included...I encountered problems running spinach tests on CentOS. I found out a git version *in*-compatable with Gitlab tests is the only binary available for centOS. I documented in the Readme my installation setup for CentOS, and also included the Git note on how to get around that by installing from source over the top of existing binary. The git version is *Nearly* the same so it is very easy to overlook.
#29
https://gitlab.com/gitlab-org/gitlab-development-kit/issues/29
I tried to follow the contributing guidelines from main gitlab the best I could.Achilleas PipinellisAchilleas Pipinellishttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/33Gitlab Runner support2015-01-08T10:37:50Zusername-removed-444Gitlab Runner supportShould be merged after !29Should be merged after !29https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/34Add nodejs as a development dependency2015-01-11T01:39:27Zusername-removed-5302Add nodejs as a development dependencyRelated to gitlab-org/gitlab-ce!262Related to gitlab-org/gitlab-ce!262username-removed-444username-removed-444https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/35Add key require rvm2015-01-12T11:06:12Zusername-removed-83964Add key require rvmAdd gpg command in Vagrantfile for download key required on rvm
Issue #19Add gpg command in Vagrantfile for download key required on rvm
Issue #19https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/36These are dependencies too2015-01-13T10:36:09ZSid SijbrandijThese are dependencies toousername-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/37Add kerberos package to ubuntu installation instructions2015-01-16T22:57:22Zusername-removed-444Add kerberos package to ubuntu installation instructionsStack trace of error from bundle install
```
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/home/dzaporozhets/.rvm/rubies/ruby-2.1.5/bin/ruby -r ./siteconf20150116-17237-rl0g9.rb extconf.rb
checking for ...Stack trace of error from bundle install
```
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/home/dzaporozhets/.rvm/rubies/ruby-2.1.5/bin/ruby -r ./siteconf20150116-17237-rl0g9.rb extconf.rb
checking for main() in -lc... yes
checking for krb5_init_context() in -lkrb5... no
creating Makefile
make "DESTDIR=" clean
make "DESTDIR="
compiling ruby_krb5_auth.c
ruby_krb5_auth.c:24:18: fatal error: krb5.h: No such file or directory
#include <krb5.h>
^
compilation terminated.
make: *** [ruby_krb5_auth.o] Error 1
make failed, exit code 2
Gem files will remain installed in /home/dzaporozhets/.rvm/gems/ruby-2.1.5/gems/timfel-krb5-auth-0.8 for inspection.
Results logged to /home/dzaporozhets/.rvm/gems/ruby-2.1.5/extensions/x86_64-linux/2.1.0/timfel-krb5-auth-0.8/gem_make.out
An error occurred while installing timfel-krb5-auth (0.8), and Bundler cannot continue.
Make sure that `gem install timfel-krb5-auth -v '0.8'` succeeds before bundling.
```username-removed-444username-removed-444https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/38Apt update2015-01-21T11:07:31Zusername-removed-83964Apt updateIf the repository have updates the packages to install get a 404 not foundIf the repository have updates the packages to install get a 404 not foundusername-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/39Add libkrb5-dev dep2015-01-29T09:05:43ZDrew BlessingAdd libkrb5-dev depVagrant fails because `libkrb5-dev` isn't installed. Add the package to the `apt-get` install line.Vagrant fails because `libkrb5-dev` isn't installed. Add the package to the `apt-get` install line.https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/40More details about git and directories2015-02-05T08:59:01ZSid SijbrandijMore details about git and directoriesusername-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/41Add Debian install section in README2015-02-12T17:28:36Zusername-removed-444Add Debian install section in READMETested on Debian 8 beta Tested on Debian 8 beta username-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/42Change 'that' to 'than'. Yeah...2015-02-14T22:56:50Zusername-removed-70524Change 'that' to 'than'. Yeah...![Screen Shot 2015-02-14 at 13.56.29](https://gitlab.com/uploads/_ralph/gitlab-development-kit/edf23842f7/Screen_Shot_2015-02-14_at_13.56.29.png)
And with this, a huge step forward in the comprehensibility of the README has been taken...![Screen Shot 2015-02-14 at 13.56.29](https://gitlab.com/uploads/_ralph/gitlab-development-kit/edf23842f7/Screen_Shot_2015-02-14_at_13.56.29.png)
And with this, a huge step forward in the comprehensibility of the README has been taken, I'm sure you'll all agree. (I'm sure there are some useful contributions coming down the line, honest).https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/43Updated readme with warning about system ruby2015-02-21T19:50:09ZPatricio CanoUpdated readme with warning about system rubySid SijbrandijSid Sijbrandij