We run our automated Selenium tests via pipeline. We run at least once a day. However we're pushing the limits of a single step definition, so we're looking at a multi-step pipeline to avoid maxing out the time allotment per step.
The problem is, there's no way to "ignore" the errors in a step (aside from parallel steps, which don't help in this case, as the total execution time is still the same). Unless there is? I'm hoping I'm missing something simple. Is there an easy approach to keeping the tracking of test outcomes without blocking following steps?
Also, I'd really rather not use after-script to trigger a pipe or pipeline for this, because having a unified build log is important to the team that deals with test failures and releases.
Figured it out. A simple "[command] 2> /dev/null || true" appears to work.
Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.