| Age | Commit message (Collapse) | Author |
|---|
|
|
|
In MODULES-891 the question arose whether https sources are supported.
This test shows that it works.
|
|
Consider the submodules flag on specific revision cloning
|
|
|
|
Merge 1.3.x to master
|
|
|
|
* Corrected the list of supported platforms under Limitations
* Spelled “revision spec” instead of “revisionspec”.
|
|
Release 1.3.0
|
|
|
|
Update README per DOC-1501
|
|
(MODULES-821) Don't use /tmp
|
|
Very often /tmp is mounted noexec for security reasons related to it
being writable by all users. This stopped vcsrepo's git provider from
working.
This pull request uses puppet's statedir as it is not writable by all
users and is a good candidate for transient state like the git
provider's identity script for the $GIT_SSH command.
An alternative in the future that wouldn't require a temporary file is
to set $GIT_SSH_COMMAND instead of $GIT_SSH, except this was added in
git 2.3 and is too new to depend on.
|
|
Modulesync updates
|
|
|
|
|
|
|
|
Clean up puppet lint warnings
|
|
Testing updates
|
|
|
|
1. Remove any "what this affects" sections, except where particularly warranted.
2. Make sure that for each parameter, where applicable, there is a data type and a default value.
3. Make sure that for each parameter that's applicable, there is a note if the parameter is optional.
4. Make sure the links in the README work and are accurate.
5. Update the link in the Contributing section to point here: https://docs.puppetlabs.com/forge/contributing.html
6. General copyediting.
|
|
Shallow clone with one commit that corresponds to arbitrary tag from arbitrary branch
|
|
Enforce the style guide's recommendation of single quotes as the default.
|
|
|
|
|
|
There were puppet lint warnings due to indentation in several examples.
This commit cleans up the warnings.
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
|
|
Add support for 'conflict' parameter to populate svn --accept arg
|
|
(BKR-147) add Gemfile setting for BEAKER_VERSION for puppet...
|
|
Fix remote hash ordering for unit tests
|
|
Without this commit, the unit tests for the git provider changing
multiple remotes mocks the remotes in a particular order. While in
practice it doesn't matter which remote the update_remotes method
updates first, the unit tests must be able to mock them in the correct
order. For ruby 1.8.7, a Hash will not necessarily produce key value
pairs in the same order on each run, which causes intermittent failures
in the unit tests. This change sorts the :source property values before
trying to update them, and updates the unit tests to expect the values
in alphabetical order.
|
|
puppetdb, etc
- support for BEAKER_VERSION and BEAKER_RSPEC_VERSION in gemfile
|
|
This commit makes the following changes to the test matrix:
- Runs tests on ruby 2.1.5 instead of 2.0.0
- Runs tests on ruby 1.8.7 with puppet 3.x
- Adds an environment to run on an intermediate 3.x puppet version
instead of latest (specifically 3.4.x)
- Adds an environment to run with the future parser on latest puppet.
This would affect the test runs for the validate and spec checks.
- Runs the tests on docker
|
|
The modulesync config repo is dropping universal support for puppet
2.7, but individual repos should still keep support until the next
naturally-occuring major release.
|
|
puppetlabs_spec_helper takes care of these for us.
|
|
|
|
Updating 'excludes' in readme to be more concise.
|
|
Clarified what the parameter 'excludes' is intended to do.
|
|
Pin rspec gems
|
|
|
|
|
|
|
|
|
|
Implemented multiple remotes feature for git provider.
|
|
|
|
Add submodules feature to git provider
|
|
|
|
Update let to use instance variable instead.
|
|
Since lets can't be used in before :all any more.
|
|
removing private tests
|
|
removing private tests, due to rspec3 not handling private methods
|
|
Add IntelliJ files to the ignore list
|
