Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 355724

Summary:	Providers should not switch branch/tag unless explicitly told to do so
Product:	z_Archived	Reporter:	Thomas Hallgren <thomas>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	354085

Description Thomas Hallgren

2011-08-24 11:39:31 EDT

Buckminster currently defaults to using the SVN trunk and Git master when the cquery has no advice to switch the branch/tag. This leads to a bunch of problems when integrating with tools like Hudson.

Example:
The build checks out a releng project from Git using branch 'dev'. It then imports using the CQUERY that it finds there. The CQUERY doesn't have any advice node so the when the git reader finds other projects to include in the build in the same clone, it now makes an attempt to switch to the 'master' branch which in turn leads to conflicts.

This can be solved by adding an advice to the CQUERY that appoints the branch where the CQUERY resides but remembering to do that every time a new branch is created will quickly become a nightmare. A much better alternative is to let 'no applicable branch/tag advice' mean 'use current HEAD'.

Comment 1 Thomas Hallgren

2011-08-25 03:38:05 EDT

Fixed for the Git provider. This isn't really applicable for SVN since the resolution is performed against the remote repository and it has no notion of a 'current'.

The fix is in http://git.eclipse.org/c/buckminster/buckminster.git/commit/?id=beaacc2f7b36294026f1da58bc0baca97024769b