diff options
| author | Paul Sokolovsky <paul.sokolovsky@linaro.org> | 2013-04-18 06:39:10 +0300 |
|---|---|---|
| committer | Paul Sokolovsky <paul.sokolovsky@linaro.org> | 2013-04-18 06:39:10 +0300 |
| commit | f3ab84413769c200e3dd9159b66418d28625de02 (patch) | |
| tree | 38738fb83015d450b8910d56c5ef7ce7787b6f5e /utils | |
| parent | a952945088382363b584bf830f3b7901d1f9aeb5 (diff) | |
Kinda complete docs.
Diffstat (limited to 'utils')
| -rw-r--r-- | utils/new-publish/README | 26 |
1 files changed, 25 insertions, 1 deletions
diff --git a/utils/new-publish/README b/utils/new-publish/README index c37027e..e63e000 100644 --- a/utils/new-publish/README +++ b/utils/new-publish/README @@ -23,7 +23,7 @@ External Interface Build jobs use publishing API using the shell command calls. To perform publishing build calls following script: -publish --token=<token> --type=<build_type> <build_id> <glob_pattern>... +publish --token=<token> --type=<build_type> --strip=<strip> <build_id> <glob_pattern>... <token> Token to authenticate publishing request. It is expected that security @@ -34,7 +34,25 @@ publish --token=<token> --type=<build_type> <build_id> <glob_pattern>... "openembedded", etc. Generally, this selects target area for publishing, but may influence other build parameters, like directory structure, metadata, etc. +<strip> + String number of components from paths produced by <glob_pattern>. +<build_id> + Build ID of the form <job_name>/<build_no>. This allows identification + of particular build job and its specific build case. build_id is usually + used directly as path (URL) component to access build artifacts. +<glob_pattern> + Shell glob patterns to capture artifact files. There may be more than one, + separate by spaces, or (for compatibility with Jenkins), by commas (in this + case no spaces allowed). Patterns must follow shell syntax, i.e. + multi-level match (**) is not supported. +Example: + +$ publish --token=SECRET --type=android --strip=2 panda/10 out/target/*.tar.bz2 + +With this command, artifacts can be expected to be found on URL like + +http://snapshosts/android/panda/10/*.tar.bz2 Internal Implementation ----------------------- @@ -48,3 +66,9 @@ historical reasons). Current publisher process goes as: Builder -> Master -> Snapshots + +Publishing starts on build slave with SFTPing artifact files to master +(using one account with chrooted SFTP access), then triggering further +processing by calling out (by SSH) sshd-config fixed script on master. +This script recursively applies same processing (chroot SFTP, fixed script) +to publish files to snapshots. |