| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
We need the user to find their HOME, and we don't want to guess about the HOME.
|
|
|
|
|
|
| |
Certain versions of `git` misbehave if git configuration is
inaccessible in $HOME. We need to ensure $HOME matches the
user who is executing `git` not the user running Chef.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Removed uneeded 'converge' commands and some log_level param assumptions from spec
|
|
|
|
|
| |
Removed uncessary complexity with checking for presence of both
parameters for setup_remote_tracking_branches.
|
|
|
|
|
| |
Organized the remote branches setup tests into describe blocks.
Removed some trailing spaces.
|
|
|
|
|
| |
Using 'git config' instead of 'git remote --set-url' to assure
compatibility with git < 1.7.0
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Refactored the method to use appropriate git command depending
on the current status of git config.
|
| |
|
|
|
|
| |
provider
|
|
|
|
|
| |
live stream is no longer enabled by default in mixin/shellout, so the
special casing is now increasing noise and very annoying in tests.
|
|
|
|
|
|
|
| |
Conflicts:
lib/chef/provider/git.rb
spec/unit/provider/git_spec.rb
|
|
|
|
|
|
|
| |
Conflicts:
lib/chef/provider/git.rb
spec/unit/provider/git_spec.rb
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Annotated tags have their own SHA and also point to a SHA in the git
repo. Using git ls-remote $REPO $TAG* the tagged SHAs can be
identified by the '^{}' suffix appended to the corresponding tag name.
When resolving the remote reference, we now search for $TAG* and use
the SHA of the tagged commit (with ^{}) if it is there and otherwise
use the SHA with an exact match for $TAG (to avoid capturing anything
extra via the glob used to return refs).
If no revision is specified, we force 'HEAD' in the git ls-remote call
to constrain what can come back from the remote. Further, we protect
against a badly chosen annotated tag named 'HEAD'.
The functional test suite includes a git bundle of a small example
repo. We found that locally cloning this bundle provided the closest
simulation of `git ls-remote` behavior. YMMV depending on git version.
The test suite could be extended to improve overall coverage, but does
verify the desired behavior for annotated tags.
|
|
|
|
| |
so that converge and converge! are no longer a method in the provider and why_run, respectively. There is instead set_updated_status in provider. Everything is now converged in why_run's add_action, so neither of the converge methods should ever need to be called. Updated tests to reflect this. Removed all calls to converge, and replaced with set_updated_status only for tests that are looking at the update status of a provider, where the converge behavior has been mocked out.
|
|
The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!
|