[#CIB-1110] Pulse Remote API Enhancement - Build Artifacts List

Pulse

Pulse Remote API Enhancement - Build Artifacts List

Created: 14/Jun/07 09:26 PM Updated: 03/Aug/07 05:40 AM

Component/s:

Remote API

Affects Version/s:

1.2.29

Fix Version/s:

1.2.34

Description

« Hide

It would really be helpful if the BuildResult type also included an array of artifacts from the build, such as an array of links to the artifacts produced.

Another helpful addition would be for the BuildResult to include the build revision as well.

Thanks!

-Matt

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

jason - 17/Jun/07 03:35 PM

Hi Matt,

Fair enough request. We might get a chance to squeeze this in at some point in 1.2, otherwise in 2.0.

[ Permlink | « Hide ]

jason - 20/Jul/07 08:34 AM

Raised and resolved the inclusion of the build revision separately in ~~CIB-1145~~.

[ Permlink | « Hide ]

Matt Spaulding - 20/Jul/07 11:25 PM

Thanks!

You guys are awesome :)

[ Permlink | « Hide ]

jason - 03/Aug/07 05:37 AM

Added in change 3592.

[ Permlink | « Hide ]

jason - 03/Aug/07 05:40 AM

The new function is getArtifactsInBuild(token, projectName, id), and it returns an array of structs, one struct for every artifact in the build. The struct contains:

- the stage name
- the command name
- the artifact name
- a permalink for the artifact

The permalink is of the form described on this page:

http://confluence.zutubi.com/display/pulse0102/Pulse+Url+Scheme

It is actually a fragment of a full URL., starting with "display" and ending with the artifact name. To use this link, prepend the base URL for Pulse and append the path of the file within the artifact that you want to access. If the artifact is an HTML report, appending is not necessary (Pulse will take you to the index file for the report).