bitbucket

README

Tested versions

• Bitbucket.com (2019-08-21)

Bitbucket API Docs

• Create auth token
• https://developer.atlassian.com/bitbucket/api/2/reference/resource/

All exported data

Permissions

Users that was added to default Developer groups has sufficient permissions for export.

Developers groups has the following permissions by default

This group has the following repository access

• Write access to new team repositories
• Can create repositories for team
• Can't update team settings or administer repositories

API call examples

The password can be an app password (https://confluence.atlassian.com/bitbucket/app-passwords-828781300.html)

curl --user USER:PASSWORD https://api.bitbucket.org/2.0/user

Development commands

Minimal required args
go run . export --agent-config-json='{"customer_id":"c1"}' --integrations-json='[{"name":"bitbucket", "config":{"url":"https://api.bitbucket.org", "user":"XXX","password":"YYY"}}]'

All args
go run . export --agent-config-json='{"customer_id":"c1", "skip_git":false}' --integrations-json='[{"name":"bitbucket", "config":{"url":"https://api.bitbucket.org", "user":"XXX","password":"YYY", "excluded_repos":[],"only_git":false,repos:["pinpt/test_repo"], "stop_after_n":1}}]'

URL      string `json:"url"`
APIKey string `json:"api_key"`

// ExcludedRepos are the repos to exclude from processing. This is based on github repo id.
ExcludedRepos []string `json:"excluded_repos"`
OnlyGit       bool     `json:"only_git"`

// Repos specifies the repos to export. By default all repos are exported not including the ones from ExcludedRepos. This option overrides this.
// Use bitbucket nameWithOwner for this field.
// Example: user1/repo1
Repos []string `json:"repos"`

// StopAfterN stops exporting after N number of repos for testing and dev purposes
StopAfterN int `json:"stop_after_n"`

Onboard Users

• The account_id field will be used as the RefID which is a unique identifier across all atlassian(https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/#introducing-atlassian-account-id-and-nicknames)

Missing data

• It is not possible to get emails from users /teams/:name/members
• It is not possible to get usernames from users /teams/:name/members

Does updating pr node children update updated_at field on parent?

This is needed so that incremental export does not have to get call for pr comments and reviews on every single pr and other similar cases.

testing different cases

• create pr
  • created_on 2019-09-19T16:48:02.187173+00:00
  • updated_on 2019-09-19T16:48:02.230229+00:00
• create a comment on pr
  • created_on 2019-09-19T16:48:02.187173+00:00
  • updated_on 2019-09-19T16:49:44.417294+00:00 (updated)
• edit the comment on pr
  • created_on 2019-09-19T16:48:02.187173+00:00
  • updated_on 2019-09-19T16:50:36.033829+00:00 (updated)
• added reviewer
  • created_on 2019-09-19T16:48:02.187173+00:00
  • updated_on 2019-09-19T16:51:31.502755+00:00 (updated)
• approve from reviewer
  • created_on 2019-09-19T16:48:02.187173+00:00
  • updated_on 2019-09-19T16:54:01.492411+00:00 (updated)

updated_on got updated for all scenarios

TODO

• There is a pull request state called SUPERSEDED, not sure how to interpret this kind of PR

Notes

-- It's not possible to get URL for reviews -- If the user needs to have the admin level, otherwise the call to get commit stats will fail with status 404