You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by GitBox <gi...@apache.org> on 2019/04/10 17:51:12 UTC
[GitHub] [incubator-daffodil] stevedlawrence opened a new pull request #206:
Decrease time needed for continue integration builds
stevedlawrence opened a new pull request #206: Decrease time needed for continue integration builds
URL: https://github.com/apache/incubator-daffodil/pull/206
- In the TravisCI configuration, we only enabled coverage when running
tests. However, coverage actually needs to be enabled during
compilation, since that enables a compiler plugin. By only enabling it
when running tests, sbt will recompile when the tests are run, so we
end up compiling Daffodil twice. Instead, always enable coverage on
every sbt command so that we only compile once.
- In the TravisCI configuration, enable caching of ivy and sbt
directories and provide a few extra memory options that seem to help.
- Also modify TravisCI so that when RAT check fails it cats the rat report.
- Add support for Azure Pipelines. This isn't supported (yet) by ASF
Infra, but it has alot of advantages over TravisCI. It supports more
parallel builds, has a larger maximum build time, organizes build
stages better, handles our large text output, supports Windows.
Additionally, it supports JUNit test integration so we can easily tell
exactly which tests fail and how long each test took to run. The
configuration file is more complex than TravisCI, but is much more
powerful and should be our primary CI tool once ASF supports it.
- Remove the large AB tests. Not only do these fail on Windows due to
line ending issues, but they do not provide any additional test
coverage.
- Some CLI performance command tests expected no output, which required
a timeout, which just takes to long. So just remove the expectation of
nothing. The tests do continue and essentially check the same thing,
just in a different and faster manner.
These changes get TravisCI build consistently between 30-35 minutes,
rather the 40-50+, which caused a build timeout. Note that Azure
Pipelines consistently takes between 20-25 minutes, so we should switch
as soon as ASF supports it.
DAFFODIL-2105
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services