oguzgu opened a new issue, #8627: URL: https://github.com/apache/incubator-devlake/issues/8627
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened ### Issue Description Bitbucket connection authentication works inconsistently between API calls and Git clone operations. ### Steps to Reproduce 1. Create Bitbucket connection using email address + API token with proper scopes (as required by the UI) 2. Add a Bitbucket repository to a blueprint 3. Run the blueprint ### Actual Behavior - **First run**: Clone fails because DevLake uses **email address** for Git clone, but Bitbucket requires **username** - **Workaround attempt**: Update `_devlake_blueprints` table to set mode='ADVANCED', then edit blueprint JSON to replace email with username in the git URL - **Result**: Clone succeeds once, then fails on subsequent syncs (reverts back to email) ### Alternative Approach Tried: SSH Configured `privateKey` in advanced blueprint mode with SSH URL format. - **First run**: Works - **Subsequent runs**: Fails with error: `Identity file /tmp/gitext-pk* not accessible: No such file or directory` The temporary SSH key file gets created but then becomes inaccessible, causing permission denied errors. ### Environment - DevLake version: v1.0.3-beta7 - Connection type: Bitbucket Cloud - Authentication: API token with proper scopes ### Expected Fix DevLake should either: 1. Allow specifying both email (for API) and username (for Git) in Bitbucket connection settings, OR 2. Automatically resolve username from email via Bitbucket API, OR 3. Fix SSH privateKey handling to persist properly across multiple runs ### What do you expect to happen Connection should work for both API calls and Git clone operations using the same credentials. ### How to reproduce ### Steps to Reproduce 1. Create Bitbucket connection using email address + API token with proper scopes (as required by the UI) 2. Add a Bitbucket repository to a blueprint 3. Run the blueprint ### Anything else _No response_ ### Version v1.0.3-beta7 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
