Github ECA migration feedback
During the week of September 17th, we will be updating the Github app that performs the ECA checks for commits. We invite the community to provide feedback before that time! Should you encounter any issues with the ECA check during the immediate time after the launch of the update functionality, please report those issues to this issue. After that time period, please submit a ticket to the helpdesk.
How this impacts you
In terms of impact to the end user, there is no change to day-to-day operation and work within our projects! The Git ECA service is already in use in our Gitlab and Gerrit platforms and is used to validate commits from Github through the Drupal implementation. Should you have any currently open pull requests that are validated in the old system, submitting new changes will automatically switch the pull requests to the new system. There will be no changes to how ECA checks are performed when we roll out this change.
What is changing in the system
As part of our systems upgrade for our internal sites, our ECA platform for Github, which is currently hosted through Drupal, will be migrated to a separate standalone service. The URL where the commit statuses lead will change to be hosted under api.eclipse.org, along with some minor UI improvements we've made as we have built up this service.
How are we mitigating risk
While some of the migration work has been happening in the background, our next phase of the migration will happen in Github itself at the organizational level. To better support the community and ensure minimal impact on all of our organizations, we will be updating the ECA check app after thorough testing in small-scale deployments and local environments where possible. In the short term, the previous solution will still be available but no longer linked, should there be an issue in the larger deployment and a reversion needed.