Using puppet version 3.6.2.
How can I upgrade puppet master version in RHOS.
Do I need to make any change in agent node?
Related
I'm trying to upgrade Jfrog artifactory from 6.4.1 version to the latest 7.x version.
I'm not able to find the upgrade path in the manual.
Is there an official document on the upgrade path for the same?
The document that you referred is the correct document for the upgrade process.
I belive you are referring to Artifactory installed path. If yes, the default path would be /opt/jfrog/artifactory/. If it is zip installation in linux, there is a possibility that you might have installed in your own path. You can find the path below command in linux.
ps -ef | grep artifactory
If it is windows, you can open services and get the installed path of Artifactory. Later perform an upgrade.
Please be informed, that first you need to upgrade from 6.4.1 to 6.10 as there are some breaking changes. Later you can perform an upgrade to 7.x version. Depending on the installation type, you can follow the upgrade steps mentioned in the same document.
For version below 6.10.x, first upgrade to 6.10.x and then upgrade to the version that is mentioned in the upgrade document.
When I generate a microservice project the consule docker-compose file suggests version 0.9.7 of the docker docker image.
Would it be ok to use the most recent version which is version 1.0.7, or is there a specific reason for version 0.9.3 ?
Currently we are using node.js v0.12.6 in linux and i need to upgrade to the latest version. From the download site https://nodejs.org/en/download/ , I can download node-v4.4.1-linux-x64.tar.
1) Can you please suggest whether i can upgrade from v0.12.6 to v4.4.1 directly?
2) Is there any documents to refer for this upgrade.
3) In the previous releases: https://nodejs.org/en/download/releases/, i see Vo series of node.js ends with Node.js v0.12.12. so just want to make sure that i am upgrading to the right version.
Thanks
Siva.
I have gone through several upgrades of Node (starting from 0.4.x and now on 4.x). As with all runtime upgrades (not just Node) there is no standard procedure. However the process I outline below should probably help:
On your development and QA machines, use NVM, to start with source(0.12.6) and migrate to target(4.4.1):
Install NVM from here: https://github.com/creationix/nvm
Go through the instructions to install node 0.12.6, and install all your packages and dependencies.
Run your tests and ensure everything is working as expected for your source environment
Create and switch to a new branch of your code for 'upgrade'
nvm install v4.4.1
upgrade each of your npm dependencies manually, commit package.js granularly
Run your tests and fix where needed, commit fixes granularly
When you are confident, you should have a new branch that works as desired on the new version (4.4.1)
Have QA follow their testing procedures on the new 'upgrade' branch
Go through a normal test/fix cycle with branch and merge from/to 'upgrade'
When everyone is happy, merge upgrade and launch.
Good Luck!
I have a npm module which is already released under 4.x.x version and have breaking changes comparing to 3.x.x stable version.
However I have some updates to 3.x.x version and want to patch its' npm version. Is it possible? Can I manage 2 major versions on npm?
Will https://docs.npmjs.com/cli/publish npm publish --tag do the trick?
However I have some updates to 3.x.x version and want to patch its' npm version. Is it possible? Can I manage 2 major versions on npm?
Yes, it's possible. Something that's common is to have the master branch for new developement and branch off older versions if you want to patch them and name them e.g. 3.x.
So if we assume your module has previously been released as 3.1.2 and you want to fix a bug, i.e. you want to publish 3.1.3 (patch release). Simply branch off from 3.1.2 (assuming you have a git tag v3.1.1):
git checkout v3.1.2
git checkout -b 3.x
# make changes and commit
npm version patch # will bump package.json, commit that and tag
npm publish
I wrote a node package which contains breaking changes in the next release. Does there exist a way to notify developers about that via console while upgrading via npm?
I don't think there is a solution to inform the via console, but if your new version is given by an new "major" number, it should not break the code.
Breaking example
Client dependency: ~1.2.2
Your old version: 1.2.2
Your new version: 1.2.3
The client will upgrade to version 1.2.3.
Not breaking example
User dependency: ~1.2.2
Your old version: 1.2.2
Your new version: 1.3.0
The client will not upgrade.