Re-updating CICD labs .

labs/shipped-cicd/1.md

@@ -11,11 +11,10 @@ Continuous Deployment (CD) is a practice that closely related to CI. CD deploys
 
 1. Log in to <a href="https://ciscoshipped.io">Shipped UI</a>.    
 
-2.  Select a project from **Your Projects** drop-down list, or create a new one.
+2. Select a project from **Your Projects** drop-down list, or create a new one.
 
     ![](posts/files/shipped-cicd/assets/project-select.png)
 
-
 3. Add a new service (Golang for example).
 
     ![](posts/files/shipped-cicd/assets/2.PNG)
@@ -40,7 +39,7 @@ Continuous Deployment (CD) is a practice that closely related to CI. CD deploys
 
 8.  Enter a name for the environment, click **Save**. 
 
-8.  Click **Deploy Build**.
+9.  Click **Deploy Build**.
 
     ![](posts/files/shipped-cicd/assets/12.PNG)    
 

labs/shipped-cicd/2.md

@@ -6,20 +6,21 @@
     ![](posts/files/shipped-cicd/assets/6.PNG)
 
 
-1. Make some changes in your git project to verify that Shipped triggers a new build.
+2. Make some changes in your git project to verify that Shipped triggers a new build.
 
     ![](posts/files/shipped-cicd/assets/7.PNG)
 
-1. Commit changes.  
+3. Commit changes.  
     When you commit changes, an associated webhook tells Shipped to trigger a build. Each commit triggers a seperate build.
 
      ![](posts/files/shipped-cicd/assets/8.PNG)
 
-1. Verify the build progress for the latest commit.
+4. Verify the build progress for the latest commit.
 
     ![](posts/files/shipped-cicd/assets/9.PNG)
 
-1. Deploy latest build.
+5. Deploy latest build.
 
     ![](posts/files/shipped-cicd/assets/10.PNG)
 
+    ![](posts/files/shipped-cicd/assets/16.PNG)

labs/shipped-cicd/3.md

@@ -1,48 +1,23 @@
 
-## Configure Environment Settings
+## Environment Configurations
 
 1. Click the **Deploy** tab.  
 
-    ![](posts/files/shipped-cicd/assets/Environment-settings.png)
+    ![](posts/files/shipped-cicd/assets/13.PNG)
 
-4.  Select your environment, then click **Settings**.
+2. Change containers value to 3 and click on save button.
+
+    ![](posts/files/shipped-cicd/assets/14.PNG)
 
-1. Click **Environment Settings** to display the settings. 
+Note : Once done with Enviroment specific setting, We need to redeploy build.
 
-    ![](posts/files/shipped-cicd/assets/Environment-settings-CI.png)
+3. Redeploying the latest build. Deploying a build to an environment means that your project will be deployed to the environment you select. It replaces any previous deployment of the build to that environment.
 
-## Enable Auto Deploy
+    ![](posts/files/shipped-cicd/assets/17.PNG)
+
+4. When project deployment finish We can see progress bar disapper and small green button appers like "Mesos". That was the host link.
 
-1. Click the **Auto Deploy**, then click **Back to Environments**. 
-
-1. Click **Deploy Build**. 
-
-
-## Add a New Deploy Target
-
-
-1. Click **Settings** on the environment page. 
-
-    ![](posts/files/shipped-cicd/assets/Environment-target.png)
-
-1. Click **+ New Target**, then click **+ Add New Target**. 
-
-    ![](posts/files/shipped-cicd/assets/Environment-target-marathon.png)
-
-1. Click **Add Deploy Target**, and select **Marathon**. 
-
-    ![](posts/files/shipped-cicd/assets/Deployed-target.png)
-
-1. Enter information in the following fields:
- - **Name** - The name of your target. 
- - **URL** - The URL of your target and must be in this format, for example, https://mycorp-control-01.mycorp.shipped.cisco.com:8080
- - **URL Template** - The template must be in this format, for example,    
-    http://%smycorp.shipped.cisco.com
-
-        ![](posts/files/shipped-cicd/assets/Environment-add-deploy-target.png)
-
-1. Optionally, click the check box next to **Enable HTTP Authentication**, then enter the user name and password. 
-
-1. Click **Save**.
+    ![](posts/files/shipped-cicd/assets/16.PNG)
 
+Wow, You have successfully built and deployed your project with custom environment settings.