Search Mailing List Archives
jane at ebi.ac.uk
Wed Dec 21 07:27:58 PST 2011
Nice! I love the little weather report icons. GO is looking pretty sunny
right now, despite my best efforts :-)
Can we configure it to send email alerts when the GO build fails? I see
you can get an RSS for fails, but that's for all the ontologies.
On 19/12/2011 19:52, Chris Mungall wrote:
> We're experimenting with using Jenkins - a continuous integration service typically used for software builds - with ontologies. You can keep an eye on it here:
> You'll be interested in the "build-go" job (and perhaps also "build-go-xp-chebi")
> You'll see that both have the dreaded red ball right now - this means the last build failed. GO also has a storm cloud over it meaning the last few builds failed. You want a nice bright sunny disposition, like PO.
> Why is the build failing? For GO it's because Oort checks to see if any two classes are inferred to be equivalent - we still have the protein-kinase regulation by problem. Once you commit the fix, check back with Jenkins - you should see the blue ball. There are also problems with go_xp_chebi& the "cellular X" classes.
> (unfortunately there is a lag with CVS - when we switch to SVN the build will be triggered almost automatically)
> You can see the last commit here:
> it's all hooked to to cvs, so it's a nice way of going back and tracking down problems.
> Commit a few more non-problematic changes and GO should start to get sunny.
> Note that the results of the Oort build don't go anywhere yet - this is just for you to QC check.
> We'll be folding in more QC checks - the idea is that this will replace the daily cron, and can ultimately be used to deploy the derived files too.
> go-ontology mailing list
> go-ontology at lists.stanford.edu
More information about the go-ontology