Skip to content

Commit 9c03b22

Browse files
authored
ZTS: CI Documentation Updates
Update the CONTRIBUTING.md documentation to refer to the GitHub Actions workflows which have replaced the buildbot infrastructure. Signed-off-by: Brian Behlendorf <[email protected]> Closes #16561
1 parent 56ab541 commit 9c03b22

File tree

1 file changed

+4
-11
lines changed

1 file changed

+4
-11
lines changed

.github/CONTRIBUTING.md

Lines changed: 4 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -145,22 +145,15 @@ Once everything is in good shape and the details have been worked out you can re
145145
Any required reviews can then be finalized and the pull request merged.
146146

147147
#### Tests and Benchmarks
148-
* Every pull request will by tested by the buildbot on multiple platforms by running the [zfs-tests.sh and zloop.sh](
148+
* Every pull request is tested using a GitHub Actions workflow on multiple platforms by running the [zfs-tests.sh and zloop.sh](
149149
https://openzfs.github.io/openzfs-docs/Developer%20Resources/Building%20ZFS.html#running-zloop-sh-and-zfs-tests-sh) test suites.
150150
* To verify your changes conform to the [style guidelines](
151151
https://github.com/openzfs/zfs/blob/master/.github/CONTRIBUTING.md#style-guides
152152
), please run `make checkstyle` and resolve any warnings.
153-
* Static code analysis of each pull request is performed by the buildbot; run `make lint` to check your changes.
154-
* Test cases should be provided when appropriate.
155-
This includes making sure new features have adequate code coverage.
153+
* Code analysis is performed by [CodeQL](https://codeql.github.com/) for each pull request.
154+
* Test cases should be provided when appropriate. This includes making sure new features have adequate code coverage.
156155
* If your pull request improves performance, please include some benchmarks.
157-
* The pull request must pass all required [ZFS
158-
Buildbot](http://build.zfsonlinux.org/) builders before
159-
being accepted. If you are experiencing intermittent TEST
160-
builder failures, you may be experiencing a [test suite
161-
issue](https://github.com/openzfs/zfs/issues?q=is%3Aissue+is%3Aopen+label%3A%22Type%3A+Test+Suite%22).
162-
There are also various [buildbot options](https://openzfs.github.io/openzfs-docs/Developer%20Resources/Buildbot%20Options.html)
163-
to control how changes are tested.
156+
* The pull request must pass all CI checks before being accepted.
164157

165158
### Testing
166159
All help is appreciated! If you're in a position to run the latest code

0 commit comments

Comments
 (0)