Expose URL to the CI build

[xoxys]

Component

server

Describe the bug

Woodpecker copies CI_PIPELINE_URL to DRONE_BUILD_LINK https://github.com/woodpecker-ci/woodpecker/blob/main/pipeline/frontend/metadata/drone_compatibility.go#L31. This is IMO wrong as the drone build link contains a link to the drone job e.g. https://drone.example.com/octocat/hello-world/42 while the CI pipeline URL contains a link to the forge event (e.g. commit) octocat/Hello-World@8019104

While looking into it, it looks like there is no DRONE_BUILD_LINK equivalent available in Woodpecker yet? Exposing a proper URL to the Woodpecker pipeline would be helpful for notification plugins where I would like to get redirected to the Pipeline logs instead of the forge.

System Info

{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-4d83ea0d"}

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
• Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

[xoxys]

Especially as there is CI_COMMIT_URL already, I'm wondering why CI_PIPELINE_URL also contains a link to the forge.

[anbraten]

I somehow remember this bug being mentioned somewhere before. I agree that CI_COMMIT_URL should be pointing to the forge and CI_PIPELINE_URL to the WP-UI

[xoxys]

Can you give me a pointer where .Link for the pipeline is set?

[anbraten]

In pipeline/stepBuilder.go we set CI_PIPELINE_URL to m.Curr.Link which should be the link to the forge.

[xoxys]

But where is m.Curr.Link coming from?

[anbraten]

pipeline/frontend/metadata.go