459

TeamCity Integration for Confluence

by StiltSoft Labsfor Confluence Server 3.5 - 6.12.2

Unsupported

Unsupported

Unsupported

Free app

View TeamCity build activity in Confluence and Jira with ease

View TeamCity build activity in Confluence and Jira with ease

View TeamCity build activity in Confluence and Jira with ease

Add macros showing TeamCity build data

Show TeamCity data from any server and any project

View TeamCity build activity in your Jira

Insert TeamCity Activity, Agents, Build Configuration and Project macros on Confluence pages.

Set application links, projects (inluding nested) and build configurations for showing TeamCity data you need.

Try TeamCity Integration for Jira to be aware of all TeamCity activities during development. ☛ Learn more

More details

TeamCity Integration for Confluence creates the link between your continuous integration servers and team collaboration platform. You and your team get options to view or follow the recent TeamCity activity while planning or collaborating on Confluence pages or transition to TeamCity skipping authentication.

Get benefit from the following features and capabilities:

View TeamCity activity for all projects with information about associated builds;
Track build results and view information about build start and its duration;
Support for multiple TeamCity instances with simultaneous data retrieval from each of them;
Seamlessly proceed to TeamCity to find out details on build configuration and build results;
Easily browse build change log with description of added modifications;
Quickly integrate Confluence and TeamCity servers with application links.

You can also try TeamCity Integration for Jira for viewing progress on your projects or individual issues.

Reviews for cloud

(4)Sign in to write a review

by Kenneth Rainey on 2014-04-14

This plugin references builds by name rather than the unique ID. consequently, if you have two projects called 'Prod,' for example, the plugin will always pull in details for the first, irrespective of which project you've selected in the macro editor. TeamCity generates a unique ID for each build configuration, and that is what should be used to reference the build configuration. I'm not sure who had the idea to use name for this plugin, but it's a disastrous design decision, as it renders the plugin unusable.

5 out of 5 found this review helpful

Was this review helpful?Yes No

by Michał Wieczorek on 2014-02-27

Nice, but not working for anonymous users.

Was this review helpful?Yes No

Reviews for server

(4)Sign in to write a review

by Kenneth Rainey on 2014-04-14

This plugin references builds by name rather than the unique ID. consequently, if you have two projects called 'Prod,' for example, the plugin will always pull in details for the first, irrespective of which project you've selected in the macro editor. TeamCity generates a unique ID for each build configuration, and that is what should be used to reference the build configuration. I'm not sure who had the idea to use name for this plugin, but it's a disastrous design decision, as it renders the plugin unusable.

5 out of 5 found this review helpful

Was this review helpful?Yes No

by Michał Wieczorek on 2014-02-27

Nice, but not working for anonymous users.

Was this review helpful?Yes No

Reviews for Data Center

(4)Sign in to write a review

by Kenneth Rainey on 2014-04-14

This plugin references builds by name rather than the unique ID. consequently, if you have two projects called 'Prod,' for example, the plugin will always pull in details for the first, irrespective of which project you've selected in the macro editor. TeamCity generates a unique ID for each build configuration, and that is what should be used to reference the build configuration. I'm not sure who had the idea to use name for this plugin, but it's a disastrous design decision, as it renders the plugin unusable.

5 out of 5 found this review helpful

Was this review helpful?Yes No

by Michał Wieczorek on 2014-02-27

Nice, but not working for anonymous users.

Was this review helpful?Yes No

Cloud Pricing

Server Pricing

Data Center Pricing

Basic support resources are available for this app.

Vendor support resources

Find out how this app works.

Community discussions connect you to the vendor and other customers who use this app.

See existing Q&A in Atlassian Community Ask a question in the Atlassian Community

Atlassian-hosted discussions connect you to other customers who use this app.

Versions

Version 1.5.0 • Confluence Server 3.5 - 6.12.2 • Released 2016-11-11

Summary

Support for nested projects and access for anonymous users

Details

New in this release

Added a capability to select nested projects.
Added support for Confluence 6.0.
Updated the icon for the add-on.
Added the diagnostics message when selecting data in macros in case of the incorrectly configured application link.
Added a capability to show the build data outputted by TeamCity macros to anonymous users in Confluence.
Added the automatic hiding of archived projects when configuring TeamCity macros.

Fixed in this release

Resolved the compatibility issue with TeamCity 10 when fetching data from projects with features.
Resolved the issue with placing Confluence links instead of TeamCity links when viewing the list of changed files.
Resolved the issue with fetching incorrect data for TeamCity projects because of using project names instead of project ID's.
Resolved the markup issue when showing TeamCity Activity table on the page

Installation

Log into your Confluence instance as an admin.
Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
Click Find new apps or Find new add-ons from the left-hand side of the page.
Locate TeamCity Integration for Confluence via search. Results include app versions compatible with your Confluence instance.
Click Install to download and install your app.
You're all set! Click Close in the Installed and ready to go dialog.

To find older TeamCity Integration for Confluence versions compatible with your instance, you can look through our version history page.