Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private Bitbucket Repository Not Finding Branches #17

Open
stuartmitchelhill opened this issue Jan 5, 2025 · 2 comments
Open

Private Bitbucket Repository Not Finding Branches #17

stuartmitchelhill opened this issue Jan 5, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@stuartmitchelhill
Copy link

To Reproduce

  1. Setup Dokploy on VPS
  2. Setup Custom Domain and SSL
  3. Configure GIT for Bitbucket as per instructions in documentation (https://docs.dokploy.com/docs/core/bitbucket)
  4. Setup New Project
  5. Configure Application from Bitbucket
  6. Loading branches throws 400/404
Screenshot 2025-01-06 at 9 34 41 AM

Current vs. Expected behavior

After configuring bitbucket for and the correct workspace, when setting up a new application I expect the repository branches to load correctly, currently the api call to bitbucket.getBitbucketBranches throws a 400/404

Provide environment information

Operating System:
	OS: Ubuntu 24.10
	Arch: arm64
Dokploy version: v0.16.1
VPS Provider: DigitalOcean
What applications/services are you trying to deploy?
	Next.js App

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

@stuartmitchelhill stuartmitchelhill added the bug Something isn't working label Jan 5, 2025
@stuartmitchelhill
Copy link
Author

Looks like the issue stems from how the repo "slug" is being handled in the API call. The API call is using the repository name instead of slug, i.e. Project Repo when it should use project-repo

@Siumauricio
Copy link
Contributor

Yes, I think it's more of a documentation error, for workspaces you should use the slug of your organisation/space, I will transfer this issue to the docs!

@Siumauricio Siumauricio transferred this issue from Dokploy/dokploy Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants