@@ -10,68 +10,68 @@ See https://golang.org/wiki/Gomote
1010
1111Usage:
1212
13- gomote [global-flags] cmd [cmd-flags]
13+ gomote [global-flags] cmd [cmd-flags]
1414
15- For example,
16- $ gomote create openbsd-amd64-60
17- user-username-openbsd-amd64-60-0
18- $ gomote push user-username-openbsd-amd64-60-0
19- $ gomote run user-username-openbsd-amd64-60-0 go/src/make.bash
20- $ gomote run user-username-openbsd-amd64-60-0 go/bin/go test -v -short os
15+ For example,
16+ $ gomote create openbsd-amd64-60
17+ user-username-openbsd-amd64-60-0
18+ $ gomote push user-username-openbsd-amd64-60-0
19+ $ gomote run user-username-openbsd-amd64-60-0 go/src/make.bash
20+ $ gomote run user-username-openbsd-amd64-60-0 go/bin/go test -v -short os
2121
2222To list the subcommands, run "gomote" without arguments:
2323
24- Commands:
25-
26- create create a buildlet; with no args, list types of buildlets
27- destroy destroy a buildlet
28- gettar extract a tar.gz from a buildlet
29- list list active buildlets
30- ls list the contents of a directory on a buildlet
31- ping test whether a buildlet is alive and reachable
32- push sync your GOROOT directory to the buildlet
33- put put files on a buildlet
34- put14 put Go 1.4 in place
35- puttar extract a tar.gz to a buildlet
36- rm delete files or directories
37- rdp RDP (Remote Desktop Protocol) to a Windows buildlet
38- run run a command on a buildlet
39- ssh ssh to a buildlet
24+ Commands:
25+
26+ create create a buildlet; with no args, list types of buildlets
27+ destroy destroy a buildlet
28+ gettar extract a tar.gz from a buildlet
29+ list list active buildlets
30+ ls list the contents of a directory on a buildlet
31+ ping test whether a buildlet is alive and reachable
32+ push sync your GOROOT directory to the buildlet
33+ put put files on a buildlet
34+ put14 put Go 1.4 in place
35+ puttar extract a tar.gz to a buildlet
36+ rm delete files or directories
37+ rdp RDP (Remote Desktop Protocol) to a Windows buildlet
38+ run run a command on a buildlet
39+ ssh ssh to a buildlet
4040
4141To list all the builder types available, run "create" with no arguments:
4242
43- $ gomote create
44- (list tons of buildlet types)
43+ $ gomote create
44+ (list tons of buildlet types)
4545
4646The "gomote run" command has many of its own flags:
4747
48- $ gomote run -h
49- run usage: gomote run [run-opts] <instance> <cmd> [args...]
50- -builderenv string
51- Optional alternate builder to act like. Must share the same
52- underlying buildlet host type, or it's an error. For
53- instance, linux-amd64-race is compatible
54- with linux-amd64, but openbsd-amd64 and openbsd-386 are
55- different hosts.
56- -debug
57- write debug info about the command's execution before it begins
58- -dir string
59- Directory to run from. Defaults to the directory of the
60- command, or the work directory if -system is true.
61- -e value
62- Environment variable KEY=value. The -e flag may be repeated
63- multiple times to add multiple things to the environment.
64- -path string
65- Comma-separated list of ExecOpts.Path elements. The special
66- string 'EMPTY' means to run without any $PATH. The empty
67- string (default) does not modify the $PATH. Otherwise, the
68- following expansions apply: the string '$PATH' expands to
69- the current PATH element(s), the substring '$WORKDIR'
70- expands to the buildlet's temp workdir.
71- -system
72- run inside the system, and not inside the workdir; this is implicit if cmd starts with '/'
73-
74- Debugging buildlets directly
48+ $ gomote run -h
49+ run usage: gomote run [run-opts] <instance> <cmd> [args...]
50+ -builderenv string
51+ Optional alternate builder to act like. Must share the same
52+ underlying buildlet host type, or it's an error. For
53+ instance, linux-amd64-race is compatible
54+ with linux-amd64, but openbsd-amd64 and openbsd-386 are
55+ different hosts.
56+ -debug
57+ write debug info about the command's execution before it begins
58+ -dir string
59+ Directory to run from. Defaults to the directory of the
60+ command, or the work directory if -system is true.
61+ -e value
62+ Environment variable KEY=value. The -e flag may be repeated
63+ multiple times to add multiple things to the environment.
64+ -path string
65+ Comma-separated list of ExecOpts.Path elements. The special
66+ string 'EMPTY' means to run without any $PATH. The empty
67+ string (default) does not modify the $PATH. Otherwise, the
68+ following expansions apply: the string '$PATH' expands to
69+ the current PATH element(s), the substring '$WORKDIR'
70+ expands to the buildlet's temp workdir.
71+ -system
72+ run inside the system, and not inside the workdir; this is implicit if cmd starts with '/'
73+
74+ # Debugging buildlets directly
7575
7676Using "gomote create" contacts the build coordinator
7777(farmer.golang.org) and requests that it create the buildlet on your
@@ -80,7 +80,6 @@ then proxy your request via the coordinator. To access a buildlet
8080directly (for example, when working on the buildlet code), you can
8181skip the "gomote create" step and use the special builder name
8282"<build-config-name>@ip[:port>", such as "[email protected] ". 83-
8483*/
8584package main
8685
0 commit comments