In this exercise, you are going to create a Docker Registry in Azure as well as a VSTS build that will build two Docker container images and publish then to the registry. In a later lab you will configure a Release in VSTS to deploy and run the containers.

This exercise assumes you have completed the exercises to create a Team Project and have set up the Docker private VSTS agent. You should also set up Maven package management and have a MyShuttleCalc package in the feed. This exercise uses a team project named jdev-labs, though your team project name may differ.

Create a Docker Container Registry in Azure

1. Open a browser and navigate to the Azure Portal

2. Click the + icon in the upper left of the menu, type azure container registry and press Enter.

   

3. Click on Azure Container Registry and then click the Create button from the Azure Container Registry item blade.

   

4. Enter a name, create or use an existing resource group, and choose a location. Enable the Admin user option, and enable managed registry. This allows you to not have to manage a storage account for the images (similar to managed disks with VMs). Select the Basic pricing tier. Click Create when you are done.

   

5. After a few moments, your registry will be created.

Update the pom.xml File for MyShuttle2

In this task you will update the pom.xml file for the MyShuttle2 application so that it can consume the MyShuttleCalc package from the Maven package feed.

1. In Chrome, navigate to your VSTS account and team project. Click on the Build & Release Hub, click on Packages, and select the Maven feed. Click on Connect to Feed. Click on the copy button in the section labeled Add this feed to your project pom.xml inside the <repositories> tag.

   

2. Open the MyShuttle2 project.

3. Click on the pom.xml file.

4. In the <repositories> element there is a reference to a Maven repo. Replace the existing value with the repository settings you got from the VSTS.

5. Find the <dependency> with <groupId>com.microsoft.exampledep</groupId> and update the version number to match the version number of the MyShuttleCalc package in your package feed. This may look something like:

    ...
    <dependency>
      <groupId>com.microsoft.exampledep</groupId>
      <artifactId>MyShuttleCalc</artifactId>
      <version>1.0.6</version>
    </dependency>
    ...
   

6. Copy the maven settings file from the MyShuttleCalc project (you updated this file in another lab to include the authentication settings for the Maven package feed). Run the following command in a terminal:

    cp ~/MyShuttleCalc/maven/settings.xml ~/MyShuttle2/maven/
   

IntelliJ

1. You may have to reload the Maven project to update the plugins and dependencies. You can do this by clicking View -> Tool Windows -> Maven and then clicking the reload button (the top-left icon in the Maven project view).

   

2. From the top toolbar of IntelliJ, click Build -> Build Project and make sure there are no errors.

3. Click VCS -> Commit. Add a commit message Updating feed settings. Click the drop-down on the Commit button and select Commit and Push. Click Push on the prompt.

   

Eclipse

1. You may have to reload the Maven project to update the plugins and dependencies. You can do this by right-clicking on the myshuttle working set/project, then selecting Maven -> Update Project. Then, keep the checkbox for myshuttle checked and press OK.

   

2. Right-click on the myshuttle working set/project, then select Run As -> Maven build.

   

   In the configuration window, type in compile as the Maven Goal then press the Run button.

   

   Important: Ensure that you have already copied the settings.xml file from MyShuttleCalc to the .m2 folder before you run this. Otherwise, you can specify the settings.xml file in MyShuttle2 by clicking on the File System… button to the right of the User settings field in the configuration window to reference a settings file other than in the default .m2 folder.

3. Commit and push your changes through Team Explorer Everywhere.

Create a VSTS Build to Build Docker Images

In this task you will create a VSTS build definition that will create two containers (a MySql database container as well as a Tomcat container for running the MyShuttle2 site). The build will publish the containers to the Azure Container Registry that you just created.

1. Connect to the virtual machine with the user credentials which you specified when creating the VM in Azure.

2. Open Chrome and browse to http://<youraccount>.visualstudio.com (where youraccount is the account you created in VSTS).

3. Click on the jdev-labs project and navigate to the Build & Release Hub.

4. Click on Builds to go to the Builds view. Click on + New to create a new Build definition.

   

5. Type maven into the search box. Select the Maven template and click Apply.

6. Change the name of the build to MyShuttle2.

7. On the Get Sources step, ensure that the repo is MyShuttle2, and the branch is master. Toggle the Advanced Settings toggle and change Tag Sources to “On Success”.

   

8. Click on the Maven pom.xml step and edit the following values:

   Parameter	Value	Notes
   Options	-DskipITs --settings ./maven/settings.xml	Skips integration tests during the build
   Server URL	http://10.0.0.4:8080	Selects JaCoCo as the coverage tool
   Source Files Directory	src/main	Sets the source files directory for JaCoCo

   

9. Click on the Copy Files task. Set the Contents property to:

    target/myshuttledev*.*
    target/test-jars/*
    *.release.*
   

   

   The Publish Build Artifacts task publishes everything in the artifact staging directory. The Copy Files task copies the following artifacts into this directory so that they are available for Release (which you will create in a later lab):

   • myshuttledev.war - the site war file
   • myshuttledev-tests.jar - integration test jar
   • target/test-jars - dependency jars required to run the test jar
   • Release yml files - for docker operations
   • Release xml files - test configuration files

10. Under the list of tasks, click Add Task. Type docker into the search box and then click the Apply button next to the Docker Compose task.

    

11. If it is not positioned after the Publish Artifact task, then drag the Docker Compose task under it so that it is the last step in the build.

12. Configure the settings of the Docker Compose task as follows:

    Parameter	Value	Notes
    Container Registry Type	Azure Container Registry	This is to connect to the Azure Container Registry you created earlier
    Azure Subscription	Your Azure subscription	The subscription that contains your Azure registry
    Azure Container Registry	Your registry	Select the Azure Container registry you created earlier
    Additional Image Tags	$(Build.BuildNumber)	Sets a unique tag for each instance of the build
    Include Latest Tag	Check (set to true)	Adds the latest tag to the images produced by this build

    

13. Right-click the Docker Compose task and click Clone to create a copy of the task.

14. Position the new task so that it is below the Build Images task.

15. Update the action to Push services.

    

16. Click on the Triggers. Enable the Continuous Integration trigger. Set the branch filter to * to trigger off commits to any branch.

    

17. On the Options page, set the queue to default so that your dockerized agent is the agent to run this build.

18. Click Save and Queue to save and queue this build. Click the Queue button in the dialog and then click the link in the green bar that appears at the top to view the live logs for the build run.

19. You should see a successful build in a short while. Click on the build number to navigate to the Summary page.

    

20. Click on the Artifacts link just below the build histogram to open the artifacts. Click Explore next to the drop artifact. Your drop should look like this:

    

21. Navigate back to the Azure Portal and find your Azure Container Registry. Click on Repositories. You should see a db and a web repository. If you click on one of the repos, you will see a latest tag as well as tags for each build number.