Run update-bug on patchset-created again

Now that the update-bug script no longer tries to update bug
assignments, it's possible to run it on patchset-created events
again. Go back to doing that until someone has time to build a
suitable replacement for it.

This partially reverts commit
1ccf5e68e5.

Change-Id: Idf589eb818d208d65d1f1430ddec962b015165c0
Depends-On: https://review.opendev.org/782538
This commit is contained in:
Jeremy Stanley 2021-03-23 15:22:49 +00:00
parent aa4f1b4256
commit dbcc867cc7
1 changed files with 1 additions and 1 deletions

View File

@ -7,10 +7,10 @@ export PROJECTS_YAML=/var/gerrit/etc/projects.yaml
export PROJECTS_INI=/var/gerrit/etc/projects.ini
# Use timeout to kill any process running longer than 10 minutes.
timeout -k 2m 10m /usr/local/bin/update-bug patchset-created "$@"
timeout -k 2m 10m /usr/local/bin/notify-impact patchset-created "$@" --impact SecurityImpact --dest-address 'openstack-security@lists.openstack.org'
# TODO: reenable these once jeepyb no longer relies on the old Gerrit DB
#timeout -k 2m 10m /usr/local/bin/update-blueprint patchset-created "$@"
#timeout -k 2m 10m /usr/local/bin/update-bug patchset-created "$@"
#if [ -f /var/gerrit/etc/ssh_welcome_rsa_key ] ; then
#timeout -k 2m 10m /usr/local/bin/welcome-message patchset-created \
# --verbose --ssh-user=welcome-message \