Run `N` scripts within task.
See original GitHub issueHello good people of maid,
Would it be possible if we could implement the ability to run synchronously N
number of scripts within a Task?.
E.j:
## build
Run task `test` after this
Retrieves the configuration from a website:
```bash
curl https://website.com/myConfiguration > config.json
```
Manipulate somehow the downloaded configuration:
```js
const config = require('./config.json');
// ....
```
## test
```bash
jest --config config.json
```
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Run scripts on devices - P9 Tasks feature
In short, with Tasks you've got the ability to remotely command devices to perform jobs from ... Scripts that can be run on...
Read more >Add a scripting task - N-able
Add a scripting task · Click Configuration > Scheduled Tasks > Add/Delete. · Click Add > Scripting. · Enter a Task Name. ·...
Read more >Task Scripts - Concourse Tutorial by Stark & Wayne
One way to fix that is to open up the file in Notepad++, click on "Edit->EOL Conversion->Unix". Save the file and execute the...
Read more >2.1. Creating and running a script
This is the most common way to execute a script. It is preferred to execute the script like this in a subshell. The...
Read more >Perform a different task each time a bash script is executed
Yes its easy to do this by remembering/persisting what was run the last time. $ echo "1" > current_counter $ cat current_counter 1...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it sounds fairly useful. It’d be especially beneficial for the cases when you really needed to use different languages to solve a problem without polluting the task namespace.
@olstenlarck Can you expound on your concerns?
I’d vote to just keep it as is. The top level text describes what the task does overall. Other paragraphs near code blocks can exist just to document what each one does, but I don’t know that the help text really needs to document ever single code sequence that the task runs.