revi-archive/Teamcity-Phabricator-Plugin
1
0
Fork 0
Code Activity
Archiving just in case where repo gets deleted
18 commits 1 branch 0 tags 147 KiB
Java 83.7%
PHP 16.3%
Find a file
Steven Cooney cefb59b73a Remove BRANCH_NAME Parameter 
In the past TeamCity allowed us to spoof the branch we ran a build configuration on. We were going to utilise this with each differential revision having its own TeamCity branch. However in a recent change (post 2018.2.2) branches specified in builds must have a corresponding VCS branch otherwise the build is marked as failed. We therefore don't need a branch name within the teamcity plugin.

We are still passing through the REVISION_BUILD to allow us to display the snapshot within TeamCity.
2019-06-05 11:22:53 +01:00
Harbormaster-Teamcity-Plugin Remove BRANCH_NAME Parameter 2019-06-05 11:22:53 +01:00
Teamcity-Phabricator-Plugin Remove BRANCH_NAME Parameter 2019-06-05 11:22:53 +01:00
.gitattributes Add .gitattributes file 2019-06-03 11:47:37 +01:00
.gitignore Add Basic TeamCity Phabricator Plugin 2019-05-30 13:53:15 +01:00
README.md Send Build Result to Harbormaster 2019-06-03 11:23:30 +01:00

README.md

Splint

X-Lab's Linting Spine

Things

This repository holds the plugins created to link together our internal systems. The original premise to link Phabricator, TeamCity and SonarQube to enable linting on differential reviews.

Below are the plugins:

  • Harbormaster-Teamcity-Plugin
  • Teamcity-Phabricator-Plugin
  • SonarQube-Phabricator-Plugin

Harbomaster-Teamcity-Plugin

The harbormaster plugin allows us to trigger a build configuration within TeamCity as part of a harbormaster build plan.

The plugin requires:

  1. TeamCity URI
  2. Build Configuration to trigger a build for
  3. TeamCity access token to authenticate with the server

To deploy simply drag the contents of the folder to src/extensions/ on the Phabricator instance and then restart the application.

Teamcity-Phabricator-Plugin

The teamcity plugin comprises of server and agent plugins for teamcity.

Server

The server plugin monitors builds with the phabricator feature enabled waiting for builds to finish and notify phabricator.

Once build is triggered from phabricator using Harbomaster-Teamcity-Plugin and the phabricator build feature is configured on the build configuration then the server plugin will wait and listen for the build to finish before reporting the result back to harbormaster to be displayed in phabricator.

Getting Started

Harbormaster-Teamcity-Plugin No building is needed for for the harbormaster plugin just dev away and copy the files into the src/extensions folder with your phabricator instance

Teamcity-Phabricator-Plugin

You will need to move in to the Teamcity-Phabricator-Plugin/ folder:

  • To build the plugins (server and agent) just run: mvn package

By default the teamcity plugin is equipped with teamcity-sdk-maven-plugin which allows for a local instance of teamcity with debugging capabilities. See their documentation for how to use: https://github.com/JetBrains/teamcity-sdk-maven-plugin

Useful Links