dsayers
commented
8 years ago Yes, I am aware of this issue. There is apparently an issue in the pipeline build script that was not caught during testing. It may be a week or so before I can try to fix it.
In the meantime, there is a work around. Here is what someone else who bumped into this issue did....
I got passed the problems we were seeing today.
The Environment Variable for DIALOG_ID kept getting a double-quote added to the end. Once I removed the double-quote, everything worked fine. When I look at the pipeline.yml file, I'm guessing if we change the lines that sets the DIALOG_ID substring (e.g. DIALOG_ID=${DIALOG_ID:1:${#DIALOG_ID}-4 }) to remove an extra character; it may fix the problem.
I noticed updating the pipeline.yml file wasn't being used in the build process; so I updated the "configure and deploy" configuration directly to make the change. It works as expected now.
From: John Ferguson notifications@github.com To: cfsworkload/watson-conversation watson-conversation@noreply.github.com Date: 05/02/2016 03:57 PM Subject: [cfsworkload/watson-conversation] Deploy through Bluemix pipeline issue (#2)
https://github.com/cfsworkload/watson-conversation When we deploy it to Bluemix it works. Then after a re-deploy it does not initiate with starter content and is unresponsive. We see it as being great for prototyping but we don't know why this happens and we can go no further. Any thoughts?
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
JFerguson576
https://github.com/cfsworkload/watson-conversation When we deploy it to Bluemix it works. Then after a re-deploy it does not initiate with starter content and is unresponsive. We see it as being great for prototyping but we don't know why this happens and we can go no further. Any thoughts?