JetBrains / JetBrains/teamcity-git

What are the intentions of this repository?

Open
#5 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
14
Forks
10
PR merge metrics
No merged PRs in 30d

Description

Hi,

I have previously modified this plugin to add some local customization, and I am now trying to update that work so we can also upgrade our TeamCity instance.

However, I am no longer able to build the repository from a clean checkout.

Could you clarify whether this repository is intended to build out of the box using only publicly available dependencies?

Some of the issues I am seeing:

* The current `MAJOR_VERSION` is `2024.11`, which causes Maven to resolve artifacts such as `org.jetbrains.teamcity:bom:pom:2024.11-SNAPSHOT`. That artifact does not appear to be available from the public TeamCity Maven repository.
* If I override the TeamCity version to a newer available version, for example `2026.1`, the build progresses further but then fails because artifacts such as `org.jetbrains.teamcity:oauth-integration-agent` cannot be resolved.
* The build also appears to require local properties such as `TC_LOCAL_REPO` and `TeamCityDist`, but I have not found documentation explaining what values should be used or how the local repository should be populated.

Specifically:

1. Should `teamcity-git` build from a clean checkout using public Maven repositories?
2. If so, which branch/tag and TeamCity artifact version should external users use? I tried using `release/version of TC`.
3. Is there documentation for populating `TC_LOCAL_REPO` and configuring `TeamCityDist`?
4. Are artifacts such as `2024.11-SNAPSHOT` and `oauth-integration-agent` expected to be public, or are they internal-only?

Any guidance would be appreciated, as we need to decide whether maintaining a local fork of this plugin is still a viable approach.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Maven configuration that defines MAJOR_VERSION, TC_LOCAL_REPO, and TeamCityDist, and trace how the referenced TeamCity artifacts are resolved. Done means documenting whether clean public builds are supported, the valid branch and TeamCity version, local repository setup, and which artifacts are internal-only.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.