Automate FishEye

What HumDay can do in FishEye

3 documented operations change something in FishEye.

• POSTRetrieve a list of reviews for a changeset in a given repository./rest-service-fe/search-v1/reviewsForChangeset/{repository}
• POSTRetrieve a list of reviews for each given changeset in a given repository./rest-service-fe/search-v1/reviewsForChangesets/{repository}
• POSTRetrieves detailed information about a set of changesets in a repository, designed to be used with the FishEye commit graph/rest-service-fe/commit-graph-v1/details/{repository}

What HumDay can read from FishEye

These are the operations a schedule or a trigger can watch.

• GETExecute a query across repositories./rest-service-fe/search-v1/crossRepositoryQuery
• GETList all the repositories./rest-service-fe/repositories-v1
• GETExecute a FishEye query against a specific repository./rest-service-fe/search-v1/query/{repository}
• GETExecute a FishEye query (that contains a "return" statement) against a specific repository./rest-service-fe/search-v1/queryAsRows/{repository}
• GETGet a list of information about files and directories in a path./rest-service-fe/revisionData-v1/pathList/{repository}
• GETGet a list of the file revisions for a specific path./rest-service-fe/revisionData-v1/pathHistory/{repository}
• GETList of changesets from a repository./rest-service-fe/changeset-v1/listChangesets
• GETfinds slice data the query/rest-service-fe/commit-graph-v1/slice/{repository}
• GETGet a list of changesets on a repository./rest-service-fe/revisionData-v1/changesetList/{repository}
• GETGet the information about a repository./rest-service-fe/repositories-v1/{repository}
• GETRead repository/rest-service-fe/revisionData-v1/revisionInfo/{repository}
• GETRead repository/rest-service-fe/revisionData-v1/revisionTags/{repository}
• GETRead csid/rest-service-fe/revisionData-v1/changeset/{repository}/{csid}

How automating FishEye works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live FishEye account.
4. Grant access, then go live. You approve the specific FishEye operations it may use — and only those.

Automate FishEye with these

• OData for namespace microsoft.graph11412 operations
• GitHub811 operations
• Atlassian The Jira Cloud platform474 operations
• Gitlab358 operations
• JIRA 7.6.1324 operations
• Appcenter App Center Client323 operations
• Gitea .321 operations
• Bitbucket292 operations
• Keycloak Admin281 operations
• Apple App Store Connect251 operations
• Files.com222 operations
• Vmware vRealize Network Insight Reference161 operations

Categories

• Developer tools

Questions about FishEye automation

Can HumDay connect to FishEye?

Yes. HumDay reads FishEye's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 16 operations are documented.

Do I need to write code to automate FishEye?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your FishEye account.

What can HumDay do in FishEye?

3 of the 16 documented operations change something in FishEye, and 13 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my FishEye account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to FishEye is held behind that approval.

Where this came from

The operations above are read from a published API description for FishEye at docs.atlassian.com/fisheye-crucible/latest_backup/wadl/fisheye.wadl. Descriptions are the provider’s own words, not ours. Last published 2018-11-21.