How to deploy on the SIP
This section combines different how-to related to deploying an application on the SIP.
Prerequisites
The how-tos in this section assume that:
- Your organization was onboarded on to the SIP by an ISG board member. If your organization is listed here there is a good chance that you are setup to use the SIP.
- You have a GitLab repository configured and linked to teamcity.
- You have installed sipctl on your system. See also VSETH CLIs for installation instructions.
All How-tos
- Change an Application's Branch
- Delete a SIP deployment or application
- Deploy an Application
- How to decommission a deployed SIP application
- List Applications or Deployments
- Move a deployment
- Onboard a new organization on an existing cluster
- Register an application
- Troubleshooting Deployment Issues
I have this code repo. How do I run it on SIP?
To deploy a repository you first have to register an SIP-application. After that you can create a deployment:
Overview
| Question | Answer for Applications | Answer for Deployments |
|---|---|---|
| What is it? | A literal copy of your sip.yml inside the cluster, with some more information. | A literal copy of an application. |
How do I create it? | ||
Where does it reside? What namespaces does it have? | In the application namespace of your organisation, e.g. "amiv-apps". | In one of the "executable" namespaces of your organisation, e.g. "amiv-test", "amiv-staging", "amiv-prod". |
| How do I update it after changes to sip.yml? | Automatically by teamcity during the build (in exceptional cases you can use "sipctl push", be careful what you do) | Automatically if you chose "--auto-update". Otherwise "sipctl update". |
Can I reach my website after creating it? Will my container start running after creation? | Definitely no. | Yes, if you chose "--auto-update". Otherwise, run "sipctl update" on the deployment. Then: Yes |