Hi Mez, I totally understand your frustration. Current situation is that ci.jenkins.io is very unstable due to numerous factors. The most of CI runs fail, and on Friday we had an ACI outage which has not been resolved yet. On my side I had to postpone Jenkins core PR merges into weekly due to CI, and it is not the first time. I would say that ci.jenkins.io is basically unusable at the moment.
Why? As usual, we need contributors there. Olivier and other infra team members are doing a great job to keep the things afloat, bit right now it is a non-stop firefighting. JIRA, Confluence, ci.jenkins.io, and many other stories. We need more contributors in the infra team to share the maintenance load and to finally improve the setup. Ideally we should make ci.jenkins.io a reference setup which is reusable by other Jenkins users. Starting from November 15th, I personally commit to focus on infrastructure and, specifically, on ci.jenkins.io as a top priority. I will have less time for other areas like Jenkins Core, bit I consider the current state as a grave danger to the project. I invite everyone else to consider contributing to the infrastructure: https://jenkins.io/projects/infrastructure/#contributing Best regards, Oleg -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e310142d-4770-4c0d-a18d-89de3673ad96%40googlegroups.com.
