All geek questions in one place

CruiseControl.NET build tag issue

I put my assemblies using the CCNETLABEL environment variable and SVN version number. I ran into a problem:

Assume ProjectA depends on ProjectB

ProjectA is build number X, and ProjectB is build number Y

When ProjectA starts, ProjectB is also created.

Since CCNETLABEL = X + 1, my version marking was obtained as follows:

Build number ProjectA = X + 1 And build number ProjectB = X + 1 instead of the expected Y.

This leads to versioning issues because builds are considered "newer" versions.

My question is:

I do not want to flag every assembly created due to a particular project change with this CCNETLABEL project. Ideally, I would like ProjectA to just make the assumption that ProjectB is already built, which saves the processing time needed to create ProjectB.

+3
source share
1 answer

In the ccnet.config file element for each project, I used "Rebuild", which forces all related projects to rebuild. Changing this to "Build", he only builds dependent projects, if there are changes that require compilation. Since CCNET retrieves the latest version, this will never be a problem. The problem is resolved.

+1
source

Source: https://habr.com/ru/post/1747999/

More articles:


All Articles