Versions Compared

Old Version 7

changes.mady.by.user Marnix Kraus

Saved on

compared with

New Version 8

changes.mady.by.user Marnix Kraus

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TeamCity helps us with a couple of things. It performs automatic unit tests of the framework tests themselves and it also performs automatic unit tests for the product tests when you made changes to the framework. These product tests are triggered when a new successful NuGet package was built. It is then updated onto the product and the tests are run.

The automatic updates of product tests are still under construction.

Jira
serverDeltares Issue Tracker
serverId20635570-6a34-3a69-a785-26a57a470c5b
keyTOOLS-23763
. We hope to get this working soon with the latest 3.4 release of NuGet, so that it will be easier for framework developers to see if they forgot anything or if backwards compatibility is broken. Another workaround would be to make our own PowerShell script, but this would be very cumbersome, since it won't be stable at all.

Framework Release Management

There are no concrete agreements for releasing a framework (pinning it on TeamCity). There are a couple of things you could think of.

  • First, pin the build on TeamCity.
    • At this moment, TeamCity is the only place where this NuGet feed lives. It could be the case that ICT is not aware of the importance of TeamCity. It could be possible that we need a better place to store the released framework versions. For example, in SVN.
  • Then, update the version numbers in the csprojs of the framework for further development.
  • Maybe we should make some release notes.
  • Make an announcement about the release.
  • You could update the supported products to the latest version of this released framework. Make sure that all the tests still succeed.