You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Devtron CI allows passing runtime parameters during pipeline execution, but these parameters are not automatically exposed as environment variables within the CI pipeline steps. This limits the usability of dynamic configurations and custom scripting within the build process.
If anyone wants to use the variable value in any scripting then they have use JQ or some other tool to grep the value from CI_CD_EVENTS variable, which obviously is not known by any end user.
🎤 Pitch / Usecases
We have a use case to update the Base Docker image, which we can pass from the build args of the docker build, and we are passing the value of base Image using a runtime Parameter to grep the value I'm passing build args like this
🔖 Feature description
Currently, Devtron CI allows passing runtime parameters during pipeline execution, but these parameters are not automatically exposed as environment variables within the CI pipeline steps. This limits the usability of dynamic configurations and custom scripting within the build process.
If anyone wants to use the variable value in any scripting then they have use JQ or some other tool to grep the value from CI_CD_EVENTS variable, which obviously is not known by any end user.
🎤 Pitch / Usecases
We have a use case to update the Base Docker image, which we can pass from the build args of the docker build, and we are passing the value of base Image using a runtime Parameter to grep the value I'm passing build args like this
By enabling this feature, the user can directly use the Value like
$BASE_IMAGE
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: