On 08/09/2013 01:58 PM, Samuel Padgett wrote:
On Friday, August 9, 2013 4:12:34 PM UTC-4, Kohsuke Kawaguchi wrote:
I am bit overwhelmed at the wall of text in that spec, but I suppose
this is about making Jenkins implement a set of REST APIs so that
Eclipse can talk to different servers without individually implementing
an adapter?
Yes, that's it. Eclipse or any OSLC Automation consumer. Here's a more
accessible introduction, although it's still a draft:
http://open-services.net/wiki/automation/OSLC-Automation-Primer-2.0/
I see a few interesting scenarios:
Thanks. From my point of view, I'd love to see the HTTP transcript of
some communications to get the sense of the protocol. I suspect other
people considering to implement it would be in the same situation, if
they are not familiar with OSLC.
(1) Jenkins as an automation provider
Automation consumers make requests to kick off builds in Jenkins and see status.
For instance, I'm in my IDE and want to request a build.
Right.
(2) Jenkins as an automation consumer
Jenkins makes an automation request when a build completes, for instance, to
kick off automated tests in another tool.
I didn't think about this, but you are right.
If someone (you?) is interested in driving the implementation but need
help for Jenkins expertise, we'd be happy to help.
Thanks, I might be taking you up on that.
- Sam
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
