Opened 14 years ago
Closed 12 years ago
#27 closed TODO (General task list) (fixed)
Automated testing infrastructure
| Reported by: | David Sommerseth | Owned by: | Samuli Seppänen |
|---|---|---|---|
| Priority: | major | Milestone: | beta 2.3 |
| Component: | Community services | Version: | |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
Setup a testing infrastructure based on Beaker.
Change History (7)
comment:1 Changed 14 years ago by
| Status: | new → accepted |
|---|
comment:2 Changed 13 years ago by
comment:3 Changed 12 years ago by
| Milestone: | → beta 2.3 |
|---|
comment:4 Changed 12 years ago by
| Component: | Generic / unclassified → Community services |
|---|
comment:6 Changed 12 years ago by
When the public test server was taken offline, we obviously lost the t_client.sh integration in our buildslaves. So, before or soon after 2.3 alpha release ensure that
- Upgrade buildbot to latest stable release
- The new public test server is configured
- Add t_client.sh rules to buildmaster's master.cfg
comment:7 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
We now have a working testing infrastructure based on t_client.sh which buildbots makes use of. In addition some of the developers have also this access directly. Closing this one as fixed.
Note: See
TracTickets for help on using
tickets.
Beaker may be an overkill. There is now t_client.sh integration in buildslaves, which is a kind of "mini-Beaker" environment. In practice, buildslave try to connect using 4 different configuration files to a remote servers after each build. This should catch most obvious issues easily.