Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi there,
I´m struggling at the moment with CI/CD stuff with Talend 7.1.
I have installed TAC 7.1, Nexus 3, Maven, GIT and Jenkins... Now I was working with this documentation as Talend CommandLine is deprecated up from 7.1.
https://help.talend.com/reader/Zpzt_P_L6RrGuFyEnxwwqw/xz8cn7USQYf1my78_RbF6w
Now, I have the problem not to know how it is possible to create Processes to get the projects synchronized from GIT to Nexus.
I´ve installed all the Plugins in Jenkins which are described there, I used and configured the scripts show in the documention to reach repos.
I used Linux groovy script to start Pipeline-Creation. And now the documentation says to use the CommandLine which isn´t installed because it is not needed since 7.1
Has anybody created Build-Processes from GIT to Nexus Artifactory to help me out?
Thx to all...
Hi, CommandLine is required. Verify the commandLine installation modes.
Documentation says
Note: The Talend CommandLine server mode generation type is deprecated, it is recommended to use the local generation type instead.
For 7.1.1 this help center article might also help you
Hi Ram,
thanks for your reply.
Does that mean that I have to install a Talend Studio on my CI-Server as well?
Normally I just have the studio on my clients.
Which folder in Talend Studio is the commandline-folder where I can use the commandline.sh file?
Thx....
I have another question, how do I install the command line as described on your blog-post?
It is described as an requirement, but where do I find the install modes?
At the end of the prerequisites i added a Note with the Documentation links for inytalling Talend software
You can install the software either with the installer or manually.
Using installer you can choose (Advanced mode + Custom install) and install only those software modules which you need.
https://help.talend.com/reader/qwBdtxGavqRDlnID~sGVQg/EQc8Y~zU6HGg644ls4yPow
Installing commandline manually
https://help.talend.com/reader/qwBdtxGavqRDlnID~sGVQg/Jw2F44hykY8u_r3AjZO8Yg
Thanks Ram,
that really helps.
Two more questions:
- Do I have to use the installer the first time with a user because of the license?
- For Deployment, all examples are just showing a case with "One Project and one Job".
My goal will be to have a Jenkins Pipeline which looks into my Bitbucket and create builds from all new and changed jobs.
I don´t want to have an deployment pipeline per Job, and I don´t want to change my Maven-Settings if a new job should be build also.
That means:
Developers creates/changes a job, push to GIT-Master, Jenkins starts build and finds the correct to job (without defined in Settings, maybe with a wildcard "*"??) for the Build and pushes it to Nexus
I haven´t seen such a script yet...
Thx again...