f0dcd403e7
Second phase wan't running properly due to path issue Add extra echo command to make sure there's data in the pom
...
Signed-off-by: Daan Hoogland <daan@onecht.net>
2015-06-21 15:13:24 +02:00
f0e1c8908b
Send output to oblivion because of this message in travis log view: This log is too long to be displayed. Please reduce the verbosity of your build or download the raw log.
...
Signed-off-by: Daan Hoogland <daan@onecht.net>
2015-06-21 15:13:24 +02:00
880f116a62
This is a quick fix to attempt to resolve most of the travis failures Most of the failures have been due to transient network failures, that are causing dependency artifact downloads to fail Maven does not have a way to retry this without restarting the whole build, so the mvn dependency plugin is the best bet Unfortunately, running a dependency:resolve on the project returns yet to be compiled dependencies, and causes it to fail... There is an option to excludeGroupIds and excludeArtifactIds in the docs for this goal, but unfortunately they don't seem to work This drafts a dummy pom in a quick and dirty way, just to download all the deps in one go, while retrying for RETRY_COUNT times if it fails
...
Signed-off-by: Daan Hoogland <daan@onecht.net>
2015-06-21 15:13:24 +02:00
1eb6f929ab
CLOUDSTACK-8429: optimizing travis to run configurable set of tests only after configurable runs
2015-05-05 14:11:41 +05:30
89fa251119
CLOUDSTACK-8429: travis: running junit tests only in the first job
...
added a new environment variable RUNUNITTESTS
running full build if RUNUNITESTS is true else skipping tests
job1 now runs only unittests
removed some of the test files from job9 and job10 as they are timing
out.
This closes #218
2015-05-01 22:57:31 +05:30
b38d0b6b43
Fix RAT issue
2014-09-01 11:22:36 +01:00
26069aa377
[CLOUDSTACK-6115] Investigate the use of TravisCI for CloudStack integration testing
2014-09-01 10:56:44 +01:00
Rafael da Fonseca
Abhinandan Prateek
Rajani Karuturi
Ian Duffy