Answers: <p>IMHO if your successful build doesn't push to an artifact repository, there's a problem in your pipeline.</p>
  
  <p>Jenkins or Bamboo do <em>not</em> aim at keeping built artifacts forever and they don't give you any versioning delivery, as such that's a point of failure in your delivery system. </p>
  
  <p>I'd advise to review your method to use an artifact repository and that will solve this XY problem of keeping a successful build inside the build system used as an artefact source.</p>
  
  <p><strong>Note</strong>: I can't speak for Bamboo's team, but adding this capacity involves raising the code complexity for a 'side usage'. As such it can makes sense Bamboo's team avoid it to avoid adding code complexity for a feature not in their overall goal. I don't think they avoid it to enforce a best practice, but more to avoid raising unnecessary (from the product point of view) complexity to their code base.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-07-20T12:06:22.347Z
Answers: would you say Bamboo does not offer this feature exactly therefore to enforce this best practice (your personal opinion)?
Answers: Ta Mu
Answers: CC BY-SA 3.0
Answers: 2017-07-20T12:11:19.520Z
Answers: I can't speak for Bamboo's team, but adding this capacity involve raising the code complexity for a 'side usage', as such it can makes sense Bamboo's team avoid it to avoid adding code complexity for a feature not in their overall goal. I don't think they avoid it to enforce a best practice, but more to avoid raising unnecessary (in the product point of view)  complexity to their code base.
Answers: Tensibai
Answers: CC BY-SA 3.0
Answers: 2017-07-20T11:56:31.773Z
Answers: 2017-12-07T10:41:07.267Z
Answers: 2017-12-07T10:41:07.267Z
Answers: Tensibai
Body: <p>In Jenkins, you could configure the system to retain a certain number of either successful or failed builds.</p>
  
  <p>With Bamboo, it seems like you can just retain a certain number of builds which rotates the last successful build after 10 failed builds out of the system.</p>
  
  <p>Is there a way in Bamboo to retain the last successful build for an unlimited time?</p>
  
  <p>UPD wait, but is that true with the 10 builds limitation, really?
  I have just realized that I could click the UI through the whole build history, both successful and unsuccessful builds.
  <a href="https://i.sstatic.net/C2NAr.jpg" rel="nofollow noreferrer">https://i.sstatic.net/C2NAr.jpg</a></p>
  
Tags: <bamboo>
Title: Retaining at least one successful build in Bamboo
UserDisplayName: Ta Mu
ThreadText: # Retaining at least one successful build in Bamboo
  
  (Asked by: username_0 on 2017-07-20)
  
  In Jenkins, you could configure the system to retain a certain number of either successful or failed builds.
  
  With Bamboo, it seems like you can just retain a certain number of builds which rotates the last successful build after 10 failed builds out of the system.
  
  Is there a way in Bamboo to retain the last successful build for an unlimited time?
  
  UPD wait, but is that true with the 10 builds limitation, really?
  I have just realized that I could click the UI through the whole build history, both successful and unsuccessful builds.
  <https://i.sstatic.net/C2NAr.jpg>
  
  **Tags:** bamboo
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-07-20. Score: 7 | Accepted answer
  
  IMHO if your successful build doesn't push to an artifact repository, there's a problem in your pipeline.
  
  Jenkins or Bamboo do *not* aim at keeping built artifacts forever and they don't give you any versioning delivery, as such that's a point of failure in your delivery system.
  
  I'd advise to review your method to use an artifact repository and that will solve this XY problem of keeping a successful build inside the build system used as an artefact source.
  
  **Note**: I can't speak for Bamboo's team, but adding this capacity involves raising the code complexity for a 'side usage'. As such it can makes sense Bamboo's team avoid it to avoid adding code complexity for a feature not in their overall goal. I don't think they avoid it to enforce a best practice, but more to avoid raising unnecessary (from the product point of view) complexity to their code base.
  
  > **Comments:**
  > **username_0**: would you say Bamboo does not offer this feature exactly therefore to enforce this best practice (your personal opinion)?  
  > **username_1**: I can't speak for Bamboo's team, but adding this capacity involve raising the code complexity for a 'side usage', as such it can makes sense Bamboo's team avoid it to avoid adding code complexity for a feature not in their overall goal. I don't think they avoid it to enforce a best practice, but more to avoid raising unnecessary (in the product point of view)  complexity to their code base.  
  
  ---
  
  