...
Project Jumpstart: Source control, build-and-deploy systems, bug tracking, and other code-management tools are in the works.
- Deployment: This is a manual, web-mastered process right now. We are moving toward an automated process using Bamboo, by Atlassian. This is IPS current deployment policy.
- jira.mit.edu: The teams represented on the MAP Working Group, and any IS&T team, can track development project in jira.
- svn.mit.edu: IPS uses the central subversion repository supported by OIS.
Charter: The privileges and responsibilities of MAP Working Group membership.
Support Notes
- IPS maintains mailing isda-integrators@mit.edu. This is for anyone we know about who is integrating with one of our services. Email isda-ops@mit.edu if you need to be included on this list. We email this list about work on the systems that might result in a loss of service or drop in performance.
- isda-ops@mit.edu is the support email for support of the server-based components of MAP including SOA and continuous-integration systems with IS&T and the MAP Working Group. This is not the support email for developers in the MIT community using the MAP SASH stack, MyEclipse, or other development tools.
- The isda-ops mailing list corresponds to the ISDA::Admin queue in Request Tracker.
- Operational support for the systems is staffed in-house 8am to 6pm Monday through Friday.
- We attempt best-effort 24-7 availability by making all systems as fully redundant as MIT's data center can provide, and monitoring the baseline systems and critical applications on 24-7 pageable contracts with IS&T Server Operations.