Since scap will be used to deploy mediawiki as well as other code, the default lock_file of /var/lock/scap is inadequate. The lock file should be changed so that by default a deploy of one repo won't interfere with the deploy of another.
Description
Description
Revisions and Commits
Revisions and Commits
| Restricted Differential Revision | |||
| rMSCA Scap | |||
| rMSCA369990b345d0 Scap deploy should use a repo-dependent lock file. | |||
Event Timeline
Comment Actions
I recently added a sync.flag (in D36), I think that could take the place of a lock file in /var/lock/scap. @thcipriani: Does that sound reasonable to you? The lock file could exist in the same location as the scap.cfg I suppose.
Comment Actions
@mmodell, sounds like merging the two lock files is a reasonable approach. While both files have different semantics, both have the same effect of locking deployments.
Might also be neat if the sync.flag could contain a reason, like we have with puppet agent --disable