CI Integration with Artifactory/Nexus/etc - Dynamic key-values set for manual pipeline job parameters (i.e. available versions to deploy)
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Given a deployment pipeline that serves as environment re-build/deploy clean version X.Y.Z of application. When I want to run the pipeline to (re-)create the environment with version 1.2.0, I have to provide it in the 'build' parameter (assuming that it is later accessed via variable in the code).
This is error prone. And it also creates complication for such a logical task - provide version to deploy (considering that version should exist in artifact repository). Is there Gitlab way of tackling this, in example having an integration that would allow dynamically loaded pipeline parameters for such scenarios?
Further details
I am seeking for a way to reduce amount of manual and verification steps (like checking available versions, copy paste) via enabling dynamic build of key+values for manual pipelines (i.e. version parameter will be loaded based on releases in Maven repository)
References to related issues
- gitlab-ce#47468 (Pre-populate variable keys + value for manual pipelines)
- gitlab-ce#24935 (Specify variables when running a manual job)