Almost every developer has worked with some sort of version control and repository management. GitHub, one of the most famous code developing and collaborating platforms, is the most famous for its use of repository practice. Therefore, it is not a surprise that we implement the same tactics which give developers complete autonomy to develop their code in their own sort of a sandbox.
In this article:
Continuing after the team creation, here is the same view of the team:
Create a Repository
For a clarity, we the Repository/Component terms are used interchangeably here. Every component resides in a particular repository.
Press New repo button to give a name to your new repository.
Please note: As with the naming of the team you can only use letters, digits,
_ to name your repository. No spaces!
Press Create to get a window similar to the picture below:
In this particular example, the name of the repository is salesforce-acme and it belongs to the acme-production team. This screen shows the further instructions and guidelines on how to proceed further. More information is given in the how to deploy a component page.
Here are the necessary steps for the clarity:
Upload SSH key
Please upload your public SSH key here if you haven't uploaded it yet - check Manage your SSH Key for more information
Clone our "Hello World" component
git clone https://github.com/elasticio/hello-world-nodejs.git salesforce-acme cd salesforce-acme
Edit code to make your own component
Please read our documentation to learn how to implement your components.
Push your code
git remote add elasticio firstname.lastname@example.org:salesforce-acme.git git push elasticio master
Manage your Repository
Here is how the main Development page would look like after the deployment of your custom component
To manage your repository click on the name to see the page where the following details can be seen:
This is the URL that you can push the code for deploying the updates.
Please note: the cloning of your repositories is not supported. To update the code push it again to create the next version of it. Please contact our support if you need the copy of your repository.
Environment variables for the repository can be set from here. Consult our documentation on How to define env vars for components.
This feature gives a possibility to set the component as Private or Public. Private means that you and your team only and Public is for the entire community.
Here the deployment history of the repository will be listed containing:
- The date of deployment
- the version of the repository deployment and the commit ID.
- Status of the build - green check mark means success. If the deployment failed it will show red cross.
- State of the build - showing which build is currently in use.
- Log of the deployment - clicking the "View" button will open a pop-out window showing the log of that particular deployment.