Sunday, 23 April 2017

gerrit and npm versioning

I am working a fairly complex nodeJs - angular project with over ~ 30 different git projects. We use gerrit (feature branch workflow) for source code control, Jenkins and Nexus.

Nexus maintains two internal repositories, develop and release. Jenkins builds for develop branch publish into develop nexus repo, while for release and hot fix branches publish to release nexus repo.

Merge of feature branches into develop results in patch version increment.

When we build an RC we increment the major number. This ensures that a hot fix feature will not accidentally pick an later release candidate. However this resulted in additional complexities that I will not bore you with.

We also use npm-shrinkwrap.

The problems I have with our current process is that is over complicated and very time consuming. It is time consuming because merging the release branch into develop always requires you to resolve conflicts in package.json because of version number changes. And when you have to do over 30 projects it takes time.

So the question is what are people doing out there?

Maybe all this shows ignorance of semantic versioning rules



via nick

No comments:

Post a Comment