When submitting a pull-request, Jenkins will attempt to verify the changes to ensure it does not break our builds and/or passes QA tests.

The following commands may be used to interact with that service:

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

If the build fails for other various reasons you can rebuild.

"retest this please" to start a new build
"retest this please CLEAN" to start a new build, non-incremental

If your Pull-Request depends upon another repo / branch to build properly, you can specify that using the following syntax in the Pull-Request description:

DEPENDS: https://github.com/freenas/ports/tree/kris/testbranch

An example would be, sending a pull-request for the freenas/samba repo, but it depends upon port changes in the freenas/ports repo. You would first push your port changes to a branch in freenas/ports (kris/testbranch in this example). Then when creating your pull-request for freenas/samba, you would insert text into the pull-request description field as shown above.

If your Pull-Request needs to build aginst another build profile (I.E. fn_head) add the following to the PR description:

PROFILE: fn_head

(This branch will become the next feature release, I.E. 11.1)

(This branch will become the FreeNAS 12.0 feature release)

(This branch will become the next major OS feature release, I.E. 13.0)

(This branch will become the next minor update release, I.E. 11.0-U4)