GitLab Development Kit merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests2019-09-20T00:07:53Zhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/237Added webpack to Procfile2019-09-20T00:07:53ZPhil Hughesme@iamphill.comAdded webpack to ProcfileAdds webpack dev server command to `Procfile`Adds webpack dev server command to `Procfile`Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/309GDK on minikube2019-09-19T23:56:11ZGrzegorz BizonGDK on minikube## How to use it?
1. Start minikube `minikube start`
1. Create pod `kubectl create -f gdkube.yml`
1. See a starting pod `kubectl get pods`
1. Wait for GDK to start `kubectl logs -f gdk-[pod-id]`
1. Get the URL to GDK `minikube se...## How to use it?
1. Start minikube `minikube start`
1. Create pod `kubectl create -f gdkube.yml`
1. See a starting pod `kubectl get pods`
1. Wait for GDK to start `kubectl logs -f gdk-[pod-id]`
1. Get the URL to GDK `minikube service gdk --url`
1. Open in the browser
![gdk_minikube](/uploads/ca1ba5e6a3b89534c57ef4d220b0a801/gdk_minikube.png)
Step 1 of #243username-removed-128633username-removed-128633https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/357Specify in GDK directory2017-10-07T06:04:24Zusername-removed-1144264Specify in GDK directoryBecause never having messed with gitlab-docs before,
I misinterpreted this line to mean "Go and clone
https://gitlab.com/gitlab-docs, then run this make
command in it"Because never having messed with gitlab-docs before,
I misinterpreted this line to mean "Go and clone
https://gitlab.com/gitlab-docs, then run this make
command in it"Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/355Move vagrant directory2017-10-04T18:50:16ZMatija Čupićmatteeyah@gmail.comMove vagrant directoryMoves the vagrant build directory to `./vagrant` instead of `./docker` to avoid any confusion.Moves the vagrant build directory to `./vagrant` instead of `./docker` to avoid any confusion.Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/354Fix doc preview typo2017-10-02T20:00:07ZJames RamsayFix doc preview typoInstructions to generate HTML files incorrectly included `rake` in the command causing it to fail.Instructions to generate HTML files incorrectly included `rake` in the command causing it to fail.10.1Achilleas PipinellisAchilleas Pipinellishttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/352Improve the troubleshooting instructions to install charlock_holmes2017-10-01T17:57:13Zusername-removed-128633Improve the troubleshooting instructions to install charlock_holmesSome project (e.g. Gitaly) set the `path` option, which seems to force the
`disable_shared_gems` option. Thus it's better to set the flag globally.Some project (e.g. Gitaly) set the `path` option, which seems to force the
`disable_shared_gems` option. Thus it's better to set the flag globally.Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/351Make sure gitlab-shell is updated first to avoid the warnings2017-09-29T09:51:30ZAchilleas PipinellisMake sure gitlab-shell is updated first to avoid the warningsTo avoid the warning that gilab-shell is an old version and needs to be updated, make sure we update it first.
Just a minor nitpick, since it's updated either way :)To avoid the warning that gilab-shell is an old version and needs to be updated, make sure we update it first.
Just a minor nitpick, since it's updated either way :)Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/347Use make to install gitaly2017-09-28T16:54:19ZAndrew Newdigateandrew@gitlab.comUse make to install gitalySee https://gitlab.com/gitlab-org/gitlab-development-kit/issues/282 and https://gitlab.com/gitlab-org/gitaly/merge_requests/372See https://gitlab.com/gitlab-org/gitlab-development-kit/issues/282 and https://gitlab.com/gitlab-org/gitaly/merge_requests/372Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/350Add a troubleshooting item to install charlock_holmes 0.7.3 on macOS Sierra2017-09-26T12:50:26Zusername-removed-128633Add a troubleshooting item to install charlock_holmes 0.7.3 on macOS SierraCloses #286Closes #286Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/349Lock Rubocop version to 0.49.12017-09-25T11:45:50ZGrzegorz BizonLock Rubocop version to 0.49.1## Description
Fix CI pipeline by locking Rubocop to 0.49.1 version
/cc @jacobvosmaer-gitlab## Description
Fix CI pipeline by locking Rubocop to 0.49.1 version
/cc @jacobvosmaer-gitlab10.1Jacob Vosmaer (GitLab)Jacob Vosmaer (GitLab)https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/335Adds gdk diff-config command to preview config changes2017-09-22T12:08:24ZJames EJAdds gdk diff-config command to preview config changes# What
Adds `gdk diff-config` command to preview a diff of changes which will be made to `gitlab/config/gitlab.yml` and other config files.
# Why
I want to be able to see what changes will be made to `gitlab.yml` before overwrit...# What
Adds `gdk diff-config` command to preview a diff of changes which will be made to `gitlab/config/gitlab.yml` and other config files.
# Why
I want to be able to see what changes will be made to `gitlab.yml` before overwriting it. Especially when working on a feature which requires me to change things. Similarly I keep a line commented out in Procfile and don't want to unnecessarily reset that.
# How
1. Creates a temporary backup at file.unchanged
1. Runs `Make` to update the config file
1. Runs `git diff --color --no-index file file.unchanged`
1. Restores file
After all files have been updated the `Make` output is printed to `stderr`, followed by the diff output to `stdout`. This allows `gdk diff-config | less` to show just the relevant output.
~~Works by creating a temporary blob with `git hash-object -w` for each file, making changes, comparing and finally restoring the original file.~~
~~The comparison step works by using `git mktree` to create a fake tree object for the config files, another after making changes, and using `git diff old_tree new_tree` to compare the two.~~
# Screenshot
After the following `gdk diff-config` I can update a single file with `make gitlab/config/database.yml` instead of overwriting my changes to two other files at the same time with `gdk reconfigure`:
![diff from 'gdk diff-config'](/uploads/98e51cfd49154123881e3730992359ec/Screen_Shot_2017-08-28_at_19.20.50__50_.png)
10.1Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/343Log to files not stdout during bootstrap2017-09-19T08:48:58ZJacob Vosmaer (GitLab)Log to files not stdout during bootstrapFixes GDK builds that fail due to too much gitaly log ouput.Fixes GDK builds that fail due to too much gitaly log ouput.Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/345Fix syntax EOT content in Vagrantfile2017-09-18T17:50:00Zusername-removed-83964Fix syntax EOT content in Vagrantfilehttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/346Remove extra white space2017-09-18T05:31:34Zusername-removed-83964Remove extra white spacehttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/344Fix gdk update double exec2017-09-15T10:52:47ZAlessio CaiazzaFix gdk update double execThe second exec in `gdk update` will never be executedThe second exec in `gdk update` will never be executedGrzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/342Have GDK pull itself on 'gdk update'2017-09-15T09:26:29Zusername-removed-487110Have GDK pull itself on 'gdk update'Closes #246Closes #246Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/341Fix large-db-ldif undefined method error2017-09-12T16:30:07ZJames LopezFix large-db-ldif undefined method errorJacob Vosmaer (GitLab)Jacob Vosmaer (GitLab)https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/318Add rubocop to the CI suite2017-09-12T16:30:05ZMatija Čupićmatteeyah@gmail.comAdd rubocop to the CI suiteAdds rubocop to the CI suite and fixes various offenses.Adds rubocop to the CI suite and fixes various offenses.Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/340Checkout locales/*/gitlab.po after compiling2017-09-12T06:45:13ZBob Van Landuyt :neckbeard:Checkout locales/*/gitlab.po after compilingCompiling touches the timestamp of each file and adds `#fuzzy` &
`#obsolete` tags to the strings. These can safely be discarded. The
changes that were part of `gitlab.po` should already be stashed from
the `gitlab/.git/pull` task.
This ...Compiling touches the timestamp of each file and adds `#fuzzy` &
`#obsolete` tags to the strings. These can safely be discarded. The
changes that were part of `gitlab.po` should already be stashed from
the `gitlab/.git/pull` task.
This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/3352110.0Grzegorz BizonGrzegorz Bizonhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/329Add basic support for running the docs site locally2017-09-07T17:10:19ZAchilleas PipinellisAdd basic support for running the docs site locallyGrzegorz BizonGrzegorz Bizon