Is there a way to achieve this? We are trying to get all the changesets that are linked to an issue.
I tried with JIRA and FishEye APIs, but there seems to be no straight forward integration. One way that I see is to use the EyeQL but that also doesn't seem to be straight.
Any suggestions?
Community moderators have prevented the ability to post new answers.
Hi Nikhil,
The way the source tab in JIRA works seems to be what you want - it is achieved via Fisheye's rest api. See this page for the exact details http://docs.atlassian.com/fisheye-crucible/latest/wadl/fisheye.html#d2e132
The simplest way I can see is to make a GET request to http://your_fisheye_instance:port/context/rest-service-fe/changeset-v1/listChangesets?rep=your_repository_name&comment=JIRA-Key-123 and parse the output. This query is faster than the equivilent EyeQL query, but obviously, it does not have the advanced filtering capabilities of EyeQL (like date range and/or file name globbing for example).
Thanks Joe. This is closer to what I'm doing. But the catch is, the message might not always be just the Issue ID. hence I was using EyeQL to use matches.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We do it like this with rest:
fisheye/api/rest/query?rep=repoName&query=select%20revisions%20from%20dir%20%22/%22%20where%20comment%20matches%20%22issueKey%22
Without escaping that translates to
"fisheye/api/rest/query?rep=repoName&query=select revisions from dir "/" where comment matches "issueKey""
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is exactly the same that I'm also doing. But along with the to check if the file was deleted/added/changed we use /api/revision
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
nice to see, that there is a changeset-v1 service in the fisheye rest api. But why can't I find any word about this in the fisheye documentation???
Cheers
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you need to write a fisheye rest plugin yourself - or simply use svnkit to grab all the commits yourself and parse out the keys. both of which i have done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have a similar kind of requirement. I need to get all changesets and associated jira issue ids in a date range. First one is something we can do with EyeQL. But what about getting jira issue ids. Please note that I am new to crucible. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ganesh,
I don't think there is a way to get the Issue IDs from FishEye Rest. We have an SVN hook that asks for a valid JIRA ID while commiting. This JIRA id is then searched in the comments while finding the changesets from FishEye. Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Could you give me a more detailed explanation of what you wish to do and how you envisage it happening. For example, do you wish to drive the process my inside Jira or outside of Jira?
Regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can I confirm that you are using FishEye?
If yes, and you have linked the repository to the Jira project, then you should have a new tab on the Issue activity stream that shows all of the changesets associated with a specific issue.
I can give you a more detailed answer if this is not showing for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes Michael, we are using FishEye and we can see the source tab as well. We are basically trying to do this automatically through APIs to incorporate some sort of builds for only specific changesets for specific issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.