Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900036 (JBPAPP6-578)

Summary:	Mead: Add git (internal repo) commit hash to each .jar's MANIFEST.MF
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Ondřej Žižka <ozizka>
Component:	Build	Assignee:	Paul Gier <pgier>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	mikeb, pgier, rsvoboda, vtunka
Target Milestone:	---
Target Release:	EAP 6.0.0
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-578
Whiteboard:	eap_qa_req
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-02 09:10:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ondřej Žižka 2012-03-13 14:50:39 UTC

project_key: JBPAPP6

All .jar's comming from MEAD should have a git commit hash to make it easy to check if two same-named jars were also built from the identical commit - which is not always true.

Here is a Jenkins job which shows that some jar's already have it:
http://hudson.qa.jboss.com/hudson/job/eap-60-repository-maven-check-manifest/lastSuccessfulBuild/artifact/test-output.txt
{code}
Scm-Version: ce8e04c4605336d0e72cb808c684c56ad6f02b50
{code}
Some just have
{code}
SCM: r${buildNumber}
{code}

This is a request to have a correct git commit hash in every .jar.

Comment 2 Mike Bonnet 2012-03-13 16:04:51 UTC

git is already present in the EAP 6 buildroots.  It sounds like the buildNumber property is not being set in some cases.  This needs to be fixed in each pom.xml, probably by using the Maven buildnumber plugin.

Comment 3 Ondřej Žižka 2012-03-13 17:45:54 UTC

Labels: Added: eap_qa_req

Comment 4 Paul Gier 2012-03-21 18:47:02 UTC

Upstream I added configuration to the jboss-parent to add the SCM revision using the build number plugin.  Maybe we can use the same config for our Mead builds, however the commit ID wouldn't be included in Ant based builds.

Comment 5 Paul Gier 2012-04-19 14:07:21 UTC

I updated the jboss-parent pom with the upstream changes to add the git ID to each build.  This should fix the issue for any Maven based projects that we rebuild.  The others will wait until a later release.

Comment 6 Rostislav Svoboda 2012-05-02 09:10:50 UTC

Verified on EAP 6.0.0 ER6

Automated job created: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-scm-revision/

Comment 7 Anne-Louise Tangring 2012-11-05 17:29:07 UTC

Docs QE Status: Removed: NEW