search

ContentMine / meta

A repository in which to file and fix meta issues (issues affecting more than one ContentMine repo or project)
0 stars 0 forks source link

Continuous Integration: broken builds #4

Open ghost opened 7 years ago

ghost commented 7 years ago

Several of @ContentMine's GitHub repositories have Travis CI instances attached that currently have failing builds.

With any luck, fixing #1 will solve this. If it doesn't, then we need to investigate further.

tarrow commented 7 years ago

Hehe; I wish fixing #1 would do.

Unfortunately the problem is conceptually more difficult. In short we need to have a maven repo were we put the built artefacts that can be used by the CI when it needs to get a dependency for a project "down the stack"

Currently we have a hacked together maven repo (it is the one hosted at https://github.com/contentmine/cm-pom/tree/mvn-repo). This is "cool" but also not great. We should be using a maven repo that is syndicated into maven central.

PMR has made an account following this: http://central.sonatype.org/pages/ossrh-guide.html to start the process.

We then need the CI to deploy to this repo so that other CI processes for builds "down the stack". I worked on trying to get this sorted for a day or so. We could have a teleconference about setting this up if you like. I really want it to work but it was always talking too much time.

ghost commented 7 years ago

@tarrow wrote:

Hehe; I wish fixing #1 would do.

Unfortunately the problem is conceptually more difficult. In short we need to have a maven repo were we put the built artefacts that can be used by the CI when it needs to get a dependency for a project "down the stack"

As discussed when you visited, an adequate CI would build all the dependencies and cache them in its own .m2 local Maven repository. Having read more over the weekend about the travis-ci.org hosted service, I am hopeful that it can do this.

Currently we have a hacked together maven repo (it is the one hosted at https://github.com/contentmine/cm-pom/tree/mvn-repo). This is "cool" but also not great.

Agreed

We should be using a maven repo that is syndicated into maven central.

For deployment, yes. For CI, I'm not so sure.

PMR has made an account following this: http://central.sonatype.org/pages/ossrh-guide.html to start the process.

AFAIK, that's on the back-burner for now.

We then need the CI to deploy to this repo so that other CI processes for builds "down the stack". I worked on trying to get this sorted for a day or so. We could have a teleconference about setting this up if you like. I really want it to work but it was always talking too much time.

Thanks for the offer, and for your work on this :)

@petermr has asked me to look into CI, starting with CI for https://github.com/ContentMine/euclid and https://github.com/ContentMine/svg . So, am assigning this bug to me. Will contact you if need assistance.

ghost commented 7 years ago

Re-opening, as issue has not been resolved and seems to have been closed erroneously. (Cf. https://github.com/ContentMine/meta/issues/5#issuecomment-308723497 .)