Unable rerun build which triggered before repo renamed

Issue #16210 open
Ronald Chia
staff created an issue


Rerun previous build after renaming repository will receive the following error during the "Build setup" step.

+ GIT_LFS_SKIP_SMUDGE=1 git clone --branch="master" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/USER/New_Name.git $BUILD_DIR ; git reset --hard <commit-hash> ; git remote set-url origin git@bitbucket.org:USER/New_Name.git
Cloning into '/opt/atlassian/pipelines/agent/build'...
remote: Repository USER/Old_Name not found
fatal: repository 'https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/USER/Old_Name.git/' not found

Steps to Reproduce

  1. Rename repository with previous builds triggered
    • Repository Settings>Repostiory Details>Update Name >Save repository details
  2. Navigate to Pipelines page
  3. Rerun previous build then check Build Setup step

Expected Results

The new rerun build should clone using the new repository name during Build Setup step

Current Outcome

The new rerun build will clone using the old repository name during Build Setup step

Comments (5)

  1. Aneita Yang staff
    • changed status to open


    Thanks for reaching out and for raising this bug.

    I've created an issue in our backlog to look into this bug in more detail. However, this is currently low priority for us, so it is unlikely that we'll work on this anytime soon.

    I'll keep you updated on our progress via this ticket.


  2. Umar Hussain

    Hi, I'm facing the same issue. I tried to manually trigger pipeline on a branch but it still failing. The error log shows that it is still trying to fetch repo using old name. Is there any workaround until the fix arrives?

  3. Log in to comment