Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Dec 9, 2012
  1. @marcoVermeulen
  2. @marcoVermeulen
  3. @marcoVermeulen
  4. @marcoVermeulen
Commits on Dec 7, 2012
  1. @marcoVermeulen
  2. @pledbrook
  3. @marcoVermeulen

    Upgrade to 0.9.0

    marcoVermeulen authored
  4. @marcoVermeulen
  5. @marcoVermeulen
  6. @marcoVermeulen
  7. @marcoVermeulen
  8. @marcoVermeulen
  9. @marcoVermeulen
  10. @marcoVermeulen
  11. @marcoVermeulen
  12. @marcoVermeulen
  13. @marcoVermeulen
  14. @pledbrook @marcoVermeulen

    Fix intermittent test errors with broadcast msg.

    pledbrook authored marcoVermeulen committed
    A bash prompt often crept into the output for one of the broadcast feature
    tests, which then cause that test to fail. I have set the prompt to an empty
    string, hence eliminating that source of problems :)
  15. @pledbrook @marcoVermeulen

    Change path and name of gvm user config file.

    pledbrook authored marcoVermeulen committed
    This change also exposed a problem in the Cucumber tests with isolated mode,
    so I have fixed the tests to handle separation of currently active version
    and the default version of a candidate.
  16. @pledbrook @marcoVermeulen

    Rename 'set-default' command to 'default'.

    pledbrook authored marcoVermeulen committed
  17. @pledbrook @marcoVermeulen

    Fix cucumber tests for per-shell versions feature.

    pledbrook authored marcoVermeulen committed
    Since gvm is now a function that is sourced into the current shell, the old
    Cucumber tests no longer work as they try to execute 'gvm' as a process. This
    fix instead launches an external bash process for each scenario and pipes the
    required commands to it.
    
    A lot of the magic happens in the new BashEnv class which handles the piping
    of commands and also managing the output correctly.
    
    This is further work on issue #52.
  18. @pledbrook @marcoVermeulen

    Add initial support for per-shell versions: issue #52

    pledbrook authored marcoVermeulen committed
    In order to make version changes only apply to the current shell, I had to make
    the `gvm-init.sh` script source the `gvm` one. This meant replacing all `exit`
    calls in the latter with `return`s and changing the name of the functions by
    prefixing them with `__gvmtool_` (to avoid the functions appearing in bash
    auto-completion by accident).
    
    Note that this feature is not enabled by default. The user must create a
    ~/.gvm/gvmconfig file and add 'isolated_mode=1' to it in order to enable the
    feature.
    
    To help with some of the internals, `gvm-init.sh` now exports the `GVM_DIR`
    variable if it hasn't already been set by the user. This makes it available to
    `gvm` and any plugin scripts that get executed in sub-shells.
    
    `gvm-init.sh` also sources any scripts in `$GVM_DIR/ext` whose name begins
    with `sourced-`, allowing users to extend the system with extra functionality
    implemented via bash functions. They are required to name their functions with
    `__gvmtool_<command>`. Plugins can also be implemented as straight
    `gvm-<command>.sh` scripts, but these manually need to source the `gvm` script
    if they want access to its internal functions, such as `__gvmtool_help`.
    
    In this 'isolated mode', users need some way of setting the default version of
    candidates for new shells. So I have also added a new 'set-default' command
    that updates the 'current' symlink to the specified candidate version.
Commits on Dec 6, 2012
  1. @marcoVermeulen
  2. @marcoVermeulen

    Revert "Move mongo js for release script to pick up."

    marcoVermeulen authored
    This reverts commit e7858acb71b0d338a47203353189abae299f5b6f.
  3. @marcoVermeulen
Commits on Dec 5, 2012
  1. @marcoVermeulen
  2. @marcoVermeulen
  3. @marcoVermeulen
  4. @marcoVermeulen
  5. @marcoVermeulen
  6. @marcoVermeulen
  7. @marcoVermeulen
  8. @marcoVermeulen
  9. @marcoVermeulen
Commits on Dec 4, 2012
  1. @marcoVermeulen
Something went wrong with that request. Please try again.