Welcome to your CloudBees CI Trial!

If you run into any problems, please contact the CloudBees representative that sent you your trial credentials.

If you decide to download and install plugins, CloudBees CI only supports Tier I and Tier II plugins.

After the completion of your 7-day trial, a member of the CloudBees team will get in touch with you to understand your trial experience.

Sign into your GitHub account.

Follow the instructions at https://help.github.com/en/articles/creating-a-new-repository/.

Create two repositories: one called upstream-pipeline, and another called downstream-pipeline.

Once you’re done, return to CloudBees CI.

You’ll see the "Create Pipeline" interface:

Click on Create a new Pipeline, and choose a provider from the list of options. This guide uses GitHub:

The "Create Pipeline" interface indicates that you need a GitHub access key to continue.

Click on the Create an access key here link to go to GitHub and create a key:

You’ll be redirected to GitHub for the next few steps.

In the "New personal access token" interface, provide a name for the new access token:

Scroll to the bottom of the page, and click Generate Token.

After the access token is created, click on the clipboard icon to copy the new access token:

Return to CloudBees CI. Paste the access key into the Access Key field and click Connect:

Move on to choosing repositories and creating Pipelines.

Back in the "Create Pipeline" interface, click on the organization that contains the repositories you want to set up Pipelines for:

Select the upstream-pipeline repository (which you created earlier, in the Creating GitHub repositories section) and click Create Pipeline:

The Pipeline project is created and associated with the upstream-pipeline repository.

After the Pipeline is created, you’ll see the Pipeline detail page: click on Pipelines to return to the Pipelines dashboard.

Click on the name of your newly created Pipeline. The "Create Jenkinsfile" interface is displayed:

Click Create Pipeline to create a Jenkinsfile in your Pipeline and move on to set up Pipeline stages and steps.

The Pipeline Editor is displayed:

The ` icon indicates a point at which a Pipeline stage may be added. To create a new stage, click on the ` icon:

Provide a name for the new stage:

Each stage may contain multiple steps. After naming the stage, click Add step to add a step to the stage:

Select a step type from the list. In this case, the step is going to print a message:

Click Save to save the Pipeline:

Because there’s no Jenkinsfile defined in the upstream-pipeline repository, CloudBees CI will create and commit a Jenkinsfile containing your Pipeline’s code to the root of the upstream-pipeline repository:

Provide a descriptive commit message, choose where you want to commit the Pipeline code, and click Save & run:

The Pipeline is saved and initialized, and you’re returned to the Activity View for upstream-pipeline:

Next, see how you can configure Pipelines to execute when they receive events from another Pipeline.

Click on the 'Go to classic UI' icon in the navigation bar at the top right of the page:

In the classic UI interface, click on Mobile Development Team  Manage Jenkins  Manage Plugins:

On the resulting page, confirm that you have the required plugins both installed and enabled:

After confirming your plugins, click on Manage Jenkins again and select Configure Notification:

Confirm that notifications are enabled and Operations Center Messaging is selected:

After confirming your notification settings, click Save.

Return to the "Pipelines" interface by clicking on Open Blue Ocean:

To set up the new Pipeline, click on New Pipeline:

Create a Pipeline called downstream-pipeline, associating it with the downstream-pipeline repository.

Once the Pipeline is created, on the Dashboard, click on downstream-pipeline:

After CloudBees CI offers to create the Jenkinsfile, create a stage and call it "Received an event":

Add a Shell Script step, with the following as the content of the script:

echo 'I just received a testingCompleted event'
▼

Click Save to save and commit downstream-pipeline.

Click on Pipelines to return to the "Pipelines" interface.

Click on upstream-pipeline. The "Pipeline status" interface for upstream-pipeline is displayed:

Click on Branches to switch to the Branches tab:

In the Branches tab, hover your mouse over the right-hand side of the Pipeline to bring up the Pipeline activity icons:

Click on the Edit Pipeline icon to enter the Pipeline Editor:

In the Pipeline Editor, click on the + icon after the Build stage to add a second stage:

Name this stage "Testing", and add two Shell Script steps, one containing

sleep 5
▼

echo Tests Completed!
▼

In the Pipeline Editor for upstream-pipeline, enter the key combination Control+S (most OSes) or ⌘+S (OSX) to bring up the Pipeline Script Editor:

Add the following stage entry to the Pipeline script (after the Testing stage):

