...

1. Fork apache/ozone github repository (first time)
2. Create a new Jira in HDDS project (eg. HDDS-1234)
3. Create a local branch for your contribution (eg. git checkout \-b HDDS-1234)
4. Create your commits and push your branches to your personal fork.
5. Create a pull request on github UI (please include the Jira ID in the summary)
6. Set the Jira to "Patch Available" state

Using github

Pull requests are checked by Yetus and external script with executing the different checks.

Issues with ozone label will be picked by a test script executor,  the results will be posted as github checks and saved to a dedicated repository.

If you would like to trigger a new test build, you can push a new commit or add a simple comment

/retest

Check your contribution

The easiest way to check your contribution is to use the simplified shell scripts under hadoop-ozone/dev-support/checks. The problems will be printed out the standard output:

...

The same scripts are executed by the github Github PR checker, see details in Ozone CI with Github Actions.

It's always good practice (and fast) to test with the related docker-compose based pseudo clusters:

cd hadoop-ozone/dist/target/ozone-0.5.0*-SNAPSHOT/compose/ozone
./test.sh

(To test S3 use compose/ozones3, to test security use compose/ozonsecure, etc.)

Testing

Ozone has multiple type of tests including unit tests, integration tests and acceptance tests. Please see the following page for more details: (moved) Ozone test tools

...