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

Key: QB-3483
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Mike Cordeiro
Votes: 0
Watchers: 0
Operations

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

Git revisions wrong when >1 GitHub Repo with 1 using > 1 branch

Created: 20/Dec/19 05:00 PM   Updated: 24/Dec/19 12:31 AM
Component/s: None
Affects Version/s: 9.0.24, 9.0.26, 9.0.27, 9.0.28, 9.0.29, 9.0.30
Fix Version/s: 9.0.31

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File StepLog.txt (5 kb)

Image Attachments:

1. StepStatus.jpg
(26 kb)
Environment: Windows


 Description  « Hide
When configuring a build with more than 1 GitHub repository (only 1 of which is configured to build Pull Requests), the check out steps of the single branch Repositories are attempting to use the hash from the multi-branch repository. The Step Status screen will reflect the correct hash for each repository, but in investigating the logs for the failing step, the wrong hash is being used. Attached are a screenshot of the Step Status screen (reflecting the correct hashes) and the log from the failed step (reflecting the hash from the other repository).

 All   Comments   Work Log   Change History      Sort Order:
Change by Mike Cordeiro [20/Dec/19 05:02 PM]
Field Original Value New Value
Attachment StepStatus.jpg [ 10820 ]

Change by Mike Cordeiro [20/Dec/19 05:02 PM]
Attachment StepLog.txt [ 10821 ]

Robin Shen [21/Dec/19 12:34 AM]
Please make sure to use different "destination path" when checkout multiple git repository at QB side. Otherwise, their clone directory will overlap with each other to cause issues.

Mike Cordeiro [23/Dec/19 02:15 PM]
Each of the repositories in this configuration have unique Destination Paths. The build works fine when each repository is only configured to build HEAD (no Pull Request builds), however as soon as one of the builds is configured to build PRs, this issue occurs.

Change by Steve Luo [24/Dec/19 12:25 AM]
Status Open [ 1 ] Resolved [ 5 ]
Assignee Robin Shen [ robinshine ]
Resolution Fixed [ 1 ]

Change by Steve Luo [24/Dec/19 12:25 AM]
Fix Version/s 9.0.31 [ 11918 ]

Robin Shen [24/Dec/19 12:31 AM]
Thanks for the info. This is actually a bug and has now been fixed in 9.0.31:
https://build.pmease.com/build/5030