This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I4d051f38f48d9c8d064bce455cf874aaacb4560b
The logic in the Gemfile was relying on Zuulv2 variables to find out
whether the spec helper gem was already available on disk, and since
Zuulv3 has changed things it was failing to find it and downloading the
master version instead. This patch ensures the Gemfile looks for the gem
in the right place when running in CI.
Change-Id: I0639bc4bb87db53e46bd58e255aa8c21275792cd
Instead of keeping a local copy of spec_helper_acceptance.rb and
requiring updates to all modules for any change, we can move it into the
common helper gem and require it from there. This will make it easier to
create and review changes that affect all puppet modules. Also change
the Gemfile to look for the gem in the local workspace if running in a
zuul environment.
Change-Id: I11adccf36f9aef32a46de7179d48f6ef296771e2
Add a xenial nodeset and update the spec helper to install puppet 3 from
the Ubuntu repos instead of from puppetlabs.
Change-Id: I0b34419c4f00b971725a30bccfcaff0db749c300
Use same target directory for zuul-cloner and
the regular git command.
Change-Id: I5d1f60853afc6ae6027648235864456723777cf4
Co-Authored-By: Fabien Boucher <fabien.boucher@enovance.com>
In anticipation of puppet 4, start trying to deal with puppet 4 things
that can be helpfully predicted by puppet lint plugins. Also update the
Rakefile to match the other modules, which have puppetlabs_spec_helper
and puppet-lint rake tasks included in them.
Change-Id: I715328da58e27014b2de9edd53cb3f70fd2420e3
The metadata.json was missing from this repo. Resolve
the puppet module dependency issue with Puppet 3.x/Trusty.
The patch removes the deprecated Modulefile.
Change-Id: I5dcc219260c3aeef97f9599f69aae8e741a57f6e
Releasing new version to forge requires a version bump. Bump the
version to 0.0.8.
Change-Id: I8f2b16c66bfe637b3a7b37f3fb514867dd07a1da
Reviewed-on: https://review.openstack.org/18691
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
When the supplied git revision is not a tag or remote branch checkout
the revision locally.
Change-Id: I42bdd4e089036d7520d63067862b0be7245c998f
Reviewed-on: https://review.openstack.org/17568
Reviewed-by: James E. Blair <corvus@inaugust.com>
Reviewed-by: Paul Belanger <paul.belanger@polybeacon.com>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
Change-Id: I625de5df6b9d2f9b2dc41044e5439085c3f06415
Reviewed-on: https://review.openstack.org/18190
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Tested-by: Jenkins
Releasing new version to forge requires a version bump. Bump the version
to 0.0.7.
Change-Id: I0587dc11fa0d6351789e6529364a4ea8c0b2942a
Reviewed-on: https://review.openstack.org/17495
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Tested-by: Jenkins
Previously the tag checkout code would checkout a new branch for the tag
using the current branch (master) as the base for the new branch.
Instead use the actual tag as the base for the tag branch.
Change-Id: Ic18bad7d19da3298b73f3e4185ca0bb5d4b3bf04
Reviewed-on: https://review.openstack.org/16030
Reviewed-by: Paul Belanger <paul.belanger@polybeacon.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
ensure => latest should work and trigger when the remote has new
revs, and not at other times. It will handle tags and branches apparently
and will also handle not specifying a branch in the revision.
Rather than fill the git provider with hard-coded references to
origin, it would be better to abstract out which remote the resource
is fetching from. But since this is only relevant to decentralized
version-control systems, a multiple_remotes feature was added for
the parameter to depend on. So far this is only implemented for git
remotes, but it could be implemented for other VCSs as well.
The git provider had some problems checking out SHA1s - it couldn't.
And what's worse, it lied about what it was doing saying that it did
checkout the SHA1.
There was also a bug where if you specified a different branch than you
were on, it was doing a `reset --hard` to the specified branch. For
example, if master was checked out, and you set "revision => stable", it
would `git reset --hard stable` on the master branch instead of just
checking out stable. Maybe the original author did this to get around
being unable to checkout when you had local changes, but the --force
flag to checkout will fix that.
With this change, you should now be able to specify a branch, tag, or
SHA1 in the revision attribute and have it work.