What I could do, if you agree, is to have both the standard and the ext notifcations turned on:
Standard notification: sends build summary, with no attachement, to commit ML Ext notification: send build summary + log attachement to change committers, excluding Alex. I will wait for your GO this time before proceeding. Alex, what email address (addresses) should I exclude ? Maurice -----Message d'origine----- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mercredi 4 décembre 2013 01:05 À : dev@flex.apache.org Objet : RE: Updating Mustella jenkins VM Ok, I will turn it on. -----Message d'origine----- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : mercredi 4 décembre 2013 00:56 À : dev@flex.apache.org Objet : Re: Updating Mustella jenkins VM Thank you :-) Maurice, please go ahead and turn it on for now. If not, I can do it. Thanks for getting this working so far. I will try to find some time to work on making the VM publicly available soon. Regards, Om On Tue, Dec 3, 2013 at 3:52 PM, Alex Harui <aha...@adobe.com> wrote: > It will be annoying, but I can live with it. > > -Alex > > On 12/3/13 3:41 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > >Let us keep the log files attachments coming in until we make the > >Mustella VM publicly accessible. > > > >Alex, would that work for you? > > > >Thanks, > >Om > > > > > >On Tue, Dec 3, 2013 at 3:37 PM, Maurice Amsellem < > >maurice.amsel...@systar.com> wrote: > > > >> Sorry. I already turned off the attachements. > >> > >> Anybody can turn them on back , if they wish: it's in the job > >> configuration... > >> > >> Maurice > >> > >> -----Message d'origine----- > >> De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mercredi 4 > >> décembre 2013 00:35 À : dev@flex.apache.org Objet : Re: Updating > >> Mustella jenkins VM > >> > >> It didn't occur to me until just before I wrote it. But see my > >> other reply. There's probably fewer folks on commits@ so I'll just > >> live with it for a while and see if anyone else complains. > >> > >> -Alex > >> > >> On 12/3/13 3:32 PM, "Maurice Amsellem" > >> <maurice.amsel...@systar.com> > >> wrote: > >> > >> >Ok, I will turn off the log zip attachment. > >> > > >> >But really, I would have appreciated that you said this BEFORE I > >> >did it > >> > > >> >:-( :-( :-( > >> > > >> >Maurice > >> > > >> >-----Message d'origine----- > >> >De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de > >> >OmPrakash Muppirala Envoyé : mercredi 4 décembre 2013 00:23 À : > >> >dev@flex.apache.org Objet : Re: Updating Mustella jenkins VM > >> > > >> >On Tue, Dec 3, 2013 at 3:15 PM, Alex Harui <aha...@adobe.com> wrote: > >> > > >> >> Well, I know you put a lot of time into it, but I guess I'm > >> >> suggesting that this is just going to create more noise for > >> >> folks, even if you only attach on failure. If you see the kind > >> >> of notices I get from the spam filter they aren't fun to look > >> >> at. We already have a problem with folks wanting to unsubscribe. > >> >> > >> >> Couldn't the build script simply check in the log into one of > >> >> our > >>repos? > >> >> Could we then include a link to the log file in SVN in the email? > >> >> > >> >> But sure, you can leave it as is until you get the energy to > >> >> change > >>it. > >> >> > >> >> -Alex > >> >> > >> >> > >> >Some options we have in order of increasing desirability: > >> > > >> >1. Send log file with every email notification 2. Send log file > >> >only with failure notifications 3. Check log file into git/svn > >> >and include link in the email 4. Expose the Jenkins instance on > >> >the Mustella VM to public (like > >> >builds.apache.org) > >> > > >> >I think option 4 is most desirable and shouldn't take a long time > >> >to implement. But option 1 or 2 should be good for now. > >> > > >> >Thanks, > >> >Om > >> > > >> > > >> > > >> > > >> > > >> >> On 12/3/13 3:04 PM, "Maurice Amsellem" > >> >> <maurice.amsel...@systar.com > > > >> >> wrote: > >> >> > >> >> >Alex, I understand the concern. > >> >> >I could change the config so that build logs are attached only > >> >> >upon failure, or maybe sent individually to change committers > >> >> >but not to commit list. > >> >> >The plugin is very flexible for that. > >> >> > > >> >> >On the other hand, the build logs compress very well ( 500 KB > >> >> >=> 25 > >> >> >KB) because of all the redundancy. > >> >> > > >> >> >Maybe try with this configuration for a few days, and then I > >> >> >will change the notification rules if still requested. > >> >> > > >> >> >WDYT? > >> >> > > >> >> >Maurice > >> >> > > >> >> >-----Message d'origine----- > >> >> >De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 3 > >> >> >décembre > >> >> >2013 23:57 À : dev@flex.apache.org Objet : Re: Updating > >> >> >Mustella jenkins VM > >> >> > > >> >> >I think having the logs will be very helpful, so thanks for > >> >> >doing that, but I'm wondering about our archives and all the > >> >> >folks who mirror our archives and whether these logs are worth > >> >> >archiving. Is there some other way? Stuffing the logs and/or > >> >> >zips into Git or > >>SVN? > >> >> > > >> >> >Also, it turns out the whitelist doesn't affect the spam filter > >> >> >catching zip files. I will have to fish them out of the spam > >> >> >server if > >> >>I need them. > >> >> > > >> >> >-Alex > >> >> > > >> >> > > >> >> >On 12/3/13 2:50 PM, "Maurice Amsellem" > >> >> ><maurice.amsel...@systar.com > > > >> >> >wrote: > >> >> > > >> >> >>It seems that the error below has disappeared (probably a > >> >> >>ghost process that ended). > >> >> >> > >> >> >>Status: > >> >> >>- flex-sdk_mustella-air - Build # 388 - Successful => sent > >> >> >>notification with attached 26KB build log file (480KB > >> >> >>unzipped) > >> >> >>- flex-sdk_mustella-mobile #412 in progress > >> >> >>- flex-sdk_mustella queued... > >> >> >> > >> >> >>If everything goes well, flex-sdk-mustella should fail and > >> >> >>send a huge build log file with the email. > >> >> >> > >> >> >>Maurice > >> >> >> > >> >> >>-----Message d'origine----- > >> >> >>De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] > >> >> >>Envoyé : mardi 3 décembre 2013 22:46 À : dev@flex.apache.org > >> >> >>Objet > >>: > >> >> >>RE: Updating Mustella jenkins VM > >> >> >> > >> >> >>Hi, I am configuring the Mustella Jenkins VM notifications. > >> >> >>Sorry for the burst of test notifications. > >> >> >> > >> >> >>I have launched manually mustella test and both > >> >> >>flex-sdk-mustella-mobile / flex-sdk-mustella keep on failing > >> >> >>with this > >> >> >>error: > >> >> >> > >> >> >>Commencing build of Revision > >> >> >>905f8a551b58cf92b40ef194b0578412ed37f266 > >> >> >>(origin/develop) Checking out Revision > >> >> >>905f8a551b58cf92b40ef194b0578412ed37f266 (origin/develop) > >> >> >>FATAL: Could not checkout null with start point > >> >> >>905f8a551b58cf92b40ef194b0578412ed37f266 > >> >> >>hudson.plugins.git.GitException: Could not checkout null with > >> >> >>start point > >> >> >>905f8a551b58cf92b40ef194b0578412ed37f266 > >> >> >> at > >> >> >>org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(C > >> >> >>liGit > >> >> >>A > >> >> >>PII > >> >> >>mpl > >> >> >>.java:878) > >> >> >> at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1229) > >> >> >> at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1205) > >> >> >> at > >>hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) > >> >> >> at hudson.remoting.UserRequest.perform(UserRequest.java:118) > >> >> >> at hudson.remoting.UserRequest.perform(UserRequest.java:48) > >> >> >> at hudson.remoting.Request$2.run(Request.java:326) > >> >> >> at > >> >> >>hudson.remoting.InterceptingExecutorService$1.call(Interceptin > >> >> >>gExec > >> >> >>u > >> >> >>tor > >> >> >>Ser > >> >> >>vice.java:72) > >> >> >> at > >> >> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:30 > >> >> 3) > >> >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138) > >> >> >> at > >> >> >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadP > >> >> >>oolEx > >> >> >>e > >> >> >>cutor > >> >> >>. > >> >> >>java:885) > >> >> >> at > >> >> >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE > >> >> >>xecut > >> >> >>o > >> >> >>r.j > >> >> >>ava > >> >> >>:907) > >> >> >> at hudson.remoting.Engine$1$1.run(Engine.java:58) > >> >> >> at java.lang.Thread.run(Thread.java:619) > >> >> >>Caused by: hudson.plugins.git.GitException: Command > >> >> >>"C:\Program Files (x86)\Git\bin\git.exe checkout -f > >> >> >>905f8a551b58cf92b40ef194b0578412ed37f266" returned status code 1: > >> >> >>stdout: > >> >> >>stderr: error: unable to create file mustella/jenkins.sh > >> >> >>(Permission > >> >> >>denied) > >> >> >> > >> >> >>What's going on? Should wiping out the workspace clear the > >> >> >>error or should I kill a pending process somewhere ? > >> >> >> > >> >> >>Maurice > >> >> >> > >> >> >>-----Message d'origine----- > >> >> >>De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi > >> >> >>3 décembre > >> >> >>2013 07:55 À : dev@flex.apache.org Objet : Re: Updating > >> >> >>Mustella jenkins VM > >> >> >> > >> >> >>Email account info is now on private@ > >> >> >> > >> >> >>EdB > >> >> >> > >> >> >> > >> >> >> > >> >> >>On Tue, Dec 3, 2013 at 12:28 AM, Maurice Amsellem > >> >> >><maurice.amsel...@systar.com> wrote: > >> >> >>> Hi, > >> >> >>> > >> >> >>> I would like to activate Email-ext plugin on Mustella Jenkins VM. > >> >> >>> This would allow us receiving more informed build reports > >> >> >>>notifications (such as build log in zip files). > >> >> >>> > >> >> >>> No objection ? > >> >> >>> > >> >> >>> PS: I will need the SMTP password to configure Email-ext. > >> >> >>> > >> >> >>> Regards > >> >> >>> > >> >> >>> Maurice Amsellem > >> >> >>> SYSTAR R&D - BusinessBridgeFX > >> >> >>> > >> >> >> > >> >> >> > >> >> >> > >> >> >>-- > >> >> >>Ix Multimedia Software > >> >> >> > >> >> >>Jan Luykenstraat 27 > >> >> >>3521 VB Utrecht > >> >> >> > >> >> >>T. 06-51952295 > >> >> >>I. www.ixsoftware.nl > >> >> > > >> >> > >> >> > >> > >> > >
