Question: Missing Build Parameters for Replay

[almozavr]

Context

• Gitlab plugin version: > 1.2.0
• Jenkins version: X.Y.Z > 2.3
• Job type: Pipeline

Problem description

Due to docs gitlab sets hook data via environment and not through build parameters -> it makes replay meaningless which is very disturbing in terms of debugging. Could you explain why it is not possible to use build parameters? Github plugin still does it and works as intended. Thanks!

[omehegan]

@almozavr can you elaborate on why this makes replay "meaningless?" Are you referring to the replay feature of Pipelines?

The reason this change was made is explained here: https://jenkins.io/blog/2016/05/11/security-update/ I don't know how the GitHub plugin would still be using parameters at this point. It would only work if you overrode the security fix, so I suspect that is not really the case.

[almozavr]

@omehegan by "Replay" I mean job feature (http://take.ms/z4HB8) It's unusable with gitlab plugin because those environment params gitlab passes to concrete job on trigger are not available (and are missing) during replay

[omehegan]

@almozavr OK, I will look into this, it sounds like a bug.

[a-hab]

2 ½ years later this bug still exists. Whats the status on this matter?

[rafabc]

3 year later, any advance?

[Kimamisa]

This MR "might" help : https://github.com/jenkinsci/gitlab-plugin/pull/898/files

[Themesaul]

It keeps happening, do you know if it is going to be fixed? it is a problem because from GitLab you can't force a build without doing an extra commit either.