On 2 July 2014 19:29, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
On Wed, 2 Jul 2014 00:38:16 +0300 Paul Sokolovsky Paul.Sokolovsky@linaro.org wrote:
Hello,
As part of the migration, we would like to simplify email/smtp setup of android-build. Currently, it runs local smtpd to forward email. ci.linaro.org and other Jenkins instances just use google server to send email. We'd like to switch to reuse this account, which means there's one piece less software to maintain on android-build.
I hope nobody is concerned with this change in general. One issue we may expect though, is that email will come from new email address (ci_notify@linaro.org), so it may need to be approved to post to mailing list(s). To not leave too many fixes for next week, I'm going to switch android-build to new account today, to hopefully catch issues yet this week.
And first issue already popped up -
https://android-build.linaro.org/jenkins/job/linaro-android-restricted_vexpr... tried to send to linaro-android-restricted-builders@linaro.org , but that email account doesn't exist (verified by sending separate test email). Note that the job above also sends emails to linaro-android-restricted-builder-notifications@linaro.org (note "-notifications"), and that address appears to work (at least it doesn't bounce). Does anybody know what we have here? Perhaps linaro-android-restricted-builders@linaro.org just should be removed?
This can be removed. The email address were changed by ITS to match the google groups when they were doing migrations.
Let me know if you are/may be affected by these changes.
Thanks, Paul
On Thu, 26 Jun 2014 18:24:35 +0200 Milo Casagrande milo.casagrande@linaro.org wrote:
On Thu, Jun 26, 2014 at 5:36 PM, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
I would like to schedule migration for Friday next week, July 4. If you have any concerns, please let me know.
I also didn't receive any response regarding disk space concerns raised in the original mail (quoted below). Since then, I faced yet another with having so many jobs - it now takes quite a while to migrate them for any changes. So, my plan remains to stick with the current disk space, and then discuss and schedule cleaning of historical release builds.
If you don't agree with this tentative direction, and would rather see disk space (and maintenance effort) growing, please speak up soon.
Milo, please approve this plan and schedule otherwise if you see it ok.
Plan sounds good to me.
I would say that if there are no concerns (or no replies) to start cleaning up old builds, making sure they are on releases.l.o. Thanks Paul for working on this.
Ciao.
-- Best Regards, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android