Commit e72f3e7
committed
Retry artifacts after 2h, not 24h, for melt/smelt
This uses a newly added feature of pombast to specify a settings.xml
file to use with relevant pombast actions like melt and smelt
(see scijava/pombast@12a42f6).
In such a file, we can set the updatePolicy of each repository.
It is tempting to pass -U to all of pombast's mvn invocations, forcing
rechecks for missing artifacts every single time. But that would be
overkill, adding more overhead to each smelt component build, whereas
reducing the update window from 24 hours to 2 hours means that we
won't recheck for (probably still) missing artifacts for every smelted
component that depends on it during a single run, but rather we'll
recheck "soon" -- hopefully the next time CI runs ~2 hours later.
Why 2 hours? Because the pombast CI smelt run takes ~90 minutes when
no previous successes have been cached. Would it be better to somehow
reset the last-checked metadata before starting the smelt, so that
every CI build behaves as though it's the first one of the day?
Perhaps! But for now, let's try the 2h interval and see how it goes.1 parent 2bcb0f4 commit e72f3e7
2 files changed
Lines changed: 23 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
4 | 5 | | |
5 | 6 | | |
6 | 7 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
0 commit comments