On 24/05/16 01:03, Ramin K wrote:
On 5/22/16 3:41 AM, Alex Samad wrote:
Hi
just starting out with puppet.
I found
this
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control
old page
talks about checking /etc/puppet into svn.
But on my centos install I have /etc/puppetlabs/puppet
do I add /etc/puppetlabs or /etc/puppetlabs/puppet to svn and if the
later what about my codedir ?
I have one of the largest SVN backed Puppet systems. It's painful,
slows us down, and we're getting off it this quarter. Finally.
If you don't have much dev experience, the idea that each branch
exists as a set of files in SVN initially sounds great. However the
inability to split work off into branches both short and long lived
starts to take its toll. Also tooling it hard, can't push a branch for
someone else to check out. You end up having "scratch space" for tests
that eventually have to be merged. It makes it hard to do sweeping
changes as scratch space has to encompass it all at least in most
schemes I've observed.
I'm sure there are ways around some of the problems, but git based
branch development is ridiculously good with minimal investment. That
said git will seem like more work than you'd like when you have one or
two people working on the codebase. I never appreciated till I was on a
larger team.
Answering the other question, I recommend starting with
/etc/*puppetwhatever*/environments/{production|stage|etc}/ as releasses
of your src control rather than deploying directly to /etc/puppetlabs/
from src control.
Ramin
Alex, listen to Ramin!
Since I started coding, I have used (in order):
SCCS
RCS
CVS
ClearCase
Perforce
SVN
git
With the exception of git they have all been a total pain to use.
With git, being different from the others it may seem daunting at first.
Also, at the beginning your are bound to make beginner mistakes.
Take the advice to start early with git. Even if you are just
exploring/hacking/learning - that way if you screw things up it is not
the end of the world, and you learn the right way. Contrast that with
having to do everything with quality at some later point where you have
a working system and "retrofitting" - now you have to figure out all the
git related stuff at once without any prior experience.
Don't bother going first to SVN and then use the SVN to git. I have
migrated SVN to git - it works, but then you have to learn that domain
as well (it has its pitfalls).
As you go along you want to hang out on Slack or IRC (which ever suits
you best). There you will find many helpful colleagues that will help
you out, be it with puppet or git.
Best,
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/bc18a34f-ab2f-86a5-c9aa-d8ff1865c27b%40puppet.com.
For more options, visit https://groups.google.com/d/optout.
