Hey Gus
> -- Does anyone else attempt to make queries against Jenkins of this sort?
For scientists and researchers it's extremely important to be able to store,
retrieve and search metadata. We have an idea of how to extend the metadata
plug-in [1] (probably via several Pull Requests), so that it provides the
following features:
- Automatically collect metadata of Jenkins items (jobs, builds, artifacts,
etc)
- Let users collect extra metadata with builders/publishers/etc. For
instance, Cell Profiler [2] has a metadata module that can collect metadata
from file names. So a file named TRIAGE-CP001-20151120035003.txt could generate
metadata such as {code: "CP001", date:"2015-11-20 03:50:03UTC"} if the user
selected a File Name Metadata Collector
- Store the metadata in an embedded triple store (Jena) using an ontology
created for Jenkins, which will import other ontologies such as DC, W3C Prov,
etc.
- A search module and interface, that supports both Lucene (via jena-text
module) and SPARQL.
The idea behind it is to have a pre defined ontology, which will ease learning
about the data model used for the metadata, and transform Jenkins into a SPARQL
endpoint. That way you'll be able to even query remote Jenkins for metadata too.
We have had some discussions about it already, but I will try to have a working
version in the following months. As an example, this question "Show me all the
jobs that use this set of slaves" could be answered by a SPARQL query similar
to this one (syntax not tested, just a quick example):
PREFIX jenkins: http://
SELECT ?jobs
WHERE {?jobs a jenkins:Job .?jobs jenkins:hasSlave ?slave .?slave
jenkins:slaveName ?slaveName .?slaveName IN ('...')
}
> -- Has anyone used the Metadata plugin, or some other plugin or home-grown
> solution to solve this issue?
I used it and had a look at the code, and I feel like I can extend it to
support the ontology and SPARQL. @Ioannis used it too, maybe he can give his
feedback on it too.
This is something that is necessary for experiments and scientific pipelines.
It would be interesting if we could in some way join forces to work on it :-)
Cheers
[1] https://groups.google.com/forum/#!topic/biouno-developers/2u1dQ0uX5RM[2]
http://www.cellprofiler.org/CPmanual/Metadata.html
From: Gus Reiber <[email protected]>
To: [email protected]
Sent: Monday, March 30, 2015 1:29 PM
Subject: Grouping jobs by project, status, or attributes other than folder
location
Hey all, I currently using the folder plugin to group my projects together,
but am finding that it is difficult to get cross-cutting job
status/stage/attribute views of the jobs contained within those folders. Here
are a set of examples of the sorts of queries I would like to be able to
generate views based upon:
- Show me all the jobs related to a particular project (for me, this is
typically the folder)
- Show me all the jobs that deploy to "production" (many folders might have
a job that does this)
- Show me all the jobs that use this set of slaves
- Show me all the jobs triggered by a submission from 'John Dowe' (I can
never trust that J.D., he is all over the place)
- Show me all the jobs tied to this repository
The metadata plugin seems like it is geared towards this
issue:https://wiki.jenkins-ci.org/display/JENKINS/Metadata+plugin
....so I guess I have two questions:-- Does anyone else attempt to make queries
against Jenkins of this sort?-- Has anyone used the Metadata plugin, or some
other plugin or home-grown solution to solve this issue?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/3f9c0f9e-abb0-4092-804e-489f505be2ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/2095356288.690480.1427744927153.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
