A "Task Provider" is an
OpenCatapult extension which provides specific implementation of a job task. It holds an important role because
OpenCatapult itself is designed to be a platform-agnostic system which means it should not make any assumptions about how a task should work.
OpenCatapult provides the mechanism through which task providers execute, correctly and in the defined sequence. You can think of
OpenCatapult as a cassette player and the task providers as the cassettes:
The task provider (cassette) contains the music that will be generated whereas the cassette player (
OpenCatapult) simply plays the cassette tape.
If you went through the quick start you may have noticed that you had to define a task provider when creating your first project. That's because without a "tape", the "cassette player" would have no music to play.
At the moment, there are 8 types of Task Provider.
OpenCatapult provides built-in Task Providers for most of them:
A "Generator Provider" defines what you are asking
OpenCatapultto create. For example, you may consume or create a provider that builds a .NET MVC based intranet, or a PHP based eCommerce site. A task provider can even be created for an Amazon Alexa voice app;
OpenCatapultdoesn't care what is music is on the cassette tape, it just knows how to play whatever you have selected.
The default Generator Provider is
Polyrific.Catapult.TaskProviders.AspNetCoreMvcwhich produces an ASP.NET Core MVC application.
Build Providers answer the question of how your code will be built and deployed.
OpenCatapultallows you to define a CI/CD pipeline that works your way by creating a build provider that defines every actionable step in your build & release flow.
The default Build Provider is
Polyrific.Catapult.TaskProviders.DotNetCorewhich builds a Dotnet Core application into a ready to deploy artifact.
The Repository Provider dictates where your source code will live. You can create or consume task providers for almost any kind of version control service so that your code is checked in to a location of your choosing.
The default Repository Provider is
Polyrific.Catapult.TaskProviders.GitHubwhich stores the source code to GitHub repository.
The Hosting Provider lets you declare where your app should be deployed. You can create or consume a hosting provider that will deploy your apps to Azure, AWS, Rackspace, on-premise, or any other place of your choosing.
The default Hosting Provider is
Polyrific.Catapult.TaskProviders.AzureAppServicewhich provides the implementation of application deployment to Azure App Service.
The Database Provider handles how the changes on the defined data models are reflected to the application database. You can create or consume a Database Provider for specific database services (e.g. SQL Server, MySQL, PostgreSQL, etc) with optional ORM (e.g. Entity Framework, NHibernate, ActiveRecord, etc).
The default Database Provider is
Polyrific.Catapult.TaskProviders.EntityFrameworkCorewhich provides the implementation of Entity Framework Core to work with SQL Server database.
The Test Provider lets you define various tests for your application. You can create or consume a Test Provider for specific test runners, e.g. XUnit, NUnit, Karma, etc.
The default Test Provider is
Polyrific.Catapult.TaskProviders.DotNetCoreTestwhich utilizes Dotner Core Test tool to execute test scenarios for the defined test runner.
The Storage Provider facilitates the need to upload or download an artifact in the case where the Build Server and Deployment Server are located in different machines.
The Generic Task Provider helps you to create a simple action without having to create a specific task provider for it. It can be any actions like copying files, replacing file content, checking installed tools, etc.
The default Generic Task Provider is
Polyrific.Catapult.TaskProviders.GenericCommandwhich allows user to enter some commands to be run in a command line tool. In most of the time it will be the only Generic Task Provider you ever need.