stage('Publish Event') {
  steps {
    script {
      publishEvent simpleEvent('testingCompleted')
    }
  }
}
▼

The final result should look like this:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Build the software'
      }
    }
    stage('Test') {
      steps {
        sh 'sleep 5'
        sh 'echo Tests Completed!'
      }
    }
    stage('Publish Event') {
      steps {
        script {
          publishEvent simpleEvent('testingCompleted')
        }
      }
    }
  }
}
▼

When you are satisfied that the script is correct, click Update to save your changes.

Back in the Pipeline Editor, click Save to commit your changes and run the Pipeline.

Click on Pipelines to return to the "Pipelines" interface.

Click on downstream-pipeline. The "Pipeline status" interface for downstream-pipeline is displayed:

Click on Branches:

In the Branches tab, hover your mouse over the right-hand side of the Pipeline to bring up the Pipeline activity icons:

Click on the Edit Pipeline icon to enter the Pipeline Editor:

In the Pipeline Editor for downstream-pipeline, enter the key combination Control+S (most OSes) or ⌘+S (OSX) to bring up the Pipeline Script Editor:

Add the following trigger entry to the Pipeline script (below the agent any section):

triggers {
  eventTrigger(simpleMatch('testingCompleted'))
}
▼

The final result should look like this:

pipeline {
  agent any
  triggers {
    eventTrigger(simpleMatch('testingCompleted'))
  }
  stages {
    stage('Received an event') {
      steps {
        echo 'I just received a testingCompleted event'
      }
    }
  }
}
▼

When you are satisfied that the script is correct, click Update to save your changes.

Back in the Pipeline Editor, click Save to commit your changes and run the Pipeline.

Return to the Branches view for upstream-pipeline. Click the Run icon:

In the lower right corner, click on the status indicator to go to the Pipeline’s status page:

From the Pipeline’s status page, click on the status indicator, which takes you to the Pipeline’s detailed status page:

In this interface, you can click on any Pipeline stage to see more details of the stage, as well as expand the steps. For instance, this is the expanded view of the "Test" stage for upstream-pipeline:

Expand the Publish Event stage and note that upstream-pipeline reports it published an event:

Click on the "X" in the upper right of the detailed Pipeline status page to return to the Pipelines display:

Finally, go to the downstream-pipeline Pipeline status page. Note that the Pipeline has been triggered by a received event:

Navigate to the detailed Pipeline page and click on the Received an event stage, expanding the steps. The Pipeline was triggered by the testingCompleted event sent by upstream-pipeline:

Activate CloudBees CI’s Role-based matrix authorization strategy feature.

Create a new admin role with appropriate permissions.

Create an 'Administrators' group and apply the admin role and user to this group.

Restrict all other users to the Overall > Read permission.

Sign in to CloudBees CI using your CloudBees CI admin user account.

You may see the CloudBees CI classic UI, the Blue Ocean/Pipelines interface, or the Teams Dashboard.

On the Manage Jenkins page, click the Configure Global Security option:

In the Access Control  Security Realm section, keep the default Jenkins' own user database setting but select its Allow users to sign up check box option.

Click Save at the end of the page.

Log out of CloudBees CI and on the log in page, notice the new Create an account feature.

Click Create an account and on the resulting Sign up page, specify the details for an additional account (e.g. Username alex for the purpose of this trial guide).

Once the details have been added, click Sign up and if you see Success on the resulting page, the user was successfully created.

Log out again and create another user (e.g. Username gurwant for the purpose of this trial guide).

Ensure you are signed in to CloudBees CI using your CloudBees CI admin user account.

If you see the CloudBees CI classic UI, click Teams on the left:

On the Teams Dashboard page, click the "Administer Team" icon to the right of your team controller’s name (which is the team controller you set up ealier) to open the controller’s Team Administration page.

On the Team Administration page, click Members to access the Team Members section and then Add a user or group to add a CloudBees CI user to your team controller.

Enter the name of a new user (gurwant) into the Add a user or group field and select the user’s role on the right (e.g. Team Member).

Enter the name of another new user (alex) into the Add a user or group field and select the user’s role on the right (e.g. Team Guest).

Click Save changes.

Click Logout at the top right.

Log in as gurwant and access Teams. Notice that gurwant only has permission to create and view existing Pipelines (i.e. no access to the Administration area).

Log out again.

Now log in as alex and access Teams. Notice that alex only has permission to view existing Pipelines.