Be the first to post a text review of Breki CCNet Utilities. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• CruiseControlUtils-1.7.314.3 Released (for CCNet 1.3)

  Contributed by Tobias Jahn. A new release contains some new options for generating labels. You can now generate both build number and revision number from a file. Also, the revision number can be generated by an external tool (this is similar to SvnRevisionLabeller). 1. Installation: - copy ccnet.Breki.plugin.dll to the CC.net "server" subdirectory - modify CC.net configuration file and save it 2. Configuration: Version format: "M.m.b.r" M - major number m - minor number b - build number r - release number Parameters: - BuildNumberScheme: defines the algorithm for generating build numbers. Possible values: "Increment": increments an existing build number "NoIncrement: uses an existing build number "MonthDaySinceReleaseStart": (default) generates build number based on the release start date and formula: number of months since release start * 100 + current day in month "FromVersionFile": uses the build number from the version file - RevisionNumberScheme: defines the algorithm for generating release numbers. Possible values: "DailyIncremental": (default) increment an existing revision number if the previous build was on the same day as the new one or reset to 0 if those days differ "SecondsSinceMidnight": number of seconds since the start of today / 10 "FromVersionFile": uses the build number from the version file "FromExternalApp": uses the output of an external application (needs RevisionAppPath and RevisionAppArgs). - MajorNumber: major number to use (not required, default is 1) - MinorNumber: minor number to use (not required, default is 0) - ReleaseStartDate: start date of the release (not required). Has to be in the MM/DD/YYYY format. - VersionFilePath: (not required) path to the file containing the version information. The file should only contain version, which should be in the format "M.m.b.r" (NOTE: build and release numbers are ignored) This information is used to extract the following: - major number - minor number - build number (only needed if "BuildNumberScheme" is set to "FromVersionFile") - release start date: labeller uses last modified time of the file as a release start date When VersionFilePath parameter is used, MajorNumber, MinorNumber and ReleaseStartDate are ignored. - Prefix: (not required, default is empty string) prefix for the label - RevisionAppPath: Path to external application (only needed if "RevisionNumberScheme" is set to "FromExternalApp") - RevisionAppArgs: Arguments passed to external application (only needed if "RevisionNumberScheme" is set to "FromExternalApp") Example of the CCNet labeller configuration block: <labeller type="BrekiLabeller"> <BuildNumberScheme>MonthDaySinceReleaseStart</BuildNumberScheme> <RevisionNumberScheme>DailyIncremental</RevisionNumberScheme> <VersionFilePath>ProjectVersion.txt</VersionFilePath> <MajorNumber>1</MajorNumber> <MinorNumber>1</MinorNumber> <ReleaseStartDate>07/18/2006</ReleaseStartDate> <Prefix>MyProject-</Prefix> </labeller> Example for a labeller which takes the build number from a file and uses an external application for the revision: <labeller type="BrekiLabeller"> <BuildNumberScheme>FromVersionFile</BuildNumberScheme> <RevisionNumberScheme>FromExternalApp</RevisionNumberScheme> <VersionFilePath>...somepath...\Version.txt</VersionFilePath> <RevisionAppPath>...somepath...\CvsCommitCount.exe</RevisionAppPath> <RevisionAppArgs>some arguments</RevisionAppArgs> </labeller>

  posted by igorbrejc 663 days ago

• brekiccnetutils CruiseControlUtils-1.7.314.3 file released: CruiseControlUtils-1.7.314.3.zip

  posted 663 days ago

• File released: /brekiccnetutils/CruiseControlUtils-1.7.314.3/CruiseControlUtils-1.7.314.3.zip

  posted 663 days ago

• brekiccnetutils CruiseControlUtils-1.6.23.1 file released: CruiseControlUtils-1.6.23.1.zip

  posted 877 days ago

