This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
laforge gerrit-no-reply at lists.osmocom.orglaforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/26423 ) Change subject: jobs/redmine-fetch: close issues on gerrit merge ...................................................................... Patch Set 5: > Patch Set 5: > > Or maybe I'm thinking too complicated... we could set up a cronjob that calls "bin/rails runner "Repository.fetch_changesets" -e production" in the redmine docker container every 10 minutes or so, it seems that then we don't need to set up a mapping. excellent. > The "downside" is that it doesn't close issues immediately after merging gerrit patches, but that's probably not important. no, the exact time is not important, 10mins is fine. -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/26423 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: Ia7c6c8426e5ca0de04378cedd0360c368e9d5027 Gerrit-Change-Number: 26423 Gerrit-PatchSet: 5 Gerrit-Owner: osmith <osmith at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: laforge <laforge at osmocom.org> Gerrit-Comment-Date: Tue, 30 Nov 2021 10:50:26 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211130/5857a1c1/attachment.htm>