Page History

...

The builds and tests will be automatically run when a contributor pushes a commit to their personal fork. Contributors can also manually re-run the actions for a certain commit, see the GitHub documentation for details.

Disabling testing

Contributors who wishes to push commits to their personal fork without triggering automatic builds an tests being run can do so by opting out from automatic testing. A contributor who wishes to disable automatic builds and tests for all changes can disable GitHub Actions for their personal fork. See the GitHub documentation for how to disable GitHub Actions completely for a repository.

Contributors can choose to run automatic builds and tests for commits pushed to branches with certain names. To enable this the contributors creates a GitHub Secret with the name JDK_TEST_ENABLE. The value of JDK_TEST_ENABLE is a regular expression denoting the branch names for which commits should be tested. For example, setting the secret JDK_TEST_ENABLE to test-.* makes automatic builds and tests being run for commits pushed to branches whose names matches the regular expression test-.* . The default value for JDK_TEST_ENABLE is .*.

Contributors can choose to disable automatic builds and tests for commits pushed to branches with certain names. To enable this the contributors creates a GitHub Secret with the name JDK_TEST_DISABLE. The value of JDK_TEST_DISABLE is a regular expression denoting the branch names for which commits should not be tested. For example, setting the secret JDK_TEST_DISABLE to wip-.* makes automatic builds and tests not being run for commits pushed to branches whose names matches the regular expression wip-.* . The default for JDK_TEST_DISABLE is wip(-|/).*|masterGitHub Actions are enabled by default for repositories on GitHub.