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
Publish release packages as workflow artifacts. An effort should be made to keep only relevant files for an installation.
As a developer I want to publish release artifacts So That it becomes easier to release DTaaS.
Describe the problems your feature request solves
The software release is a manual process at the moment. The release artifacts can be created from
github actions. Thus an automated release cycle can be introduced into the project.
Describe the solution you'd like
The files needed to be kept for complete installation are:
deploy/ (all contents of this directory)
files/ (all contents of this directory)
LICENSE.md
README.md
SECURITY.md
These files need to be published as a single zip file on the github actions page.
Describe alternatives you've considered
Another possibility is to customize the artifacts for different installation scenarios - localhost and server. But this can be done in the future.
Success Criterion
Publishable release artifacts (single zip file) produced from github actions.
Checklist:
zip file available for download
Installation successful from sources in zip file
Developer documentation updated
The text was updated successfully, but these errors were encountered:
Describe the feature
Publish release packages as workflow artifacts. An effort should be made to keep only relevant files for an installation.
As a developer I want to publish release artifacts So That it becomes easier to release DTaaS.
Describe the problems your feature request solves
The software release is a manual process at the moment. The release artifacts can be created from
github actions. Thus an automated release cycle can be introduced into the project.
Describe the solution you'd like
The files needed to be kept for complete installation are:
These files need to be published as a single zip file on the github actions page.
Describe alternatives you've considered
Another possibility is to customize the artifacts for different installation scenarios - localhost and server. But this can be done in the future.
Success Criterion
Publishable release artifacts (single zip file) produced from github actions.
Checklist:
The text was updated successfully, but these errors were encountered: