Use unreleased packages with Travis

We’re working on a series of packages, with one core package and a series of companions adding some functionalities. The core package is not currently released, but we would like to use it for testing of the other packages on Travis.

Here’s the thing: even though it builds and tests fine on our machines, Travis wants nothing to do with it.

Here’s the log: Travis CI - Test and Deploy Your Code with Confidence

Has any of you done something similar? What’s the secret?

Why are you not using the default script (i.e. not specify a script: at all)?

2 Likes

Well I’ll be damned, it’s working. I don’t know why I was not using the default script (probably a leftover from something else).