Skip to content

Commit

Permalink
CR remarks
Browse files Browse the repository at this point in the history
  • Loading branch information
MichielOda committed May 6, 2024
1 parent 49c6cfd commit 509aaeb
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,17 +5,17 @@
>
> The old readme file can be found here: [old readme](oldReadme.md)
## Migration to .NET Tools
## Transition to .NET Tools

Instead of using the GitHub action, we are now using .NET tools. These are more flexible as they can be used on any commonly used platform like GitHub, GitLab, Azure DevOps, ...
Our workflow has evolved from relying solely on GitHub actions to embracing the versatility of .NET tools. This transition offers enhanced flexibility, enabling seamless integration across various widely utilized platforms such as GitHub, GitLab, Azure DevOps, and more.

The GitHub Action did 3 things in 1 which wasn't always what was wanted by our users:
Previously, the GitHub Action encompassed a bundled approach, performing three distinct tasks:

- Creating a package
- Uploading a package to Catalog
- Deploying a package to a DataMiner
1. Generating a package
1. Uploading the package to the Catalog
1. Deploying the package to a DataMiner

These 3 steps have been converted into their own .NET tool and can be used separately depending on the scenario.
However, this bundled functionality didn't always align with the specific needs of our users. In response, we have modularized these tasks into individual .NET tools, allowing for tailored usage based on the unique requirements of each scenario.

Below is an example of a full migration of the GitHub action:

Expand Down

0 comments on commit 509aaeb

Please sign in to comment.