topic Re: Continuous Integration: Is it mandatory to have command line installed on the CI server? OR can we use a remote command line? in Installing and Upgrading

Continuous Integration: Is it mandatory to have command line installed on the CI server? OR can we use a remote command line?

Anonymous — Sat, 16 Nov 2024 09:43:32 GMT

Hi,

We are trying to implement continuous build using Bamboo (CI server), ci.builder and commandline. And we prefer to use remote command line for instead of installing it on all Bamboo agents. Can someone suggest if it is supported to use remote command line in this case?

Thanks,

Sowjanya.

Re: Continuous Integration: Is it mandatory to have command line installed on the CI server? OR can we use a remote command line?

Anonymous — Fri, 09 Jun 2017 06:50:07 GMT

Hi
Take a look at the Configuring Jenkins to generate the sources section in this documentation.
https://help.talend.com/reader/mpVLyjeAbBh7eHWdz_0SlQ/HF8MMjUq3bllDlzOz2lqxw?section=sect-sdlc-generating_sources_remotely
That’s new in 6.3, before 6.3, Commandline needs to be local.

Regards
Shong

Re: Continuous Integration: Is it mandatory to have command line installed on the CI server? OR can we use a remote command line?

Anonymous — Fri, 09 Jun 2017 12:01:54 GMT

Hi,

The recommended way is to have CommandLine local. The reason for this is because you will configure Bamboo to be watching your SVN or Git repo, and trigger the build each time there is a commit (of course you need your project to be in manual commit so as you don't trigger a build for every little changes). Bamboo will get the job designs and then the CommandLine local will generate the java source code from the job designs that has already been retrieved. That's why it is needed locally. It is also the fastest way to build.

The documentation https://help.talend.com/reader/mpVLyjeAbBh7eHWdz_0SlQ/HF8MMjUq3bllDlzOz2lqxw explains the above is the recommended way. However, as shown below highlighted from the documentation, you can use the commandline remotely. This may involve doing the same operation "Getting the Project & Job Designs" twice. Bamboo will detect that there has been a change, then an agent will trigger, and use remote commandline to login into the Talend project and export the design and java sources of the jobs. Then you will need to retrieve those java sources in a zip files back to your bamboo agents machines and then unzip them into the correct directory structure and run Maven. Your Bamboo agent machines needs to be able to access the Talend Nexus thirdparty repositories to do a Maven build and download your dependencies. Here, your build may take more time, and you need to do the extra operations of copying files etc.