-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test external projects again #169
test external projects again #169
Conversation
3c90548
to
07aa192
Compare
Hm. What sort of repositories are you looking for? Would anything do, or are we trying to cover specific testing scenarios fi? |
The more complicated ones..
|
93c5557
to
2c788da
Compare
1e2ff4b
to
4815e4d
Compare
e071c3f
to
3b9e651
Compare
3b9e651
to
79e0b85
Compare
I have remove @130s: I'd like to merge it soon, please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Introducing _EXTERNAL_REPO
is a good idea as it clarifies the jobs that are using repositories external from industrial_ci
repo.
Just curious, what does wrap test
mean?
It's a wrapper for the actual travis test that adds the external repo feature. |
This PR introduces a new feature for internal-use.
it can be used to run
industrial_ci
for external repositories, just as travis would do.That's why I have introduced an internal script
_wrap_test.sh
.@Jmeyer1292, @shaun-edwards, @gavanderhoorn, @ipa-fxm, @130s: Do you have some suggestions for other candidates?
In the end it should be a nice mix of ~5 external repos.