chek-in&deliver accept change-set build run-test changeset discard changeset java API
I am newbie and have read re-portable API,OSLC or java API to create requirement document etc.
I want to :
but am a bit confused with the huge Documentation, where to start or check example to achieve the goal, any tip/link/sample is appreciated.
|
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Jun 07 '22, 2:49 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Neither the Reportable REST API, nor the OSLC API (which is not a Java API) provide any SCM operations. The Reportable REST API for EWM only supports to read information. The OSLC API is only for work items/change management.
Looking at the list 1,2,3 would be best implemented as some kind of build using the build API and the SCM Command line. The step 4 does not seem to make a lot of sense.
I would suggest to first come up with a consistent description what the business case is and what the result of the operation is. Describe the desired result and how the manual steps would be to get there. Then you can start asking for APIs, if it is impossible to do that in the tool.
Comments Actually the scenario for the use case is like the 4 steps. yes step 4 make no sense (as the last approved changes will be written to repository) but assume it is the case. Idea is to automate it using Rest Api, command line, plain java API etc. I guess all the steps can be done in EWM except number 3 which carry out by running testcase script in jazz App. I'll try go through Build API and scm command as you suggested and then will be back if needed, Thank you
The scenario does not make any sense in many aspects. There is no use case or business case that explains what this is supposed to achieve. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.