search

ewilderj / doap

RDF schema for describing software projects
https://github.com/ewilderj/doap/wiki
Apache License 2.0
270 stars 58 forks source link

Connecting a project to a Continuous Integration (CI) server #15

Open cmungall opened 11 years ago

cmungall commented 11 years ago

I would like to be able to describe a relationship between my projects and URLs for Jenkins jobs that build and test these projects.

ewilderj commented 11 years ago

Can you specify the metadata required for Jenkins or other CI servers?

cmungall commented 11 years ago

Not sure if this is overmodeling, but we probably want separate classes for a server instance and a job on a server. The URL of the job is the more important of the two.

I think a single class 'continuous integration server job' and a property that connects either a file release or a project to a job is sufficient for now.

Some people may want to record the server type (e.g. Jenkins, Cruise Control), but this list should be fairly open ended so I wouldn't recommend making a class for each.

It may be useful to categorize jobs according to their purpose - e.g. steam test, nightly build, ... this also could be quite open ended. Entering a rdfs:comment for the job may be sufficient.

fernando-silva commented 11 years ago

See OSLC Automation Specification (http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.0/#Introduction)

ewilderj commented 5 months ago

I am going to mark this as help wanted, as I would love a few more potential users to look at the right model.