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
The current project lacks a working Build & Deploy script or pipeline.
I suggest the use of a tool suck as Apache Ant.
Alternatively, rewriting of the build and deploy scripts to work cross-platform. (or at all)
CI/CD Pipeline
It would be both more convenient for the contributors of this project as well as the users of it if we would integrate with a CD/CD pipeline. This would be of great help for ease of testing releases on all platforms as well as offering the resulting 'jar' and run scripts in a release bundle without having to download the whole source code. (offering releases is possible now too, it just would have to be done manually)
From the tools I have used I recommend Azure Pipeline as it is free and easy to use. They also offer direct integration with Github. Since it is all done in the cloud no additional human input is required.
Alternatively, we could use Jenkins which is also free.
Testing
The project lends itself to a great deal of future problems which may break previously working examples.
We could create a simple mechanism of testing Alk code examples. (maybe add annotations in the files describing the expected output state)
This way we can spot problems with the current builds directly in the pipeline before making a release.
The text was updated successfully, but these errors were encountered:
Build & Deploy
The current project lacks a working Build & Deploy script or pipeline.
I suggest the use of a tool suck as Apache Ant.
Alternatively, rewriting of the build and deploy scripts to work cross-platform. (or at all)
CI/CD Pipeline
It would be both more convenient for the contributors of this project as well as the users of it if we would integrate with a CD/CD pipeline. This would be of great help for ease of testing releases on all platforms as well as offering the resulting 'jar' and run scripts in a release bundle without having to download the whole source code. (offering releases is possible now too, it just would have to be done manually)
From the tools I have used I recommend Azure Pipeline as it is free and easy to use. They also offer direct integration with Github. Since it is all done in the cloud no additional human input is required.
Alternatively, we could use Jenkins which is also free.
Testing
The project lends itself to a great deal of future problems which may break previously working examples.
We could create a simple mechanism of testing Alk code examples. (maybe add annotations in the files describing the expected output state)
This way we can spot problems with the current builds directly in the pipeline before making a release.
The text was updated successfully, but these errors were encountered: