Skip to main content
System StatusContact Support
VersionOne Community

Role: Developer / Contributor - Visibility

Objective

As a developer or team lead, you want more visibility into where that story is in the software delivery process.

The follow steps simulate the development process and show how the business value flows into the value stream.

Steps

  1. Login to GitLab

    You will use the GitLab web UI to make a commit and initiate the delivery process. GitLab can be accessed at the same address as Continuum, but on port 80. The address should be in the original email that was sent. Use the following credentials to login to GitLab.

    Username: root
    Password: Demo1234

     
  2. Select the stores-ui project, then select files.


  3. Edit a File

    In this simplified workflow, the developer will make a commit on the "master" branch and that will trigger a webhook sent to Continuum.

    Find the README.md file and click on it. Then click on the EDIT button that appears above the file.

  4. Add a line to this file and some text (1, below).

    Scroll down to the bottom of the page and add a commit message: "Made a change to the README file, S-01026" (2).

  5. Click the "COMMIT CHANGES" button below the commit message (3, above). This will trigger the webhook to Continuum.
  6. View the Pipeline in Continuum.

    Return to the Continuum user interface. Navigate to "pipelines" in the top menu, "pipeline instances" (1).  Select the top "Merge Build" pipeline (2).

  7. View the Pipeline steps by expanding the Jenkins Merge Build box (1).  Notice the Jenkins - Build step number 3. This called a Jenkins job and passed in the Git commit and branch name and build the software, producing an Artifact in step 5.

    Click on the line "Jenkins - Build" (2). The Jenkins log will popup. This log and the status information are stored in Continuum and therefore you do not need login credentials to Jenkins to see this information. This works the same way with TeamCity, Bamboo, TFS, etc.


  8. Click on the "Manifest" tab on the left (1, below). You will see the Changes (commits) and Workitems (stories) appear in the middle that are associated with this instance of automation. Click on each of the rows on the right (2) to see the data now associated with the pipeline instance (3).



Results

Commits pushed to the source code repository, in this case GitLab, trigger a webhook that pushes a notification to Continuum. Continuum attempts to match the commits to stories or defects in the ALM planning tool, in this case VersionOne Lifecycle. The commit is then inserted into workflow which starts with the "Merge Build" pipeline. An artifact is created as output of the build process.

This example tied commits to business value to automation and artifacts. As the artifact then flows through the delivery process, business value can be tracked.

  • Was this article helpful?