Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,359,908
Community Members
 
Community Events
168
Community Groups

Unable to get change set using crucible REST API call.

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 Sep 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
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

177 views 1 6
Read article

Atlassian Community Events