We are happy to announce that OpenCatapult v1.0.0-beta2 has been released. You can get it by checkout the code to
v1.0.0-beta2 tag after cloning it from GitHub.
git checkout v1.0.0-beta2
If you prefer to download the binaries, the
win-x64 packages are also available in the release website.
So what are in this release?
Web User Interface
The biggest thing in this release is that we have completed the initial implementation of Web UI. Users may choose to work with CLI or Web UI now to have interaction with OpenCatapult.
This is an Angular website. And, just like other components, we have provided a build script to run it locally in your machine. The only requirement is that you need to have Node.js and NPM installed on your machine.
Please find the steps to create your first OpenCatapult project by using Web UI in the docs.
Rename Task Provider namespaces and packages
In the last
v1.0.0-beta1 release, we announced that we renamed the term
Task Provider. It reflected only on how we call the term. However, none of the things in the code was changed.
In this release, we started to do the changes in code level by renaming namespaces and package names:
- Polyrific.Catapult.Plugins.Core ==> Polyrific.Catapult.TaskProviders.Core
- Polyrific.Catapult.Plugins.AspNetCoreMvc ==> Polyrific.Catapult.TaskProviders.AspNetCoreMvc
- Polyrific.Catapult.Plugins.AzureAppService ==> Polyrific.Catapult.TaskProviders.AzureAppService
- Polyrific.Catapult.Plugins.DotNetCore ==> Polyrific.Catapult.TaskProviders.DotNetCore
- Polyrific.Catapult.Plugins.DotNetCoreTest ==> Polyrific.Catapult.TaskProviders.DotNetCoreTest
- Polyrific.Catapult.Plugins.EntityFrameworkCore ==> Polyrific.Catapult.TaskProviders.EntityFrameworkCore
- Polyrific.Catapult.Plugins.GitHub ==> Polyrific.Catapult.TaskProviders.GitHub
For Task Provider creators, please use the new Core package to be referenced from your Task Provider project:
dotnet add package Polyrific.Catapult.TaskProviders.Core
The changes are also done in CLI, where the
plugin command is renamed to
dotnet occli.dll provider list
In API, we also rename
/plugin endpoint into
--wait options to
queue log command
--wait options to
queue log command in CLI to make the process to wait for the incoming log stream without exiting. If this option is not included, the process will directly end if the log stream is not ready, and the user needs to retry it again to check.
dotnet occli.dll queue log -p ProjectA -n 1 --wait
DisplayName property to
As the name implies, this new
DisplayName property will be used to display Project name in certain places. If not defined, it will be filled with the value from the existing
Improve build scripts
- Add a title to the shell windows for each component.
- Set connection string to
appsettings.[env].jsinstead of directly to
appsettings.json. This environment setting file is also added to the
.gitignoreso it won’t be accidentally checked in to the repository.
- Allow the new
build-web.ps1script to be invoked from the
- Add new switch arguments to the
-noWeb. It allows the users to run only one UI of their preference: the CLI or the Web UI.
- Fix the issue where suspended Engine can still access API endpoints
- Fix timezone issue for
Please go check the changes yourself, and let us know what you think. Thank you.