SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Building ontologies using Jenkins

gates avatar
gates
12 diapositives · 368 Views · Jul 18, 2014

Building ontologies using Jenkins. Changing requirements for ontology engineering. Original ontology build pipeline What pipeline? Life on the bleeding edge: Editors version and public version were identical Ontology editing has become ontology engineering

#building ontologies using jenkins #building ontologies using jenkins ppt #powerpoint #presentation
Building ontologies using Jenkins - slide 1
01 / 12Building ontologies using Jenkins
1 / 17

Télécharger la présentation

Building ontologies using Jenkins
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Building ontologies using Jenkins

  2. Changing requirements for ontology engineering • Original ontology build pipeline • What pipeline? • Life on the bleeding edge: Editors version and public version were identical • Ontology editing has become ontology engineering • We’re applying software engineering methodology • Automated test suites • Build process: classification using Elk, subset generation, obo/owl, derived files • Versioned releases

  3. Jenkins: a Continuous Integration Server • Continuous Integration (CI): • Builds, tests executed upfront • Concept from agile programming • We’re applying to ontology engineering • CI server: • Monitors source code repository • Integration tests triggered whenever developer commits changes • Configurable • Builds final product • Different solutions available • Jenkins, Hudson

  4. Example basic workflow • Local (e.g. EBI): • Developer makes local modifications using OBO Edit • Commits changes to SVN • (optionally) checks dashboard in web browser

  5. Example basic workflow • Local (e.g. EBI): • Developer makes local modifications using OBO Edit • Commits changes to SVN • (optionally) checks dashboard in web browser • Server: • Jenkins polls SVN • External commit triggers Jenkins to launch the build-go job (using Oort) • build-go job: • Load main ontology • Import: • disjointness axioms • Taxon constraints • Launch reasoner: Elk or hermit • Write reasoner report • Fail if unsatisfiable classes found • Run additional perl checks, ensure external xrefs resolve, etc

  6. Example basic workflow FAIL SUCCESS • Write reasoner report • If previous build was fail, Jenkins sends ‘service resumed’ email • Downstream jobs are triggered • (e.g. bigger integrated builds, deployment) • Jenkins sends email alert to mail list • GO editor debugs using Protégé 4, fixes using oboedit then recommits

  7. Current status • Jenkins is being used for validation • Invaluable for ontology developers • System relatively easy to set up and maintain • Release process still (mostly) run by central cron • Only running limited subset of checks • Missing classification step • Need to consolidate • Extend to annotations

  8. Release pipeline changes • Current: • Go_ext is direct nightly copy of editors file • Other files are filtered • No inter-ontology links • Immediate changes: • Editors file will include additional axiom tracking info • This will be removed from all release versions • Using obolibrary standard versioning scheme • New obo2owl conversion • Deprecate version that is built using MySQL pipeline • Encourage bioinformaticians to use this • http://wiki.geneontology.org/index.php/Ontology_Release_Files_Proposal

  9. Future changes • Editors version will eventually switch to OWL • Advantages • owl:imports • Direct use of reasoning • Disadvantages • Protégé lacks many OE features

  10. Future changes • Editors version will eventually switch to OWL • Advantages • Owl:imports • Direct use of reasoning • Disadvantages • Protégé lacks many OE features

  11. Thanks • Heiko • Seth • Sebastian Bauer (Charite.de) • Ontology editors