allow retester to work with optional contexts

[0xmichalis]

Soon tide will be able to handle optional github contexts. We should also find a solution for having the commenter ignore optional contexts too.

@stevekuznetsov @fejta @cjwagner

/area prow
/kind feature

[0xmichalis]

@sdodson fyi

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[BenTheElder]

Maybe its first comment can have /skip?
/remove-lifecycle rotten

[0xmichalis]

Maybe its first comment can have /skip?

Note that /skip works only with contexts owned by prow.

[BenTheElder]

Sure, but I don't know if we need to solve "PR is lgtm + approve but not merging and failing a non-prow presubmit while using fejta-bot", OTOH: "PR is lgtm + approve but not merging while failing a non-blocking prow presubmit while using fejta-bot" seems simple to fix.

[BenTheElder]

Or: cutting down fejta-bot spam that isn't due to important failures seems like a good idea, but fejta-bot will also spam for any context not passing that is blocking besides ones that aren't prow currently (and non-blockng prow). I'm not sure if we need to immediately handle all of these.

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: 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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.