Enable golint and trigger plugins for kubernetes-sig-testing/frameworks

[jamesjoshuahill]

Following #6902

• enable triggers plugin to enable the /test command
• enable golint plugin because the repo is mostly golang

[hoegaarden]

/ok-to-test

[cjwagner]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cjwagner, jamesjoshuahill

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• prow/OWNERS [cjwagner]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@jamesjoshuahill: Updated the plugins configmap

In response to this:

Following #6902

• enable triggers plugin to enable the /test command
• enable golint plugin because the repo is mostly golang

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.

[BenTheElder]

isn't the lint plugin globally available now? @cjwagner

[cjwagner]

This will enable it for the entire kubernetes-sig-testing org if that is what you mean, but that seems fine to me.

If you are asking if the golint plugin gets webhooks for all repos without having to be explicitly enabled, we don't have any mechanism for plugins to do that AFAIK.

[hoegaarden]

Thanks @cjwagner for merging, thanks @BenTheElder for double-checking/reviewing!

Shouldn't enabling the trigger plugin (this PR) and adding a trigger RE (in the other PR) allow me to trigger a test with a comment on a PR like here. Is there still some configuration missing? Where could I check for logs or so?

[BenTheElder]

@hoegaarden you did trigger it, but you've got reporting disabled. from http://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/directory/pull-frameworks-test/ it appears that the job failed once or twice without posting logs. You can check for your job after triggering at https://prow.k8s.io/, though this only holds recent jobs that have not been GCed from the cluster. Pod logs are viewable there.