Skip to content

Conversation

@HemanthMudalaiah
Copy link
Contributor

No description provided.

Hemant Gowda added 4 commits November 2, 2016 11:14
* Tests for analysed modules collection initialize.
* Tests for the where method in analysed collection module
* Documenting how to integrate with jenkins.
* Checking if the gitlab configuration and jenkins threshold are set.
Editing Description,Summary in rubycritic_extension.gemspec
Alternatively if you're using GitLab you can pass `pull_request_id` as the third argument which will post a comment to the respective pull_request:

```bash
$ rubycritic_extension -b base_branch,feature_branch,pull_request_id

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parameters should be space separated not comma separated (like unix commands)
eg.

rubycritic-ext -b base_branch feature_branch -p pull_request_id

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On second thought -b and -p can be optional, since we can assume the extension does only two things -

  1. runs rubycritic on two branches - hence first 2 args are branch names
  2. optionally posts to PR - hence third arg optional pull_request_id


For posting comment on a pull_request in GitLab below are the configuration. Create a file in config directory `rubycritic_app_settings.yml` with following details

```ruby

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants