publish cloud button doesn't respond

[fdev2020]

Hi,

i'm working on talend locally,  i have put my credential for talend cloud.

But when i tried to publish my job the publish cloud button doesn't respond and anything happened.

Could you please help to deploy my job on talend cloud .

KR.

Fulgence

[manodwhb]

Which version of talend are you using? Before that are you able to publish?

[fdev2020]

i'm using the 7.3.1

It's my first publish cloud , i did not do that previously.

KR, 

Fulgence

[alang1]

My limited experience tells me that the Studio does not indicate the status of the deployment.  You need to wait for it to deploy and check for the appearance of the new item in the Management Console.  A detailed account of the activity can be found in a log file on the server. 

[fdev2020]

Hi @alang ,

I did it many times but nothing happened and in the management console it was not deployed.

[Anonymous]

Hi fdev2020
You can check the deploy status in Progress view, see

Regards
Shong

[fdev2020]

Hi @shong,

Thanks for you reply.

There nothing in my progress view.

are you in remote mode with your job?

[manodwhb]

I think, may be some files corrupted similar case I have see with my friend and they have contacted with Talend, to get it resolve.

[fdev2020]

@manodwhb thanks for your reply,
are these files about the talend version 7.3.1 ?
So i have to contact talend to get it resolve right?

[alang1]

I see. So, I had similar struggles, and I too had a support call with Talend. They were very helpful in getting my issue resolved. I will summarize the results in case your issue is the same as mine:

1. When deploying (in my case SOAP services), you must stop current versions before you deploy.  If you don't, there will be errors in the deployment.

2. In order to fix this, you have to go onto the remote engine server and run the Karaf client to fix things.

   a. On the remote server, navigate to the Talend runtime folder.  In my case:  D:\Talend\7.2.1\runtime

   b. in the bin folder, there is a bat file: D:\Talend\7.2.1\runtime\bin\client.bat

   c. first, run the 'list' command to see what is running:

  

   d. To find my feature, I used feature-list with a grep as shown below followed by a feature-stop:

   e. Use the following commands to stop, uninstall and remove your features

• feature:stop (shown above)
• feature:uninstall
• feature:repo-remove

   f. Now, with a clean slate, I was able to deploy again from Studio and all was good.

   g. Most importantly, I had to make sure that any future deployments were done AFTER using MC to undeploy the artifact.

BTW, I had seen a similar post (https://community.talend.com/t5/Design-and-Development/Odd-ESB-Route-deployment-through-the-TAC/m-p/...) before contacting Talend support. But couldn't quite understand until I had someone walk me through it. The support I got on this was great.  Just wish that the deployment wasn't so temperamental.