|
|
|
|
|
|
by other_herbert
1876 days ago
|
|
|
It’s really down to goals... you should have something that triggers based on open pull requests and does a sanity check and ideally deployed to a test environment... that should be “quick” to give feedback in addition to reviews... Then in the main build that hopefully is deploying to a qa environment that can do more testing, bundle artifacts for whatever dependencies need them, all that kind of stuff... That’s how ours is set up... we use Jenkins with parallel parts where possible (like build the ui while tests that hit the db are run) it’s a process that takes time to get right and time to optimize... We’re at about 5 mins for the quick part and 8 or so for the slower part Both of those will probably get worse as we are planning to include full ui testing on the deployed environment too |
|
|