db: add 1:N parentship between build and buildset

a build can be a parent of another build via trigger,
inherit force scheduler, and rebuild button.

This commit only add the data, and make the UT works again

subsequent commit will implement the logic

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
buildset: add parentship to db and data api

update docs and tests

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Propagate optional arguments for schedulers apis

I'm too scared to fix all the unit tests if I passed those via standard
keyword arguments

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
png status by revision hash
fix pngstatus test
update docs for statuspng
Trigger: refactor step for nine

switch to new style step, simplify it, use the new parent_buildid api

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
upgrade js libs

we fix all the js libs, it has been too problematic with CI.
remove json2 and html5shiv, as nobody is testing IE8 anyway.

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
LoggingBuildStep: dont finish the log

the log is finished by RemoteCommand, so no need to
finish it in gotResults()

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
pep8 fixes

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Merge branch 'jslibs_bump' into trigger_ui
Merge kviktor/buildbot:png-status-by-revision (PR #1083)
db fix
fix trigger when there is no patch in source stampt
fix buildrequest url
autopep8
Merge branch 'nine' of github.com:buildbot/buildbot into nine
fix db

mysql and pg do implicit indexes, that needs to be specified.
another db fix

did forget datetime2epoch, and pg is the only backend to care about it.

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
is this the last db fix?

or should I install pg on my dev environment?

Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>