SwarmOps
ReferenceCommandsswarmops land-group

Page kind: Reference

swarmops land-group#

Describes v0.11.0Last changed View as Markdown

Land changes in order onto a ref as one operation: one changeset each, one move.

Each HEAD, with its first-parent chain since its merge base with the ref's head, is merged onto what the clean ones before it make, as land-check plans them. The clean ones are recorded as a chain of landed changesets, each on the one before, with one move of the ref to the last: one operation in op log, all of it or none after a crash. A conflicting change is reported, as land reports it, and passed over; one with nothing to land lands nothing. With no clean change it is E_NOTHING_TO_LAND, each change's outcome in details.items. A ref that moves after the plan makes it plan again.

Metadata
Group
write
Since
0.11.0
Mutates
yes
Identity required
yes
MCP tool
land_group
Envelope op
land_group
Exit codes
0
Errors
none

Syntax#

Syntax
swarmops land-group [OPTIONS] <HEAD>...

Required arguments#

Syntax: <HEAD>.

The changes' heads, in the order they land: 1 to 32.

Optional arguments#

The command also takes the global options.

Syntax: --onto <REF>. Default: main.

The ref they land on: main or a release ref (release/NAME).

Syntax: --max-attempts <N>. Default: 8.

How many times to plan and publish before E_CAS_RETRY_EXHAUSTED: 1 to 32.

Syntax: --max-conflict-bytes <N>. Default: 32768.

The most bytes of hunk text each conflicting change's report carries, as land's.

Examples#

No recorded example yet.

No recorded example yet.

Return information#

result is a LandGroupResp (swarmops schema LandGroupResp prints its JSON Schema).

FieldTypeRequiredDescription
attemptsintegeryesHow many times the group planned and published.
headstringyesThe last landed changeset: what the target names now.
itemsarray of LandGroupItemOutyesEach change's outcome, in the request's order.
opintegeryesThe operation that recorded the chain and the move: its number in op_log.
rebased_ontostringyesThe target's head the chain landed on: the first landed changeset's parent.
targetstringyesThe ref the changes landed on.
warningsarray of stringnoProblems found after the chain became durable; the land itself succeeded. Omitted when empty.

Envelope op: land_group.

Exit codes:

  • 0: Success.

Errors#

No golden step shows this command failing yet.

Any command that opens a store may also fail with a store error, such as E_NOT_A_REPO, E_IO or E_STORE_CORRUPT; a command line the grammar refuses is E_INVALID_ARG (exit 2).

See also#

On this page