Travis and private Nexus server about cedar-project HOT 2 CLOSED

Response from Travis (via Graham):

[...begin quote...]
Thanks for reaching out and sorry for this issue.

I think I know the problem. Travis CI executes some default steps "under the hood" for Java projects. In the "install:" steps, we call "mvn install -DskipTests=true". This is what we see in your build log and this call doesn't have your Maven settings file thus that's why it fails.

If you don't need this default step (i.e. mvn install), you can add the following to your .travis.yml file:

install: true

Else, if you need it, you can add the following:

install: mvn install -DskipTests=true --settings .m2/travis-settings.xml

Can you try one of these suggestions and let us know if it helps?

Please send us the resulting build log(s) and we will continue from there.

Thanks in advance and have a great day!

-- Dominic.
[...end quote...]

from cedar-project.

We now have commercial version. Graham has opened help ticket. Here is problem description:

I have a repo called cedar-parent (https://github.com/metadatacenter/cedar-parent) that has has no dependencies. When I push to the ‘develop’ branch I successfully deploy a SNAPSHOT POM artifact (0.9.0-SNAPSHOT) to our Nexus server (http://nexus.bmir.stanford.edu/#nexus-search;quick~cedar) from the Travis build server.

My second repo called biosample-exporter (https://github.com/metadatacenter/biosample-exporter) depends on the generated parent artifact but, as mentioned, Travis seems to completely ignore my Maven configuration pointing to our Nexus server so does not find the artifact.

Here is the configuration file for the biosample-exporter:

https://github.com/metadatacenter/biosample-exporter/blob/develop/.m2/travis-settings.xml

(Note that all examples above are on the ‘develop’ branch.)

Here is the error:

https://travis-ci.org/metadatacenter/biosample-exporter

from cedar-project.