scalar clone: add --no-maintenance option
When creating a new enlistment via 'scalar clone', the default is to set up situations that work for most user scenarios. Background maintenance is one of those highly-recommended options for most users. However, when using 'scalar clone' to create an enlistment in a different situation, such as prepping a VM image, it may be valuable to disable background maintenance so the manual maintenance steps do not get blocked by concurrent background maintenance activities. Add a new --no-maintenance option to 'scalar clone'. Signed-off-by: Derrick Stolee <stolee@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
9816e24a78
commit
882ce0c475
@@ -9,7 +9,7 @@ SYNOPSIS
|
||||
--------
|
||||
[verse]
|
||||
scalar clone [--single-branch] [--branch <main-branch>] [--full-clone]
|
||||
[--[no-]src] <url> [<enlistment>]
|
||||
[--[no-]src] [--[no-]tags] [--[no-]maintenance] <url> [<enlistment>]
|
||||
scalar list
|
||||
scalar register [--[no-]maintenance] [<enlistment>]
|
||||
scalar unregister [<enlistment>]
|
||||
@@ -97,6 +97,11 @@ cloning. If the HEAD at the remote did not point at any branch when
|
||||
A sparse-checkout is initialized by default. This behavior can be
|
||||
turned off via `--full-clone`.
|
||||
|
||||
--[no-]maintenance::
|
||||
By default, `scalar clone` configures the enlistment to use Git's
|
||||
background maintenance feature. Use the `--no-maintenance` to skip
|
||||
this configuration.
|
||||
|
||||
List
|
||||
~~~~
|
||||
|
||||
|
||||
9
scalar.c
9
scalar.c
@@ -426,7 +426,7 @@ static int cmd_clone(int argc, const char **argv)
|
||||
const char *branch = NULL;
|
||||
char *branch_to_free = NULL;
|
||||
int full_clone = 0, single_branch = 0, show_progress = isatty(2);
|
||||
int src = 1, tags = 1;
|
||||
int src = 1, tags = 1, maintenance = 1;
|
||||
struct option clone_options[] = {
|
||||
OPT_STRING('b', "branch", &branch, N_("<branch>"),
|
||||
N_("branch to checkout after clone")),
|
||||
@@ -439,11 +439,13 @@ static int cmd_clone(int argc, const char **argv)
|
||||
N_("create repository within 'src' directory")),
|
||||
OPT_BOOL(0, "tags", &tags,
|
||||
N_("specify if tags should be fetched during clone")),
|
||||
OPT_BOOL(0, "maintenance", &maintenance,
|
||||
N_("specify if background maintenance should be enabled")),
|
||||
OPT_END(),
|
||||
};
|
||||
const char * const clone_usage[] = {
|
||||
N_("scalar clone [--single-branch] [--branch <main-branch>] [--full-clone]\n"
|
||||
"\t[--[no-]src] [--[no-]tags] <url> [<enlistment>]"),
|
||||
"\t[--[no-]src] [--[no-]tags] [--[no-]maintenance] <url> [<enlistment>]"),
|
||||
NULL
|
||||
};
|
||||
const char *url;
|
||||
@@ -565,7 +567,8 @@ static int cmd_clone(int argc, const char **argv)
|
||||
if (res)
|
||||
goto cleanup;
|
||||
|
||||
res = register_dir(1);
|
||||
/* If --no-maintenance, then skip maintenance command entirely. */
|
||||
res = register_dir(maintenance);
|
||||
|
||||
cleanup:
|
||||
free(branch_to_free);
|
||||
|
||||
@@ -177,7 +177,16 @@ test_expect_success 'progress without tty' '
|
||||
test_expect_success 'scalar clone warns when background maintenance fails' '
|
||||
GIT_TEST_MAINT_SCHEDULER="crontab:false,launchctl:false,schtasks:false" \
|
||||
scalar clone "file://$(pwd)/to-clone" maint-fail 2>err &&
|
||||
grep "could not turn on maintenance" err
|
||||
grep "could not toggle maintenance" err
|
||||
'
|
||||
|
||||
test_expect_success 'scalar clone --no-maintenance' '
|
||||
GIT_TEST_MAINT_SCHEDULER="crontab:false,launchctl:false,schtasks:false" \
|
||||
GIT_TRACE2_EVENT="$(pwd)/no-maint.event" \
|
||||
GIT_TRACE2_EVENT_DEPTH=100 \
|
||||
scalar clone --no-maintenance "file://$(pwd)/to-clone" no-maint 2>err &&
|
||||
! grep "could not toggle maintenance" err &&
|
||||
test_subcommand ! git maintenance unregister --force <no-maint.event
|
||||
'
|
||||
|
||||
test_expect_success '`scalar clone --no-src`' '
|
||||
|
||||
Reference in New Issue
Block a user