Entries tagged [gitbox]

Monday April 04, 2022

New and enhanced GitBox platform sees the light of day

As we head into April and the middle of the spring of 2022, we are pleased to announce that we have migrated our writable git repository service, gitbox.apache.org, to a new location, a new cluster of hardware bits, and a new platform. The migration took around 35 minutes to complete, and while completely seamless and hidden to most users, it does add some new features that we have not had before, as well as redesigning some existing ones.

New, faster hardware behind the scenes

The first big change is the change in the hardware powering our services. We have more than tripled our computing performance, increased our disk read/write throughput by more than 17x, and increased our network throughput ten-fold. In basic terms, this means we can process pushes of new commit much faster, whether they originate from GitHub or are pushed directly to gitbox by a committer, both in terms of storing them, but also in terms of communicating the changes to our end-users, the developers. It also makes our service much more resilient towards high demands at peak office hours.

New, modern, and modular micro-services

While this sounds like a game of "buzzword bingo", it really represents many months of careful planning and upgrading of the complex designs behind GitBox, pushing them into the very forefront of back-end synchronization setups. All of our main components (code synchronization, event notification, provenance and quality assurance communications, as well as repository and account management) have been split into distinct "pipservices", which is a term we use internally at the Apache Infrastructure Team for denoting single packages of services, or "apps", that are installed and run independently of each other. These all tie into our configuration management system, and can be enabled, tweaked/upgraded or disabled quickly and as demand dictates. This change simplifies our day-to-day workflows and allows to much easier assessment of resource consumption and aids debugging by separating both processes and security environments.

New unified portal for all repository and account management needs

With GitBox version 2 we have also launched a new portal for managing repositories and accounts, called Boxer. With Boxer, our developers can link their GitHub accounts with their Apache credentials, providing them with write access to GitHub. We have removed the old, cumbersome process of linking, and replaced with a flow-based approach that instantly allows a new developer to join a team. Where the old process typically required hours of waiting for our central team management system to catch up, linking and getting slotted into the right teams can now be done in a matter of minutes, if not seconds, and requires no other action than visiting our Boxer portal on gitbox.

Private git repositories

A final thing we'd like to mention is the new ability for projects to use a private git repository for issues or a more sensitive nature. Each project can now have their own private repository space, available to the entire PMC for whatever need they may find themselves in. At present, this will require asking the infrastructure team, as we'd like to work with projects to ensure the best handling of sensitive information.

We continuously strive to better ourselves and provide state-of-the-art services and thinking, and it is our sincere hope that these upgrades will prove useful for the developers at the foundation.

If there are any questions on these changes, we ask that you reach out to us at users@infra.apache.org with your feedback/questions.

With warm regards and excitement,

Daniel, on behalf of the Infrastructure Team at the Apache Software Foundation.

Friday December 07, 2018

Relocation of Apache git repositories on git-wip-us.apache.org to gitbox.apache.org


Hello Apache projects,

I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org.

Why this move?
The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub.

Timeframe for relocation
Initially, we are asking that projects voluntarily request to move their repositories to gitbox. The voluntary time frame is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over.

To have your project moved in this initial phase, you will need:

  • Consensus in the project (documented via the mailing list)
  • File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories)

To sum up the preliminary timeline;

  • December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation
  • January 9th -> February 6th: Mandated (coordinated) relocation
  • February 7th: All remaining repositories are mass migrated

This timeline may change to accommodate various scenarios.

Using GitHub with ASF repositories
When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner.

All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well.



Hot Blogs (today's hits)

Tag Cloud