[devel at bb.net] strange behavior when sendchange by buildbot sendchange -p

[Cong Monkey]

Hi Devs,

As the follow special send change behavior maybe by design, it will
confuse the end user.

As send change cmd in
http://docs.buildbot.net/latest/manual/cmdline.html, if I use
sendchange for some custom change trigger which is not base by code
change, the build step will always get the old property.

I try to debug buildbot master to find what happened, as each trigger
may store the information associate with primary key which calculate
by source code attribute in database(I use PostgreSQL). when the
trigger is not done for source code(which no code related info or the
same dummy info), it will always be calculated the same primary key,
which always get the old associate property!  The builder will be run
with the old property!!!

If I pass a dummy version which is different every time, the new
properties will be pass properly.

For my scenes, I do test on a last version product to check weather is
health or not, and that version is always store at some place symbol
link to the latest version by our build process, so I do not need the
version info.

Maybe this behavior can be write down at some place like FAQ?

Tks,
Cong