Difference between revisions of "Solum/FeatureBlueprints/GitIntegration"
(→Implementation) |
|||
| Line 11: | Line 11: | ||
=== Implementation === | === Implementation === | ||
| + | |||
| + | We posit that the git integration workflow can be as follows. To setup the git repository within Solum for a user's application, we propose that Solum API provide a 'register' resource. A user would invoke this resource and pass in the application name (app name) as part of the request body. The Solum system will create a git repository for that user and the specified app name. A 'post-receive-hook' will be created in this git repository (contents described below). The git repository URL will be sent back to the user in the response of the 'register' call. Users will have to add this URL as a 'remote' for their local repository. Let's call this as an application's solum remote. Adding a solum remote will be a one time step, which will need to be performed only once per application. Once the solum remote is setup, whenever the user pushes the code to it, the configured post-receive-hook will get triggered and perform actions which will lead to deployment of the application in the Solum system. The URL to access the application will be sent back to the user as part of the response of git push. | ||
| + | |||
| + | Post-receive-hook: | ||
| + | -------------------------- | ||
| + | There are several options for | ||
Revision as of 19:11, 6 October 2013
Git Integration
Functionality
As an application developer, I want to push my code to my git repository, and have the platform automatically detect the code push and generate a running application using the new code.
I would be able to use git push for deploying a new application, or to update an existing application.
I would be able to specify the the meta-data for the application (AppName, app instance size, instance count, auto scale policies, etc) via an application manifest file. The application manifest file will be stored at the root location of my code project's directory, and will be automatically picked up by the platform in response to a git push.
Implementation
We posit that the git integration workflow can be as follows. To setup the git repository within Solum for a user's application, we propose that Solum API provide a 'register' resource. A user would invoke this resource and pass in the application name (app name) as part of the request body. The Solum system will create a git repository for that user and the specified app name. A 'post-receive-hook' will be created in this git repository (contents described below). The git repository URL will be sent back to the user in the response of the 'register' call. Users will have to add this URL as a 'remote' for their local repository. Let's call this as an application's solum remote. Adding a solum remote will be a one time step, which will need to be performed only once per application. Once the solum remote is setup, whenever the user pushes the code to it, the configured post-receive-hook will get triggered and perform actions which will lead to deployment of the application in the Solum system. The URL to access the application will be sent back to the user as part of the response of git push.
Post-receive-hook:
There are several options for
