[MAGNOLIA-5872] Add branch name in the "build number" property Created: 05/Aug/14  Updated: 20/Aug/14  Resolved: 18/Aug/14

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 4.5.22, 5.2.8, 5.3.3

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLEE-368 Add branch name in the "build number"... Closed
dependency
depends upon BUILD-105 Update to buildnumber 1.3 Closed
relation
is related to MAGNOLIA-3041 Add revision in the "build number" pr... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

The "license" file exposes a BuildNumber property, which currently contains a timestamp and git revision nr; it'd be nice if this would also give the branch name. This is possible since BUILD-105. Requires updating parent poms to v29.

Example patch (am not convinced by the "format", so please come up with better)

diff --git a/magnolia-core/src/main/resources/info/magnolia/cms/license/license.xml b/magnolia-core/src/main/resources/info/magnolia/cms/license/license.xml
index 1ac8b4e..f38a7d2 100644
--- a/magnolia-core/src/main/resources/info/magnolia/cms/license/license.xml
+++ b/magnolia-core/src/main/resources/info/magnolia/cms/license/license.xml
@@ -20,7 +20,7 @@
     <Meta>
         <VersionNumber>${magnoliaNiceVersion}</VersionNumber>
         <Edition>${magnoliaEdition}</Edition>
-        <BuildNumber>${magnoliaReleaseDate} (rev. ${buildScmRevisionNumber})</BuildNumber>
+        <BuildNumber>${magnoliaReleaseDate} (rev. ${buildScmRevisionNumber} on branch ${buildScmBranch})</BuildNumber>
         <Provider>${pom.organization.name}</Provider>
         <ProviderAddress>
             <![CDATA[


Generated at Mon Feb 12 04:09:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.