We have two pending pull requests for JENKINS-45057. I think it worth to consider backporting them. Will try to get one of the fixes landed in the next weekly
четверг, 27 июля 2017 г., 17:07:01 UTC+2 пользователь Andreas Mandel написал: > > All valid points, for sure. This aspect of the Train Model was not clear > to me... I need to find a way for me how to reduce the risk to run into > such issues as much as possible for our productive system. We do tests in > advance and feedback - but actually this is not very formal (on our side) > and for sure it lacks some heavy load tests and tests that leave the system > at work for a longer time period. > > Now that I'm affected, I think it is important to somehow flag the LTS > with such issues - actually one can do a Jira Query to find all known open > issues or use the https://jenkins.io/changelog-stable/ page to check for > the weather condition and then decide based on the likely long list of > tickets if it is OK do go forward or not. > > I can not say why the issue did not get more attention earlier. IMHO it is > a kind of time bomb for every Jenkins installation, it might be undetected > for smaller installations especially if they go with the weekly releases > and so get restarted at least once a week. > > At the end we try to support to get the issue solved - hope this happens > soon. > > Thanks and kind regards, Andreas. > > Am Donnerstag, 27. Juli 2017 12:56:55 UTC+2 schrieb Daniel Beck: >> >> >> > On 27. Jul 2017, at 07:19, Andreas Mandel <[email protected]> >> wrote: >> > >> > Thanks for the feedback. Does this mean, according to plan, you release >> LTS versions even with blocker issues? Or do you judge the severity of the >> issue different? >> >> Yes. The train model means we leave the station no matter what. Otherwise >> we just get bogged down in discussions what constitutes a blocker issue >> while holding off releases to include well-soaked bug fixes. >> >> > but time is unfortunately quite limited. >> >> If I'm right with my guess of 2.53 as the first affected release, the >> problem was around for almost 3 months between introduction of the issue >> and the original report, which was created only after 2.60.1 was released. >> As we rely on users reporting and voting on issues they encounter for >> things like deciding on an LTS baseline, it's no surprise this got in. >> >> I asked a month ago in a comment for people who encounter this issue to >> narrow down in which release the problem was introduced. Despite having 20 >> watchers now, nobody seems to have taken the time to do that yet. >> >> Does that look consistent with an urgent blocker issue to you? >> >> -- 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/aef7efb7-7708-491c-ad13-f6007716a939%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
