fedora-ci / general

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

Open
Close Issue

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

@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?
Edited by msrb

Yes, https://src.fedoraproject.org/rpms/python3-docs/pull-request/32 -- sorry for not mentioning it sooner.

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.

Oh. My bad.

I've renamed the issue.

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?

@msrb @jbair PTAL
Metadata
None

feature jenkins

None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.