Skip to content

Ambiguity in configuration documentation #216

Open
@bpstahlman

Description

@bpstahlman

According to the README...

Select and configure Git SCM
Add Repository URL, [email protected]:${repositoryOwner}/${repositoryName}.git

But the sample configuration call...

bitbucketpr(projectPath:'<BIT_BUCKET_PATH>', ...)

...doesn't set a key called "Repository URL". The closest thing I see is "projectPath", whose value is listed as <BIT_BUCKET_PATH>. But what exactly is this path? The Bitbucket base URL, or the full URL for the project? Does the plugin append the repositoryOwner and repositoryName to projectPath? E.g., something like...

<BIT_BUCKET_PATH>/rest/api/1.0/projects/${repositoryOwner}/repos/${repositoryName}

Also, how does the configuration performed via bitbucketpr(...) interact with the connection information stored in the Bitbucket endpoint (configured apart from any specific project)? IOW, is it possible to "piggyback" off the connection/credentials information used to checkout the project?

Can this plugin use an SSH key, or is http(s) required? (I'm currently using SSH to checkout the project, but I have a username/password account I could use instead.)

In an attempt to find answers to some of these questions, I searched for the terms "projectPath", "repositoryName", etc. within the plugin's source on GitHub, but those terms weren't even found. Any insights you can provide would be appreciated...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions