| | 2 | |
|---|
| | 3 | * Release ?.?.? (?) |
|---|
| | 4 | |
|---|
| | 5 | ** New Features |
|---|
| | 6 | |
|---|
| | 7 | *** Configurable public_html directory (#162) |
|---|
| | 8 | |
|---|
| | 9 | The public_html/ directory, which provides static content for the WebStatus() |
|---|
| | 10 | HTTP server, is now configurable. The default location is still the |
|---|
| | 11 | public_html/ subdirectory of the buildmaster's base directory, but you can |
|---|
| | 12 | change this by passing a suitable argument when creating the WebStatus() |
|---|
| | 13 | instance in your master.cfg file: |
|---|
| | 14 | |
|---|
| | 15 | c['status'].append( WebStatus(8080, public_html="/var/www/buildbot") ) |
|---|
| | 16 | |
|---|
| | 17 | *** Lock access modes |
|---|
| | 18 | |
|---|
| | 19 | ?"exclusive"/"counting" owners of a Lock |
|---|
| | 20 | |
|---|
| | 21 | |
|---|
| | 22 | ** Bugs Fixed |
|---|
| | 23 | |
|---|
| | 24 | *** Buildslave missing_timeout= fired too quickly (#211) |
|---|
| | 25 | |
|---|
| | 26 | By providing a missing_timeout= argument when creating the BuildSlave |
|---|
| | 27 | instance, you can ask the buildmaster to send email if a buildslave is |
|---|
| | 28 | disconnected for too long. A bug in the previous version caused this |
|---|
| | 29 | notification to be sent too soon, rather than waiting until the timeout |
|---|
| | 30 | period expired. This should be fixed now. |
|---|
| | 31 | |
|---|
| | 32 | *** Test command display fixed (#332) |
|---|
| | 33 | |
|---|
| | 34 | In the previous version, a steps.shell.Test step would display the parsed |
|---|
| | 35 | test results (in the step's box on the waterfall display) in lieu of any |
|---|
| | 36 | other descriptive text the step might provide. In this release, these two |
|---|
| | 37 | pieces of information are combined. |
|---|
| | 38 | |
|---|
| | 39 | ** Minor Changes |
|---|
| | 40 | |
|---|
| | 41 | The buildmaster's version is logged to its twistd.log file at startup. The |
|---|
| | 42 | buildslave does the same, to its own logfile. |
|---|
| | 43 | |
|---|
| | 44 | Remote commands now record how long each command took. The "elapsedTime=" |
|---|
| | 45 | message will appear in the step's main logfile. |
|---|
| | 46 | |
|---|
| | 47 | The "buildbot restart" command no longer fails if the buildbot wasn't already |
|---|
| | 48 | running. |
|---|
| | 49 | |
|---|
| | 50 | The FileUpload and FileDownload steps now create their target directories |
|---|
| | 51 | (and any missing intermediate directories) before writing to the destination |
|---|
| | 52 | file. |
|---|
| | 53 | |
|---|
| | 54 | The per-build and per-step web pages now show the start, finish, and elapsed |
|---|
| | 55 | time of their build or step. |
|---|
| | 56 | |
|---|
| | 57 | ??"fix sendchange when HEAD is specified" |
|---|
| | 58 | |
|---|
| | 59 | ** Compability With Other Tools |
|---|
| | 60 | |
|---|
| | 61 | The mercurial commit hook (buildbot.changes.hgbuildbot) in the previous |
|---|
| | 62 | version doesn't work with hg-1.0 or later (it uses an API function that was |
|---|
| | 63 | present in the hg-0.9.5 release, but was removed from hg-1.0). This |
|---|
| | 64 | incompability has been fixed: the new version of buildbot should be |
|---|
| | 65 | compatible with hg-1.0 and newer (and it probably retains compability with |
|---|
| | 66 | hg-0.9.5 and earlier too). (#328) |
|---|
| | 67 | |
|---|
| | 68 | The Git tool has traditionally provided two ways to run each command, either |
|---|
| | 69 | as subcommands of /usr/bin/git (like "git checkout"), or as individual tools |
|---|
| | 70 | (like /usr/bin/git-checkout). The latter form is being removed in the |
|---|
| | 71 | upcoming 1.6 Git release. Previous versions of Buildbot have used the |
|---|
| | 72 | git-checkout form, and will break when Git is upgraded to 1.6 or beyond. The |
|---|
| | 73 | new Buildbot release switches to the subcommand form. Note that this is a |
|---|
| | 74 | change on the buildslave side. |
|---|
| | 75 | |
|---|
| | 76 | ?? The Git checkout command will now use the default branch (as set in the |
|---|
| | 77 | steps.source.Git() step definition) if the changes that it is building do not |
|---|
| | 78 | specify one. |
|---|
| | 79 | |
|---|