0

In my company we work on the same app from different teams.

Background

  • I have created a local nuget server
  • Each team build it's own package
  • After pushing to Git-TFS server, something must increase the version number from x.y.z to x.y.z+1 inside project-name.nuspecfile and also inside each project'spackages.config` file using this package.
  • New release will be created ater pushing to Git-TFS server so multiple releases will be created each day.
  • Each team must work on the other team's latest version released packages

Questions

  1. What is the best way to increase the version number in project-name.nuspecfile and also in each project'spackages.config` file using this package after pushing to Git-TFS? Is there a better way to accomplish my goal?

  2. How do I make each project check for update in a specific packages update in the build process?

Stav Alfi
  • 13,139
  • 23
  • 99
  • 171

1 Answers1

0

1) This is a little dated, but here's an implementation of auto incrementing http://digitaldrummerj.me/Nuget-Auto-Incrementing-Version/

2) Getting the packages to auto-update for you would be a bit trickier, at that point, I would argue that the teams should have some level of communication that they released a new package and what changed

Eric Walter
  • 875
  • 1
  • 8
  • 17
  • Every push to the git-tfs server, new release should be created so multiple releases will be created each day. There must be a sulotion. It can't be I'm the only developer in the world in this situation. – Stav Alfi Sep 20 '17 at 20:48
  • What does your branching strategy look like? – Eric Walter Sep 20 '17 at 20:55
  • Each developer upload from his personal task branch to development branch and when his pull request is accepted, new release needs to be created with increasing number. – Stav Alfi Sep 20 '17 at 20:59