Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Travis CI: Build and test all targets affected by commit range#101

Draft
ChrisCummins wants to merge 5 commits intomasterfrom
feature/travis_ci
Draft

Travis CI: Build and test all targets affected by commit range#101
ChrisCummins wants to merge 5 commits intomasterfrom
feature/travis_ci

Conversation

@ChrisCummins
Copy link
Copy Markdown
Owner

@ChrisCummins ChrisCummins commented Feb 13, 2020

This uses Bazel's CI script and Travis' COMMIT_RANGE to ensure that all targets affected by a patchset are built and tested.

This is a huge improvement over having a "dummy" Travis config in the core phd project and then project-specific configs for exported projects like labm8 / ProGraML / clgen, etc.

@ChrisCummins ChrisCummins force-pushed the feature/travis_ci branch 5 times, most recently from 5100118 to 2ef7ab6 Compare February 19, 2020 16:42
@ChrisCummins ChrisCummins force-pushed the feature/travis_ci branch 2 times, most recently from 7301071 to 2408ac7 Compare April 26, 2020 10:41
This uses Bazel's CI script to build and run tests on targets affected
by the commit range that Travis CI is testing for.

Signed-off-by: format 2020.01.16 <github.com/ChrisCummins/format>
Signed-off-by: format 2020.01.21 <github.com/ChrisCummins/format>
Signed-off-by: format 20.02.05 <github.com/ChrisCummins/format>
Signed-off-by: format 20.02.05 <github.com/ChrisCummins/format>
Signed-off-by: format 20.02.05 <github.com/ChrisCummins/format>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant