Introduction
This package has been done start during sprint@ploneconf2009. The goal is first to provide nighly load tests to Plone. The other goal is to be able to do the same on any other Plone project fast.
Using buildbot and funkload together, allow you to have feedbacks about performance impact done by your last code modifications every day in mail or ttw.
Credits
How to use it
First the process:
Create a new funkbot project (projectname, vcs type, vcs address of the buildout)
Go inside, init the buildout (buildout init or python bootstrap.py)
launch the buildout will install buildbot and funkload
launch master and slave daemons
Connect your webbrowser to http://localhost:9080
Ask a force rebuild will launch the build of your project.
Now the command line:
paster create -t funkbot plone4
virtualenv plone4
cd plone4
source bin/activate
easy_install zc.buildout
buildout
master start && mycomputer start
firefox http://localhost:9080
Where things are
The main things to understand is that you are creating a buildbot. So the first buildout doesn’t build the project. It build the buildbot that will build the project (sic).
TODO
add static for serving funkload reports ttw (in progress)
send mail at the end of tests with funkload reports inside
Changelog
1.0 - 2009-11-01
Initial release [toutpt]
Paste template to create a buildbot that trigger funkload [toutpt]
Metadata
Release files for collective.funkbot 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.funkbot-1.0.zip | 26.1 kB | Without provenance | Details for collective.funkbot-1.0.zip |
Release files / collective.funkbot-1.0.zip
| Download URL | collective.funkbot-1.0.zip |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84d159e774b661f2f6964ba15c5225580029679a07bd05da4a6196cf50c7a92c
|
|
BLAKE2b-256 checksum How to use checksums |
542e704b7cf8a52c55370435bad010bd579edfdd2206ea71d92b99253a265ce5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.funkbot 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.