StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I think, you have to <strong>seriously re-think</strong> about used workflow, because LAMP-per-dev is only <em>slightly</em> better than editing sites in-place</p> <ul> <li>I can't see place for Bitbucket in serious corporate development - in-house resources are at least more manageable</li> <li>I can't see reasons don't use Staging Mercurial-server (pseudo-central) with Staging internal LAMP-server (which you have and use now)</li> </ul> <p>I can imagine at least two possible choices (fast, dirty, draft idea, not ready-to-use solution), both are <a href="http://hgbook.red-bean.com/read/handling-repository-events-with-hooks.html" rel="nofollow">hook</a>-based</p> <h2>Less manageable, faster for implement</h2> <p>Every developer have in own local repo hook, which after (each?) commit export his tip and copy exported to related site space. Workflow: commit - test results on internal site</p> <p>Advantages: easy, fast to implement</p> <p>Disadvantages: Can't prevent (due to distributed nature) overwriting of tested code by code from another developer</p> <h2>Manageable deploy, harder to implement and manage</h2> <p>LAMP-server become also Mercurial-server, which hosts "central" clones of all site-repos, updated by push only from developer local repo. Each repo on this server must get two hooks:</p> <ul> <li>"before-push" checks, is it allowed to push now, or site "locked" by previous developer</li> <li>"post-push", which export-copy received data and perform also control function for hook 1: based on conditions (subject of discussion) lock/unlock pushes to repo</li> </ul> <p>Workflow: commit - push - test results - tag WC with special (moved) tag - commit tag - push unlocking changeset into repo </p> <p>Advantages: manageable single-point testing</p> <p>Disadvantages: possible delays due to push-workflow and blocking of pushes. The need to install, configure, support additional server. Complexity of changegroup and pretxnchangegroup hooks</p> <p><strong>Final notes and hints for solution 2:</strong> I <em>think</em> (<strong>not tested</strong>), special tag (with -f for movement across changesets) can be used as unlock sign (bookmark will not satisfy condition "move by hand"). I.e - developer commit (and pushes) non-tagged changeset, tag (f.e) "Passed" mark some older changeset. When testing results on Staging server is done, developer tag WC with the above tag, commit tag and pushed to central repo. changegroup hook must detect pushing of .hgtags and (in some-way) allow future data-pushes (control-pushes must be allowed always)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload