EssentialsX

EssentialsX

Bukkit Plugins
2M Downloads

In-game updater offers update to nonexistent build when a build fail occurs (dev branch)

Giantvince1 opened this issue ยท 1 comments

commented

Type of bug

Error in console, Other unexpected behaviour

/ess dump all output

Error 504 when running command; no link available

Error log (if applicable)

No response

Bug description

The update mechanism of the plugin tries to say I'm out of date when I'm on 2.21.0-dev+151-f2af952.

Current screenshot from the website as of 7:30 PM CST just before the new year:
{973EFB93-0B71-43B5-B8C9-E20F1A0DF20B}

Current output of /ess version:

[19:29:24 INFO]: [Essentials] CONSOLE issued server command: /ess version
[19:29:24 INFO]: Server version: 1.21.3-R0.1-SNAPSHOT 1.21.3-82-5a60ffb (MC: 1.21.3)
[19:29:24 INFO]: Brand version: Paper
[19:29:24 INFO]: EssentialsX version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: LuckPerms version: 5.4.151
[19:29:24 INFO]: Vault version: 1.7.3-b131
[19:29:24 INFO]: PlaceholderAPI version: 2.11.6
[19:29:24 INFO]: EssentialsXChat version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: EssentialsXDiscord version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: EssentialsXDiscordLink version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: EssentialsXProtect version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: EssentialsXAntiBuild version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: EssentialsXGeoIP version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: EssentialsXSpawn version: 2.21.0-dev+151-f2af952
[19:29:24 INFO]: Economy Layer: None
[19:29:24 INFO]: You are running an unsupported server version!
[19:29:24 INFO]: Fetching version information...
[19:29:24 INFO]: You're 1 EssentialsX dev build(s) out of date!
[19:29:24 INFO]: Download it here: https://essentialsx.net/downloads.html

Steps to reproduce

Start a Minecraft server that works with this plugin and have the core plugin installed.
Run /ess version and see the update notification.
Check website: still dev+151.

Expected behaviour

I would expect Essentials to be able to ignore completely failing builds from GitHub and/or Jenkins instead of falsely reporting there's a new update.

Actual behaviour

Essentials is seeing the failed build from GitHub and/or Jenkins but not acknowledging that the build actually failed and hence is not a valid update.

Additional Information

No response

commented

fixed