Pipeline: Support Bitbucket Server Pull Request PipelineResource updates

[amlozano]

Expected Behavior

I am able to update Bitbucket pull request status via PullRequest PipelineResource update

Actual Behavior

Only GitHub and GitLab are supported in go-scm

Additional Info

It would be nice to have Bitbucket Pull Request update support in tekton, to complete the tier of most used SCMs.

[vdemeester]

Note that PipelineResource are going through a major redesign (and won't make it to the v1beta1 api). But in any case, we are looking into adding support for more provider (be it by PipelineResource or generic Tasks from the catalog).

/kind feature

[amlozano]

Oh, I didn't know about that redesign, I am new to the project (as an user) and I didn't find any issue related to the extensibility for BitBucket PR. If you think this can be re-defined in another way or it doesn't make sense anymore after the redesign, feel free to modify or close the ticket.

[orefalo]

I am also looking at bitbucket support. that's pretty much a show stopper for me, i can't change scm provider

[vdemeester]

@amlozano @orefalo for the time being (aka while PipelineResource are re-designed), you should be able to use any provider using a re-usable task. For git, it would be the git-clone task

[orefalo]

Tks,

I gave it another try and I can't figure how to authenticate against my git repo.

[orefalo]

nevermind, found this
https://github.com/tektoncd/pipeline/blob/master/docs/auth.md

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.