Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update of *jitsu* docs and implementation needed #509

Open
Martii opened this issue Nov 18, 2014 · 0 comments
Open

Update of *jitsu* docs and implementation needed #509

Martii opened this issue Nov 18, 2014 · 0 comments

Comments

@Martii
Copy link

Martii commented Nov 18, 2014

First off the docs at https://www.nodejitsu.com/documentation/jitsu/deploy/#repeated-deployments are incorrect regarding jitsu... version increment never asks e.g.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant