CommandLine set path for user defined components NullPointerException

[Safus]

Hi,

Can't set the path of my user defined components using the commandLine.

I have tried every thing ; surrounding argument with (") and ('), escaping the \ and the / .... but nothig worked for me .

to clear the path with the -c it works fine.

If it's a bug hope that there is a workaround since it's really pressing.

Safus

[Anonymous]

 

[Safus]

I can't open the link :

"Oops! Looks like we ran into a problem with your request. Please contact Talend Customer Support for further assistance."

[Anonymous]

@safouane BEN MANSOUR​ , it is an internal article, you don't have permissions to access it, I have edited rhall's post and add a screenshot of the article.

About the NPE issue when running the setUserComponentPath command, I see there was a bug on the older versions and it has been fixed. Can you let us know which version of Command Line you are using? We need to make a testing to check if the issue still exists.

Regards

Shong

[Safus]

We are using this commandLine version with TAC V8 (8.0.1.20211109_1610)

talend> showVersion

8.0.1.20211109_1610

I don't think that is still possible to define usrCompoentPath at TAC level, can't see it anywhere !

[Anonymous]

Hello,

Commandline as a server is no longer supported.

Instead you should be looking at the CI based solution that relies in scriptMode, you can find example here for executeScript: https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/regenerate-pom-files

As for the custom components I'd suggest to check the following approach:

https://help.talend.com/r/en-US/8.0/share-custom-component-in-studio

This will cause the component to be uploaded to the GIT repository. Unfortunately this has to be done for each project / branch.

Talend 8 TAC doesn't have the ability to generate via commandline. You should be using Artifact Tasks. (Artifacts can be published via studio / CI: https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/ci-jenkins )

Cheers,

Balázs

[Safus]

Hello,

Thank you for your reply. But it does not unfortunately answer my first question.

Has this commandLine's version 8.0.1.20211109_1610 a bug when defining the userComponentsPath like described in the official documentations.

https://help.talend.com/r/en-US/8.0/installation-guide-big-data-linux/accessing-user-defined-compone...?

------------------------------

Commandline as a server is no longer supported.

> Yes I know, but some answers here gave me a doubt.

Instead you should be looking at the CI based solution that relies in scriptMode, you can find example here for executeScript: https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/regenerate-pom-files

> Our process uses a combination of commandLine's cmd, CI based solution, API,s calls to insure an automatic upgrade of our talend product (From 7.3.1 to 8.0.1) I still don't see how using CI based solution can fix the problem of user defined components.

As for the custom components I'd suggest to check the following approach:

https://help.talend.com/r/en-US/8.0/share-custom-component-in-studio

This will cause the component to be uploaded to the GIT repository. Unfortunately this has to be done for each project / branch.

> We can not even think about this solution since we are talking about hundreds of projects, multiple branchs, tags, ... thousands of jobs ...

Talend 8 TAC doesn't have the ability to generate via commandline. You should be using Artifact Tasks. (Artifacts can be published via studio / CI: https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/ci-jenkins )

> Not sure about what you want to say here, but the framework we developed is capable of generating, building, resolving dependencies, insure git migration and we did already upgrade so many projects/tasks using what I explained few lines above.

The only problem now is when we try to migrate projects which contain User defined components.

Reading the official documentation https://help.talend.com/r/en-US/8.0/installation-guide-big-data-linux/accessing-user-defined-compone... it seems quite simple to define the path and we are looking for :

1- Confirmation that the version of the commandLine 8.0.1.20211109_1610 represents a bug NPE (or maybe not ?)

2- Looking for a workaround (a simple one!!) like for example defining the path in a configuration file of the commandLine (maybe ??)

[Anonymous]

Hello,

As V 8.0 we need to upload user defined components to the GIT repository. With your situation hundreds of projects, multiple branchs, tags, ... thousands of jobs, it seems to be a very big migration task. Could you please raise a support case on talend support portal so that our colleagues from support team will give you a remote assistance with priority through support cycle.

Let us know if there is any help we can give.

Best regards

Sabrina

[Safus]

Hello,

again thank you for your message. But again, my question deserves an answer.

It's a Yes or No question and I don't now why you (Talend employees) keep avoiding it.

Reading the official documentation (of the v8 IMPORTANT !) https://help.talend.com/r/en-US/8.0/installation-guide-big-data-linux/accessing-user-defined-compone... it seems quite simple to define the path :

1- Version 8.0.1.20211109_1610 of the commandLine represents a NPE bug ?

Best regards

Safus

[Anonymous]

Hello,

Apologies for the delay in response.

We are checking this with DOCT team to see if there is a bug in "defining the userComponentsPath" doc and will come back to you as soon as we can.

As discussed about your NPE issue, please find below the help document which you need to check while installing command-line version 8;

https://help.talend.com/r/en-US/8.0/installation-guide-data-management-platform-windows/installing-t...

How did you install your commandline in V 8.0?Have you tried to upgrade commandline Via Running the commandline_upgrade.bat?

Thanks for your time.

Best regards

Sabrina