Page History

...

GitHub Actions is a way to describe workflows that should be triggered when certain events occur, such as the push of a commit to personal fork. For contributors that have a personal fork of the jdk repository then builds and tests will be executed when a commit is pushed to the contributor's personal fork.

Builds

GNU/Linux

x86-64

• Release
• Debug ("fastdebug")
• Release without precompiled headers

macOS

x86-64

• Release
• Debug ("fastdebug")

Windows

x86-64

• Release
• Debug ("fastdebug")

Tests

tier1

• GNU/Linux x86-64
• macOS x86-64
• Windows x86-64

Triggering builds and tests

Configuring workflows to run

When you create a new personal fork of the jdk repository, GitHub Actions are disabled by default. When you visit the Actions tab for your personal fork, you will see a message similar to this: "Workflows aren't being run on this forked repository". Click on the green button labelled "I understand my workflows, go ahead and enable them" to allow the jdk builds and tests to execute for branches in your personal fork.

Triggering builds and tests

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

...

The definitions for the GitHub Actions for the jdk repository are available in the .github/workflows directory.

Builds

GNU/Linux

x86-64

• Release
• Debug ("fastdebug")
• Release without precompiled headers

macOS

x86-64

• Release
• Debug ("fastdebug")

Windows

x86-64

• Release
• Debug ("fastdebug")

Tests

tier1

• GNU/Linux x86-64
• macOS x86-64
• Windows x86-64