Hi Katie, thanks for the report.

I'm afraid I don't 100% understand your question. When you say you want to "clone into origin instead of the branch name", are you saying you wish the branch name to be named 'origin', or are you trying to perform a clone operation in Bitbucket?

If you could please share some exact steps of what you're trying to do, that'd be really helpful. Thank you!

I also experienced what appears to be this or a very similar issue. The Git SCM plugin defaults the remote name to "origin" when the refspec is not provided in the job config. The Bitbucket Server Integration SCM plugin, by comparison, uses the repo name as the remote and does not appear to provide a way to override this.

When I started switching jobs to use the Bitbucket Server Integration plugin I had to rework several scripts that performed git operations and assumed the remote was origin. The ability to set the refspec would have avoided these changes.

A slightly obfuscated example from the job build console log before and after converting a job:

Git SCM

> git fetch --tags --progress --prune --depth=10 -- ssh://git@<bitbucket>:7999/<project>/<repo>.git +refs/heads/*:refs/remotes/origin/* # timeout=10

Bitbucket Server Integration

> git fetch --tags --progress --prune --depth=10 -- ssh://git@<bitbucket>:7999/<project>/<repo>.git +refs/heads/*:refs/remotes/<repo>/* # timeout=10

The versions I am working with are:

• Jenkins 2.303.3
• Bitbucket Server Integration 3.2.0
• Git plugin 4.10.3
• git version 2.14.4

I see this behavior in both freestyle projects and pipeline projects.

A quick sample of the jenkinsfile for the pipeline job that has the issue:

pipeline {
    agent any
    stages {
        stage( 'Jenkins setup' ) {
            steps {
                script {
                    checkout BbS(
                        branches: [[name: "<repo>/master"]],
                        credentialsId: '<credentials>',
                        extensions: [
                            [$class: 'CloneOption', depth: 10, noTags: false, reference: '', shallow: true],
                            [$class: 'RelativeTargetDirectory', relativeTargetDir: '<dir>'],
                            [$class: 'CleanBeforeCheckout'],
                            [$class: 'PruneStaleBranch']
                        ],
                        id: '<id>',
                        mirrorName: '',
                        projectName: '<project>',
                        repositoryName: '<repo>',
                        serverId: '<server id>',
                        sshCredentialsId: '<credentials>'
                    )
                }
            }
        }
    }
}

I see. Perhaps it comes from BitbucketSCM.initializeGitScm, which passes getRepositorySlug() as String name to the UserRemoteConfig constructor.

BitbucketSCMSource.initializeGitScmSource does the same, but that does not seem to affect the clone on the agent. Does it affect something on the controller, instead?

In the Bitbucket Branch Source plugin, BitbucketGitSCMBuilder doesn't seem to configure the remote name, except when building a pull request merge. I suppose GitSCMBuilder.remoteName then retains its default value.

I retitled this issue to match what minielim described. I hope this is also what keblack789 meant.

Yes this is what i meant! are there any updates on this issue?

Hi,

Same "issue" here. I would like to override the remote name (to use 'origin') instead of the name of the repository.

Regards,

This creates a bug also for the submodule update. The submodule init searches for the "origin" remote entry in order to resolve the relative paths for submodules.

Since this plugin set entries like:

[remote "reponame"]
    url = ssh://git@bitbucket.example.com/projname/reponame.git 

instead of

[remote "origin"]
    url = ssh://git@bitbucket.example.com/projname/reponame.git
    fetch = +refs/heads/*:refs/remotes/origin/*

the git submodule init fails with:

warning: could not look up configuration 'remote.origin.url'. Assuming this repository is its own authoritative upstream. 

This happens also if the submodule init is set at the job level (job config).

System Configuration:

• Jenkins 2.346.3
• Bitbucket Server Integration Plugin Version 3.3.2
• Git plugin Version 4.14.2
• Git version 2.38.1

sigusro, can you reproduce the error with submodules if you don't use the Bitbucket Server Integration plugin at all, and instead use the "Git" branch source and add the "Configure remote name" behaviour? If so, I think it should be filed as a separate bug.

Kalle, thank you for your reply.

This behavior happens only when using this plugin. It works OK using others like the simple Git plugin.

I don't see a reason for a separate bug since the root cause is the usage of the slug instead of defaulting to "origin", hence the the topic of this ticket.

Any update here ? All other SCM/Git related plugin allow overriding the name of the remote