Opened 10 years ago

Last modified 4 years ago

#212 new enhancement

buildbot doesn't respond to darcs tags

Reported by: zooko Owned by:
Priority: patches-accepted Milestone: 0.9.+
Version: 0.7.6 Keywords: darcs
Cc:

Description

Darcs tags are patches -- buildbot should respond to the event of a darcs tag arriving, but apparently it ignores them, possibly because they don't touch any files.

Change History (8)

comment:1 Changed 10 years ago by zooko

  • Keywords darcs added

comment:2 Changed 9 years ago by zooko

So now I care about this issue even more, because I want to problem my buildbots to do certain things *only* in the case of a darcs tag. Namely, build binaries of the software and upload the binaries to http://pypi.python.org/pypi/zfec and http://pypi.python.org/pypi/pycryptopp , respectively.

comment:3 Changed 9 years ago by dustin

  • Milestone changed from undecided to 0.7.+

I think the typical solution to this is to create a "fake" change with a fake file in it. Want to hack something up?

comment:4 Changed 9 years ago by zooko

tahoe #422 (have buildslaves automatically build debian packages of foolscap, zfec, pycryptopp, etc.) would be able to benefit from fixing this ticket.

Dustin: I don't yet understand what you mean about a "fake" change with a fake file. I would have thought that the solution would be to find the part of buildbot code that says "If there are changed in the source tree" and replace it with "If there was a patch".

comment:5 Changed 9 years ago by dustin

I don't recall the details, but there was a case in one of the VCs where a commit could be made that didn't really change anything -- essentially a tag. One way to make buildbot recognize this was to create a Change with files=fake?. Your suggestion might work too.

comment:6 Changed 6 years ago by dustin

  • Type changed from defect to enhancement

comment:7 Changed 5 years ago by dustin

  • Priority changed from major to patches-accepted

comment:8 Changed 4 years ago by dustin

  • Milestone changed from 0.8.+ to 0.9.+

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.