[
https://issues.apache.org/jira/browse/HADOOP-16003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721950#comment-16721950
]
Akira Ajisaka commented on HADOOP-16003:
----------------------------------------
According to the infra team,
{quote}
> * Is it an atomic move? Or will both repos live at the same time?
Pretty much atomic. Depending on the size of the repos, it will take up
to a few minutes for the move to happen. You will not be able to push to
git-wip while the move is in progress, so there is no chance of 'split
brain' issues here.
> * Do we need a stop-the-world period and messaging sent out?
> * When do the git-wip repos get deleted and/or stop getting updates?
git-wip repos are put in write-only mode, and removed once the migration
has completed, which usually takes around a minute or two. the git-wip
URL will stop working, so you will have to change remotes to the new
gitbox URL.
{quote}
we need to update the jenkins jobs as soon as the migration is completed.
> Migrate the Hadoop jenkins jobs to use new gitbox urls
> ------------------------------------------------------
>
> Key: HADOOP-16003
> URL: https://issues.apache.org/jira/browse/HADOOP-16003
> Project: Hadoop Common
> Issue Type: Task
> Reporter: Elek, Marton
> Priority: Major
>
> As it's announced the INFRA team all the apache git repositories will be
> migrated to use gitbox. I created this jira to sync on the required steps to
> update the jenkins job, and record the changes.
> By default it could be as simple as changing the git url for all the jenkins
> jobs under the Hadoop view:
> https://builds.apache.org/view/H-L/view/Hadoop/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
