Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Tracked Resource Set Provider for Bugzilla Workshop
Please refer to Building and running the TRS Adapter for Bugzilla sample
- Basic understanding of Resource Description Framework (RDF), Open Services for Lifecycle Collaboration (OSLC http://open-services.net/) and OAuth (http://oauth.net/core/1.0/)
This workshop will focus on the implementation of Tracked Resource Set (TRS) provider. It is intended to provide a foundation in the skills required for developing Tracked Resource Set Provider implementations.
As the TRS is based on OSLC, this workshop is designed as the supplement for the workshop OSLC Workshop and depends on its OSLC provider/consumer functions.
NOTE: There are two versions of the TRS workshop. One is based on a draft version of the OSLC Tracked Resource Set specification (see Tracked Resource Set Technical Preview) and another is based on the latest specification. Please refer to Building and running the TRS Adapter for Bugzilla sample
This workshop leads you to go through steps to enable Bugzilla as Tracked Resource Set Provider, which is an already-working implementation. This will make Bugzilla capable of sending Change Logs.
It is built on top of OSLC-CM compatible adapter which implements OSLC Change Management(CM) provider, it is recommended to try OSLC Workshop first. The basic understanding of CM provider is also required for this workshop.
Once you will complete this workshop, you will have the fundamental skill of :
- TRS service REST API implementation
- The extension of OAuth implementation
- OSLC resources definition for TRS