mirror of
https://github.com/golang/go.git
synced 2025-05-05 23:53:05 +00:00
Created Gomote (markdown)
parent
66ed20dd74
commit
49a6e22c13
77
Gomote.md
Normal file
77
Gomote.md
Normal file
@ -0,0 +1,77 @@
|
|||||||
|
# Using gomote
|
||||||
|
|
||||||
|
## Installing
|
||||||
|
|
||||||
|
```
|
||||||
|
$ go get -u golang.org/x/build/gomote
|
||||||
|
```
|
||||||
|
|
||||||
|
## Using
|
||||||
|
|
||||||
|
TODO: examples. For now:
|
||||||
|
|
||||||
|
```
|
||||||
|
The gomote command is a client for the Go builder infrastructure.
|
||||||
|
It's a remote control for remote Go builder machines.
|
||||||
|
|
||||||
|
Usage:
|
||||||
|
|
||||||
|
gomote [global-flags] cmd [cmd-flags]
|
||||||
|
|
||||||
|
For example,
|
||||||
|
$ gomote create openbsd-amd64-60
|
||||||
|
user-username-openbsd-amd64-60-0
|
||||||
|
$ gomote push user-username-openbsd-amd64-60-0
|
||||||
|
$ gomote run user-username-openbsd-amd64-60-0 go/src/make.bash
|
||||||
|
$ gomote run user-username-openbsd-amd64-60-0 go/bin/go test -v -short os
|
||||||
|
|
||||||
|
To list the subcommands, run "gomote" without arguments:
|
||||||
|
|
||||||
|
Commands:
|
||||||
|
|
||||||
|
create create a buildlet
|
||||||
|
destroy destroy a buildlet
|
||||||
|
gettar extract a tar.gz from a buildlet
|
||||||
|
list list buildlets
|
||||||
|
ls list the contents of a directory on a buildlet
|
||||||
|
ping test whether a buildlet is alive and reachable
|
||||||
|
push sync the repo of your pwd to the buildlet
|
||||||
|
put put files on a buildlet
|
||||||
|
put14 put Go 1.4 in place
|
||||||
|
puttar extract a tar.gz to a buildlet
|
||||||
|
rm delete files or directories
|
||||||
|
run run a command on a buildlet
|
||||||
|
|
||||||
|
To list all the builder types available, run "create" with no arguments:
|
||||||
|
|
||||||
|
$ gomote create
|
||||||
|
(tons of builder types)
|
||||||
|
|
||||||
|
The "gomote run" command has many of its own flags:
|
||||||
|
|
||||||
|
$ gomote run -h
|
||||||
|
create usage: gomote run [run-opts] <instance> <cmd> [args...]
|
||||||
|
-builderenv string
|
||||||
|
Optional alternate builder to act like. Must share the same
|
||||||
|
underlying buildlet host type, or it's an error. For
|
||||||
|
instance, linux-amd64-race or linux-386-387 are compatible
|
||||||
|
with linux-amd64, but openbsd-amd64 and openbsd-386 are
|
||||||
|
different hosts.
|
||||||
|
-debug
|
||||||
|
write debug info about the command's execution before it begins
|
||||||
|
-dir string
|
||||||
|
Directory to run from. Defaults to the directory of the
|
||||||
|
command, or the work directory if -system is true.
|
||||||
|
-e value
|
||||||
|
Environment variable KEY=value. The -e flag may be repeated
|
||||||
|
multiple times to add multiple things to the environment.
|
||||||
|
-path string
|
||||||
|
Comma-separated list of ExecOpts.Path elements. The special
|
||||||
|
string 'EMPTY' means to run without any $PATH. The empty
|
||||||
|
string (default) does not modify the $PATH. Otherwise, the
|
||||||
|
following expansions apply: the string '$PATH' expands to
|
||||||
|
the current PATH element(s), the substring '$WORKDIR'
|
||||||
|
expands to the buildlet's temp workdir.
|
||||||
|
-system
|
||||||
|
run inside the system, and not inside the workdir; this is implicit if cmd starts with '/'
|
||||||
|
```
|
Loading…
x
Reference in New Issue
Block a user