Commit 3f0bbdb
committed
ci-build.sh: give hints when the build goes wrong
In particular, people get javadoc errors a lot, which are confusing
because when even a single javadoc error happens, Maven's javadoc plugin
logs every javadoc *error and warning* at error level, resulting in the
dreaded [ERROR] prefix all over all the javadoc output, burying the
actual javadoc errors amongst the typically more plentiful warnings.
You can actually find these errors though, because they are prefixed
with 'error:' rather than 'warning:'. So we now grep them out and
regurgitate them after declaring the build failed, as a helpful hint
to why the failure occurred.
And if no javadoc-specific errors are found, then we grep for common
words indicating error or failure, and regurgitate those instead.
And if none of those keywords are found, we declare failure at helping.
This commit is dedicated to Nicolas Chiaruttini.1 parent f0b105e commit 3f0bbdb
1 file changed
+35
-6
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 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 | + | |
22 | 51 | | |
23 | 52 | | |
24 | 53 | | |
| |||
208 | 237 | | |
209 | 238 | | |
210 | 239 | | |
211 | | - | |
212 | | - | |
| 240 | + | |
213 | 241 | | |
214 | 242 | | |
215 | 243 | | |
216 | | - | |
217 | | - | |
| 244 | + | |
218 | 245 | | |
219 | 246 | | |
220 | 247 | | |
221 | | - | |
222 | | - | |
| 248 | + | |
223 | 249 | | |
| 250 | + | |
| 251 | + | |
| 252 | + | |
224 | 253 | | |
225 | 254 | | |
226 | 255 | | |
| |||
0 commit comments