Commit bfe0355
1 parent d269f34 commit bfe0355
1 file changed
+3
-0
lines changedLines changed: 3 additions & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
25 | 25 |
| |
26 | 26 |
| |
27 | 27 |
| |
| 28 | + | |
| 29 | + | |
| 30 | + | |
28 | 31 |
| |
29 | 32 |
| |
30 | 33 |
| |
|
1 parent d269f34 commit bfe0355
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
25 | 25 |
| |
26 | 26 |
| |
27 | 27 |
| |
| 28 | + | |
| 29 | + | |
| 30 | + | |
28 | 31 |
| |
29 | 32 |
| |
30 | 33 |
| |
|
5 commit comments
nirvn commentedon Nov 6, 2017
@m-kuhn , while your at it, maybe disable the always-failing ci/dockercloud check altogether? :)
nyalldawson commentedon Nov 6, 2017
+1
m-kuhn commentedon Nov 6, 2017
ping @3nids
3nids commentedon Nov 6, 2017
ok I deactivated autobuild.
I'll try to find another solution later.
m-kuhn commentedon Nov 6, 2017
Am I correct, that our main goal with this is the regular deployment of a docker container and we are not so much interested in the status, and the "failing" status is just a side-effect of a underpowered upstream infrastructure?