You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After an initial deploy you can redeploy as often as you would like. Note however that jitsu will ask to increase the package build version, e.g the x in 0.0.z-x will be incremented. A manual increase of the patch z version will skip the step below and immediatly deploy your application.
... is completely incorrect in 0.14.0 and on nodejitsu as of within the last hour or so.
Secondly I have just had some correspondence with support and they claim that jitsu no longer supports the r switch... in which case you should probably remove that option from the jitsu package and not just in the server side script.
Thirdly deployment from multiple locations with the current auto-increment system is problematic due to the last point... e.g. A feature request was mentioned in the support issue to allow gh commit hash (7 digit) for the r switch... but that makes nodejitsu completely unreliable and fails to activate a snapshot. npmjs.org doesn't have an issue with this... why should nodejitsu/jitsu?
As I have previously mentioned this has already been discussed with support directly but needs to be addressed here with this questionable deployment system not living up to what it promises.
I am thoroughly disappointed.
The text was updated successfully, but these errors were encountered:
First off the docs at https://www.nodejitsu.com/documentation/jitsu/deploy/#repeated-deployments are incorrect regarding jitsu... version increment never asks e.g.
... is completely incorrect in 0.14.0 and on nodejitsu as of within the last hour or so.
Secondly I have just had some correspondence with support and they claim that jitsu no longer supports the
r
switch... in which case you should probably remove that option from the jitsu package and not just in the server side script.Thirdly deployment from multiple locations with the current auto-increment system is problematic due to the last point... e.g. A feature request was mentioned in the support issue to allow gh commit hash (7 digit) for the
r
switch... but that makes nodejitsu completely unreliable and fails to activate a snapshot. npmjs.org doesn't have an issue with this... why should nodejitsu/jitsu?As I have previously mentioned this has already been discussed with support directly but needs to be addressed here with this questionable deployment system not living up to what it promises.
I am thoroughly disappointed.
The text was updated successfully, but these errors were encountered: