History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3406
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Sebastian Potasiak
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Configuration fails when there's an additional non-existent remote repository added to git repository

Created: 12/Jun/19 10:57 AM   Updated: 17/Jun/19 06:32 AM
Component/s: None
Affects Version/s: 7.0.28
Fix Version/s: 9.0.12

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
For a git repository defined in QuickBuild we have to add an extra remote repository, but when the address of the repository is wrong or the remote repository doesn't exist anymore, we get following error when trying to run the configuration (it's thrown before checking build condition):


2019-06-12 10:19:07 - Failed to run command: git fetch --all --tags -q
Command return code: 1
Command error output: error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

fatal: remote error: Repository not found
The requested repository does not exist, or you do not have permission to
access it.
error: Could not fetch external_repository
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.


In my opinion, since QuickBuild lets us define only one (origin) remote repository, it shouldn't try to fetch all remotes, but only the origin. Otherwise, we cannot do anything about this issue, as there's no way to handle errors thrown before checking build condition is triggered.

 All   Comments   Work Log   Change History      Sort Order:
No work has yet been logged on this issue.