Yes. Support Core plugin setup is something we could do as a part of the instance update. Ideally we need integration with an online service like Sentry in Jenkins Evergreen so that we can automate log processing and notifications
On Sun, Oct 27, 2019, 13:30 Arnaud Héritier <[email protected]> wrote: > Oleg i can propose my help too. > For sure I won’t be able to dedicate a major part of my time but I suppose > that everything is good to take. > > I am already infra member but I don’t have an admin access on > ci.jenkins.io > > Do we have the support-core plugin installed on this instance ? If no, can > we add it ? > > If I can have access to a support bundle I will do a health check review > like we do for our customers at CloudBees. > > Can it help? > > Le dim. 27 oct. 2019 à 09:31, Oleg Nenashev <[email protected]> a > écrit : > >> 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 >> . >> > -- > ----- > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/xqC8vW_emJI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--n1U8f%2BKtL%3DecORahj3vGp7VzznCmZ8BaPrgm_Lg2b7w%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--n1U8f%2BKtL%3DecORahj3vGp7VzznCmZ8BaPrgm_Lg2b7w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPfivLAqfqf39FqdirThb%2BZMNwcZ%3D3M09PqPXWBV_HQYFsMh1w%40mail.gmail.com.
