Hi Michal,

Thanks for the quick reply, much appreciated on a Friday evening :-)

I did the following:

* - E - debian@weblate-host:/srv/weblate$ sudo docker-compose -f 
docker-compose-infrastructure.yml logs -f weblate
* https://lab.enough.community/main/app/settings/integrations and clicked on 
**test**
* saw the following output:

weblate_1       | INFO received GitLab notification on repository 
https://lab.enough.community/main/app, branch master,0 matching components, 0 
to process
weblate_1       | 172.20.0.1 - - [27/Jul/2018:21:22:14 +0000] "POST 
/hooks/gitlab/ HTTP/1.0" 200 67 "-" "-"
weblate_1       | [pid: 124|app: 0|req: 1303/5723] 172.20.0.1 () {42 vars in 
561 bytes} [Fri Jul 27 21:22:14 2018] POST /hooks/gitlab/ => generated 67 bytes 
in 31 msecs (HTTP/1.0 200) 7 headers in 398 bytes (1 switches on core 0)

Which is encouraging: they seem to communicate well. Then I kept the logs -f 
and pushed a change to the https://lab.enough.community/main/app repository and 
saw:

weblate_1       | INFO received GitLab notification on repository 
https://lab.enough.community/main/app, branch master,0 matching components, 0 
to process
weblate_1       | 172.20.0.1 - - [27/Jul/2018:21:26:56 +0000] "POST 
/hooks/gitlab/ HTTP/1.0" 200 67 "-" "-"
weblate_1       | [pid: 124|app: 0|req: 1305/5728] 172.20.0.1 () {42 vars in 
561 bytes} [Fri Jul 27 21:26:56 2018] POST /hooks/gitlab/ => generated 67 bytes 
in 43 msecs (HTTP/1.0 200) 7 headers in 398 bytes (1 switches on core 0)

which tells me the hook is taken into account. However, when I go to 
https://weblate.enough.community/projects/enough/#repository, the latest 
repository change is old. When I click **Rebase** on the **Repository tools** 
panel to the right, it updates with the new value.

I see weblate 3.1.1-1 was published a few hours ago and I'll give it a try 
https://hub.docker.com/r/weblate/weblate/tags/

Thanks for the tip!

On 07/27/2018 07:59 PM, Michal Čihař wrote:
> Hi
> 
> On Fri, 2018-07-27 at 18:52 +0200, Loïc Dachary wrote:
>> In https://weblate.enough.community/ 3.0.1 weblate instance, the http
>> s://weblate.enough.community/projects/enough project is setup with ht
>> tps://lab.enough.community/main/app/ and initialized correctly. The h
>> ttps://weblate.enough.community/hooks/gitlab/ hook was added in
>> GitLab and tested to work at https://lab.enough.community/main/app/se
>> ttings/integrations. However it does not trigger anything and https:/
>> /weblate.enough.community/projects/enough/#repository stays
>> unmodified. If I click pull on this page, the update happens as
>> expected.
>>
>> Obviously I'm missing something, probably trivial, and I would very
>> much appreciate any idea you may have to guide me in the right
>> direction.
> 
> Check the application logs (by default they are sent to syslog), maybe
> repository URL does not match. Anyway Weblate 3.1 contains some
> improvements in this (originally targeted at BitBucket, but might help
> in your case as well).
> 
> 
> 
> _______________________________________________
> Weblate mailing list
> [email protected]
> https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
> 

-- 
Loïc Dachary, Artisan Logiciel Libre

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Weblate mailing list
[email protected]
https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate

Reply via email to