search

cloudfoundry / bosh-io-releases

List of releases tracked by bosh.io
Apache License 2.0
3 stars 55 forks source link

move-prometheus-boshreleas-to-cloudfoundry #116

Closed saadia-kadiri closed 2 weeks ago

saadia-kadiri commented 1 month ago

prometheus-boshrelease has moved from bosh-prometheus gh org to cloudfoundry gh org

linux-foundation-easycla[bot] commented 1 month ago

CLA Signed

The committers listed above are authorized under a signed CLA.

jpalermo commented 1 month ago

Before merging @saadia-kadiri, I just want to confirm expected behavior from this change.

The pipelines will be updated such new releases will not be generated and added here

The existing releases will continue to show up here on bosh.io, but you will no longer see bosh-prometheus/prometheus-boshrelease listed on the index page of releases.

All existing releases, and all future releases will be built for cloudfoundry/prometheus-boshrelease and that will show up on the releases index page.

So the main downside would be if somebody is consuming the release from the existing path, they will not see any future releases there and at some point they would hopefully realize this and switch to the new path.

jpalermo commented 1 month ago

@saadia-kadiri , this seems fine as long as you're all fine with the behavior I outlined above?

gmllt commented 4 weeks ago

@jpalermo, So if @saadia-kadiri modifies the PR to only add the new repositories without removing the old ones, someone who wanted to see the old release could still see it.

Is there a way to indicate that the old path is deprecated in favor of the new path?

jpalermo commented 3 weeks ago

Keeping both would allow someone who didn't know about the change to continue to get new updates. Both would show up on the releases page, which might cause some confusion.

There is not currently any way to annotate a release as deprecated.

An ideal solution would be to add sort of aliases key to this repo so any previous release paths could be handled by the new path. You'd need to change the web app to handle that new structure though. I haven't looked at the code closely, but I kinda bet the change would be pretty straight forward.

saadia-kadiri commented 3 weeks ago

@jpalermo, For the moment, we will maintain both paths. We'll consider implementing aliases at a later time.

rkoster commented 2 weeks ago

Thanks! @saadia-kadiri

rkoster commented 2 weeks ago

Pipeline changes have been synced: