CI Builder doesn't find jobs within a project

[Anonymous]

Hi,

I'm following the Continuous Integration steps in the help center and I'm coming across a strange issue where the Ci Builder (running on Jenkins) can find projects but no jobs inside them. It successfully retrieves the projects from git, put them in the workspace and identifies the folders that are projects (presumably by finding the talend.project file). When I navigate to one of the projects and look inside the process folder i can see jobs with .item and .properties files, but the console output from jenkins reports it cannot find them:

[INFO] 
[INFO] *****************************************************
[INFO] List projects from:/jenkins/workspace/gentest
[INFO]   Not valid folder (no talend project) in:.Java
[INFO]   Found project:LOCAL_PROJECT
[INFO]   Found project:AAA_JDBC
[INFO] 
[INFO] Creating the detected projects for Commandline workspace.
[INFO]   Created project (base on existing folder): LOCAL_PROJECT
[INFO]   Created project (base on existing folder): AAA_JDBC
[INFO] 
[INFO] *****************************************************
[INFO] Starting to generate sources for the detected projects
[INFO] 
[INFO] Preparing for the project: LOCAL_PROJECT
[INFO]  Logon project
[INFO]  Generating sources...
[INFO]  Logoff project
[WARNING] There's no job in current project!
[INFO]  Successfully generated the sources to:
[INFO]   /base/vendor/Talend/projectSourcestest/LOCAL_PROJECT
[INFO] 
[INFO] Preparing for the project: PMA_JDBC
[INFO]  Logon project
[INFO]  Generating sources...
[INFO]  Logoff project
[WARNING] There's no job in current project!
[INFO]  Successfully generated the sources to:
[INFO]   /base/vendor/Talend/projectSourcestest/PMA_JDBC
[INFO] 
[INFO] Finished to generate sources for all detected projects
[INFO] *****************************************************

Has anyone seen this before or got any clues as to what it could be?

Thanks!

[Anonymous · Accepted solution]

This was because i was using a local-generate in the build_pom.xml and in the maven goals using a remote generation.

This is resolved now.

[Anonymous]

Hi Jacob, 

Thanks for your post, I am facing a similar issue, can you be more explicit as your below resolution

"This was because i was using a local-generate in the build_pom.xml and in the maven goals using a remote generation". Any further clarity will be greatly appreciated.

[Anonymous]

In the CI tool you have to point to the build_pom.xml and inside it you specify the goals, in my case i had set the goal in the build_pom.xml to "local-generate" but in the CI build goal i had "generate". These need to be the same, hope this helps!

[Anonymous]

Thanks Jacob for your prompt response, I had moved past that earlier and able to package and compile the Talend code from Bitbucket and deployed it to Nexus Repository. But we require that only those jobs which have been changed are deployed to the Nexus repository not the entire *developer branch and then at other attempts to publish to Nexus I get the below error;

[ERROR] Failed to execute goal org.apache.maven.plugins: maven-deploy-plugin:2.7:deploy (default-deploy) on project code.Master: Failed to deploy artifacts: Could not transfer artifacts org.talend.master.test_project:code.Masterom:6.4.1 from/to talendNexus…………..

..Master/6.4.1/code.Master.6.4.1.pom. Return Code is: 400, ReasonPhrase: Bad Request -> [Help 1]

Let me know your thoughts.

[Anonymous]

Hi Jacob,

I am having the same issue when Jenkins is triggered, I get the below warning.

[INFO]  Logon project
[INFO]  Generating sources...
[INFO]  Logoff project
[WARNING] There's no job in current project![INFO]  Successfully generated the sources to 

 Goal for both build pom.xml and  CI build are  the same "generate".
<phase>generate-sources</phase>
<goals>
<goal>generate</goal>
</goals>
Am I missing something here ? please suggest me on this issue.

[ajaychaubey]

Return Code is: 400

Usually happens due to previously existing objects in nexus and you try to republish on the same version. You have not enabled for redeploy existing object from Nexus.

Regards,
Prasanna