no builds inside 1.0.25 folder on buildbot
orcutt989 opened this issue · comments
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/
True, let me check that 🤔
Ah I see why, because the build for that version already expired, triggering a new one.
Very cool. Buildabot doesn't have a URL like https://buildbot.../latest that you could link to in the readme?
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.
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.
I removed it as it seems to be only confusing, GitHub releases are the relevant ones anyway 😉
I understand what you are saying but this is not necesarilly true.
It is on my particular setup 😉