[MRELEASE-740] release:perform in subdirectories fails if localCheckout=true

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3
• Component/s: Git, perform
• Assignee: Mark Struberg
• Reporter: Mark Struberg
• Created: 17/Feb/12 17:14
• Updated: 31/Oct/12 11:20
• Resolved: 30/Apr/12 16:02

Description

This bug only concerns DSCMs like hg or GIT.

Currently the release:perform fails when the project which should be released is not in the outermost directory of the SCM repository and the localCheckout feature is enabled. In this case we just do a file:// checkout from the current directory. But if the project being released is not in the outermost directory, then the present working directory doesn't contain a GIT repo but some parent directory does.
This is related to MRELEASE-501.

Issue Links

• is duplicated by: MRELEASE-754 Git clone fails during perform when using localCheckout
• is related to: MRELEASE-727 release plugin uses wrong checkout directory
• is related to: MRELEASE-501 create the possibility for performing a local checkout instead a clean checkout from the upstream repository for DSCMs
• supercedes: MRELEASE-702 Could not release project due to GIT clone error when working in sub-directory