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
This is an epic related to proper artifact management in genesis.
Details to be provided.
The main idea: genesis is required to have notion of "application manifest" that should be stored with sources of application being deployed via genesis. The manifest should describe how to application should be build and what artifacts should be considered as result of the build (to be processed after deployment)
As a start, I would suggest to support maven. But the system should be designed to scale to support any kind of building configuration: sbt, gradle, etc..
The text was updated successfully, but these errors were encountered:
This is an epic related to proper artifact management in genesis.
Details to be provided.
The main idea: genesis is required to have notion of "application manifest" that should be stored with sources of application being deployed via genesis. The manifest should describe how to application should be build and what artifacts should be considered as result of the build (to be processed after deployment)
Good understanding why is this needed can be obtained from here:
http://about.travis-ci.org/docs/user/build-configuration/
As a start, I would suggest to support maven. But the system should be designed to scale to support any kind of building configuration: sbt, gradle, etc..
The text was updated successfully, but these errors were encountered: