I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page: https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
Tim
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page: https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk... read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Wed, 19 Feb 2020 13:59:10 -0500 Johnny Bieren jbieren@redhat.com wrote:
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk... read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
OK, that would fit with what I'm seeing.
Is this something we can or should increase? It doesn't take long to hit 100 builds in a single release.
Tim
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Wed, Feb 19, 2020 at 10:53 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 13:59:10 -0500 Johnny Bieren jbieren@redhat.com wrote:
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk... read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
OK, that would fit with what I'm seeing.
Is this something we can or should increase? It doesn't take long to hit 100 builds in a single release.
I'd prefer if we could have some other place to store the logs and not having them only in the Jenkins jobs, for example is there any NFS storage that we could use?
Tim
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Thu, Feb 20, 2020 at 9:01 AM Bruno Goncalves bgoncalv@redhat.com wrote:
On Wed, Feb 19, 2020 at 10:53 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 13:59:10 -0500 Johnny Bieren jbieren@redhat.com wrote:
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here
https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk...
read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
OK, that would fit with what I'm seeing.
Is this something we can or should increase? It doesn't take long to hit 100 builds in a single release.
I'd prefer if we could have some other place to store the logs and not having them only in the Jenkins jobs, for example is there any NFS storage that we could use?
Or S3 O:-)
Thanks, Michal
Tim
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
Hey,
We will definitely want something as we have on downstream for artifacts storage for Testing Farm. I would even go with the same simple rsync method we use there, as it is just simple & awesome. I believe we can for sure start with S3 for that :).
Best regards, /M
On Thu, Feb 20, 2020 at 9:30 AM Michal Srb msrb@redhat.com wrote:
On Thu, Feb 20, 2020 at 9:01 AM Bruno Goncalves bgoncalv@redhat.com wrote:
On Wed, Feb 19, 2020 at 10:53 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 13:59:10 -0500 Johnny Bieren jbieren@redhat.com wrote:
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here
https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk...
read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
OK, that would fit with what I'm seeing.
Is this something we can or should increase? It doesn't take long to hit 100 builds in a single release.
I'd prefer if we could have some other place to store the logs and not having them only in the Jenkins jobs, for example is there any NFS storage that we could use?
Or S3 O:-)
Thanks, Michal
Tim
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Thu, 20 Feb 2020 09:00:28 +0100 Bruno Goncalves bgoncalv@redhat.com wrote:
On Wed, Feb 19, 2020 at 10:53 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 13:59:10 -0500 Johnny Bieren jbieren@redhat.com wrote:
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk... read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
OK, that would fit with what I'm seeing.
Is this something we can or should increase? It doesn't take long to hit 100 builds in a single release.
I'd prefer if we could have some other place to store the logs and not having them only in the Jenkins jobs, for example is there any NFS storage that we could use?
I spoke with bstinson about available storage at devconf and I'm under the impression that there is available storage in the CentOS CI infrastructure.
That being said, would it be worth making the change at this point if testing farm is imminent? That'd be a decent amount of work in terms of reworking the links to be sent out on top of making sure that everything continues to work well.
I figured that increasing the lifetime of the jobs on the master would be a quick and dirty way to improve things.
Tim
Tim
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Thu, Feb 20, 2020 at 2:26 PM Tim Flink tflink@redhat.com wrote:
On Thu, 20 Feb 2020 09:00:28 +0100 Bruno Goncalves bgoncalv@redhat.com wrote:
On Wed, Feb 19, 2020 at 10:53 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 13:59:10 -0500 Johnny Bieren jbieren@redhat.com wrote:
On Wed, Feb 19, 2020 at 12:26 PM Tim Flink tflink@redhat.com wrote:
On Wed, 19 Feb 2020 10:11:25 -0700 Tim Flink tflink@redhat.com wrote:
I'm looking back on a run that was done on 2020-02-05 and it appears as if the logs have already been removed from the Jenkins master.
The blue ocean link to the run is:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
I think that this should be the link to the classic Jenkins result page:
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pack...
Am I missing something? Are the logs supposed to be stored for longer than this?
I believe this is controlled here https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/Jenk... read as, keep 30 days or 100 builds of artifacts (whichever is less) and let a build stick around for 90 days or 100 builds (again whichever is less) Those numbers would be per pipeline job
OK, that would fit with what I'm seeing.
Is this something we can or should increase? It doesn't take long to hit 100 builds in a single release.
I'd prefer if we could have some other place to store the logs and not having them only in the Jenkins jobs, for example is there any NFS storage that we could use?
I spoke with bstinson about available storage at devconf and I'm under the impression that there is available storage in the CentOS CI infrastructure.
That being said, would it be worth making the change at this point if testing farm is imminent? That'd be a decent amount of work in terms of reworking the links to be sent out on top of making sure that everything continues to work well.
I figured that increasing the lifetime of the jobs on the master would be a quick and dirty way to improve things.
Just a note the pipeline archives the qcow2 image when test fails, so developers could use the qcow2 to debug the failure (I don't know who actually uses it though...), in case we increase the number of jobs it will have some impact on jenkins master storage usage...
Tim
Tim
Digging into this a little more, I found a run from 5 days ago (2020-02-14) which appears to have been removed from the Jenkins master
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-build...
I'm unclear if this only an issue for the rawhide pipeline or not as an older run from the F31 pipeline on 2020-02-13 is still present:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f31-build-pip...
Tim _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
-
Bruno Goncalves -
Johnny Bieren -
Michal Srb -
Miroslav Vadkerti -
Tim Flink