Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
cmungall opened this issue Mar 24, 2013 · 4 comments
Open

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

cmungall opened this issue Mar 24, 2013 · 4 comments

Comments

@cmungall
Copy link

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
Copy link
Owner

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

@cmungall
Copy link
Author

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
Copy link

@ewilderj ewilderj self-assigned this Aug 11, 2017
@ewilderj
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants