Commit d903a943 authored by Jakub Jirutka's avatar Jakub Jirutka

Revert "travis: require check when not explicitly disabled"

This reverts commit da4e9b11.

After 1.5 months it's quite clear that this was a bad idea.

Let me describe a typical situation. Contributor wants to do some small
change in abuild. They did it on their system, it works, so they open a
PR. And it fails on Travis. Why? Because of missing check(), something
totally unrelated to their change! Newbies are often confused. Others
know what to do, but adding check() is often non-trivial. Upstream does
not provide any tests, tests are broken, extra dependencies are needed,
etc. The contributor wanted to do just a small change and now they have
to deal with possibly complicated task. That's not okay.

And the worst is that it caused some devs to ignore CI results. For
example, contributor added php[57] dependency into main/uwsgi. CI failed
due to missing check(). Reviewers did not realized that php[57] is in
the community repository, not main. And some developer merged it despite
CI failed, to revert it few minutes after because it failed on build
servers! This is the exact situation that should be prevented by having

So, it's a good idea to encourage contributors to add check(), but
eagerly failing build on CI is definitely not a good way.
parent b27b200a
......@@ -79,7 +79,7 @@ for repo in $(changed_repos "$commit_range"); do
fold_start "$pkgname" "Building package $qname"
cd $qname
if REQUIRE_CHECK=1 abuild -r; then
if abuild -r; then
checkapk || :
successful_pkgs="$successful_pkgs $qname"
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment