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
Describe how to handle dependencies between repositories.
Currently Eiffel Intelligence Frontend is dependent on Eiffel Intelligence . If the front-end requires a feature in the back-end there is no point in releasing or building Docker container for the front-end until the back-end has the functionality merged.
In ETOS on the other hand there is a wish to build the containers on every merge.
Motivation
Need a unified way of handling dependencies between repositories.
Exemplification
See description
Benefits
Avoiding unusable releases and docker containers
Possible Drawbacks
N/A
The text was updated successfully, but these errors were encountered:
Description
Describe how to handle dependencies between repositories.
Currently Eiffel Intelligence Frontend is dependent on Eiffel Intelligence . If the front-end requires a feature in the back-end there is no point in releasing or building Docker container for the front-end until the back-end has the functionality merged.
In ETOS on the other hand there is a wish to build the containers on every merge.
Motivation
Need a unified way of handling dependencies between repositories.
Exemplification
See description
Benefits
Avoiding unusable releases and docker containers
Possible Drawbacks
N/A
The text was updated successfully, but these errors were encountered: