Archiving just in case where repo gets deleted
0dbf491410
Using TeamCity plugin template create an empty client and server plugin which will report back to phabricator |
||
---|---|---|
Harbormaster-Teamcity-Plugin | ||
Teamcity-Phabricator-Plugin | ||
.gitignore | ||
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:
- TeamCity URI
- Build Configuration to trigger a build for
- 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.
Useful Links
- https://confluence.jetbrains.com/display/TCD10/Web+UI+Extensions
- http://javadoc.jetbrains.net/teamcity/openapi/current/jetbrains/buildServer/serverSide/BuildServerAdapter.html
- https://github.com/JetBrains/teamcity-sdk-maven-plugin/wiki/Developing-TeamCity-plugin
- https://www.quali.com/blog/teamcity-plugin-development-journey/
- https://plugins.jetbrains.com/docs/teamcity/plugin-development-faq.html
- https://plugins.jetbrains.com/docs/teamcity/getting-started-with-plugin-development.html