Updating private Bitbucket submodule doesn't work #24988
Replies: 3 comments 2 replies
-
Can we convert this to an Issue? |
Beta Was this translation helpful? Give feedback.
0 replies
-
configure the x-auth-token as username and the token as password |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @viceice ,
Unfortunately, it didn't work, this way even the submodule's new digest ( This is the error (I tried with different Renovate versions, this log comes from
Any other ideas? Updating |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us what version of Renovate you run.
docker: 37.0.3-slim, 35-159.7-slim
If you're self-hosting Renovate, select which platform you are using.
Bitbucket Cloud (bitbucket.org)
Was this something which used to work for you, and then stopped?
I am trying to get this working for the first time
Describe the problem
I have two private Bitbucket Cloud repos:
AAA
andBBB
.BBB
serves as a submodule forAAA
. This is the.gitmodule
configuration in theAAA
repo:As the
.gitmodule
shows, it is configured withgit
/ssh
, nothttps
, however Renovate tries to work with the submodule using thehttps
protocol.Currently, in the
AAA
, theBBB
submodule could be updated. TheBBB
commit kept inAAA
isede6c88
while the newest commit isd9357cd
.In the
Renovate
config file I set:The
token
is the Bitbucket Cloud Access token.I run Renovate with docker, having the `LOG_LEVEL=debug" set on.
In the logs, I see:
So far I am happy, I see that the git submodule was taken into consideration by Renovate.
I see that Renovate was able to see that the update in the submodule is required. The
currentDigest
andnewDigest
are correctly recognized by Renovate.Later logs:
And unfortunately the next log is the error:
If I change the token in the configuration to this (prefix the token with
x-token-auth
as Bitbucket Cloud proposes):I get a different error, from different git command:
However when I execute the command on my machine, it works:
BTW I also tried with username/password in many different ways... If needed I can deliver more logs.
Any help? I saw some issues and discussions here, but none of them provided any solution, maybe my approach based on Bitbucket Cloud Acces token could be a direction to go?
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
Placeholder value, please select the correct response from the dropdown
Beta Was this translation helpful? Give feedback.
All reactions