Needed Templates for output variables
long-term
S
Standard Opossum
Currently Templates has Input variables but there is no Output variables at the template level. So when using a template, one should know the exact step inside the template to read the output variables, which makes the concept of template inefficient. If the template had output variables, then the template can be treated as black box - hiding the inner step details and one only needs to know what input to provide and what output variables to read.
Log In
Rohan Gupta
Merged in a post:
Ability to have output variables for stages
U
Utrecht blue Reindeer
We have created templates for each stage, and have encapsulated all build logic in the build stage. However, when we want to pass out info from the build stage such as the code coverage or scan results, our only option right now is to have them as output variables for the step where we run the test or get the scan results, and then reference this step from the build stage in subsequent stages. Since the step name is critical to all subsequent references, any change to this step within the template can cause subsequent things to break. We would like the stage template to have the ability where we can change anything within it, without breaking the builds referencing them as long as they use the right template inputs and outputs. This way nobody needs to look into the internals of a stage template, and are immune from the changes that might happen to the template as long as the contract (template id, and input and output variables) is intact.
Rohan Gupta
marked this post as
long-term
This is planned for our long term plan, we are looking to provide inputs and outputs for templates, this feature is tied to a broader initiative we are working on and will likely be available in beta at the beginning of next year.