Changeset 1197 for obs_notify_generic
- Timestamp:
- Oct 13, 2015, 12:33:31 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
obs_notify_generic/README.md
r1186 r1197 31 31 ------------- 32 32 33 All configuration is done in the file33 All configuration for this plugin is done in the file 34 34 35 35 ``` … … 45 45 but can be configured. 46 46 47 The best configuration to start is by47 The starting configuration could look like this: 48 48 49 49 ``` … … 53 53 ``` 54 54 55 This logs all UNKNOWN events. With this configuration this are all events, as no specific events are defined.55 This logs all UNKNOWN events. With this configuration this are all events, as no specific notification types are defined. 56 56 57 57 Usefull notification types are … … 62 62 Each event come with a number of parameter. These will also be logged. 63 63 64 The configuration direct ove `filter` limits a notification type to certain cases. Filter can be regexes.64 The configuration directive `filter` limits a notification type to certain cases. Filter can be regexes. 65 65 66 66 Example: … … 75 75 }, 76 76 { 77 "filter" => { 'project' => '.*:bareos', 'repo sitory' => 'SLE_12' },77 "filter" => { 'project' => '.*:bareos', 'repo' => 'SLE_12' }, 78 78 "action" => 'logger "project $project published for repository $repository', 79 79 "log" => 0, … … 84 84 ``` 85 85 86 Mea ing:86 Meaning: 87 87 * type=REPO_PUBLISH_STATE 88 88 * ignore it … … 92 92 93 93 Limitations: 94 * the `action` run as user obsrun. As the OBS service run as daemon, only very few environment variables are set. 95 * the `action` s should have a short runtime. As long as these scripts run, some other services from the obs are blocked. Maybe the scripts are forcefully ended by the OBS service.94 * the `action` run as user obsrun. As the OBS service run as daemon, only very few environment variables are set. It might help to call scripts using `sudo -u USERNAME` 95 * the `action` script do run in background, to prevent blocking other OBS services. Output will be write to `${logfile}.out.log`.
Note:
See TracChangeset
for help on using the changeset viewer.