linuxserver / docker-jellyfin

GNU General Public License v3.0
600 stars 92 forks source link

[BUG] Nightly builds seem to have stopped 19 days ago #207

Closed jarylc closed 9 months ago

jarylc commented 11 months ago

Is there an existing issue for this?

Current Behavior

External trigger running off of nightly branch. To disable this trigger, set a Github secret named PAUSE_EXTERNAL_TRIGGER_JELLYFIN_NIGHTLY
External version: 20230720.4-unstable
Last pushed version: 20230703.12-unstable
New version 20230720.4-unstable found; but the last build was less than 6 hours ago; skipping trigger

Expected Behavior

Nightly builds should continue

Steps To Reproduce

Not applicable

Environment

Not applicable

CPU architecture

x86-64

Docker creation

Not applicable

Container logs

Not applicable
aptalca commented 11 months ago

https://ci.linuxserver.io/blue/organizations/jenkins/Docker-Pipeline-Builders%2Fdocker-jellyfin/activity

thespad commented 11 months ago

They merged a PR upstream that has completely broken their networking config and nobody seems to have noticed/cared, but it's causing our CI tests to fail.

jarylc commented 11 months ago

Ah, I see. I didn't check the Jenkins logs.

Seems more of an upstream issue in that case, shall I leave this issue open to track this?

LinuxServer-CI commented 10 months ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

thespad commented 10 months ago

Upstream issue https://github.com/jellyfin/jellyfin/issues/10070

LinuxServer-CI commented 9 months ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

drizuid commented 9 months ago

closing as we do not offer support for our nightly tags and this is an upstream issue but was also resolved by upstream 14 hours ago.

github-actions[bot] commented 8 months ago

This issue is locked due to inactivity