Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1264265 > unrolled thread
| Started by | Ian Jackson <ijackson@chiark.greenend.org.uk> |
|---|---|
| First post | 2025-10-01 14:00 +0200 |
| Last post | 2025-10-02 13:50 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.bugs.dist
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1116966: webhook (or similar) from browse.dgit.debian.org Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-10-01 14:00 +0200
Bug#1116966: webhook (or similar) from browse.dgit.debian.org Simon Josefsson <simon@josefsson.org> - 2025-10-01 14:10 +0200
Bug#1116966: webhook (or similar) from browse.dgit.debian.org Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-10-01 14:20 +0200
Bug#1116966: webhook (or similar) from browse.dgit.debian.org Sean Whitton <spwhitton@spwhitton.name> - 2025-10-02 13:50 +0200
| From | Ian Jackson <ijackson@chiark.greenend.org.uk> |
|---|---|
| Date | 2025-10-01 14:00 +0200 |
| Subject | Bug#1116966: webhook (or similar) from browse.dgit.debian.org |
| Message-ID | <LB3F0-1WCd-3@gated-at.bofh.it> |
Package: dgit-infrastructure
Version: 13.13
Simon Josefsson writes ("webhook from browse.dgit.debian.org?"):
> Hi. I'm playing with the idea of a Debian Blend that build and publish
> packages directly from git in CI/CD, based on sources on
> browse.dgit.debian.org. I think most things are feasible to implement,
> but getting notifications of new uploads is a tricky concern. Is it
> possible to setup a webhook from when browse.dgit.debian.org gets a new
> version of a package somehow? Maybe other services will need this too,
> so you may want to design a generic mechanism. Or is there one already?
How exciting!
We should definitely have a way to support this.
I'm not sure a webhook is right, We would need to maintain a
subscriber list, and it might get rather long.
Perhaps we should send updates to a mailing list. Email already has
retries, subscription management, and so on. We could use
debian-*-changes, but that might be controversial (and we'd need to
figure out *which* list to post to). Or we could have a new list.
Ian.
--
Ian Jackson <ijackson@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
[toc] | [next] | [standalone]
| From | Simon Josefsson <simon@josefsson.org> |
|---|---|
| Date | 2025-10-01 14:10 +0200 |
| Message-ID | <LB3OF-1WWf-9@gated-at.bofh.it> |
| In reply to | #1264265 |
[Multipart message — attachments visible in raw view] — view raw
Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Package: dgit-infrastructure
> Version: 13.13
>
> Simon Josefsson writes ("webhook from browse.dgit.debian.org?"):
>> Hi. I'm playing with the idea of a Debian Blend that build and publish
>> packages directly from git in CI/CD, based on sources on
>> browse.dgit.debian.org. I think most things are feasible to implement,
>> but getting notifications of new uploads is a tricky concern. Is it
>> possible to setup a webhook from when browse.dgit.debian.org gets a new
>> version of a package somehow? Maybe other services will need this too,
>> so you may want to design a generic mechanism. Or is there one already?
>
> How exciting!
>
> We should definitely have a way to support this.
>
> I'm not sure a webhook is right, We would need to maintain a
> subscriber list, and it might get rather long.
>
> Perhaps we should send updates to a mailing list. Email already has
> retries, subscription management, and so on. We could use
> debian-*-changes, but that might be controversial (and we'd need to
> figure out *which* list to post to). Or we could have a new list.
E-mail is okay, but it is not synchronous. A separate mailing list
seems fine, and I think everything going into browse.dgit.debian.org
could be posted to the same (new) list, using some standardized
machine-readable format.
Long-term, I think I would prefer something synchronous instead, but
this is really not an urgent request, mostly a question if there already
exists some method to get notifications of new tag2upload tags somehow.
/Simon
[toc] | [prev] | [next] | [standalone]
| From | Ian Jackson <ijackson@chiark.greenend.org.uk> |
|---|---|
| Date | 2025-10-01 14:20 +0200 |
| Message-ID | <LB3Yl-1X0m-5@gated-at.bofh.it> |
| In reply to | #1264267 |
Simon Josefsson writes ("Bug#1116966: webhook (or similar) from browse.dgit.debian.org"):
> E-mail is okay, but it is not synchronous.
I'm not sure what you mean by "not synchronous".
Email shouldn't involve arbitrary delays, if everything is working
correctly. If there are delays then that's because of load on the
systems involved.
If you mean "the push to push.dgit.d.o does not succeed until all the
subscribers are notitifed" then that is true, but of course it must
work that way because otherwise failure of an external subscriber
would stop the thing from working.
> Long-term, I think I would prefer something synchronous instead, but
> this is really not an urgent request, mostly a question if there already
> exists some method to get notifications of new tag2upload tags somehow.
I can confirm that there currently isn't anything.
If you watch debian-*-changes you can treat that as an "interrupt" to
cause a rescan of *.dgit.d.o (with git ls-remote maybe). Uploads
involving *.dgit.d.o are supposed to generate a message to -changes
from dak, if they aren't REJECTed.
Ian.
--
Ian Jackson <ijackson@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
[toc] | [prev] | [next] | [standalone]
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-10-02 13:50 +0200 |
| Message-ID | <LBpYR-2blF-1@gated-at.bofh.it> |
| In reply to | #1264267 |
[Multipart message — attachments visible in raw view] — view raw
Hello,
On Wed 01 Oct 2025 at 02:07pm +02, Simon Josefsson wrote:
> Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
>
>> Package: dgit-infrastructure
>> Version: 13.13
>>
>> Simon Josefsson writes ("webhook from browse.dgit.debian.org?"):
>>> Hi. I'm playing with the idea of a Debian Blend that build and publish
>>> packages directly from git in CI/CD, based on sources on
>>> browse.dgit.debian.org. I think most things are feasible to implement,
>>> but getting notifications of new uploads is a tricky concern. Is it
>>> possible to setup a webhook from when browse.dgit.debian.org gets a new
>>> version of a package somehow? Maybe other services will need this too,
>>> so you may want to design a generic mechanism. Or is there one already?
>>
>> How exciting!
>>
>> We should definitely have a way to support this.
>>
>> I'm not sure a webhook is right, We would need to maintain a
>> subscriber list, and it might get rather long.
>>
>> Perhaps we should send updates to a mailing list. Email already has
>> retries, subscription management, and so on. We could use
>> debian-*-changes, but that might be controversial (and we'd need to
>> figure out *which* list to post to). Or we could have a new list.
>
> E-mail is okay, but it is not synchronous. A separate mailing list
> seems fine, and I think everything going into browse.dgit.debian.org
> could be posted to the same (new) list, using some standardized
> machine-readable format.
>
> Long-term, I think I would prefer something synchronous instead, but
> this is really not an urgent request, mostly a question if there already
> exists some method to get notifications of new tag2upload tags somehow.
I think the biggest issue is maintaining a list of subscribers.
dgit.debian.org doesn't have readwrite access other than through SSH.
So either we implement some subscribing and unsubscribing mechanism
accessible to DDs via SSH (urgh), or a whole new web interface for doing
it. Neither are very palatable.
Whereas if we use a mailing list then this problem is solved for us.
--
Sean Whitton
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web