Pagure tests are failing and it is impossible to see where it started, because https://ci.centos.org/job/pagure-pr/ lists only latest 10 jobs, which is not enough.
Logs are only preserved for latest three builds, which makes it impossible to see the logs from the latest successful run.
Adding https://plugins.jenkins.io/test-results-analyzer/ will at least allow to see which tests failing and which were successful over time.
What I don't see if where are these things configured. I haven't found any repository referenced from the ci.centos.org web site or its wiki.
Even the latest logs are erased. Latest build at https://ci.centos.org/job/pagure-pr/ were just 2 days ago and the logs are already gone.
Hi @abitrolly, we are moving jobs from older jenkins to new cluster where you control your namespace (jenkins admin) and you can install plugins as you wish. We already have created a space for you ([0] and [1]) with all things ready. We even tried to move Pagure once but because of some things we rolled back. Can we try to move again and have you all the access
[0] https://console-openshift-console.apps.ocp.ci.centos.org/ [1] https://jenkins-pagure.apps.ocp.ci.centos.org/
Metadata Update from @siddharthvipul1: - Issue priority set to: Waiting on External (was: Needs Review)
CC @pingou as I don't have access to Pagure instance to point to alternative Jenkins.
This requires @pingou to do this (as he has access and even if I did, I don't know how to work with Jenkins much...).
bug triaging : is the migration already done ? and if so can we close this ticket ?
@arrfab doesn't look like it is done. Old https://ci.centos.org/job/pagure-pr/ CI still shows a build 6 days ago.
well, that means that you only have a very short time to migrate, as ci.centos.org, (as shown on frontpage) is supposed to disappear end of this year, so hurry up to migrate your workload to new openshift setup ;-)
There are no logs, no history, so the server itself has little value. Maybe only configs for tests. Not sure if they are backed in version control.
It seems for me that it is easier to abandon Jenkins altogether and do Jenkins X + Tekton CI/CD from scratch.
[backlog_refinement] This needs to be migrated to new Jenkins instance. This one is legacy and project should migrate from it. You can request a namespace here. And you can find more at the SIG guide regarding CI.
Metadata Update from @zlopez: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.