Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

DISPATCH-1363 - Move RAT licence check from travis builds into a sub build #592

Merged
merged 2 commits into from
Oct 22, 2019

Conversation

jirkadanek
Copy link

Now easier to do when the matrix key is in place in .travis.yml.

Doing this also fixes the duplicated top level cache key in .travis.yml we had.

It appears that matrix is outdated syntax, and jobs should be preferred, travis-ci/docs-travis-ci-com#1500. The doc page https://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix uses matrix.include in the text and jobs.include in the yaml samples. Task for another time.

@jirkadanek jirkadanek self-assigned this Oct 17, 2019
@jirkadanek
Copy link
Author

@ganeshmurthy Is this what you've had in mind?

@ganeshmurthy
Copy link
Contributor

@jdanekrh can you please rebase this PR with master and simply add a file with no license so that the RAT check fails? This is what I would like to see. If the RAT check fails, there should be a red X mark next to the checkin. When I click on the X mark I should be taken to a page which shows all builds passing but only the RAT failing (this is already happening).

@jirkadanek jirkadanek force-pushed the jd_2019-10_rat_check_subbuild branch from 0fb488b to a9adf88 Compare October 17, 2019 19:44
@jirkadanek
Copy link
Author

@jirkadanek
Copy link
Author

jirkadanek commented Oct 17, 2019

And the PR here #593

@ganeshmurthy
Copy link
Contributor

@jdanekrh ok thanks, I will wait for the builds to complete and check back in an hour or so to see how things have worked out. Will keep you posted.

@codecov-io
Copy link

codecov-io commented Oct 17, 2019

Codecov Report

Merging #592 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #592      +/-   ##
==========================================
- Coverage   86.36%   86.35%   -0.01%     
==========================================
  Files          90       90              
  Lines       20484    20483       -1     
==========================================
- Hits        17691    17689       -2     
- Misses       2793     2794       +1
Impacted Files Coverage Δ
src/router_core/transfer.c 93.26% <0%> (-0.5%) ⬇️
src/router_core/connections.c 93.86% <0%> (-0.12%) ⬇️
src/message.c 90.99% <0%> (-0.1%) ⬇️
src/router_node.c 93.14% <0%> (+0.12%) ⬆️
src/iterator.c 89.51% <0%> (+0.16%) ⬆️
src/container.c 81.37% <0%> (+0.18%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2339c41...d2930ea. Read the comment docs.

@jirkadanek
Copy link
Author

@ganeshmurthy is Travis usually this slow during US work hours?

@ganeshmurthy
Copy link
Contributor

@ganeshmurthy is Travis usually this slow during US work hours?

@jdanekrh It has been slow the past couple of days but usually it is pretty good.

@gemmellr
Copy link
Member

The Travis rsources under /apache are shared for the entire ASF, so it depends what other projects have done, e.g if anyone is overly [ab]using the resources at a given time.

Though these are only very small jobs by comparison to many, it still helps not to use branches in the main repo simply for testing variants of changes. You can enable and run Travis on your own repo fork (which is served from a far larger resource pool, and so is typically very fast to start building) and push to / pull request against the main repo only when you think its ready.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants