search

nefarius / Legacinator

The one and only Legacinator
https://discord.nefarius.at
BSD 3-Clause "New" or "Revised" License
180 stars 3 forks source link

no builds inside 1.0.25 folder on buildbot #4

Closed orcutt989 closed 2 years ago

orcutt989 commented 2 years ago

Thanks for updating the latest build link, however it looks like there arent any builds in your folder.

https://buildbot.vigem.org/builds/Legacinator/master/1.0.25/

image

nefarius commented 2 years ago

True, let me check that 🤔

nefarius commented 2 years ago

Ah I see why, because the build for that version already expired, triggering a new one.

nefarius commented 2 years ago

Here we go.

orcutt989 commented 2 years ago

Very cool. Buildabot doesn't have a URL like https://buildbot.../latest that you could link to in the readme?

nefarius commented 2 years ago

Nope, the concept of "latest" doesn't exist on CI. Only build numbers which correspond to the build output version numbers. Why would you need a link like that? It's not recommended to share that anyway, only advanced users should tinker with the build artifacts, everyone else is supposed to use the GitHub releases, which do in fact offer a "latest" URL.

orcutt989 commented 2 years ago

Nope, the concept of "latest" doesn't exist on CI. Only build numbers which correspond to the build output version numbers.

I understand what you are saying but this is not necesarilly true. If you were publishing with GitHub actions and releasing, there are URLs that correspond to different artifact paths. There is a URL that is quite popular that people use to pull the "latest" build, this can be "pre releases" or regular releases. https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases

Why would you need a link like that? It's not recommended to share that anyway, only advanced users should tinker with the build artifacts, everyone else is supposed to use the GitHub releases, which do in fact offer a "latest" URL.

Its not that I personally need it, but your Readme insinuates that you are linking to the latest "beta" or "pre release" "experimental" release. It seems with buildbot you either have to link to the base folder or manually update to the latest artifact path which is not ideal from a functional perspective. Not a big deal, but just trying to provide some helpful feedback from the context of your Readme.

nefarius commented 2 years ago

I removed it as it seems to be only confusing, GitHub releases are the relevant ones anyway 😉

nefarius commented 2 years ago

I understand what you are saying but this is not necesarilly true.

It is on my particular setup 😉