The usage of dep. and reverse.dep. parameters

Question

The usage of dep. and reverse.dep. parameters to access and overriding the parameters of dependent configurations topic is complex. Is there an easy explanation on how they can be used with a simplified example?

Answer

Let's say there is a build chain of two builds: BuildA and BuildB. BuildB has a snapshot dependency on BuildA, so when BuildB is triggered, BuildB triggers BuildA, waits for it to finish, and then BuildB starts.

BuildA has a parameter ParameterA. This parameter needs to be defined when BuildB is triggered, i.e., BuildB (which starts after BuildA but is triggered first) should define the parameter used in BuildA.

To implement this, a parameter reverse.dep.<BuildA_ID>.ParameterA must be defined in BuildB with a value to be used when triggering BuildA. BuildA will then use this value in its ParameterA parameter. The documentation contains more details and a more complex example.

And the other way around, if there is a build chain BuildA > BuildB, i.e., BuildB has a dependency on BuildA, and BuildA has a parameter ParameterA that needs to be accessed from BuildB, dep.<BuildA_ID>.ParameterA can be used to access it. The documentation contains more details and a more complex example.