Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I've got problem with building job on Jenkins. The project juns just fine in Studio and it is pushed to GIT.
But when I try to build it using Jenkins I get this error message:
1. ERROR in C:\jenkins\workspace\aep\deploy\aep-talend-SNPAC\SNPAC_2\poms\jobs\process\fetchfile_0.1\src\main\java\snpac_2\fetchfile_0_1\FetchFile.java (at line 1646)
com.enterprisedt.net.ftp.FTPClient conn = (com.enterprisedt.net.ftp.FTPClient) connObj;
^^^^^^^^^^^^^^^^
com.enterprisedt cannot be resolved to a type
I figured out so much that it cannot find some JARs. We have a Jenkins server and a command line server, however on the command line we have a Jenkins slave so the build is run on the command line.
The JARs that it is looking for is lokated on the command line server:
c:\Talend\7.0.1\cmdline\studio\plugins\org.talend.libraries.ftp_7.0.1.20180411_1414\lib\
I have no idea how jenkins should find the JARs needed to build the project.
I do specify the path to the command line in the Maven config:
-X deploy -Dgeneration.type=local -Dproduct.path="C:\Talend\7.0.1\cmdline\studio" -DaltDeploymentRepository=snapshotRepo::default::http://nexus.ourserver.com/repository/maven-snapshots/
Any ideas?
Hi,
Yes project and environment was set up correct.
I did found the issue. As I mentioned the job did run without error in Studio. However when looking in the Code I could se errors, strange that it still ran.
I found which component(in this case ftpclose) caused the error. Just removed it and put a new ftpclose component and the problem resolved it self.
Hello,
Are you following this instructions to setup a Jenkins BuildSources job?
https://help.talend.com/reader/mpVLyjeAbBh7eHWdz_0SlQ/HF8MMjUq3bllDlzOz2lqxw
Best regards
Sabrina
Hi,
Yes project and environment was set up correct.
I did found the issue. As I mentioned the job did run without error in Studio. However when looking in the Code I could se errors, strange that it still ran.
I found which component(in this case ftpclose) caused the error. Just removed it and put a new ftpclose component and the problem resolved it self.
Hello,
Feel free to let us know if this error still reproduces on your end.
Best regards
Sabrina