Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: alejandrocelaya.blog
Running several steps of a Travis CI build in parallelCategory: javascript
However, people seem to be "abandoning" travis in favor of GitHub Actions, for different reasons.
In my case, I have moved a few very specific tasks there, where travis was becoming a bottleneck, but I still have mixed feelings about the very-verbose yaml-based config needed to configure a few GitHub Actions, compared to the more concise travis one. In this article I'll explain how I improved a travis build to run several smaller tasks in parallel jobs, without having to completely move away from it.
It is used to build a JS project for the web browser, and it has to run the next tasks: This is more or less ok, but the last two commands in script can be relatively slow and can delay the whole process.
If you are curious, this is the project in which I use this travis configuration: shlinkio/shlink-web-client.
In my case, I have moved a few very specific tasks there, where travis was becoming a bottleneck, but I still have mixed feelings about the very-verbose yaml-based config needed to configure a few GitHub Actions, compared to the more concise travis one. In this article I'll explain how I improved a travis build to run several smaller tasks in parallel jobs, without having to completely move away from it.
It is used to build a JS project for the web browser, and it has to run the next tasks: This is more or less ok, but the last two commands in script can be relatively slow and can delay the whole process.
If you are curious, this is the project in which I use this travis configuration: shlinkio/shlink-web-client.
Newsletter
Glimpse
Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Community Partners
Laravel/PHP Careers