delta/gitlab/gitlab-ce.git/scripts, branch sh-optimize-commit-stats

Merge branch 'dz-add-sast' into 'master'

2017-12-23T14:19:51+00:00

Remove security checks from static analysis and add sast job

See merge request gitlab-org/gitlab-ce!16113

Remove security checks from static analysis and add sast job

2017-12-23T14:18:39+00:00

Return exception messages in scripts/lint-changelog-yaml

2017-12-23T01:53:13+00:00

Preserve gem path so that we use the same gems

2017-12-19T09:41:59+00:00

Without this patch, I would end up with:

```
An error occurred in a `before(:suite)` hook.
Failure/Error: raise "could not connect to gitaly at #{socket.inspect} after #{sleep_time} seconds"

RuntimeError:
  could not connect to gitaly at "tmp/tests/gitaly/gitaly.socket" after 10 seconds
```

Digging into it, it's because `scripts/gitaly-test-spawn` could not
spawn the process, because it cannot find the installed gems.

I personally installed all my gems under $HOME, namely with:

* `gem install rake --user-install` or:
* `bundle install --path ~/.gem`

The gems would be installed to `~/.gem/ruby/2.4.0/gems`, where
the version is Ruby ABI version.

Now we're changing $HOME, making RubyGems think that the gems
would be installed to `tmp/tests/ruby/2.4.0/gems` which is
apparently not the case.

In order to workaround this, we could preserve $GEM_PATH
populated by RubyGems, ignoring the default path based on $HOME.

Make rubocop happy

2017-12-15T05:59:52+00:00

Use guard clause

2017-12-15T05:59:52+00:00

Improve language

2017-12-15T05:59:52+00:00

Prettify

2017-12-15T05:59:52+00:00

Use temp branch

2017-12-15T05:59:52+00:00

Pass info about who started the job and which job triggered it

2017-12-15T05:59:52+00:00