stackstorm-exchange / stackstorm-bitbucket Goto Github PK

There are two type of "BitBucket" service, one is the 'BitBucket Cloud' and another is 'BitBucket Server'.
Troublingly, these API specifications are difference[^1][^2].

Current implementation of this pack depends on the BitBucket-api library, and this seems not to support the BitBucket Server's API (or rather this is no longer maintained, but this is not the essense of this issue).
I would be happy if the feature to deal with the BitBucket Server was added.

Thank you.

[^1] BitBucket Cloud API
[^2] BitBucket Server API

Hi, team. Thank you for providing this useful pack.

I want a feature that monitors events (updating of commit, or something) on a repository like github_repository_sensor in the GitHub pack.

Thank you.

BitBucket is deprecated it's v1.0 API on December 31, 2018 https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-v1-apis/

On initial inspection, this will affect all of the actions.

Sensor seems safe, as it's using a different library pybitbucket https://bitbucket.org/atlassian/python-bitbucket/src/master/

We might consider switching the actions over to using that library.

What is the variable needed to set the server ip?

Hi All,

Hoping I'm doing something wrong but I have an issue where I cannot list repos. Action returns ok, just says service not found?

[deepwatch@stackstorm configs]$ st2 run bitbucket.list_repos
.
id: 628baaa6cdd75af3f0e20e07
action.ref: bitbucket.list_repos
context.user: soae_user
parameters: None
status: succeeded
start_timestamp: Mon, 23 May 2022 15:39:18 UTC
end_timestamp: Mon, 23 May 2022 15:39:19 UTC
result:
  exit_code: 0
  result: Service not found.
  stderr: ''
  stdout: ''

In the get_{server|cloud}_updated_commits method which is called by poll, an exception of KeyError would be occurred when a new branch is created.

On the construction processing, 'RepositorySensor' checks last commits of all branches every repository.
After that, it monitors updated commits for them. But a new branch is appeared, a KeyError exception is raised.

I think it's reasonable solution to fix the branches to monitor in the configuration than applying the dynamically changing of branch in the repository.

Because there are many branches in the remote repository and most of them are temporary one. It's waste of resources to check update commit of them.

Background

When a monitoring repository is updated, the sensor RepositorySensor dispatches the following information for each commit to the trigger bitbucket.repository_event, as described here.

• Repository name which is updated by the commit
• Branch name which is updated by the commit
• Author who commits
• Committed time
• Commit message

Problem

I want to make different Rules according to the changed file in a Repository.
But, I can't identify the changed file from the dispatched information in the current implementation.

Proposal

Changing to append the information about changed file for each commit in the dispatching information.

The sensor to monitor the Bitbucket repositories is implemented in #5.
But that implementation has a problem in the processing of detecting an update on a repository. That can't detect an amended commit.

Sensor determines 'update' by comparing a newer commit than the last detected one with the commit-time.
But an amended commit can't be notified, because that will be same time with the replaced one.