forked from metomi/rose
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrose-suite-log
executable file
·67 lines (67 loc) · 2.85 KB
/
rose-suite-log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
#!/usr/bin/env bash
#-------------------------------------------------------------------------------
# Copyright (C) 2012-2019 British Crown (Met Office) & Contributors.
#
# This file is part of Rose, a framework for meteorological suites.
#
# Rose is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# Rose is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with Rose. If not, see <http://www.gnu.org/licenses/>.
#-------------------------------------------------------------------------------
# NAME
# rose suite-log
#
# SYNOPSIS
# 1. rose suite-log [--view]
# 2. rose suite-log --update [ITEM ...]
# rose suite-log --update '*' # all task jobs
# 3. rose suite-log --archive CYCLE ...
# rose suite-log --archive '*' # all cycles
#
# DESCRIPTION
# View or update suite log.
#
# 1. Launch web browser to view suite log. If "rose bush" is not
# configured, the command will offer to start it.
# 2. Pull back task job logs from any remote hosts for specified cycle
# times or task names or IDs.
# 3. Archive (tar-gzip) job logs at the specified cycle time.
#
# If `--name=SUITE-NAME` is not specified, the name will be determined by
# locating a `rose-suite.conf` file in `$PWD` or its nearest parent
# directories. In a normal suite, the basename of the (nearest parent)
# directory containing the `rose-suite.conf` file is assumed to be the
# suite name. In a project containing a rose stem suite, the basename of
# the (nearest parent) directory containing the `rose-stem/rose-suite.conf`
# file is assumed to be the suite name.
#
# OPTIONS
# --archive
# Archive (tar-gzip) job logs at specified cycle times. Implies
# `--update`.
# --force, -f
# Same as `rose suite-log --update '*'`.
# --name=SUITE-NAME, -n SUITE-NAME
# Specify the suite name, instead of using basename of `$PWD`.
# --prune-remote
# If specified, remove job logs from remote hosts after pulling them to
# suite host.
# --tidy-remote
# Deprecated. Use `--prune-remote` instead.
# --update, -U
# Update job logs for items specified in arguments.
# --user=USER-NAME, -u USER-NAME
# View mode only. View logs of a suite of a different user.
# --view
# Launch web browser to view suite log.
#-------------------------------------------------------------------------------
exec python3 -m metomi.rose.suite_log "$@"