Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329331 - incorrect list of changes in Hudson build of git repo
Summary: incorrect list of changes in Hudson build of git repo
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL: https://hudson.eclipse.org/hudson/vie...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-03 07:04 EDT by Glyn Normington CLA
Modified: 2011-03-11 11:29 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2010-11-03 07:04:46 EDT
virgo.util.snapshot build #139 should show the following changes:

SHA:	b33f142c96e738a8e5e9090c843b0dff0a987708
Author:	Glyn Normington <gnormington@vmware.com>
Date:	Tue Nov 02 2010 14:53:45 GMT+0000 (GMT)
Subject:	[RELEASELOR] Updated properties

and:

SHA:	7f03df3f5d44027a8de7dc40973842375b859a39
Author:	Glyn Normington <gnormington@vmware.com>
Date:	Tue Nov 02 2010 14:53:45 GMT+0000 (GMT)
Subject:	[RELEASELOR] Updated versions

Instead build #139 correctly shows commit 7f03df3f5d44027a8de7dc40973842375b859a39 but lists no changes. It seems like the calculation of changes could be incorrect.
Comment 1 Eclipse Webmaster CLA 2011-01-21 15:49:36 EST
Are you still seeing this?

-M.
Comment 2 Glyn Normington CLA 2011-01-24 03:51:02 EST
I'm not sure whether this problem is still occurring because we have since instituted a nightly build and because we don't hold on to very many builds, we can't see.

What, if anything, has changed in the calculation of changes which makes you think that the problem may have gone away?
Comment 3 Eclipse Webmaster CLA 2011-03-11 11:29:22 EST
Closing as 'not_eclipse' as I don't think there's anything specific in our setup that would cause this(that wasn't a bug in either git or hudson).  We've also updated git and hudson since this bugs was filed.

-M.