Post-receive hook and automated deployment

28 views
Skip to first unread message

Yves Raimond

unread,
Aug 12, 2012, 3:54:16 PM8/12/12
to music-ontology-sp...@googlegroups.com
Hello!

As I was fixing the typo identified by Nick, I took that as an
occasion to make the process of updating the Music Ontology
specification a bit more straight-forward.

I wrote a small post-receive WebHook handler, available there:
https://github.com/motools/musicontology-postreceive, and running on
the server on which the Music Ontology specification is hosted.

At each push to our Github repository
(https://github.com/motools/musicontology), the latest code will be
pulled on the server, the specification will be generated, and the
musicontology.com website will be updated. So anyone who has push
access to our repository will see his changes immediately surfaced on
the musicontology.com website.

The website will therefore track the HEAD of our Git repository (which
seems reasonable as HEAD doesn't move very fast these days). But we
could also make it track a specific branch. What do you think?

Best,
Yves

Bob Ferris

unread,
Aug 13, 2012, 3:16:30 AM8/13/12
to music-ontology-sp...@googlegroups.com
Hi Yves,

this is very very cool. Thanks a lot for setting up this hook. Albeit, I
would vote for a deployment branch to be able to include a kind of
review phase before publishing some changes, or?


Cheers

Yves Raimond

unread,
Aug 15, 2012, 8:54:06 AM8/15/12
to music-ontology-sp...@googlegroups.com
Hello!

I had a bit of a chat with Nick about that yesterday, and we seem to
both be of the opinion that 'master' should be the authority. Reviews
should happen on branches before they're merged. It seems to be the
way we've worked since we moved to Github, so I am guessing it will
work OK?

Cheers,
Yves
> --
> You received this message because you are subscribed to the Google Groups
> "Music Ontology Specification Group" group.
> To post to this group, send email to
> music-ontology-sp...@googlegroups.com.
> To unsubscribe from this group, send email to
> music-ontology-specific...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/music-ontology-specification-group?hl=en.
>

Bob Ferris

unread,
Aug 15, 2012, 8:57:19 AM8/15/12
to music-ontology-sp...@googlegroups.com
Hi Yves,

yes this sounds absolutely reasonable for me. So let's go this way and
push changes that should be reviewed to another branch first.

Cheers
>> http://groups.google.com/group/music-ontology-specification-group?hl=en.-
Reply all
Reply to author
Forward
0 new messages