flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Updating Mustella jenkins VM
Date Tue, 03 Dec 2013 23:30:20 GMT
Doh!  Nevermind, the replies won't have the attachments.

Ok, I think we'll be ok for a while, but I will find the spam server
notices to very annoying.

Thanks for doing it,

On 12/3/13 3:24 PM, "Alex Harui" <aharui@adobe.com> wrote:

>I could be wrong, but I believe the first notification goes to commits@
>but if we reply to that to discuss it, it goes to dev@ as well.
>On 12/3/13 3:21 PM, "Maurice Amsellem" <maurice.amsellem@systar.com>
>>>We already have a problem with folks wanting to unsubscribe.
>>unsubscribe from the commits ML ?
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com]
>>Envoyé : mercredi 4 décembre 2013 00:16
>>À : dev@flex.apache.org
>>Objet : Re: Updating Mustella jenkins VM
>>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.
>>On 12/3/13 3:04 PM, "Maurice Amsellem" <maurice.amsellem@systar.com>
>>>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.
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@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.
>>>On 12/3/13 2:50 PM, "Maurice Amsellem" <maurice.amsellem@systar.com>
>>>>It seems that the error below has disappeared (probably a ghost
>>>>process that ended).
>>>>- 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.
>>>>-----Message d'origine-----
>>>>De : Maurice Amsellem [mailto:maurice.amsellem@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
>>>>Commencing build of Revision 905f8a551b58cf92b40ef194b0578412ed37f266
>>>>(origin/develop) Checking out Revision
>>>>905f8a551b58cf92b40ef194b0578412ed37f266 (origin/develop)
>>>>FATAL: Could not checkout null with start point
>>>>hudson.plugins.git.GitException: Could not checkout null with start
>>>>	at
>>>>	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
>>>>	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>	at
>>>>	at
>>>>	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:
>>>>stderr: error: unable to create file mustella/jenkins.sh (Permission
>>>>What's going on?  Should wiping out the workspace clear the error or
>>>>should I kill a pending process somewhere ?
>>>>-----Message d'origine-----
>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 3
>>>>2013 07:55 À : dev@flex.apache.org Objet : Re: Updating Mustella
>>>>jenkins VM
>>>>Email account info is now on private@
>>>>On Tue, Dec 3, 2013 at 12:28 AM, Maurice Amsellem
>>>><maurice.amsellem@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

View raw message