...
- In the Select Macro form, select the TeamCity Project macro.
- Select the appropriate TeamCity instance and the project, which data about project activity is retrieved from.
- Click Insert.
- Save the page.
Once you have saved the page, you will see the table with the following information:
- # - number of the build configuration;
- Results - results of the build completion;
- Changes - the list of changes added into the build and the user who added these changes;
- Started - date and time when the build was started;
- Duration - duration of the build creation.
You can click the entries in the Results column, to proceed to the build results in TeamCity instance.
...
| Parameter Name | Required | Default | Parameter description and accepted values |
|---|---|---|---|
project | yes | n/a | Name of the project, which activity data Project name or project ID (depending on add-on version) which build activity is fetched for. All projects are retrieved from TeamCity server. |
server | no | Uses value of the default application link with TeamCity serverBy default, the primary application link is selected. If the primary application link is used, this parameter is not available in the storage format. | Name of the application link used for integration with TeamCity server. |
macro-id | Automatically assigned | ID of the macro on the page. | Confluence assigns ID of the macro automatically. |
Storage format example
Below you can find the example of storage format. The selected application link is not indicated anyhow in the storage format.
| Code Block | ||
|---|---|---|
| ||
<p><ac<ac:structured-macro ac:name="teamcity-project" ac:schema-version="1" ac:macro-id="4e39a1cc-222b-4e85-9ba7-fffa09ed2be8"> <ac:parameter ac:name="projectserver">Amazon API client<>TeamCity StiltSoft</ac:parameter> <ac:parameter ac:name="project">SmartAttachments</ac:parameter> </ac:structured-macro></p>macro> |