[TUP-26113] Can't generate by CI due to remove pigudf after migrate a remote project from old version to 731 - Talend Open Integration Solution

Apply template

XML

Word

Printable

Details

Type: Bug
Status: closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 7.3.1
Component/s: None
Labels:
None

Steps to reproduce:
Hide

Create a 721 git project on tac, named test.

Logon the remote project test on 721 Studio, create pigudf item and commit.

Create a 731 git project on tac named test refers to the same git repository as 721 project.

Logon the remote project test on 731 Studio.

Use 731 ci-builder generate the pom from the git repository
Show
Create a 721 git project on tac, named test. Logon the remote project test on 721 Studio, create pigudf item and commit. Create a 731 git project on tac named test refers to the same git repository as 721 project. Logon the remote project test on 731 Studio. Use 731 ci-builder generate the pom from the git repository
Platform:
All
Product Build:
Talend-Studio-20200210_1943-V7.3.1SNAPSHOT
Project Size:
Small
Found in Release:

7.3.1

Description

Due to the removal of pigudf, we will meet ci generate error in the special case. Because the pigudf pom and the module relationship with root pom kept in the git repository.

Actual: generate failure.

Expect: remove the pigudf pom and module relationship with root pom while migration, generate success.

Generate error log as followed:

Started by user admin
Running as SYSTEM
BuildingUnpacking https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.6.3/apache-maven-3.6.3-bin.zip to C:\Users\tifa\.jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven on Jenkins
 in workspace D:\Talend\jenkins_workspace
Parsing POMs
Failed to transfer Could not find artifact org.example.test:code.Master:pom:7.2.1 in central (https://repo1.maven.org/maven2/)
ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.example.test.pigudf:pigudfs:7.2.1: Could not find artifact org.example.test:code.Master:pom:7.2.1 in central (https://repo1.maven.org/maven2/) and 'parent.relativePath' points at wrong local POM @ line 5, column 11

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:383)
	at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:370)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:340)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1329)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1126)
	at hudson.FilePath.act(FilePath.java:1075)
	at hudson.FilePath.act(FilePath.java:1058)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:987)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
	at hudson.model.Run.execute(Run.java:1853)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:427)
Finished: FAILURE

Attachments

Sub-Tasks

[QA] test for bug TUP-26113 Can't generate by CI due to remove pigudf after migrate a remote project from old version to 731 on 731

closed

Yan He

Activity

People

Assignee:: Nicolas Rousseau

Reporter:: Jane Ding

Fixed by:: Jane Ding

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 11/Feb/20 5:54 PM

Updated:: 14/Feb/20 10:30 AM

Resolved:: 14/Feb/20 7:53 AM