Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
CMathisUp
Partner - Contributor II
Partner - Contributor II

Talend CI - Gitlab - Can not find equinox launcher!

Hello,

 

I have attempted to add a .gitlab-ci.yml to one of my Talend projects, but when I tried to trigger the pipeline, I got this error message: 

 

[INFO] Resolve patches...
[INFO]
[INFO] Creating the detected projects for Commandline workspace.
[INFO] Created project (base on existing folder): CI_DEMO
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.536 s
[INFO] Finished at: 2025-09-25T12:48:08Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.talend.ci:builder-maven-plugin:8.0.20:generateAllPoms (default-cli) on project standalone-pom: Can not find equinox launcher! -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

 

Has anyone already faced this issue ? How should I handle this ? 

For reference, here is the script triggered for the generateAllPoms goal: 

 
mvn -U org.talend.ci:builder-maven-plugin:${CI_TALEND_BUILDER_VERSION}:generateAllPoms
 
 
where CI_TALEND_BUILDER_VERSION is: 8.0.20
 

 

Thank you very much for your help. 

 

PS: I could not find a CI/CD location, so don't hesitate to let me know if I did not post in the right location.

Thank you.

Labels (1)
  • v8.x

1 Solution

Accepted Solutions
CMathisUp
Partner - Contributor II
Partner - Contributor II
Author

In the end it turns out the problem was a wrong interpretation of variables, which led to the pipeline not being able to download the installer and perform the right actions. 

 

The configuration was as below: 

include:
    - project: "myGroup/myCIproject"
      ref: production
      file: "/global_vars.yml"
 
....
    script: 
        - mvn org.talend.ci:builder-maven-plugin:${CI_TALEND_BUILDER_VERSION}:generateAllPoms -s settings.xml -Dlicense.path=${TALEND_LICENSE} -Dtalend.studio.p2.base=${P2_BASE_URL} -Dtalend.studio.p2.update=${P2_UPDATE_URL} -e -X 

 

And the referenced project "myGroup/myCIproject/global_vars.yml" had: 

---
  CI_TALEND_BUILDER_VERSION: ${MY_CI_BUILDER}
  P2_BASE_URL: ${MY_P2BASE_URL}

 

and the variables were defined in Gitlab in Settings -> CICD Variables. It looks like this double reference caused troubles. 

When I have modified my file global_vars.yml to write the variables directly, it worked and I did not face the error anymore. 

 

If anyone has already succeeded in doing this double reference of variable, I'll be glad to read it. Else, no problem now, I found my mistake and a convenient solution. 

View solution in original post

1 Reply
CMathisUp
Partner - Contributor II
Partner - Contributor II
Author

In the end it turns out the problem was a wrong interpretation of variables, which led to the pipeline not being able to download the installer and perform the right actions. 

 

The configuration was as below: 

include:
    - project: "myGroup/myCIproject"
      ref: production
      file: "/global_vars.yml"
 
....
    script: 
        - mvn org.talend.ci:builder-maven-plugin:${CI_TALEND_BUILDER_VERSION}:generateAllPoms -s settings.xml -Dlicense.path=${TALEND_LICENSE} -Dtalend.studio.p2.base=${P2_BASE_URL} -Dtalend.studio.p2.update=${P2_UPDATE_URL} -e -X 

 

And the referenced project "myGroup/myCIproject/global_vars.yml" had: 

---
  CI_TALEND_BUILDER_VERSION: ${MY_CI_BUILDER}
  P2_BASE_URL: ${MY_P2BASE_URL}

 

and the variables were defined in Gitlab in Settings -> CICD Variables. It looks like this double reference caused troubles. 

When I have modified my file global_vars.yml to write the variables directly, it worked and I did not face the error anymore. 

 

If anyone has already succeeded in doing this double reference of variable, I'll be glad to read it. Else, no problem now, I found my mistake and a convenient solution.