#226 [citest] commend does not work when not standalone in the comment
Opened 4 years ago by churchyard. Modified 3 years ago

It seem that the "Fedora CI - scratch build" job is not restarted when we comment [citest]. Is that expected? Is there another comment to restart this?

When you comment on a PR:

[citest] [recheck]

Zuul obeys the [recheck] command, but Jenkins ignores the [citest] one.


Metadata Update from @mvadkert:
- Issue priority set to: High (was: Medium)
- Issue tagged with: feature, jenkins

4 years ago

@msrb hmm, I guess this never worked right?

@churchyard you should be able to restart the jenkins job for now, you can login via FAS there

you should be able to restart the jenkins job for now

How do I find the Jenkins job?

@msrb hmm, I guess this never worked right?

I always worked. Testing always starts (and restarts) by scratch-building.

@churchyard are we talking about any specific pull request here?

Ah, I see:

[citest] [recheck]

We are kinda strict about this now. [citest] has to be the only string in the comment (IIRC). We could loosen it up a bit.

Note that I am 99% sure this used to work before.

This ticket has been triaged as High priority 11 months ago. What can I do to help make it happen?

Log in to comment on this ticket.

Metadata