Hi AquilaNiger,

The GoCD Server v19.12.0 sending an empty message in the response seems 
like a bug to me. 

Can you help us with the following information to debug this issue further?
- run the same command with *-i *option? It will provide the response code 
and the headers.
- the contents of the logs/go-server.log during the period when the API 
call is made.

Please make sure you redact sensitive information from the logs before 
sending it.

Thanks,
Ganesh


On Wednesday, February 19, 2020 at 9:53:59 PM UTC+5:30, AquilaNiger wrote:
>
> Hi community, 
>
> we are currently in a transition phase, where we have two GoCD servers:
>
>    - Old server A is a 19.11.0, grown over time and using some "old 
>    school" configuration
>    - New server B is a 19.12.0, fresh installed and using config 
>    repositories for its pipelines
>
> We decided to copy our pipelines step by step from server A to B thereby 
> replacing the manual configuration with the nice config repositories 
> feature, which is working fine.
>
> Polling for materials is disabled, as we are using the SVN post-commit 
> hook to trigger the relevant pipelines (also see ). For the transition 
> phase I wanted to enable the hook for both servers, but unfortunately, the 
> behavior is somehow different. In the post-commit hook I'm using:
> curl https:/server-a:8154/go/api/admin/materials/svn/notify -k -u 
> $username:$password -H 'Accept: application/vnd.go.cd.v2+json' -H 
> 'Content-Type: 
> application/json' -X POST -d '{"uuid": 
> "cda78940-f9d9-4cad-b8c4-c86af5d00173"}'
> curl https:/server-b:8154/go/api/admin/materials/svn/notify -k -u 
> $username:$password -H 'Accept: application/vnd.go.cd.v2+json' -H 
> 'Content-Type: 
> application/json' -X POST -d '{"uuid": 
> "cda78940-f9d9-4cad-b8c4-c86af5d00173"}'
>
> Response of server A is 
> {
>   "message" : "The material is now scheduled for an update. Please check 
> relevant pipeline(s) for status."
> }
> and the pipeline is triggered successfully.
>
> Server B responds to the same request with 
> {
>   "message" : ""
> }
> and does not trigger anything.
>
> Now I'm wondering if 
>
>    - Something has changed in materials notification with 19.12.0
>    - the concept of config repositories somehow conflicts with such 
>    notification hooks
>    - I am doing something wrong that I'm not seeing
>
> Is the API call logged somewhere? As always any help of this great 
> community is appreciated.
>
> Thanks in advance!
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/d07cc28a-8e77-486d-905d-cea0e4e984e5%40googlegroups.com.

Reply via email to