Availability of failed runs after a rerun

[Radu Cristescu]

It is my understanding that when you rerun a pipeline, previous logs are discared. Is that right?

I received a report that a pipeline failed with some very strange errors, but by the time I went in to investigate, the pipeline had been rerun and was successful.

Given the report I had, I am really curious to see why the initial run failed, because the symptoms reported make no sense.

[Aron Gombas _Midori_]

@Radu Cristescu 

Pipeline runs are identified by an integer number like "123". When you re-run a pipeline, there will be a new run created with a new ID (e.g. "124"), with its own log! But the first run's log will still be available using the old ID.

Just go to the list of pipeline runs and click the failed run, it should display the log.

[Radu Cristescu]

Hi Aron. I look at the reported pipeline, and you are not correct.

But I did find a "Runs" dropdown button that I don't recall seeing last time I had a need to see previous runs (It's been a while). I see the failed run in there. Same integer number, but with a `/runs/{UUID}` bit inserted in the URL.

[Aron Gombas _Midori_]

Hmm.

I looked up a failed build, and found this one (691) from 4 days ago, with the "Rerun" button available:

When I clicked "Rerun", it started a new build (693).

[Radu Cristescu]

I also think there may be a confusion of terms on my part. I think in this case only one step failed and it was rerun, rather than the whole pipeline (which would produce a new integer ID).

[Radu Cristescu]

When a failed setup is rerun on its own, this dropdown presents itself.

[Ben]

Hi @Radu Cristescu 

The dropdown should show you the list of successful/failed runs for that particular build, and their associated logs when accessed.

As you're using the Premium plan - these logs are retained for 400 days as per our policy outlined here:

• https://www.atlassian.com/blog/bitbucket/upcoming-changes-to-pipelines-log-retention-policy

If you're encountering issues - please raise a formal support ticket using that Premium workspaceID as we'll need a support ticket for our system to allow us to grant the necessary access to your repository to check this on our end:

• https://support.atlassian.com/contact/

Cheers!

- Ben (Bitbucket Cloud Support)

[Radu Cristescu]

Thanks @Ben . I don't have any issues right now.

My problem seems to be psychological in nature. What happened is that I remember being told, at some point in the past, that when a step is rerun the previous runs are no longer accessible. I don't know how valid that memory is, but at least now there's that "Runs" dropdown that I don't remember seeing last time I had a situation where I wanted to see logs of past runs.

Because of that memory, I didn't even look at the "Runs" button until @Aron Gombas _Midori_ responded. It just then jumped at me. I don't know when the "Runs" dropdown appeared, but because I never used it before, and my prior thought that it doesn't exist, didn't make me go look for it. I wished for it for so long, and thought it would never appear, that I totally missed it when it did.