Add DStep to the tested projects

[jacob-carlborg]

No description provided.

[dlang-bot]

Thanks for your pull request, @jacob-carlborg! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.

Some tips to help speed things up:

• smaller, focused PRs are easier to review than big ones

• try not to mix up refactoring or style changes with bug fixes or feature enhancements

• provide helpful commit messages explaining the rationale behind each change

Bear in mind that large or tricky changes may require multiple rounds of review and revision.

Please see CONTRIBUTING.md for more information.

[jacob-carlborg]

Why is it checking out the latest tag? I want it to test master.
I think I figured it out.

[wilzbach]

Why can't you tag a new release? The idea behind not using master is that the latest release will be more stable and will change less frequently.

[jacob-carlborg]

I looked down the clone to the current master. I'll remove this later when a new tag is added for DStep.

[wilzbach]

It looks like the Jenkins Git checkout plugin only supports tags and branches :O

[jacob-carlborg]

Added a tag.

[jacob-carlborg]

It's Dub that is failing.

[wilzbach]

Yeah that's unrelated and due to #135

However, I can't overwrite the CI check here. I will try to restart it.

[MartinNowak]

Downloading a 200+MiB clang+llvm for every test is not OK, please don't unnecessarily waste resources, simply because they are not your resources.
https://ci.dlang.io/blue/organizations/jenkins/dlang-org%2Fci/detail/PR-146/2/pipeline/207#step-472-log-8
I've installed libclang-4.0-dev on all testers. I'm reverting this until dstep manages to detect that package.
#148
Let us know if you need sth. else installed.

You should also fix your Travis-CI tests to either use packages or at least cache the downloads, it's currently downloading 13x200+MiB from the llvm site.
https://travis-ci.org/jacob-carlborg/dstep/builds/334364953

[MartinNowak]

FYI @jacob-carlborg

[jacob-carlborg]

You should also fix your Travis-CI tests to either use packages or at least cache the downloads, it's currently downloading 13x200+MiB from the llvm site.
https://travis-ci.org/jacob-carlborg/dstep/builds/334364953

Should I cache that to reduce the traffic to the LLVM site? Because the Travis documentation says:

"Large files that are quick to install but slow to download do not benefit from caching, as they take as long to download from the cache as from the original source:" [1]

[1] https://docs.travis-ci.com/user/caching/#Things-not-to-cache

[jacob-carlborg]

You should also fix your Travis-CI tests to either use packages.

I cannot use packages because they are too old. I want to control myself which versions of LLVM I support.