Kateryna Dovgan
Kateryna Dovgan
Resolves #232
Related issues: #295, #168, #66 Current artifact processing process goes like this: 1. In config preprocessing (before build steps execution) all artifacts, mentioned in all steps, are collected into one...
Currently when using the `-hl` option without any further specification the name of a created file is `default` (instead of expected `universum_log.html`). Need to be expected, fixed and, maybe, covered...
Optionally report the submitted/shelved CL or Git commit hash not only to log, but also to a requested file in some formalized format. Think of a good name for such...
As #586 and #616 were hotfixes, implement an actual alternative way of calculating file diff for `universum api` if `p4 opened` fails. * Investigate client fetch in case it holds...
See https://stackoverflow.com/questions/308999/what-does-functools-wraps-do as a reference
List of scenarios that should be tested and handled properly: - [ ] requirements of special CL description format not fulfilled - [x] requirements of mandatory code review not fulfilled...
The mechanism of `background`/`critical` nested steps is now quite complicated. So we really need to explain whole "what stops what, what waits for what" thing somewhere in documentation, with examples...
Originally created on Wed, 26 Dec 2018 13:58:39 +0200 Add simple step-by-step guide as an example of usage to documentation.
Originally created on Thu, 25 Jan 2018 12:17:16 +0200 We would like to have the ability to run steps of the same project in parallel on several machines to improve...