Opened on 08/07/2015 at 01:38:10 AM
Closed on 08/17/2015 at 11:36:31 PM
#2867 closed defect (fixed)
Introduce a Puppet module for Mercurial
| Reported by: | matze | Assignee: | matze |
|---|---|---|---|
| Priority: | P3 | Milestone: | |
| Module: | Infrastructure | Keywords: | |
| Cc: | fred, fhd | Blocked By: | |
| Blocking: | #2906, #2909 | Platform: | Unknown / Cross platform |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by matze)
... aligned with our present hgweb sites at https://hg.adblockplus.org/.
Attachments (0)
Change History (7)
comment:3 Changed on 08/15/2015 at 02:09:17 PM by matze
- Blocking 2906 added
comment:4 Changed on 08/15/2015 at 02:10:09 PM by matze
- Summary changed from Introduce a Puppet module for Mercurial (hgweb) to Introduce a Puppet module for Mercurial
comment:5 Changed on 08/15/2015 at 02:10:18 PM by matze
- Status changed from new to reviewing
comment:6 Changed on 08/15/2015 at 02:34:46 PM by matze
- Blocking 2909 added
comment:7 Changed on 08/17/2015 at 11:36:31 PM by matze
- Resolution set to fixed
- Status changed from reviewing to closed
Note: See
TracTickets for help on using
tickets.
I've published a slightly improved version of last week's draft. It is still aligned with the current production setup, but using a skeleton hgaccess repository one can clone and push using the (unsafe) vagrant keys.
Setting up a new repository within the hg account, however, still requires login to the box. Improving here I don't really consider worth the effort, I'd rather switch to e.g. mercurial-server some day, dropping the custom scripts around the current setup.