Hi, I did the update on Jenkins as well:
https://builds.apache.org/job/jclouds/ I'm moving forward on the other repositories now. Regards JB On 06/01/2019 07:50, Jean-Baptiste Onofré wrote: > Hi, > > All our repositories have been migrated to gitbox. > > I'm now updating pom scm and contribution guide. > > @Ignasi: do you tackle the Jenkins update or may I ? > > Thanks, > Regards > JB > > On 05/01/2019 10:31, Ignasi Barrera wrote: >> When you're done I'll take care of updating the Jenkins builds >> >> On Sat, Jan 5, 2019, 10:31 Ignasi Barrera <[email protected] wrote: >> >>> Go for it! >>> >>> Mind updating the committers guide when you're done? >>> https://cwiki.apache.org/confluence/display/JCLOUDS/Committers+Guide >>> >>> >>> On Thu, Jan 3, 2019, 14:28 Jean-Baptiste Onofré <[email protected] wrote: >>> >>>> I'm volunteer to deal with the move to gitbox. If there's no opposition, >>>> I will start the process over the weekend. >>>> >>>> Thoughts ? >>>> >>>> Regards >>>> JB >>>> >>>> Le 3 janv. 2019 à 14:18, à 14:18, Apache Infrastructure Team < >>>> [email protected]> a écrit: >>>>> Hello, jclouds folks. >>>>> As stated earlier in 2018, all git repositories must be migrated from >>>>> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service >>>>> is being decommissioned. Your project is receiving this email because >>>>> you still have repositories on git-wip-us that needs to be migrated. >>>>> >>>>> The following repositories on git-wip-us belong to your project: >>>>> - jclouds-labs-google.git >>>>> - jclouds-labs.git >>>>> - jclouds-chef.git >>>>> - jclouds-labs-aws.git >>>>> - jclouds-labs-openstack.git >>>>> - jclouds.git >>>>> - jclouds-cli.git >>>>> - jclouds-site.git >>>>> - jclouds-karaf.git >>>>> - jclouds-examples.git >>>>> >>>>> >>>>> We are now entering the mandated (coordinated) move stage of the >>>>> roadmap, >>>>> and you are asked to please coordinate migration with the Apache >>>>> Infrastructure Team before February 7th. All repositories not migrated >>>>> on February 7th will be mass migrated without warning, and we'd >>>>> appreciate >>>>> it if we could work together to avoid a big mess that day :-). >>>>> >>>>> Moving to gitbox means you will get full write access on GitHub as >>>>> well, >>>>> and be able to close/merge pull requests and much more. >>>>> >>>>> To have your repositories moved, please follow these steps: >>>>> >>>>> - Ensure consensus on the move (a link to a lists.apache.org thread >>>>> will >>>>> suffice for us as evidence). >>>>> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA >>>>> >>>>> Your migration should only take a few minutes. If you wish to migrate >>>>> at a specific time of day or date, please do let us know in the ticket. >>>>> >>>>> As always, we appreciate your understanding and patience as we move >>>>> things around and work to provide better services and features for >>>>> the Apache Family. >>>>> >>>>> Should you wish to contact us with feedback or questions, please do so >>>>> at: [email protected]. >>>>> >>>>> >>>>> With regards, >>>>> Apache Infrastructure >>>> >>> >> > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
