Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve BitBucket support #295

Open
brianmoose opened this issue Oct 4, 2017 · 0 comments
Open

Improve BitBucket support #295

brianmoose opened this issue Oct 4, 2017 · 0 comments

Comments

@brianmoose
Copy link
Contributor

brianmoose commented Oct 4, 2017 •
edited
Loading

Since we haven't really been using BitBucket it has fallen behind. We now have a repo that is going to be using it and possibly another on the way.

Statuses is the big one that BitBucket now supports but hasn't been implemented in Civet yet. We
still just post comments.

Civet also doesn't support auto adding/removing labels and updating an existing comment.

The tests for the bitbucket API also need to be improved, at least one recent problem would have been caught if the testing was more comprehensive.
brianmoose pushed a commit to brianmoose/civet that referenced this issue Oct 4, 2017
Fix bitbucket support.
186ac5c 
Tested against a live installation and PRs, pushes, comments,
seemed to work.

refs idaholab#295
brianmoose pushed a commit to brianmoose/civet that referenced this issue Oct 4, 2017
Fix bitbucket support.
340d732 
Tested against a live installation and PRs, pushes, comments,
seemed to work.

refs idaholab#295
brianmoose pushed a commit to brianmoose/civet that referenced this issue Oct 4, 2017
Fix bitbucket support.
4514d67 
Tested against a live installation and PRs, pushes, comments,
seemed to work.

refs idaholab#295
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brianmoose