During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

Update@4:30pm: Extending maintenance to 7pm.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

During this time, the Github appliances will receive normal software updates, and you may have difficulties accessing your repositories.

Research Computing staff members will monitor the status of all computing and data resources in an effort to ensure continuous availability.

Research Computing staff members will monitor the ticketing system throughout the holiday period and answer critical user questions. Non-critical user questions will be addressed beginning %enddate%. There will also be no coffee hour consultations during this break.

Scratch file purging (on community clusters with scratch space) will continue as normal during the break, so be sure to archive your files in scratch storage or check for any upcoming purge warning email during the break. This does not apply to Data Depot or home directories -- only scratch storage.

Have a wonderful break, everyone, and we look forward to great things in the new year!

During this time, the instance will have the operating system patched and software upgrades performed on the service components that can not be completed with the server in production.

Operations requiring connection to the central server (e.g. new check-outs or pull requests, etc) may time out during the maintenance period. Operations with your own local repository will not be affected.

During this time, the instance will have the operating system patched and software upgrades performed on the service components that can not be completed with the server in production.

Operations requiring connection to the central server (e.g. new check-outs or pull requests, etc) may time out during the maintenance period. Operations with your own local repository will not be affected.

Action Required

Unfortunately, this change requires users and groups to move all their repositories on the current host (github.rcac.purdue.edu) to the new host (github.itap.purdue.edu) by January 2021. You can find instructions for migrating your repositories here: https://www.rcac.purdue.edu/knowledge/services/github/movingrepositories.

During this time, the server will undergo maintenance tasks that can not be completed with the server in production.

Operations requiring connection to the central server (e.g. new check-outs or pull requests, etc) may time out during the maintenance period. Operations with your own local repository will not be affected.

Thank you for your understanding. Please let us know if you have any questions or concerns.

During this time, Workbench instance will have the operating system patched and software upgrades performed on the service components.

Operations requiring connection to the central server (e.g. new check-outs or pull requests, etc) may time out during the maintenance period. Operations with your own local repository will not be affected.

We will provide an update by 12:00pm.

During this time, the server will undergo maintenance tasks that can not be completed with the server in production.

Operations requiring connection to the central server (e.g. new check-outs or pull requests, etc) may time out during the maintenance period. Operations with your own local repository will not be affected.

Thank you for your understanding. Please let us know if you have any questions or concerns.

During this time, the server will undergo maintenance tasks that can not be completed with the server in production.

Operations requiring connection to the central server (e.g. new check-outs or pull requests, etc) may time out during the maintenance period. Operations with your own local repository will not be affected.

Thank you for your understanding. Please let us know if you have any questions or concerns.