<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre>
<h3>Barak Korren updated OVIRT-1744:</h3>
<pre>Description:</pre>
<p>We need to revisit how we store and manage build artifacts in our environment.</p>
<p>We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact</p>
<p>We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages.</p>
<pre>was:</pre>
<p>We need to revisit how we store and manage build artifacts in our environment.</p>
<p>We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them is possible. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact</p>
<p>We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages.</p>
<blockquote><h3>Revisit build artifact storage and retnesion</h3>
<pre> Key: OVIRT-1744
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Repositories Mgmt
Reporter: Barak Korren
Assignee: infra
Priority: Highest
Labels: artifacts, repositories</pre>
<p>We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzYS3r1Q939T2sgz0QIVj1dLPZpYEx1M9925UdMVMTvSPbqBLLEAhi5vRRumEbObjddOJWaL0sPAhQX8-2B10geZMSxe3VBNCeJ0-2F89phxPnQE37FyNAnsARK3x2y1QILHOdtNXJmu3o-2BdsRAac-2FQHDbGPTJ1BaYog1-2FApMx38n6hCvj-2BIIcQWus7VxqVABc03IXuj7iQu6BxFIqj2s-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>