Why is JazzHub demanding to launch a new app when I have one that just needs to be updated?
I've done this before: make a simple node.js app at jazzhub, fixup the manifest.yml and deploy to bluemix. Then change app.js and deploy again to see the changes. Worked fine, a couple weeks ago.
In order to become familiar with the other clients and better understand the workflow, I connected from an RTC 4.0.5 Eclipse client. It found my existing workspaces and I loaded the source into Eclipse. I made a small change to app.js and delivered it to jazzhub. I went to jazzhub to deploy it and it refuses saying that the app name is taken. The Deploy button hover says "New BlueMix deployment from manifest" (that's the same option from the DeployAs button).
Why won't it simply push the updated app to BlueMix (the way it used to)?
Comments
Millard Ellingsworth
FORUM ADMINISTRATOR / JAZZ DEVELOPER Feb 17 '14, 3:54 p.m.I renamed the original version of the app at BlueMix,then deployed the updated one -- that worked. Then I made a small change to app.js at JazzHub and tried to deploy the update -- blocked for same reason (app name already exists). So the Deploy button seems to only want to do a new deployment -- which seems wrong.