[BUILD-532] Find an alternative for running the pipelines Created: 07/Sep/21 Updated: 27/Nov/23 Resolved: 27/Nov/23 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Epic Link: | Release automation |
| Team: |
| Description |
|
The webapp currently executes multiple pipelines on Jenkins. This allows:
That approach definitely works, but maybe we could consider deploying a dedicated executor for the project. Either on EC2 or on Heroku. January 20th 2022 notesAs we were running into memory issues with a growing number of tasks on a 512MB Heroku instance, I ran into the following tutorials:
We will focus on solving business problems for now, but having everything on Heroku (with a web node and additional worker nodes) looks to be possible and nicely documented. |