-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
BuildingRef is incorrectly populated on Bitbucket pipelines #935
Comments
Thank you for the excellent bug report. It looks like our bitbucket code hasn't changed since it was first introduced, so the problem must be elsewhere. Maybe this isn't a BitBucket-specific problem. While I investigate this, can you please dump the environment block from within a bitbucket pipeline so I can imagine how that data will flow through NB.GV? |
Oh gosh. 3.6 added BitBucket support, so ya, this is BitBucket specific and apparently it's just buggy. It should be returning strings that start with |
BitBucket environment variables do not include the `refs/` prefix, so we need to add them ourselves (as we do for some other cloud build services already). Fixes #935
BitBucket environment variables do not include the `refs/` prefix, so we need to add them ourselves (as we do for some other cloud build services already). Fixes #935
BitBucket environment variables do not include the `refs/` prefix, so we need to add them ourselves (as we do for some other cloud build services already). Fixes #935
@AArnott Ok! Do you still need the environment of the pipeline or should we start by testing the PR? |
I think we can test the PR at this point, as I'm pretty sure of what the environment must be. |
Ok! Here are the env variables relevant to the commit, so your guess seems good to me. Branch build Tag build |
Hi,
Since updating nbgv from v3.5.119 to v3.6.128 we are experiencing an issue with the
BuildingRef
when running on Bitbucket pipelines. Previously theBuildingRef
was set torefs/heads/<branch name>
, while in the new version it's set to only<branch name>
. This only happens when running in a Bitbucket pipeline, when running locally both versions prefix the branch name withrefs/heads/
.This issue is causing the
PublicReleaseRefSpec
matching to fail in Bitbucket which means no releases are flagged as public unless we modify the regex.Here's a minimal example of how to reproduce this issue.
The following is output from each version of nbgv.
As can be seen in the output above,
PublicRelease
andBuildingRef
differ between the two versions.The text was updated successfully, but these errors were encountered: