cncf-infra / mock-project-repo Goto Github PK

This issue is not a help request but User Acceptance Testing for help request handling

@hh made the following comment on another issue

We'll need to create a folder for syncing labels: https://github.com/kubernetes/test-infra/tree/master/label_sync#label_sync

Let's look into creating a label_sync GitHub action job that get's trigged when the labels.yaml changes.

Given that ko is used to package up the container that pga is built from, add the git commit to a file in ./kodata so that pga can report the code from whence it came.

This will assist with support and troubleshooting.

On the following action

https://github.com/cncf-infra/mock-project-repo/actions/runs/3175479385/jobs/5190559246#step:3:32

We see a stack trace from a panic ...

main.errorOnPanic.func1()
	k8s.io/prow/cmd/pga/main.go:507 +0x85

Rest of stack trace ....

k8s.io/test-infra/prow/github.(*client).BotUserCheckerWithContext(0xc000ac6040, {0x2517a48?, 0xc000064060?})
	k8s.io/[email protected]/prow/github/client.go:1358 +0x19c
k8s.io/test-infra/prow/github.(*client).BotUserChecker(0x4cb3f7?)
	k8s.io/[email protected]/prow/github/client.go:1346 +0x27
k8s.io/test-infra/prow/plugins/approve.handlePullRequest(0xc0001f2000, {0x7f637a759218, 0xc000b2c020}, {0x7f637a759290, 0xc000524300}, {{0x212c9f7?, 0x0?}, 0xc00088aab0?}, 0x0?, 0xc000bb94d8)
	k8s.io/[email protected]/prow/plugins/approve/approve.go:307 +0x23c
k8s.io/test-infra/prow/plugins/approve.handlePullRequestEvent({{0x252ebb8, 0xc000b2c020}, {0x0, 0x0}, {0x0, 0x0}, 0x0, {0x25166b8, 0xc000[33](https://github.com/cncf-infra/mock-project-repo/actions/runs/3175479385/jobs/5190559246#step:3:34)8380}, 0xc0006f2820, ...}, ...)
	k8s.io/[email protected]/prow/plugins/approve/approve.go:285 +0xbc
main.handlePullRequestEvent.func1.1()
	k8s.io/prow/cmd/pga/main.go:373 +0x79
main.errorOnPanic(0xc0000a9de8?)
	k8s.io/prow/cmd/pga/main.go:510 +0x62
main.handlePullRequestEvent.func1({0xc00071ef88?, 0x12?}, 0x22[35](https://github.com/cncf-infra/mock-project-repo/actions/runs/3175479385/jobs/5190559246#step:3:36)5c8)
	k8s.io/prow/cmd/pga/main.go:373 +0x1a6
created by main.handlePullRequestEvent
	k8s.io/prow/cmd/pga/main.go:[36](https://github.com/cncf-infra/mock-project-repo/actions/runs/3175479385/jobs/5190559246#step:3:37)5 +0x1f1

Complete RCA then provide a fix

Describe how a developer can make a contribution to Prow Github Actions (pga) by describing pga in terms of its

• architecture (runtime, comparison with Prow hook)
• runtime life cycle as a custom Github Action (and also as an executable program)
• publishing mechanism that deploys a new version of the Custom Github Action using ko
• testing from a developer environment by running pga as an executable program

This is not a bug, but a test of the bug report template.

/user-acceptance-testing
/area/pga

As per title, deliverables would include.

• Overview
• Sample Github Actions using pga
• Sample Issues/PRs that demo the plugin behavior

Add an OWNERS file to the repo root to test running Prow Github Actions.

What happened:
Thing I tried to do was...
What you expected to happen:
I expected the thing to fibronicate the widget
How to reproduce it (as minimally and precisely as possible):
Click on main then click on the "fibronicate" link
Select Rob's testing widget from the list of widgets
Click the Fibronicate button
nothing happens, widget fibronification occurs.
Please provide links to example occurrences, if any:
https://localhost:789830/fibronicator

Anything else we need to know?:
This bug report is a test

Create a bootstrap process for a new or existing project repo that allows a project maintainer to configure PGA for their needs.

List out some acceptance criteria segmented by plugin so as to report on what plugins work when started from prow-github-actions

Testing issue

This issue is not a Bug report but User Acceptance Testing for Bug report handling

What happened:
I tried the thing
What you expected to happen:
The thing to work
How to reproduce it (as minimally and precisely as possible):
Visit https://example.org/try-the-thing

Please provide links to example occurrences, if any:
https://example.org/try-the-thing

Anything else we need to know?:
Demo thing for SIG Testing meeting

As a Project Maintainer I should be able to choose what plugins are configured on my invocation of PGA from a Github Action that I am maintaining.

• Right now, the plugins.yaml file is packaged up with the ko built container pga.
• Allow a Project Maintainer to inject their own plugins.yaml file (preferably from from a standard location in the project repo where the Action is running pga)