You can clone with
HTTPS or Subversion.
It appears that the package.json write is sometimes triggered twice when deploying apps.
Can you get a screen dump of this, from what I'm seeing it is bumping the version number if it was already deployed to an unused one and only doing it once if it has not been deployed (or if it has been destroyed).
So the issue is that it is being written twice, but it is writing 2 different package.json files.
The problem with not writing twice is that if we don't write through on the first one and there is a connection error you will be prompted to save after an error (odd UX). If we don't prompt on the second we might end up w/ some UX issues from people saying it is not writing what it prompted it would. We could make version bumping not prompt the user and instead just write?
Also, adding a message about the version number being bumped a bit more explicitly.
This is an order-of-operations problem in the jitsu deploy command: https://github.com/nodejitsu/jitsu/blob/master/lib/jitsu/commands/apps.js#L99-127
Ideally the workflow should be:
@bmeck - Will you be able to resolve this issue?
[fix] #55 package.write after filling out package.json was forcing a …
…2nd analyze. Since no deps can be added during filling, don't do that.
It looks like I'm still seeing this issue in Jitsu v0.4.0.
I don't believe this is still an issue. Closing.
I've seen this issue recently. I will give you a repro this weekend.
Am not about to reproduce / haven't seen this. Closing unless someone can post reproducible steps.