Thank you Roman and Brahma for starting the discussion. > Can access the releases till 2.6.0[1]. i.e From 2.6.1 it's redirected to > the attic page.
On https://ambari.apache.org/ page, when we click on 2.6.x and/or 2.7.x releases, the reason why only upto 2.6.0 release artifacts are accessible is because: 1. All releases from 2.6.1 onwards have redirect url: http://www.apache.org/dyn/closer.cgi/ambari/ambari-2.x.y 2. All old releases upto 2.6.0 have redirect url: http://archive.apache.org/dist/ambari/ambari-2.x.y For instance, <a href="http://archive.apache.org/dist/ambari/ambari-2.6.0"; class="externalLink" title="2.6.0"><i class="none"></i>2.6.0</a> <a href="http://www.apache.org/dyn/closer.cgi/ambari/ambari-2.6.1"; class="externalLink" title="2.6.1"><i class="none"></i>2.6.1</a> and so on. If we update all urls to point to archive.apache.org, we should be able to retrieve the release artifact. Shall we update the url refs? The latest release artifact: https://archive.apache.org/dist/ambari/ambari-2.7.6/ On Thu, Jun 23, 2022 at 6:18 AM Brahma Reddy Battula <bra...@apache.org> wrote: > Thanks Roman for initiating the discussion. Following are my observations. > > >> 0. Locate prior releases of Ambari and restore them > to dist > Can access the releases till 2.6.0[1]. i.e From 2.6.1 it's redirected to > the attic page. > > >> 3. Get WIKI out of locked mode > Ambari banner was removed from wiki. > > > > Apart from that, I checked the Jenkins also and triggered the pipeline [2] > . It looks like it's working fine. Planning to integrate QA builds with > yetus. > > 1. http://archive.apache.org/dist/ambari/ambari-2.6.0/ > 2. > > https://ci-hadoop.apache.org/job/Ambari/job/Ambari-Nightly/job/branch-2.7/77/console > > > Regards, > Brahma Reddy Battula > > > > On Thu, Jun 23, 2022 at 5:46 PM Roman Shaposhnik <r...@apache.org> wrote: > > > Hi! > > > > I wanted to open this thread to capture all the things > > we need to do to bring the Ambari fully back. I think it > > would be best if we coordinate it here, since that > > way we can avoid confusing INFRA folks. So... without > > further ado -- here's a list I think makes sense. Let me > > know if I missed something OR if something on this > > list may not be needed anymore: > > > > 0. Locate prior releases of Ambari and restore them > > to dist > > > > 1. Get git/github repos out of archival mode > > > > 2. Get JIRA for Ambari out of archival mode > > > > 3. Get WIKI out of locked mode > > > > Thanks, > > Roman. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org > > For additional commands, e-mail: dev-h...@ambari.apache.org > > > > > > -- > > > > --Brahma Reddy Battula >
