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
Allow a tier to define a configuration but not force the library to be loaded by subsequent project
Feature Request
implement '@transient' annotation in pipeline_config such that during configuration aggregration if the affected item is not redefined, the final configuration annotation does not contain the annotated configuration.
the @transient would have to be redefined on each intermediate tier ... the annotation would not automatically cascade through an intermediate tier(s) to the final projects
cokieffebah
changed the title
implement annotation for allowing higher tier configuration without requiring library loading
implement annotation for allowing higher tier configuration without forcing library loading
Jan 21, 2021
Use Case
Allow a tier to define a configuration but not force the library to be loaded by subsequent project
Feature Request
implement '@transient' annotation in pipeline_config such that during configuration aggregration if the affected item is not redefined, the final configuration annotation does not contain the annotated configuration.
the
@transient
would have to be redefined on each intermediate tier ... the annotation would not automatically cascade through an intermediate tier(s) to the final projectstier 1 pipeline_config.groovy
project1 pipeline_config.groovy
project2 pipeline_config.groovy
then the project1 final configuration will not contain libraries.maven and project 2 will have libraries.maven with the base_command
The text was updated successfully, but these errors were encountered: