Details
-
Improvement
-
Resolution: Obsolete
-
Neutral
-
None
-
None
-
None
-
None
Description
The webapp currently executes multiple pipelines on Jenkins. This allows:
- to not clutter the webapp, it only orchestrates
- to leverage Jenkins configuration in order to go faster: the Maven settings, repositories, etc.
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 notes
As we were running into memory issues with a growing number of tasks on a 512MB Heroku instance, I ran into the following tutorials:
- https://devcenter.heroku.com/articles/asynchronous-web-worker-model-using-rabbitmq-in-java
- https://devcenter.heroku.com/articles/background-jobs-queueing
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.
Checklists
Acceptance criteria