tcms.issuetracker.bitbucket module

class tcms.issuetracker.bitbucket.BitBucket(bug_system, request)[source]

Bases: tcms.issuetracker.base.IssueTrackerType

Support for BitBucket. Requires:

Base_url:Repository URL - e.g. https://bitbucket.org/{workspace}/{repository}
Api_username:BitBucket Username
Api_password:BitBucket App Password - needs Issues: Read & write permission.

Note

You can leave the api_url field blank because the integration code doesn’t use it!

Warning

api_username is your BitBucket username, which you use to log in.

Note

api_password is “App Password” created in BitBucket. Here is a guide about creating and using an “App Password”; https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/

details(url)[source]

Return issue details from BitBucket

is_adding_testcase_to_issue_disabled()[source]

When is linking a TC to a Bug report disabled? Usually when not all of the required credentials are provided.

Returns:True if bug system api url, username and password are provided
Return type:bool
it_class

alias of BitBucketThread

report_issue_from_testexecution(execution, user)[source]

BitBucket creates the Issue with Title and Description

class tcms.issuetracker.bitbucket.BitBucketAPI(base_url=None, api_username=None, api_password=None)[source]

Bases: object

BitBucket API interaction class.

add_comment(issue_id, comment)[source]
create_issue(data)[source]
delete_comment(issue_id, comment_id)[source]
get_comments(issue_id)[source]
get_issue(issue_id)[source]
update_issue(issue_id, data)[source]
class tcms.issuetracker.bitbucket.BitBucketThread(rpc, bug_system, execution, bug_id)[source]

Bases: tcms.issuetracker.base.IntegrationThread

Execute BitBucket code in a thread!

Executed from the IssueTracker interface methods.

post_comment()[source]