Bug 822114

Summary:	JON 3.1 Source bits seem unusually large
Product:	[JBoss] JBoss Operations Network	Reporter:	Mike Foley <mfoley>
Component:	Installer	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	JON 3.1.0	CC:	cobrien
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-17 14:44:39 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:
Bug Depends On:
Bug Blocks:	782579

Description Mike Foley 2012-05-16 11:26:24 UTC

Description of problem:  JON 3.1 Source bits seem unusually large 

https://brewweb.devel.redhat.com//archiveinfo?archiveID=208864

-------------------

From: "Chris O'Brien via RT" <release-engineering>
To: myarboro
Cc: mfoley
Sent: Tuesday, May 15, 2012 6:03:27 PM
Subject: [engineering.redhat.com #153385] Request push JON 3.1.Beta zips to CSP 

Ticket <URL: https://engineering.redhat.com/rt/Ticket/Display.html?id=153385 >

I was extremely surprised to learn that including a full clone of the git repository is actually a feature when building from a trusted SCM rather than an archive.

My suggestion would be to scrub the clone from the source zip. May I proceed with doing so?

Comment 1 Mike Foley 2012-05-16 11:49:34 UTC

<jsanda> i need to discuss with stefan but i think the size might be due to all of the history being kept when the svn repo was migrated over to git

Comment 2 Mike Foley 2012-05-16 13:36:25 UTC

Hi Mike,

This is a known problem and it's a consequence of how brew builds are done.  I've already talked about this with Mike Bonnet and it's not a simple thing to change.  However the src components produced by brew are not the ones that we attach for each JON release to the CSP so this is really a non-issue.  As described, here in step 11, we already have a script that generates the matching src components from the relevant JON tags used, usually 27MB in size: 
  JON 3.x build instructions:
http://jon01.mw.lab.eng.bos.redhat.com:8080/display/DEV/JON+3.x+Release+Builds#JON3.xReleaseBuilds-10%29PerformsmoketestingonthebuildandthenforwardtoQEforformalreleasetesting.

Typically JON GA/BETA artifacts pushed to CSP should look like the following as an example:
http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.0.1.GA/

-Simeon

Comment 3 Christopher O'Brien 2012-05-17 14:44:39 UTC

Obtained processed sources zip and moved forward with publishing it rather than the sources zip from MEAD.