[tahoe-lafs-trac-stream] [tahoe-lafs] #122: does github webhook report tags? do they trigger the buildbot? (was: darcs+buildbot postcommit hook doesn't report tags)

[tahoe-lafs]

#122: does github webhook report tags? do they trigger the buildbot?
------------------------------------+------------------------------------
     Reporter:  warner              |      Owner:  warner
         Type:  defect              |     Status:  new
     Priority:  minor               |  Milestone:  eventually
    Component:  dev-infrastructure  |    Version:  0.5.0
   Resolution:                      |   Keywords:  buildbot darcs release
Launchpad Bug:                      |
------------------------------------+------------------------------------

Old description:

> The darcs_buildbot.py post-commit hook doesn't send a Change object to
> the buildmaster when a tag is  pushed into the repository. As a result,
> the buildbot doesn't automatically build .debs of released versions, only
> of intermediate versions. This is a pity, because it would be nice for us
> to have packages of official releases.
>
> I'm not sure what is necessary to fix this: I seem to recall that tags in
> darcs are handled very differently than regular patches, so the 'apply'
> action might not be enough to catch both. On the other hand, it might
> just be that the darcs_buildbot.py script (which is run by the apply
> action) is deficient, perhaps exiting if it sees no files changed when it
> should send a Change anyway.

New description:

 The darcs_buildbot.py post-commit hook doesn't send a Change object to the
 buildmaster when a tag is  pushed into the repository. As a result, the
 buildbot doesn't automatically build .debs of released versions, only of
 intermediate versions. This is a pity, because it would be nice for us to
 have packages of official releases.

 I'm not sure what is necessary to fix this: I seem to recall that tags in
 darcs are handled very differently than regular patches, so the 'apply'
 action might not be enough to catch both. On the other hand, it might just
 be that the darcs_buildbot.py script (which is run by the apply action) is
 deficient, perhaps exiting if it sees no files changed when it should send
 a Change anyway.

--

Comment (by warner):

 Now that we're on git, we should test to see if pushing just a git tag to
 github triggers the same sort of change message (I suspect it will). I
 don't know, however, if the buildbot will react to a tag message by
 triggering a build (I suspect it won't). This would be nice to have, so we
 don't have to push changes and tags at the same time.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/122#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage