Open albfan opened 7 years ago
docker container for bugzilla
$ docker run -p 8080:80 -p 2222:22 dklawren/docker-bugzilla
I cloned repo for patches we need to add:
Walter, I suppose you know it but that docker has sshd broken so you can enter on it with:
$ docker exec -it <container-id> /bin/bash
$ cd $BUGZILLA_ROOT
I'm adding a extension for this there with the hook bug_end_of_update
. Maybe bug_end_of_create
needs to be hook too.
This shows how to get params from hook
https://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/Extension.html#Hooks
from that we need to send something to jenkins
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API
I suppose we need to create a job parametrized with a param that gets the id of bugzilla updated
Forget the complex part of how many attachments the bug have and how many of them was already processed (we can tweak that latter) now the only important thing is to retrieve a patch from an issue and create a build from master patched with that attachment.
CI means to automatically parse new changes to report if it's sane to merge them.
So we need that bugzilla inform us when someone adds a new patch.
https://bugzilla.gnome.org/show_bug.cgi?id=781696