nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pipe release failed after updating bitbucket-pipe-release from 3.2.2 to 5.7.1

Julien HENRY_a7l2rp

Hi,

I know this is a big jump, but the release of our pipe was working fine before, and now it is failing with a cryptic message.

I suspect this is related to the inability to push or tag to master, but I have not changed anything.

The logs ends abruptly:

+ new_version=3.0.2 + USERNAME='Bitbucket Pipelines Push Bot'
+ [[ -n '' ]]
++ git config --get http.http://bitbucket.org/sonarsource/sonarqube-scan.proxy
+ HTTP_PROXY_DEFAULT=

Any idea?

Accepted answers

All comments

Igor Stoyanov

Hi @Julien HENRY . I think, this pipe is required to sue python image by default. Please, try to add:

image: python:3.10

to your release step. Waiting for your feedback.

Regards, Igor

Julien HENRY_a7l2rp

Thanks, I will try during the next release.

Fletcher, Andrew

I think the problem is actually the changes to Git around "dubious ownership"

Git command returns fatal error: "detected dubious ownership"

The line that's trying to set the HTTP_PROXY_DEFAULT variable by calling `git config` is failing and because of `set -e` this fails the whole script.

If you set `DEBUG: 'true` on the pipe then it shows that `git config --list` isn't returning anything.

I've forked the repo and added `git fsck` in the debug block and get this error:

fatal: detected dubious ownership in repository at '/opt/atlassian/pipelines/agent/build'
To add an exception for this directory, call:

 git config --global --add safe.directory /opt/atlassian/pipelines/agent/build

Adding the `whoami` and `ls -ld $(pwd)` to the debug shows:

root
drwxrwxrwx 6 nobody nobody 4096 Oct 15 08:00 /opt/atlassian/pipelines/agent/build

so whilst the script is running as root the working dir is owned by nobody which seems to be the cause of the problem.

Adding the safe.directory config early in the pipe's script does fix the problem but this needs to be something done by Atlassian (or in a forked pipe)

Igor Stoyanov

@Fletcher, Andrew thank you for your investigation.

Usually we use this option for git push: Configure repository ssh key pair and it will be safely used in pipeline to push to current repository

and your investigation related to the case described by: if neither of above is configured, the http proxy and http origin will be used to push

Our team will try to fix this http proxy and http origin option. Temporary we suggest to use Configure repository ssh key pair with this pipe.

Regards, Igor

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines

pipes