Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.bio.base bob.bio.base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.bio.basebob.bio.base
  • Merge requests
  • !36

Suggests configuration file should be the default "way" with `verify.py`

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged André Anjos requested to merge config_file into master Sep 09, 2016
  • Overview 25
  • Commits 6
  • Pipelines 1
  • Changes 10

In this merge request, the idea is we emphasize people should rather use configuration files with verify.py. The change is minor, but allows users to run the script issuing:

$ ./bin/verify.py -vv <my-config>

I mark it as a work-in-progress, because I still wanted to have <my-config> to optionally be a resource. @mguenther: could you please make so? I'm not sure I'm capable of doing this with ruining something else. This will allow us to distribute baselines inside packages, w/o requiring users to know where they are installed.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: config_file