[
https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1744:
--------------------------------
Description:
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.
was:
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 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
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.
> Revisit build artifact storage and retnesion
> --------------------------------------------
>
> 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
>
> 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.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
