Skip to content

Latest commit

 

History

History
33 lines (19 loc) · 2.68 KB

CONTRIBUTING.md

File metadata and controls

33 lines (19 loc) · 2.68 KB

Acceptance Testing Your Pull Request

Initial Run

  1. Go to the Jenkins Pipeline for this module.
  2. Wait about two minutes (the repo poll interval should be 2 minutes or less) for Jenkins to check for new PR's and branches, or check for change to existing pipelines. Any new PR's will be added to the Pull Requests View or a new branch with a Jenkinsfile in it will be added to the default 'Branches' view.
  3. New PR's or branches will start to build immediately, and any changes to existed branches or PR's will be built when the repository is polled.

Viewing Run Output

A build history will be on the lower left of the page with a progress indicator on the current build number. Click into the build number and then click on 'Console Output'.

Kicking Off Another Run

When you push new commits to a branch or PR, you can wait for the polling interval to detect the changes, or you can go directly to your pipeline and click Build Now.

If the only thing you want to do is make a slight change to the Jenkinsfile itself to see if something will work, or to add some echo debugging, you can click on Reply instead of Rebuild and a dialog will load allowing you to rebuild the same commit, but edit the Jenkinsfile manually prior to building. Your edits will affect only the current run you are about to kick off.

Viewing Results

When a build of a PR or a branch is complete you can click on the build number and a 'Test Result' link will be available for you to browse through the test case hierarchy and view failed test details. You can also view the raw console output of any given build to look for more details of failed tests that way.

Testing Community Pull Requests

This pipeline will not discover Pull Requests that come from community members that are not authorized collaberators on this repository. In order to test their PR's you have a couple options.

  1. You can add their PR commits to a branch on your own fork, and put up a PR from your own fork.
  2. You can add a branch to the upstream copy of this repository that has the community members' commits on it. The new branch will build as a branch pipeline instead of a PR pipeline.

Either way please make sure to thoroughly review the commits you are adding to ensure that only authorized code can run. These pipelines are still running on internal infrastructure and we are entrusted with ensuring that no malicious code is being run.