Hi Kalyan, For the Jenkins job, it's just a matter of changing the git repo location once it has switched. Everyone else just needs to clone the new repo location once it has switched.
Note that if you follow the Apache guidelines ( https://gitbox.apache.org/setup/), you can actually clone the github URL instead of gitbox - that's normally what I do for Apache projects that have already switched over. The advantage of this is that you can merge PRs directly from github to the project. Colm. On Thu, Jan 17, 2019 at 9:36 PM Kalyan Kumar Kalvagadda <kkal...@cloudera.com.invalid> wrote: > Colm, Thanks for volunteering. It would be helpful if you could share the > process for the same. > > From what I hear from INFRASTRUCTURE team, all the pull requests on > *git-wip-us.apache.org > <http://git-wip-us.apache.org/>* would be redirected to *gitbox.apache.org > <http://gitbox.apache.org/>* automatically so we should be good in the > short term. > I will request the INFRA team to perform the migration in next 24 hours. > Once they start it, it should be a couple of minutes process. > > > > *Thanks,Kalyan Kumar Kalvagadda* | Software Engineer > t. (469) 279- <0000000000>5732 > cloudera.com <https://www.cloudera.com> > > [image: Cloudera] <https://www.cloudera.com/> > > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image: > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera > on LinkedIn] <https://www.linkedin.com/company/cloudera> > ------------------------------ > > > On Mon, Jan 14, 2019 at 5:07 AM Colm O hEigeartaigh <cohei...@apache.org> > wrote: > > > Hi Kalyan, > > > > I can update the Jenkins job - just let me know when the gitbox repo is > > live and I will update the job. > > > > Colm. > > > > On Fri, Jan 11, 2019 at 5:19 PM Kalyan Kumar Kalvagadda > > <kkal...@cloudera.com.invalid> wrote: > > > > > Hello all, > > > > > > I'm working with INFRA team to relocate sentry from * > > git-wip-us.apache.org > > > <http://git-wip-us.apache.org>* to *gitbox.apache.org > > > <http://gitbox.apache.org>.* > > > I will be sending across the steps to follow to start using the new > > > repository once the relocation is done. > > > > > > Meanwhile, there are a couple of other things to do before performing > the > > > relocation. > > > 1. Identify any code level changes needed. (test-patch.py) > > > 2. Changes to Jenkins Job which still uses the old repository. > > > > > > Without having these changes we can not perform relocation as the > > upstream > > > jobs would fail and new patches cannot be submitted. > > > If you force any other issues please respond back. > > > > > > Also, I would need some help in updating the Jenkins job( > > > https://builds.apache.org/job/PreCommit-SENTRY-Build). I'm still > trying > > to > > > figure out a way to change the job to start using the new repository. > > > If anyone could help me out in this regard, it would be much > appreciated. > > > > > > > > > -- > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
