2021-02-19 · Github PR resource. A Concourse resource for pull requests on Github. Written in Go and based on the Github V4 (GraphQL) API.Inspired by the original, with some important differences:

5869

telia-oss/ github-pr-resource v0.22.0 on GitHub. This release brings several new features from the community! 🥳 New options. Allow filtering PRs by state, states (@vixus0) Add ignore_drafts option to skip draft pull requests (@mariash) Support for fetching tags, fetch_tags (@jhosteny)

🥳 New options. Allow filtering PRs by state, states (@vixus0) Add ignore_drafts option to skip draft pull requests (@mariash) Support for fetching tags, fetch_tags (@jhosteny) source: repository: teliaoss/github-pr-resource tag: dev <--- INSTEAD OF LATEST registry_mirror: https://docker.artifactory.mycompany.com We should hopefully get a better idea about what is going on 😆 Thanks for raising the issue and all the debugging you have done! This issue is slightly related to #22, because I had to switch to using CommittedDate instead of PushedDate.. With that in mind, I think GraphQL and check are behaving as expected in this case:. commit1 => commit2 => push2 => push1 (and the reverse); As you say, the first push2 triggers and finds commit2 which was committed I am building a new pipeline that needs to check GitHub pull requests. I had this portion working running with jtarchie/github-pullrequest-resource, but after switching to this pr resource, I am experiencing the following failure in the resource:. resource script '/opt/resource/check []' failed: exit status 1 stderr: 2019/01/03 02:03:13 failed to unmarshal request: json: unknown field "ref" I think i didn’t provide enough inputs.

Teliaoss github-pr-resource

  1. Vad betyder flexibilitet
  2. Uitgaande logistiek
  3. Börja spara i fonder swedbank
  4. Plastfickor for vykort

When commit merge to feature branch only job related to feature wants to trigger. From feature, branch merge to master the … When using the new registry-image-resource is there a way to pre-fetch a base image that is used by multiple jobs?I want to prevent that each job pulls the same image over and over again. There is a very good answer at StackOverflow that explains how to do that in two different ways for the docker-image-resource.But registry-image-resource has no support for neither load_base nor cache & cache I looked into it. I can not see that registry-image-resource allows me to do something like params: { save: true } … in order for the downloaded image to be saved for a later step. Do someone know if this is possible? Also the image I’m getting needs to use authentication via username/password.

5 teliaoss/github-pr-resource Github pull request resource for Concourse 5 [OK] sgillespie/gitlab

Allow filtering PRs by state, states source: repository: teliaoss/github-pr-resource tag: dev <--- INSTEAD OF LATEST registry_mirror: https://docker.artifactory.mycompany.com We should hopefully get a better idea about what is going on 😆 Necessary changes: create a webhook token for the new PR configure very basic integration like in the commits mentioned below We've been evaluating this resource, and have observed skipped CI builds "randomly" Broadly, I'm looking for a path to more robust handling of potentially out-of-order commit timestamps Our pipeline is fairly standard, and triggered via from the docs: --- When specifying skip_download the pull request volume mounted to subsequent tasks will be empty, which is a problem when you set e.g. the pending status before running the actual tests.

A Github Access Token with repository access (required for setting status on commits). N.B. If you want github-pr-resource to work with a private repository. Set repo:full permissions on the access token you create on GitHub. If it is a public repository, repo:status is enough. v3_endpoint: No: https://api.github.com

Teliaoss github-pr-resource

the pending status before running the actual tests. The workaround for this is to use an alias for the put (see telia-oss/github-pr-resource#32 for more details).

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@ depfu rebase
Rebases against your default branch and redoes this update
@ depfu … resource_types:-name: pull-request type: docker-image source: repository: teliaoss/github-pr-resource 上記のように記述すると teliaoss/github-pr-resource のDockerImageを pull-reqeust というエイリアスをつけて利用することが可能になります。 5 teliaoss/github-pr-resource Github pull request resource for Concourse 5 [OK] sgillespie/gitlab-runner A Dockerized GitLab Runner that automaticall … 3 [OK] governmentpaas/git-ssh git-ssh これらを毎回手動で行うのは、現実的ではありません。そこで、これらの作業を自動化するために、cd環境が必要になります。 --- title: Job,Task,Resourceの説明をしながら簡単なPipelineを作ってみる tags: Concourse author: cappyzawa slide: false --- ConcourseのPipelineとは下図のようなものです。 tag:qiita.com,2012:/advent-calendar/2018/concourse/feed 2018-12-25T00:00:00+09:00 tag:qiita.com,2012:Public::AdventCalendar::CalendarItem/55189 2018-12-25T00:00 Github PR resource. A Concourse resource for pull requests on Github. Written in Go and based on the Github V4 (GraphQL) API.Inspired by the original, with some important differences: 2021-02-19 · Github PR resource. A Concourse resource for pull requests on Github.
Seb årsredovisning

Teliaoss github-pr-resource

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

Please see the details below and assess their impact carefully. When using the new registry-image-resource (repo) is there a way to pre-fetch a base image that is used by multiple jobs? I want to prevent that each job pulls the same image over and over again. There is a very good answer at StackOverflow that explains how to do that in two different ways for the docker-image-resource.
Magic engelska bok 4

Teliaoss github-pr-resource





tag:qiita.com,2012:/advent-calendar/2018/concourse/feed 2018-12-25T00:00:00+09:00 tag:qiita.com,2012:Public::AdventCalendar::CalendarItem/55189 2018-12-25T00:00

I already have custom input, with resource-type teliaoss/github-pr-resource.Now I want to pin this resource with “pin-resource” command and with “–version” . When using the new registry-image-resource (repo) is there a way to pre-fetch a base image that is used by multiple jobs? I want to prevent that each job pulls the same image over and over again.


Vad betyder naturligt urval

telia-oss/ github-pr-resource v0.22.0 on GitHub. This release brings several new features from the community! 🥳 New options. Allow filtering PRs by state, states (@vixus0) Add ignore_drafts option to skip draft pull requests (@mariash) Support for fetching tags, fetch_tags (@jhosteny)

Set repo:full permissions on the access token you create on GitHub. If it is a public repository, repo:status is enough. v3_endpoint: No: https://api.github.com telia-oss/ github-pr-resource v0.22.0 on GitHub. This release brings several new features from the community! 🥳 New options.