![]() 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. New unified portal for all repository and account management needs 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |