0.5.0 Roadmap about puppet-archive HOT 11 CLOSED

This is pretty sweet. I'm excited to see open development and roadmap. Are there any testing needs you have that travis can't provide? That's kindof my current kick. @igalic mentioned that we may be hitting max_concurrent travis testing now.

from puppet-archive.

Travis is sufficient for now, do we have a standard gemfile/.travis.yml config for puppet-community?

from puppet-archive.

https://github.com/puppet-community/puppet-extlib has a good Gemfile, Rakefile, .travis.yml
That also provides hooks for you to setup blacksmith deploys of archive. I'm not sure if you want to keep publishing this to your own namespace or use forge.puppetlabs.com/puppet.

The secure: line comes from:
https://github.com/puppet-community/plumbing/blob/master/share/travis_secrets

from puppet-archive.

@nanliu can you publish a 0.3.1 version in forge with archive::nexus support?

from puppet-archive.

#64 would enable the bits to enable push button deploys, which would open the door to a 3.1

from puppet-archive.

@nanliu can you publish a 0.3.1 version in forge with archive::nexus support?

+1

from puppet-archive.

+1 for not having to install faraday on every system, especially when no internet access is available or a local ruby gems server. I have been working on a hacked version that bundles the gems inside the files directory.

from puppet-archive.

#82 brought us up to date with https://github.com/puppet-community/modulesync_config so we're in line with some other modules and their styling/methodology.

from puppet-archive.

Also, @nanliu should this issue be for 0.5.0 now?

from puppet-archive.

@jyaworski, issue updated, looking for volunteers to test:

• Windows platform (review & test #124).
• go function (changes in progress)
• artifactory function (changes in progress)

from puppet-archive.

Merged #124

from puppet-archive.