Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How would I go about constructing a very long pipeline?

Mike Burton September 6, 2019

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.

1 answer

1 accepted

0 votes
Answer accepted
Mike Burton September 9, 2019 edited

Figured it out. A simple "[command] 2> /dev/null || true" appears to work.

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, loom, AI, meeting recording, community

[NEW] Record your meetings with Loom

Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.

Learn more
AUG Leaders

Atlassian Community Events