<dea79fb5-629b-434c-874c-3d1a691e630b@vodafonemail.de>
I just pushed a tag to https://git.sr.ht/~jschmidt/copy-on-select-2 which should have triggered a build. But nothing happened. At all. Am I missing something?
<e5dcbfd9-2854-4c4d-ae10-b72bb34105f2@vodafonemail.de>
<dea79fb5-629b-434c-874c-3d1a691e630b@vodafonemail.de>
(view parent)
More data points: - A comparable build got triggered by a tag push 17 days ago: https://builds.sr.ht/~jschmidt/job/1389728 - I can resubmit other builds from the browser UI, so the build services seem to be working: https://builds.sr.ht/~jschmidt/job/1400083 - Tried re-tagging and re-pushing, nothing doing. - Modified .build.yml to hard-code GIT_REF to the tag I'm trying to push, submitted that with hut builds submit .build.yml -v public which resulted in successful (but unsatisfying since not automated) build https://builds.sr.ht/~jschmidt/job/1400103 Hm.
<lqnwlqc5tj6zvi3dyaet2ekrea7q2wmqgmsvovsw6mutlvs54w@dk54bcbvgaeb>
<dea79fb5-629b-434c-874c-3d1a691e630b@vodafonemail.de>
(view parent)
On 25-01-01 14:10:25, Jens Schmidt wrote: > which should have triggered a build. > > But nothing happened. At all. Had the same issue intermitently for the past couple of days. When it happened I just used hut to start a build manually. /Marius
<CC1C149D-7550-4279-8E8C-305A6A48568B@kararou.space>
<e5dcbfd9-2854-4c4d-ae10-b72bb34105f2@vodafonemail.de>
(view parent)
Do we have any news on this? I haven't had automatic build triggers for days.
<D6UVALHK8YAV.226FOWKA6WBZ0@cmpwn.com>
<CC1C149D-7550-4279-8E8C-305A6A48568B@kararou.space>
(view parent)
On Thu Jan 2, 2025 at 8:36 PM CET, Ræn Kararou wrote:
> Do we have any news on this? I haven't had automatic build triggers for days.
Back from holidays and looking into it. Are you still able to reproduce?
We had some issues with git.sr.ht being unreliable due to a DDoS attack
over the holiday, which we've now mitigated, so perhaps the problem has
resolved itself?
<489f3cac-ae8d-4973-ab51-2c438a3e10fe@vodafonemail.de>
<lqnwlqc5tj6zvi3dyaet2ekrea7q2wmqgmsvovsw6mutlvs54w@dk54bcbvgaeb>
(view parent)
> so perhaps the problem has resolved itself?
It has for one commit and for me at least, thanks.