-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
centos
The maven pom.xml setting is as follows.
<project>
<artifactId>test-api</artifactId>
<properties>
<finalName>${project.artifactId}-${git.branch}-${git.commit.id.abbrev}</finalName>
</properties>
</project>
The file should be created as follows.
ex) test-api-develop-2e14ddc.war
However, on the jenkins server it would be a folder like this:
ex) target/test-api-origin/develop-2e14ddc.war
System information is as follows.
-jenkins 2.245
-Maven Integration plugin 3.7
[JENKINS-63188] Build file is not created as finalName
Description |
Original:
The maven pom.xml setting is as follows. <properties> <finalName>${project.artifactId}-${git.branch}-${git.commit.id.abbrev}</finalName> </properties> The file should be created as follows. ex) test-api-develop-2e14ddc.war However, on the jenkins server it would be a folder like this: ex) target/test-api-origin/develop-2e14ddc.war System information is as follows. -jenkins 2.245 -Maven Integration plugin 3.7 |
New:
The maven pom.xml setting is as follows. <properties> <finalName>${project.artifactId}--${git.branch}--${git.commit.id.abbrev}</finalName> </properties> The file should be created as follows. ex) test-api-develop-2e14ddc.war However, on the jenkins server it would be a folder like this: ex) target/test-api-origin/develop-2e14ddc.war System information is as follows. -jenkins 2.245 -Maven Integration plugin 3.7 |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Description |
Original:
The maven pom.xml setting is as follows. <properties> <finalName>${project.artifactId}--${git.branch}--${git.commit.id.abbrev}</finalName> </properties> The file should be created as follows. ex) test-api-develop-2e14ddc.war However, on the jenkins server it would be a folder like this: ex) target/test-api-origin/develop-2e14ddc.war System information is as follows. -jenkins 2.245 -Maven Integration plugin 3.7 |
New:
The maven pom.xml setting is as follows. <project> <artifactId>test-api</artifactId> <properties> <finalName>${project.artifactId}--${git.branch}--${git.commit.id.abbrev}</finalName> </properties> </project> The file should be created as follows. ex) test-api-develop-2e14ddc.war However, on the jenkins server it would be a folder like this: ex) target/test-api-origin/develop-2e14ddc.war System information is as follows. -jenkins 2.245 -Maven Integration plugin 3.7 |
Description |
Original:
The maven pom.xml setting is as follows. <project> <artifactId>test-api</artifactId> <properties> <finalName>${project.artifactId}--${git.branch}--${git.commit.id.abbrev}</finalName> </properties> </project> The file should be created as follows. ex) test-api-develop-2e14ddc.war However, on the jenkins server it would be a folder like this: ex) target/test-api-origin/develop-2e14ddc.war System information is as follows. -jenkins 2.245 -Maven Integration plugin 3.7 |
New:
The maven pom.xml setting is as follows. <project> <artifactId>test-api</artifactId> <properties> <finalName>${project.artifactId}--${git.branch}--${git.commit.id.abbrev}</finalName> </properties> </project> The file should be created as follows. ex) test-api-develop-2e14ddc.war However, on the jenkins server it would be a folder like this: ex) target/test-api-origin/develop-2e14ddc.war System information is as follows. -jenkins 2.245 -Maven Integration plugin 3.7 |