AllSpice-Demos/Actions-Demo
AllSpice-Demos/Actions-Demo
13
Fork 0
Files Issues Design Reviews Actions NEW Releases Activity

Update readme.md

Browse Source
This commit is contained in:
allspice-hermes 2024-07-29 15:45:51 +00:00
parent bdeb25d50d
commit 4b829643eb
1 changed files with 7 additions and 0 deletions

7
readme.md
View File

@ -14,8 +14,15 @@ While the tech industry scales and spreads across the world, the demand for shor
AllSpice actions is the building block of Continuous Integration and Continous Deployment (CI/CD) for hardware and it represents a crucial tool that Engineering teams can leverage in order to respond to this new demands and improve their **development speed**, reduce their **time-to-market**, enhance **product quality and reliability**, have a seamless **team collaboration** and even reduce costs with early **detection of errors and issues**.
## How they work?
<div align="left">
<img src="./images/Actions-workflows.png">
</div>
AllSpice actions work in a simple way, similar to other CI/CD solutions for software like Gitlab CI/CD or Github Actions. It all starts with an event within you repo (Eg. a new design review) that triggers a runner to execute a specific set of tasks. The defined groupd of tasks are called workflows and each task is absically a script that does something for you. You can use custom scripts or pre made ones from the allspice library. You can also have as many tasks as you want in a workflow and as many workflows as you want in your repo. Below you can see a simplified diagram of how an AllSpice Action works. For more info you can go to our actions documentation.
### Testing an Action
Want to see how this works right away? Clone this repo, go to the issues tab and create a new issue. Then, go to the actions tab within the repo and you will find the results log for the runned workflows. You can also go to this repo's actions tab and see the runned workflows.
## Top 3 Actions Add-ons