n7mobile / concourse-bitbucket-pr Goto Github PK

The example of the pipeline being used:

resource_types:
 - name: bitbucket-pr
   type: registry-image
   source:
     repository: n7mobile/concourse-bitbucket-pr

resources:
 - name: pull-request
   type: bitbucket-pr
   check_every: 1m
   source:
      workspace: ((bitbucket_project))
      slug: ((bitbucket_repo))
      username: ((bitbucket-username))
      password: ((bitbucket-password))
      debug: true

jobs:
  - name: check-pr
    serial: true
    plan:
    - get: pull-request
      version: every
      trigger: true
    - put: pull-request
      params:
         repo_path: pull-request
         action: set:commit.build.status
         status: INPROGRESS
         url: example.com

Resource put fails with the following error:

selected worker: concourse-worker-5995d5548d-gpv7f
calling out cmd wioth dest  /tmp/build/put
running command: %!w(*fmt.wrapError=&{resource/out: params invalid: resource/model: version path or name is empty 0xc00001c190})

Would like to see option for paths and ignore_paths like in https://github.com/concourse/git-resource#source-configuration

• paths: Optional. If specified (as a list of glob patterns), only changes to the specified files will yield new versions from check.
• ignore_paths: Optional. The inverse of paths; changes to the specified files are ignored.

Is there anyway to send back a comment to the Pull-Request?

When attempting to set the build status, I get this error. However, I am not able to find "resource/model: version path or name is empty" in the code. There are other "resource/model:" errors, but not the one displayed below. Is there a change that has not been tracked in git, but is in the docker image?

running command: %!w(*fmt.wrapError=&{resource/out: params invalid: resource/model: version path or name is empty 0xc00007ade0})

As in the title: when I merge a develop branch into the existing PR branch the resource does not yield a new version.

Hi there @antrov, at some point Bitbucket Cloud added support for OAuth 2.0 to their API.

It would be nice if this resource provided an option that allows users to take advantage of this.

In my use case, I have an OAuth Consumer in Bitbucket Cloud set up for Concourse and I would like to use those credentials with this resource rather than a username and password.

Is this something you would consider merging in if I can find the time to send you a PR?

When I pass the url parameter for out action with $BUILD_ID variable inside it doesn't get substituted with the actual build id.

Hi. I've set up pipeline with PR resource in its simplest form. It checks BitBucket repo every 2 minutes. When new PR arrives, Concourse build is triggered as expected and completes successfully.
Some time later I push additional commits to existing PR and expect it to trigger build again, but it does not happen.
Question: is it possible to trigger build again for newer commits? Thanks.