support for travis-pro

[licarth]

Currently this plugin only supports travis-ci, would be nice if it supported travis-pro, and probably not too big of a change.

[v4ngelo]

I was able to fix this problem with the following configuration. Branch, committer info and commit messages seem to be correct:

<plugin> <groupId>org.eluder.coveralls</groupId> <artifactId>coveralls-maven-plugin</artifactId> <version>4.1.0</version> <configuration> <repoToken>${env.coveralls_repo_token}</repoToken> <serviceName>travis-pro</serviceName> </configuration> </plugin>

[trautonen]

I guess Travis Pro works like pretty much the same way as any private CI would work with the plugin. This means that you have to explicitly provide repoToken like @v4ngelo said.

If someone creates a pull request or could tell if there's way to configure Travis Pro automatically, I'm happy to do that.

[jgangemi]

i just encountered this myself and i'm not sure it's possible to auto-configure the pro account which is potentially going to be a larger issue now that all open source projects are being migrated over.

i think @v4ngelo has the best approach right now, the token just needs to be encrypted w the travis client. make sure you specify --pro otherwise the wrong api endpoints are used.