DEV Community

Query Filter
Query Filter

Posted on

docker107

The reason you cannot find the file in the project's root directory is that quantum/pom.xml is a relative path. In Maven projects, this usually means the repository is a multi-module project.

Where is the file?

The pom.xml is located inside a subdirectory named quantum.

  • TeamCity Context: In your TeamCity screenshot, the "Path to POM file" is quantum/pom.xml. This tells the build agent to look inside the quantum folder of your checked-out source code.
  • Jenkins Context: If you are running the Jenkins job on the root level, but the settings are inside quantum/pom.xml, Jenkins might be defaulting to a different parent pom.xml or its own auto-generated settings, which explains why the artifacts are ending up in the "wrong group."

Why the "Wrong Group" in Jenkins?

If the TeamCity build was publishing to the correct group but Jenkins is not, the "Group ID" control is likely in one of two places:

1. The <distributionManagement> section (Inside quantum/pom.xml)

Open quantum/pom.xml and look for this block. It defines the Artifactory URL and the target repository.

<distributionManagement>
    <repository>
        <id>artifactory-releases</id>
        <url>https://artifactrepository.citigroup.net/artifactory/libs-release-local</url>
    </repository>
</distributionManagement>
Enter fullscreen mode Exit fullscreen mode

The Problem: If Jenkins is not using the specific quantum/pom.xml as its entry point, it won't see these deployment coordinates.

2. The Jenkins Artifactory Plugin (Overriding the POM)

In Jenkins, check your Job Configuration. Many COMET jobs use the "Artifactory Plugin" which has a section called "Target Repository".

  • If this is filled out in Jenkins, it overrides whatever is written in your pom.xml.
  • The Fix: Ensure the "Target Repository" in Jenkins matches exactly what was used in TeamCity.

Action Plan for the "etsf" Migration

To fix the group/package issue:

  1. Locate the file: Go to your terminal or IDE and run: find . -name "pom.xml" | grep quantum This will confirm the exact disk location of the file you saw in the TeamCity screenshot.
  2. Point Jenkins to it: In your Jenkins "Build" step, change the Root POM field from pom.xml to quantum/pom.xml.
  3. Check for "Profiles": In the TeamCity screenshot, look at the "Additional Maven command-line parameters". If there is a -P some-profile-name, you must include that in Jenkins too. Often, the deployment logic is hidden inside a Maven Profile.

Verdict for your Rebuild:
The "wrong group" is almost certainly caused by Jenkins targeting the root directory instead of the quantum subdirectory. Aligning the "Root POM" path in Jenkins to quantum/pom.xml should restore the correct inheritance and publishing coordinates.

Does your Jenkins job currently have "pom.xml" or "quantum/pom.xml" in the Root POM field?

Top comments (0)