Developer Activity: Work on feature-branch

Login as Developer

  • You will perform this activity as a Developer.

    • Logout from Developer Hub

      Click to see how to logout
      • Navigate to the Settings side-menu of Developer Hub and click on the kebab menu in the Profile card

        Settings of Red Hat Developer Hub
      • Sign out of Red Hat Developer Hub using the Settings screen as shown.

        Signing out of Red Hat Developer Hub
    • Logout from Gitlab

      Click to see how to logout
      • Click on the Profile icon, and Sign out from the dropdown.

        Signing out of Red Hat Developer Hub
  • Login to Red Hat Developer Hub and GitLab as dev1/{common_password}

Create a feature-branch

Onboard the Feature Branch using template

  • In Red Hat Developer Hub, choose the Create side-menu, and you will see the Parasol Store Development template. Click on Choose

    choose parasol store template

  • In Step 1: Provide Information for the sandbox deployment, enter the feature-branch name my-feature-branch or the name you have picked for your branch.

    choose parasol store template step1

  • In Step 2: Provide database information. Keep all the fields as it is - no need to make changes. The parameters are already set based on the OpenShift Service names from the existing deployments of the application

    Click to view screenshot

    choose parasol store template step2

  • Click on Review, and proceed to Create

    Click to view screenshot

    choose parasol store template step3

  • Click on the Open component on catalog link

    Click to view screenshot

    parasol branch component

  • Explore the Component

    parasol branch component laanding

    • Notice that under the CI tab, a pipeline is in progress

      parasol branch first pipeline

      and turns green when it finishes the run successfully

      parasol branch first pipeline success

    • Explore the other tabs to see how Developer Hub allows a single pane of glass for the Developers' isolated/sandboxed environment

  • If you are curious to view the deployment on OpenShift: click here

    Click to view screenshot

    parasol branch deployment1

Enhancing the application

  • Click on the < > View Source button on the Component Overview page to access the source repository

    parasol branch component overview

  • Switch to the my-feature-branch

    parasol switchbranch

  • Open the README.md and then select Edit > Edit single file.

    parasol webide

  • For the sake of the workshop, let us just make some changes to the README file. E.g. add this text to the README file This service store provides the core services of Parasol web-app

  • Add a Commit Message Chore: Improved README file at the bottom of the page; make sure the Target Branch is my-feature-branch; Click Commit changes

  • You can now close the Gitlab browser.

View component on RHDH

  • From Developer Hub, access parasol-store-my-feature-branch component from here

  • Access the CI tab to view the pipeline

    parasol innerloop pipeline1

  • Very shortly, the pipeline will be marked as Succeeded

    parasol innerloop pipeline ok

    The first pipeline was triggered when you registered using the s.w template. and the next is by git commit
  • Once you are happy with the changes, you are now ready to create a merge request to the main branch.

  • This is the end of the inner-loop within the isolated/sandboxed dev environment. In the next section, as a developer you will create a merge request to the main branch, to initiate the outer loop