On Thu, Dec 28, 2017 at 12:00 AM, SZEDER Gábor <szeder.dev@xxxxxxxxx> wrote: > On Wed, Dec 27, 2017 at 8:15 PM, Lars Schneider <larsxschneider@xxxxxxxxx> wrote: >>> + then >>> + cat <<-EOF >>> + Skipping build job for commit $TRAVIS_COMMIT. >>> + This commit has already been built and tested successfully by this build job. >>> + To force a re-build delete the branch's cache and then hit 'Restart job'. >>> + EOF >>> + else >>> + cat <<-EOF >>> + Skipping build job for commit $TRAVIS_COMMIT. >>> + This commit's tree has already been built and tested successfully in build job $prev_good_job_number for commit $prev_good_commit. >>> + The log of that build job is available at https://travis-ci.org/$TRAVIS_REPO_SLUG/jobs/$prev_good_job_id >>> + To force a re-build delete the branch's cache and then hit 'Restart job'. >>> + EOF >> >> Maybe add a few newlines before and after EOF to make the text more stand out? >> Or print it in a different color? Maybe red? >> >> See: https://travis-ci.org/szeder/git/jobs/322247836#L622-L625 > > I considered using color for the first line, but then didn't do it, > because I didn't want to decide the color :) > Anyway, red is the general error/failure color, but this is neither. It > could either be green, to match the color of the build job's result, or > something neutral like blue or yellow. OTOH, the message printed in skip_branch_tip_with_tag() is not colorized, either.
