Currently, Beaker's default test harness is Beah [1]. This post will attempt to
summarize how Beah is currently developed, released and upgraded with the
rationale explained at the end. To learn briefly about Beah in the context of
Beaker, please refer to the architecture guide [2].
*Current development process*
Bugs against Beah are currently filed using the "test harness"
component under Beaker's bugzilla. All development happens on the
"master" branch.
Here is a brief overview of what is the current approach of contributing a feature,
a bug fix or another change to Beah:
- Clone beah: git clone
git://git.beaker-project.org/beah
- Create a new branch for the changes, say mybranch
- Once you are happy with the changes, push your branch to gerrit:
git push git+ssh://gerrit.beaker-project.org:29418/beah mybranch:refs/for/master
- Once the change has been approved, the patch is merged to master
*Release and upgrade process*
Currently, the release process involves tagging a new release using
tito and pushing the tag to remote beah repository. Beah releases
happen at the same time as new Beaker releases. Beah packages are served from
a yum repository at [3]. If there is a new Beah release, the harness packages have
to be updated on the Beaker server using the beaker-repo-update utility.
*Existing Beah documentation*
These are the current "mentions" of Beah in the Beaker documentation.
-
http://beaker-project.org/docs/architecture-guide/capabilities.html#test-...
-
http://beaker-project.org/docs/admin-guide/upgrading.html#new-harness-pac...
-
http://beaker-project.org/docs/user-guide/task-metadata.html
*Future plan*
As is fairly apparent from the above summary, the release cycle and documentation of
Beah is tightly coupled with Beaker's. In fact, currently there is no independent
documentation about what Beah is, where to file a bug against it or how code changes
can be contributed.
The rationale behind this post is to consolidate the current state
and use it as a base for decoupling Beah's documentation from Beaker's and
gradually
adopt a separate release cycle for Beah. Once we have done that for Beah, we
hope to do the same for some of the other projects listed at
http://git.beaker-project.org/cgit/.
Thoughts, suggestions and comments welcome.
[1]
http://git.beaker-project.org/cgit/beah/
[2]
http://beaker-project.org/docs/architecture-guide/capabilities.html
[3]
http://beaker-project.org/yum/harness/
Best,
Amit.
--
Amit Saha <
http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.