![]() ![]() Step 2) Click Launch Instance to create a new server If you are on a windows machine – try using this ![]() Step 1) login to AWS, Navigate to EC2 Dashboard If you are using your own, feel free to skip this milestone. To have a server that runs our CI, you need to either signup for a server or have your own Ubuntu server. It is a bit more tricky to SSH into a AWS server if you are using a PC, but there are good tutorials out there. This is the only milestone that differs with a PC / Mac / Linux. Prerequisites:Ġ) Basic knowledge of git and Salesforce developmentġ) have a Github account with a Salesforce respository.Ģ) have a clean Salesforce developer org.ģ) have an AWS account (Optional – if you run your own Ubuntu server) Milestone 1: Create AWS Server So when I make updates to the repo, it notifies me right away. It is much more helpful to have it notify me as soon as it fails to deploy. If I update a repo and it fails to deploy when I need it, it isn’t very helpful. Why did I set it up? I have some repositories that need to be deployable to a Salesforce. ![]() Why Continuous Integration? There are a lot of great articles on why you should use CI. We will walk through four major points: Creating an AWS Server, Setting it up, Installing and configuring Jenkins So the steps to take had changed and I couldn’t find much of a complete overview, so here is a step by step guide to create an AWS hosted Jenkins continuous integration to validate GitHub repositories against. The last time I setup a Jenkins continuous integration was from a PC and it was a while ago. I am not too much of a linux guy and I haven’t worked on a Mac for long. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |