summaryrefslogtreecommitdiff
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* Fix `bin/secpick` rainbow gem error, and security branch prefixingMichael Kozono2018-08-151-1/+3
|
* Truncate filenames created by bin/changelog to 140 charactersStan Hu2018-07-111-4/+10
|
* Improve shelling out in bin/changelogJacob Vosmaer (GitLab)2018-06-251-14/+35
|
* Merge branch 'blackst0ne-remove-spinach' into 'master'Rémy Coutable2018-05-151-13/+0
|\ | | | | | | | | | | | | Remove Spinach Closes #23036 See merge request gitlab-org/gitlab-ce!18869
| * Remove bin/spinachblackst0ne2018-05-141-13/+0
| |
* | Update secpickJames Lopez2018-05-141-1/+1
| |
* | Update secpickJames Lopez2018-05-141-1/+1
| |
* | Update secpick to use security branchesJames Lopez2018-05-141-2/+1
|/
* add initial dev task template for working on a security issueJames Lopez2018-04-171-0/+47
|
* [Rails5] Fix running spinach testsblackst0ne2018-04-101-0/+5
| | | | | | | | | | | | | | 1. Add support for `RAILS5=1|true` for the `bin/spinach` command. 2. Synchronize used spinach versions both for rails4 and rails5. For rails5 it was accidently used spinach 0.10.1 instead of 0.8.10. That brought some problems on running spinach tests. Example of failure message: NoMethodError: undefined method `line' for #<Spinach::Scenario:0x000000000c86ba80> Did you mean? lines /builds/gitlab-org/gitlab-ce/features/support/env.rb:52:in `before_scenario_run'
* [Rails5] Allow using `RAILS5` env with rspecblackst0ne-rails5-update-bin-rspecblackst0ne2018-04-031-0/+6
|
* [Rails5] Update files by `rails app:update`blackst0ne-rails5-update-files-by-rails-app-updateblackst0ne2018-03-224-18/+89
|
* Generate EE changelog under ee/changelogs/unreleased/Rémy Coutable2018-02-201-3/+4
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Remove bin/upgrade.rb as we don't seem to refer itLin Jen-Shin2018-01-261-3/+0
|
* We need Rails in order to use Gitlab.config anywayLin Jen-Shin2018-01-261-1/+1
|
* Add bin/profile-url tool and docsadd-profiler-to-applicationSean McGivern2018-01-191-0/+57
|
* Move the circuitbreaker check out in a separate processbvl-circuitbreaker-processBob Van Landuyt2017-12-081-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | Moving the check out of the general requests, makes sure we don't have any slowdown in the regular requests. To keep the process performing this checks small, the check is still performed inside a unicorn. But that is called from a process running on the same server. Because the checks are now done outside normal request, we can have a simpler failure strategy: The check is now performed in the background every `circuitbreaker_check_interval`. Failures are logged in redis. The failures are reset when the check succeeds. Per check we will try `circuitbreaker_access_retries` times within `circuitbreaker_storage_timeout` seconds. When the number of failures exceeds `circuitbreaker_failure_count_threshold`, we will block access to the storage. After `failure_reset_time` of no checks, we will clear the stored failures. This could happen when the process that performs the checks is not running.
* Add Performance category to the changelogZeger-Jan van de Weg2017-10-131-0/+1
| | | | Resolves gitlab-org/gitlab-ce#36417
* Merge branch '21949-add-type-to-changelog' into 'master'Robert Speicher2017-08-101-35/+99
|\ | | | | | | | | | | | | Let's start labeling our CHANGELOG entries Closes #21949 See merge request !11579
| * Let's start labeling our CHANGELOG entriesJacopo2017-07-221-35/+99
| | | | | | | | | | | | Added the type attribute to a CHANGELOG entry. When you create a new entry the software asks for the category of the change and sets the associated type in the file.
* | Don't require stackprof in GemfileRémy Coutable2017-08-091-1/+2
|/ | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Remove bin/ci/upgrade.rb as not working allTakuya Noguchi2017-06-241-3/+0
|
* Add gitaly source installation instructionsJacob Vosmaer2017-03-211-0/+16
|
* remove remaining vestiges of teaspoon test runnerMike Greiling2017-01-101-8/+0
|
* Remove trailing whitespace when generating changelog entrynuke-ugly-spaces-in-changelog-generatorAdam Niedzielski2016-12-091-3/+8
|
* Simplify `branch_name` in bin/changelogrs-simplify-changelog-branch_nameRobert Speicher2016-12-021-1/+1
| | | | | The `--short` option has existed since at least 1.8.1: https://git-scm.com/docs/git-symbolic-ref/1.8.1
* Add StackProf to the Gemfile, along with a utility to get a profile for a specNick Thomas2016-11-291-0/+16
|
* Update help banner for bin/changelogRobert Speicher2016-11-031-1/+1
| | | | [ci skip]
* Add a `--force` option to bin/changelogrs-changelog-forceRobert Speicher2016-11-021-1/+7
|
* Add specs for ChangelogOptionParser in bin/changelogrs-bin-changelogRobert Speicher2016-10-311-1/+2
|
* Add a bin/changelog scriptRobert Speicher2016-10-311-0/+163
|
* Re-organize queues to use for Sidekiqseparate-sidekiq-queuesYorick Peterse2016-10-211-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370
* Use ENABLE_SPRING to use it by defaultmake-spring-optionalKamil Trzcinski2016-06-171-1/+1
|
* Use 'exec' in Unicorn and Sidekiq launch scriptsJacob Vosmaer2016-04-282-3/+3
| | | | | | | | | | | | | | | | When running Unicorn or Sidekiq in the foreground this change removes an intermediate /bin/sh process. This makes process supervision in the GitLab Development Kit more reliable. This change does not affect Omnibus-GitLab (because there we do not use these launch scripts). Installations from source do use the launch scripts but for the standard GitLab init script this change will not make a difference. Custom installations using Upstart or Systemd may be affected however, because under certain configurations these systems count exactly how many forks happen during process startup, and we are reducing that number by one here.
* Re-generate Spring binstubs for updated version of SpringRobert Speicher2016-04-226-10/+30
| | | | | | | Prevents output like this: Array values in the parameter are deprecated. Please use a String or nil. An Array was passed in from bin/rspec:3:in `load'
* Use rake db:reset instead of db:setupYorick Peterse2016-04-141-1/+1
| | | | | | | | | | | | Using db:reset ensures existing tables are first dropped. This in turn ensures that we can drop tables regardless of any foreign key constraints. While CE currently doesn't have any foreign keys EE defines the following relation: remote_mirrors.project_id -> projects.id MySQL will complain whenever you try to drop the "projects" table first even when using "DROP TABLE ... CASCADE".
* Direct sidekiq boot output to log filesimplify-procfileJacob Vosmaer2016-01-151-1/+1
| | | | This behavior got lost in the previous commit.
* Improve bin/ launchersJacob Vosmaer2016-01-142-3/+15
|
* Add 'resume' capability to parallel-rsync-repossync-all-reposJacob Vosmaer2015-12-081-14/+29
|
* Merge branch 'master' into sync-all-reposJacob Vosmaer2015-12-086-12/+34
|\
| * Fix mailer queuefix_mailer_queueValery Sizov2015-12-031-1/+1
| |
| * Rails update to 4.2.4Valery Sizov2015-11-255-11/+33
| |
* | Add RSYNC variable to parallel-rsync-reposJacob Vosmaer2015-10-051-1/+14
| |
* | Add parallel-rsync-repos script and start docsJacob Vosmaer2015-09-251-0/+26
|/
* Merge branch 'master' into ci-and-ce-sitting-in-a-tree-k-i-s-s-i-n-gDmitriy Zaporozhets2015-09-092-3/+34
|\
| * Properly daemonize the mail_room processimprove-mail_room-wrapperJacob Vosmaer2015-08-272-3/+34
| | | | | | | | | | | | | | | | | | The old invocation only worked by accident because we have a '&' somewhere in the init script for expediency. When ran from a terminal, the mail_room daemon process ended up in the session of the terminal. This commit adds a small wrapper that tries to do the textbook daemonization steps (double fork, setsid etc.) while also taking care that the pidfile is written before the 'start' process exits.
* | Groundwork for merging CI into CEDouwe Maan2015-08-252-1/+4
|/
* Fix bin/mail_room.Douwe Maan2015-08-191-8/+9
|
* Update init scripts.Douwe Maan2015-08-192-1/+52
|
* Remove GuardRobert Speicher2015-06-031-16/+0
| | | | None of the GitLab B.V. developers were using it.