Is it possible to pass additional non-variables in Gitlab CI for a manual job?

Question

Software Deployment

I have a project that consists of 3 related applications, each of which is developed in its own repository, and versioned separately. Applications run in docker. There is a task to roll out applications to the test server for manual testing.

Now the question is:
There is a version of application1 that needs to be rolled out for testing. From a commit in a branch, I can determine its version. What is the best way for me to specify the versions of companion applications that should be deployed side by side? Given that these are different repositories and completely different versions of applications ...

What are the popular approaches here? Ideally, it would be if the developer in the manual job could specify which versions to deploy, but I did not find how to do this in Gitlab CI.

Answer 1

> Ideally, it would be if the developer in the manual job could specify which versions to deploy, but I did not find how to do this in Gitlab CI.
You can't set ANYTHING in the manual job itself. But there are two options to get out:
1. set variables when instantiating the pipeline

2. make an interface through which it will be possible to trigger the creation of a pipeline / job via API with all the necessary variables - for example, using Rundeck