Build links for instanced pipelines don't work

[jamiegosling]

We use Instanced Pipelines, and the build links we get for them in GitHub don't appear to work. Here is an example of a link from cogito:

https://concourse/teams/teamname/pipelines/pipeline_name/jobs/job_name/builds/5?vars=%7B%22DEPLOYMENTID%22%3A%222%22%2C%22DESC%22%3A%22Daily+tests+for+Preprod+2%22%2C%22TITLE%22%3A%22PREPROD+TESTS%22%7D

an example of a working link for the above build

https://concourse/teams/teamname/pipelines/pipeline_name/jobs/job_name/builds/5?vars.DEPLOYMENTID=%222%22&vars.DESC=%22Daily%20tests%20for%20Preprod%202%22&vars.TITLE=%22PREPROD%20TESTS%22

[marco-m-pix4d]

Hello @jamiegosling, thanks for reporting.
Sounds unexpected to me, I remember this was working 🤔
The code in question is

cogito/cogito/putter.go

Lines 336 to 340 in 9328bb4

	// BUILD_PIPELINE_INSTANCE_VARS: {"branch":"stable"}
	// https://ci.example.com/teams/main/pipelines/cogito/jobs/autocat/builds/3?vars=%7B%22branch%22%3A%22stable%22%7D
	if env.BuildPipelineInstanceVars != "" {
	buildURL += fmt.Sprintf("?vars=%s", url.QueryEscape(env.BuildPipelineInstanceVars))
	}

What is the cogito version you are using? You can see it as the first line output of any step:

[INFO]  cogito: This is the Cogito GitHub status resource.
    Tag: 0.12.0, commit: a18efc3, build date: 2023-11-03

[jamiegosling]

Hi @marco-m-pix4d,

Looks like we're on the latest version:

This is the Cogito GitHub status resource. Tag: 0.12.0, commit: a18efc3, build date: 2023-11-03

Looking at it I wonder if it needs a function to convert the JSON instance vars into URL parameters in the format vars.parameter1=value1&parameter2=value2?

[aliculPix4D]

Sounds unexpected to me, I remember this was working

@marco-m-pix4d can it be that it changed depending on the Concourse version? this is still "experimental" feature subject to changes.

Instanced Pipelines/Instance Groups are currently experimental, and are subject to change.

@jamiegosling just curious a bit, which Concourse version you are using?

[marco-m-pix4d]

can it be that it changed depending on the Concourse version?

Possible. In any case, this makes me think that in general from Cogito we could hit a Concourse endpoint that returns its version and log it, this could be helpful for troubleshooting in general...

[aliculPix4D]

Possible. In any case, this makes me think that in general from Cogito we could hit a Concourse endpoint that returns its version and log it, this could be helpful for troubleshooting in general...

Yes, we have it in header of every request.

X-Concourse-Version: 7.X.X

[marco-m-pix4d]

Ah even better! Good catch.

[jamiegosling]

Sounds unexpected to me, I remember this was working

@marco-m-pix4d can it be that it changed depending on the Concourse version? this is still "experimental" feature subject to changes.

Instanced Pipelines/Instance Groups are currently experimental, and are subject to change.

@jamiegosling just curious a bit, which Concourse version you are using?

@aliculPix4D we are using Concourse v7.10.0

[aliculPix4D]

My attempt to fix this: #153