search

docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
232 stars 40 forks source link

Not working: Docker hub automated build Integration with BitBucket #1470

Closed chukka closed 3 years ago

chukka commented 6 years ago

Hi Team,

We have a team account in BitBucket (BB), lets say https://bitbucket.org/myteam with John as owner and we have different users (admin/developers/users) with different permissions like admin/write/read permissions under it .

we want to integrate an automated build from docker_hub with https://bitbucket.org/myteam/repo.git with non owner account say Tom's account and when i select bitbucket, my repository is not listed! hence i can’t select one to complete the setup.

However, when try to integrate docker hub automated build with john (owner account ) it lists the repository (https://bitbucket.org/myteam/repo.git )

Is there a perquisite from dockerhub that only owner of the git repo in BB can access the repo from docker hub and integrate the automated build ?

Is there something wrong with the bitbucket repositories listing based on permissions ?

Thanks Chukka

SeBsZ commented 5 years ago

I have the same question. Is it possible to receive an answer here? I linked a Bitbucket user that I know has access to the repository, but dockerhub does not list any repositories. Any idea why?

archon810 commented 5 years ago

Running into this problem as well. Anyone from the Hub team here?

CarlQLange commented 5 years ago

This is also broken for me at the moment. I get the following JS stack trace when trying to set up the integration:

builds:61 
Uncaught TypeError: Cannot read property 'deploykey' of undefined
    at A (swarm.faabc1465b10c974313a.js:1)
    at s.configureFinalMapState (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at s.computeStateProps (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at s.updateStatePropsIfNeeded (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at s.render (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at c._renderValidatedComponentWithoutOwnerOrContext (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at c._renderValidatedComponent (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at c.performInitialMount (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at c.mountComponent (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at Object.mountComponent (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at mountChildren (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at m._createInitialChildren (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at mountComponent (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at Object.mountComponent (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at c.performInitialMount (vendor_dashboard.cf6e03778d5449d1801e.js:1)
    at c.mountComponent (vendor_dashboard.cf6e03778d5449d1801e.js:1)

Broken for Github and Bitbucket, it seems.

bushong1 commented 5 years ago

Us too @CarlQLange.

CarlQLange commented 5 years ago

I recreated my entire docker hub repository and it worked afterwards, but that was not a fun experience :(

meticulous-dft commented 5 years ago

@CarlQLange That is not related to the bitbucket issue. We had a bug in last Friday's deployment causing the deploy key problem. It is fixed yesterday.

github-actions[bot] commented 3 years ago

We are clearing up our old issues and your ticket has been open for one year with no activity. Remove stale label or comment or this will be closed in 15 days.