My notes: - Metadata is like a tree data structure, and typed - you see types like "boolean", "number" as the built-in types
- validator?
- Wants to improve the UI a bit
- Table control?
- integrate search into Jenkins' search?
- build also has metadata
(inherits
- you sure Metadata should be an interface?
- descriptive metadata generation
Cause, Builder, JobProperty, etc.
- database plugin integration?
- better build history view, with filtering, etc.
"Builds" page is needed
- lucene as a library plugin?
- view job filter?
- metadata contributor for nodes?
- rsandell will try to be at FOSDEM
2012/12/14 Sandell, Robert <[email protected]>
> Hello all Jenkins devs!****
>
> ** **
>
> On the office hours next week Tomas W and I have the privilege of hosting
> a session on the metadata plugin [1], and specifically on how you can
> integrate support for it in your own plugins.****
>
> The announcement from Kohsuke is at [2].****
>
> ** **
>
> More than a year ago, I had an idea that it would be really great if jobs
> and builds in Jenkins had some metadata attached to them in some kind of
> uniform format. That way, it would be a lot easier for an administrator or
> user to find jobs related to the same product, or which builds have failed
> for the latest version of our internal Android SDK – to make Jenkins able
> to answer ad-hoc questions similar to a database. And if we could make it
> pluggable, so other plugins could contribute that data, we might be able to
> answer our QA team’s questions about how many findbugs issues there are in
> total on all applications on a particular product branch; something we
> today only could make a guesstimate on using the names of the jobs in
> Jenkins – but that would not be very accurate.****
>
> ** **
>
> So my plan for Wednesday 19 December is to show you a bit on how the
> plugin looks at the moment in “vanilla mode”, and then make a live
> implementation to make the Gerrit Trigger plugin a metadata contributor to
> show you how easy it is, and to give you some tips ´n tricks.****
>
> ** **
>
> Then, if there is time (and I think there will be), I’ll show you some of
> the more advanced integration that is done in the external resource
> dispatcher plugin [3]. ****
>
> ** **
>
> I hope we can get some fruitful discussions about these two plugins and on
> what might be needed to change/enhance in them before their official
> release.****
>
> ** **
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/Metadata+plugin ****
>
> [2] http://jenkins-ci.org/content/office-hours-next-week-metadata-plugin**
> **
>
> [3]
> https://wiki.jenkins-ci.org/display/JENKINS/External+Resource+Dispatcher**
> **
>
> ** **
>
> ** **
>
> *Robert Sandell***
>
> Software Tools Engineer****
>
> SW Environment and Product Configuration****
>
> Development Environment****
>
> ****
>
> Sony Mobile Communications****
>
> Tel: +46 (0)10 80 12721****
>
> sonymobile.com****
>
> ****
>
> [image: SONY make.believe]****
>
> ** **
>
> ** **
>
--
Kohsuke Kawaguchi
<<image001.jpg>>
