Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cathive/concourse-bitbucket-pullrequest-resource
fetches pull request from BitBucket Server/Cloud and updates the status of the PR
https://github.com/cathive/concourse-bitbucket-pullrequest-resource
bitbucket-cloud bitbucket-server concourse-resource continuous-integration pull-request
Last synced: 11 days ago
JSON representation
fetches pull request from BitBucket Server/Cloud and updates the status of the PR
- Host: GitHub
- URL: https://github.com/cathive/concourse-bitbucket-pullrequest-resource
- Owner: cathive
- License: apache-2.0
- Created: 2017-10-12T18:44:48.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2017-10-17T11:11:49.000Z (over 7 years ago)
- Last Synced: 2024-11-16T08:23:53.218Z (2 months ago)
- Topics: bitbucket-cloud, bitbucket-server, concourse-resource, continuous-integration, pull-request
- Language: Shell
- Homepage:
- Size: 12.7 KB
- Stars: 0
- Watchers: 3
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Authors: AUTHORS.md
Awesome Lists containing this project
README
# BitBucket Pull Request Resource
Tracks changes for all *git* branches managed by BitBucket (Server or Cloud) for pull requests.
**This resource is meant to be used with [`version: every`](https://concourse.ci/get-step.html#get-version).**
## Origins of this project
We have had some issues with the existing resources that implemented BitBucket pull request handling
and therefore decided to roll our own. Most of the scripts are based on work from other GitHub
repositories:
* [philicious/concourse-git-bitbucket-pr-resource](https://github.com/philicious/concourse-git-bitbucket-pr-resource)
* [zarplata/concourse-git-bitbucket-pr-resource](https://github.com/zarplata/concourse-git-bitbucket-pr-resource)
## Installation
Add the following `resource_types` entry to your pipeline:
```yaml
---
resource_types:
- name: bitbucket-pr
type: docker-image
source:
repository: cathive/concourse-bitbucket-pullrequest-resource
tag: latest # You'll probably want to use a verionsed tag to ensure that your builds are reproducible
```
## Source Configuration
* `base_url`: *Required*. base URL of the bitbucket server, without a trailing slash.
For example: `http://bitbucket.local`
* `username`: *Required*. username of the user which have access to repository.
* `password`: *Required*. password of that user
* `project`: *Required*. project for tracking
* `repository`: *Required*. repository for tracking
* `limit`: *Optional*. limit of tracked pull requests `default: 100`.
* `git`: *Required*. configuration is based on the [Git
resource](https://github.com/concourse/git-resource). The `branch` configuration
from the original resource is ignored.
* `bitbucket_type`: *Optional*. `cloud` for BitBucket Cloud or `server` for a self-hosted BitBucket Server. `default: server`
### Example
``` yaml
resources:
- name: my-repo-with-pull-requests
type: bitbucket-pr
source:
url: http://bitbucket.local
username: some-username
password: some-password
project: cathive
repository: concourse-bitbucket-pullrequest-resource
git:
uri: https://github.com/cathive/concourse-bitbucket-pullrequest-resource
private_key: ((git-repo-key))
jobs:
- name: my build
plan:
- get: my-repo-with-pull-requests
trigger: true
version: every
- task: unit test
...
inputs:
- name: my-repo-with-pull-requests
run:
...
on_failure:
put: my-repo-with-pull-requests
params:
state: FAILED
name: "unit test"
dir: my-repo-with-pull-requests
on_success:
put: my-repo-with-pull-requests
params:
state: SUCCESSFUL
name: "unit test"
dir: my-repo-with-pull-requests
```
## Behavior
### `check`: Check for changes to all pull requests.
The current open pull requests fetched from Bitbucket server for given
project and repository. Update time are compared to the last fetched pull request.
If any pull request are new or updated or removed, a new version is emitted.
### `in`: Fetch the commit that changed the pull request.
This resource delegates entirely to the `in` of the original Git resource, by
specifying `source.branch` as the branch that changed, and `version.ref` as the
commit on the branch.
All `params` and `source` configuration of the original resource will be
respected.
### `out`: Update build task status.
This updates the build status of the task.
#### Parameters
* `dir`: *Optional*. set to name of the resource if resource name is different than repository name