Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14340 > unrolled thread
| Started by | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| First post | 2022-08-14 09:20 +0200 |
| Last post | 2022-08-14 19:00 +0200 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Auto-handling of closed bugs - how does it work? Julian Gilbey <julian@d-and-j.net> - 2022-08-14 09:20 +0200
Re: Auto-handling of closed bugs - how does it work? Stefano Rivera <stefanor@debian.org> - 2022-08-14 10:50 +0200
Re: Auto-handling of closed bugs - how does it work? Julian Gilbey <julian@d-and-j.net> - 2022-08-14 15:10 +0200
Re: Auto-handling of closed bugs - how does it work? Sandro Tosi <morph@debian.org> - 2022-08-14 17:40 +0200
Re: Auto-handling of closed bugs - how does it work? Julian Gilbey <julian@d-and-j.net> - 2022-08-14 19:00 +0200
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2022-08-14 09:20 +0200 |
| Subject | Auto-handling of closed bugs - how does it work? |
| Message-ID | <EUg4F-twH-1@gated-at.bofh.it> |
A question of curiosity: when I push a commit to salsa with a "Closes: #nnnnn" in the changelog, the BTS gets a "tag: pending" notification. I looked and looked, and could not find out how salsa does this? Could anyone enlighten me? (The standard debian-ci scripts, which the repositories use for their CI, appear to only do something with RC bugs.) Best wishes, Julian
[toc] | [next] | [standalone]
| From | Stefano Rivera <stefanor@debian.org> |
|---|---|
| Date | 2022-08-14 10:50 +0200 |
| Message-ID | <EUhtL-uj2-27@gated-at.bofh.it> |
| In reply to | #14340 |
Hi Julian (2022.08.14_07:18:49_+0000) > A question of curiosity: when I push a commit to salsa with a "Closes: > #nnnnn" in the changelog, the BTS gets a "tag: pending" notification. > I looked and looked, and could not find out how salsa does this? > Could anyone enlighten me? (The standard debian-ci scripts, which the > repositories use for their CI, appear to only do something with RC > bugs.) It's a salsa webhook: https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages We don't have tooling that automatically configures all the repos, but when we migrated to salsa, we set them all up for tagpending, and posting to #debian-python-changes on IRC SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
[toc] | [prev] | [next] | [standalone]
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2022-08-14 15:10 +0200 |
| Message-ID | <EUlxn-wXg-3@gated-at.bofh.it> |
| In reply to | #14343 |
On Sun, Aug 14, 2022 at 08:45:32AM +0000, Stefano Rivera wrote: > Hi Julian (2022.08.14_07:18:49_+0000) > > A question of curiosity: when I push a commit to salsa with a "Closes: > > #nnnnn" in the changelog, the BTS gets a "tag: pending" notification. > > I looked and looked, and could not find out how salsa does this? > > Could anyone enlighten me? (The standard debian-ci scripts, which the > > repositories use for their CI, appear to only do something with RC > > bugs.) > > It's a salsa webhook: > https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages > > We don't have tooling that automatically configures all the repos, but > when we migrated to salsa, we set them all up for tagpending, and > posting to #debian-python-changes on IRC Ah, super, thanks! I'll start adding those to the projects I've created. Best wishes, Julian
[toc] | [prev] | [next] | [standalone]
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Date | 2022-08-14 17:40 +0200 |
| Message-ID | <EUnSy-ygA-3@gated-at.bofh.it> |
| In reply to | #14343 |
> It's a salsa webhook: > https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages > > We don't have tooling that automatically configures all the repos, but > when we migrated to salsa, we set them all up for tagpending, and > posting to #debian-python-changes on IRC shameless plug, i fixed most of the packages in our repo to have the proper wehbooks using https://github.com/sandrotosi/dpt-repos-check/blob/main/dpt-fix-integrations-webhooks.py (and now automation is available in pypi2deb, when you let it create the repo on salsa) -- consider new packages wont get the right setup old webhooks, etc I should probably run it more periodically -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
[toc] | [prev] | [next] | [standalone]
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2022-08-14 19:00 +0200 |
| Message-ID | <EUp7X-yXQ-13@gated-at.bofh.it> |
| In reply to | #14346 |
On Sun, Aug 14, 2022 at 11:38:10AM -0400, Sandro Tosi wrote: > > It's a salsa webhook: > > https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages > > > > We don't have tooling that automatically configures all the repos, but > > when we migrated to salsa, we set them all up for tagpending, and > > posting to #debian-python-changes on IRC > > shameless plug, i fixed most of the packages in our repo to have the > proper wehbooks using > https://github.com/sandrotosi/dpt-repos-check/blob/main/dpt-fix-integrations-webhooks.py > (and now automation is available in pypi2deb, when you let it create > the repo on salsa) -- consider new packages wont get the right setup > old webhooks, etc > > I should probably run it more periodically Oh wow, that's awesome, thanks!! Best wishes, Julian
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web