Unable to get change set using crucible REST API call.

Ganesh Virupakshan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 5, 2013

crucible_uat/rest-service/repositories-v1/simple-jar-demo works fine

<site>:8070/crucible_uat/rest-service/repositories-v1/change/simple-jar-demo?FEAUTH=<Authkey>

throws an exception or a 404.


I am did not find meaningful examples for the usage of the call.

If an example for usage of /rest-service/repositories-v1/changes/{repo}/{path:.*$}?oldestCsid=<value>&includeOldest=<value>&newestCsid=<value>&includeNewest=<value>&max=<value> is provided it will be useful.


what should be used in the path. The path in the output of the first command does not work..

When any of the suggested (changes, Browse, history) is used the error repository not found appears.

1 answer

1 accepted

0 votes
Answer accepted
lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 18, 2013

Hi Ganesh,

The rest-service/repositories-v1/change, rest-service/repositories-v1/changes, rest-service/repositories-v1/content resources in Crucible are only relevant for repositories that are managed by a Crucible SCM plugin.

For repositories managed natively, you will need ot use the FishEye resources - you'll probably want to use the revisionData-v1 ones: https://docs.atlassian.com/fisheye-crucible/latest/wadl/fisheye.html#d2e4.

Best regards,

Łukasz Pater

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events