• CruiseControlUtils-1.6.23.1 Released (for CCNet 1.3)

  A new version of BrekiLabeller for CruiseControl.NET is released. It is built for CCNet version 1.3. BrekiLabeller is a custom CCNet labeller which allows build labelling in the "prefix-M.m.B.R" format. Also allows defining various build and revision numbering schemes and using project version text file as the version number source. Similar to NAnt Contrib <version> task. 1. Installation: - copy ccnet.Breki.plugin.dll to the CC.net "server" subdirectory - modify CC.net configuration file and save it 2. Configuration: Version format: "M.m.b.r" M - major number m - minor number b - build number r - release number Parameters: - BuildNumberScheme: defines the algorithm for generating build numbers. Possible values: "Increment": increments an existing build number "NoIncrement: uses an existing build number "MonthDaySinceReleaseStart": (default) generates build number based on the release start date and formula: number of months since release start * 100 + current day in month - RevisionNumberScheme: defines the algorithm for generating release numbers. Possible values: "DailyIncremental": (default) increment an existing revision number if the previous build was on the same day as the new one or reset to 0 if those days differ "SecondsSinceMidnight": number of seconds since the start of today / 10 - MajorNumber: major number to use (not required, default is 1) - MinorNumber: minor number to use (not required, default is 0) - ReleaseStartDate: start date of the release (not required). Has to be in the MM/DD/YYYY format. - VersionFilePath: (not required) path to the file containing the version information. The file should only contain version, which should be in the format "M.m.b.r" (NOTE: build and release numbers are ignored) This information is used to extract the following: - major number - minor number - release start date: labeller uses last modified time of the file as a release start date When VersionFilePath parameter is used, MajorNumber, MinorNumber and ReleaseStartDate are ignored. - Prefix: (not required, default is empty string) prefix for the label Example of the CCNet labeller configuration block: <labeller type="BrekiLabeller"> <BuildNumberScheme>MonthDaySinceReleaseStart</BuildNumberScheme> <RevisionNumberScheme>DailyIncremental</RevisionNumberScheme> <VersionFilePath>ProjectVersion.txt</VersionFilePath> <MajorNumber>1</MajorNumber> <MinorNumber>1</MinorNumber> <ReleaseStartDate>07/18/2006</ReleaseStartDate> <Prefix>MyProject-</Prefix> </labeller>

  posted by igorbrejc 878 days ago

• File released: /brekiccnetutils/CruiseControlUtils-1.6.23.1/CruiseControlUtils-1.6.23.1.zip

  posted 878 days ago

• brekiccnetutils CruiseControlUtils-1.5.8.0 file released: CruiseControlUtils-1.5.8.0.zip

  posted 923 days ago

• CruiseControlUtils-1.5.8.0 Released (for CCNet 1.2.1)

  A new version of BrekiLabeller for CruiseControl.NET is released. It is built for CCNet version 1.2.1. BrekiLabeller is a custom CCNet labeller which allows build labelling in the "prefix-M.m.B.R" format. Also allows defining various build and revision numbering schemes and using project version text file as the version number source. Similar to NAnt Contrib <version> task. 1. Installation: - copy ccnet.Breki.plugin.dll to the CC.net "server" subdirectory - modify CC.net configuration file and save it 2. Configuration: Version format: "M.m.b.r" M - major number m - minor number b - build number r - release number Parameters: - BuildNumberScheme: defines the algorithm for generating build numbers. Possible values: "Increment": increments an existing build number "NoIncrement: uses an existing build number "MonthDaySinceReleaseStart": (default) generates build number based on the release start date and formula: number of months since release start * 100 + current day in month - RevisionNumberScheme: defines the algorithm for generating release numbers. Possible values: "DailyIncremental": (default) increment an existing revision number if the previous build was on the same day as the new one or reset to 0 if those days differ "SecondsSinceMidnight": number of seconds since the start of today / 10 - MajorNumber: major number to use (not required, default is 1) - MinorNumber: minor number to use (not required, default is 0) - ReleaseStartDate: start date of the release (not required) - VersionFilePath: (not required) path to the file containing the version information. The file should only contain version, which should be in the format "M.m.b.r" (NOTE: build and release numbers are ignored) This information is used to extract the following: - major number - minor number - release start date: labeller uses last modified time of the file as a release start date When VersionFilePath parameter is used, MajorNumber, MinorNumber and ReleaseStartDate are ignored. - Prefix: (not required, default is empty string) prefix for the label Example: <labeller type="BrekiLabeller"> <BuildNumberScheme>MonthDaySinceReleaseStart</BuildNumberScheme> <RevisionNumberScheme>DailyIncremental</RevisionNumberScheme> <VersionFilePath>ProjectVersion.txt</VersionFilePath> <MajorNumber>1</MajorNumber> <MinorNumber>1</MinorNumber> <ReleaseStartDate>07/18/2006</ReleaseStartDate> <Prefix>MyProject-</Prefix> </labeller>

  posted by igorbrejc 923 days ago

• File released: /brekiccnetutils/CruiseControlUtils-1.5.8.0/CruiseControlUtils-1.5.8.0.zip

  posted 923 days ago