Bug #8354

keeping a repository up to date

Added by micah - 11 months ago. Updated 7 months ago.

Status:Needs Decision Start date:07/11/2011
Priority:Normal Due date:
Assignee:Nick Fagerlund % Done:

0%
Category:vcsrepo Spent time: -
Target version:-
Keywords: Branch:
Votes: 1

Description

It is non-obvious how you can clone a git repository and then make sure that cloned repository stays up to date.

I eventually asked on #puppet-dev and was told I should use ‘revision => master’ along with ‘ensure => latest’, which is a somewhat surprising setting, as master is a branch, not really a revision. Perhaps this could be better documented in the README, or perhaps made more obvious in how the module is used for that purpose.

History

#1
Updated by micah - 11 months ago

  • Status changed from Unreviewed to Closed

Uh, I managed to submit this with nothing… sorry about that.

#2
Updated by micah - 11 months ago

  • Status changed from Closed to Re-opened

It is non-obvious how you can clone a git repository and then make sure that cloned repository stays up to date.

I eventually asked on #puppet-dev and was told I should use ‘revision => master’ along with ‘ensure => latest’, which is a somewhat surprising setting, as master is a branch, not really a revision. Perhaps this could be better documented in the README, or perhaps made more obvious in how the module is used for that purpose.

#3
Updated by Ken Barber 10 months ago

  • Category set to vcsrepo

#4
Updated by James Turnbull 7 months ago

  • Description updated (diff)
  • Status changed from Re-opened to Accepted

#5
Updated by James Turnbull 7 months ago

  • Status changed from Accepted to Needs Decision
  • Assignee set to Nick Fagerlund

Nick – docs?

Also available in: Atom PDF