Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-ocl.dev] Eclipse OCL 3.1.0 RC3

Hi Adolfo

I think my commit of OCLinEcore documentation may have been just after your
build,
so it might be worth another try at an unsigned build, and then downloading
the
Update site from the Workspace for a quick documentation check.

	Regards

		Ed  

> -----Original Message-----
> From: mdt-ocl.dev-bounces@xxxxxxxxxxx 
> [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Adolfo 
> Sánchez-Barbudo Herrera
> Sent: 31 May 2011 13:22
> To: mdt-ocl.dev@xxxxxxxxxxx
> Subject: Re: [mdt-ocl.dev] Eclipse OCL 3.1.0 RC3
> 
> Hi All,
> 
> Just for you information. I'm pending on the following bugzilla 
> resolution to make our RC3 build:
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=347744
> 
> In the last build I did some hours ago, the console shows 
> that all the 
> process prior to the signing step looks free of errors...
> 
> Best Regards,
> Adolfo.
> 
> El 31/05/2011 6:37, Ed Willink escribió:
> > Hi Adolfo
> >
> > Orbit now has an R20110523182458 (as well as an S20110523182458). 
> > Changing our builds to R made no difference.
> >
> > I think the missing parameters means than none of the platform 
> > build.type guards in ocl-platform.rmap pass, so no platform.
> >
> > Looking at the Xtext parameters, they don't look too hard to clone; 
> > only the reference repository looks harder.
> >
> > (They have a "sign" parameter which could save time on N-builds.)
> >
> > (There is also a Publish Javadoc config: is this the 'same' as our 
> > 'MANAGE_JAVADOC")
> >
> > I'll leave it to you.
> >
> >      Ed
> >
> > On 31/05/2011 06:08, Ed Willink wrote:
> >> Hi Adolfo
> >>
> >> My start ability was back so I tried a build; it went 
> straight off; 
> >> indeed no job parameterization. Failed on an Orbit access. 
> I'll see 
> >> what's missing.
> >>
> >> 80% of recent jobs have failed, glancing at a couple suggests file 
> >> permission issues.
> >>
> >> I suspect Denis is busy; strangely no further update message.
> >>
> >>     Ed
> >>
> >> On 31/05/2011 00:40, Adolfo Sanchez Barbudo wrote:
> >>> Ed,
> >>>
> >>> I've realized that there is missing info in the job's 
> >>> configuration... among other things, users' access, which was the 
> >>> cause why we weren't able to run the job... The job 
> parameters are 
> >>> also missed...
> >>>
> >>> I hope to fix the issue tomorrow's morning... Perhaps, we should 
> >>> also warn Denis and/or cross project mail list about the issue...
> >>>
> >>> Best Regards,
> >>> Adolfo.
> >>>
> >>> 2011/5/30 Adolfo Sanchez Barbudo <adolfosbh@xxxxxxxxxxxxxxxx 
> >>> <mailto:adolfosbh@xxxxxxxxxxxxxxxx>>
> >>>
> >>>     Ed,
> >>>
> >>>     Ok. I still have no access to run hudson job's... Let's try to
> >>>     do the RC3 tomorrow.
> >>>
> >>>
> >>>     Regards,
> >>>     Adolfo.
> >>>
> >>>     2011/5/30 Ed Willink <ed@xxxxxxxxxxxxx 
> <mailto:ed@xxxxxxxxxxxxx>>
> >>>
> >>>         Hi Adolfo
> >>>
> >>>         The queue of 30 jobs has cleared now that slave1 is back,
> >>>         but all but two failed quickly; remote channel issue.
> >>>
> >>>         I too have no start job access. I suspect this may be a
> >>>         deliberate control measure by the Hudson admins; 
> why let us
> >>>         start what cannot finish?
> >>>
> >>>         I guess they're too busy fixing things to keep us fully in
> >>>         the loop.
> >>>
> >>>         I'll announce a late RC3 unless you have other ideas by
> >>>         22:30 (15 minutes time).
> >>>
> >>>             Regards
> >>>
> >>>                 Ed
> >>>
> >>>
> >>>         On 30/05/2011 21:30, Adolfo Sanchez Barbudo wrote:
> >>>>         Another possibility:
> >>>>
> >>>>         - Wait 1 hour/ 2 hours... If the things still remain as
> >>>>         they are now... then do the announce... and try tomorrow
> >>>>
> >>>>         I'm going to prepare the dinner... I'll be back 
> in an hour,
> >>>>
> >>>>         Regards,
> >>>>         Adolfo.
> >>>>
> >>>>         2011/5/30 Adolfo Sanchez Barbudo
> >>>>         <adolfosbh@xxxxxxxxxxxxxxxx
> >>>>         <mailto:adolfosbh@xxxxxxxxxxxxxxxx>>
> >>>>
> >>>>             Ed,
> >>>>
> >>>>             The point is that I CAN'T START a job. So I can't do
> >>>>             anything right now... I'd definitely wait 
> until servers
> >>>>             are stable. If the servers are stable, perhaps the
> >>>>             current state of project can successfully be built...
> >>>>
> >>>>             My opinion is:
> >>>>
> >>>>             1. Announce the delay Eclipse OCL RC3 until 
> tomorrow's
> >>>>             morning.
> >>>>             2. Try to run an S-build in the morning:
> >>>>                  a) If we can't run builds yet  => raise 
> a bugzilla
> >>>>             to Eclipse Hudson.
> >>>>                  b) If we can, we could take a decision depending
> >>>>             of the result of the built.
> >>>>
> >>>>             What do you think ?
> >>>>
> >>>>
> >>>>             Regards,
> >>>>             Adolfo.
> >>>>
> >>>>             2011/5/30 Ed Willink <ed@xxxxxxxxxxxxx
> >>>>             <mailto:ed@xxxxxxxxxxxxx>>
> >>>>
> >>>>                 Hi Adolfo
> >>>>
> >>>>                 The Download for docbook zips failed while I
> >>>>                 watched. So it's failed now.
> >>>>
> >>>>                 It seems that with limited network connectivity,
> >>>>                 the download may be a problem.
> >>>>
> >>>>                 Option 1:
> >>>>
> >>>>                 revert the documentation to the 
> non-auto-generated
> >>>>                 form.
> >>>>                 will probably need a retry, so realistically 3
> >>>>                 builds through a massive
> >>>>                 slow Hudson queue.
> >>>>
> >>>>                 Option 2:
> >>>>
> >>>>                 manually do the zip downloads so that they don't
> >>>>                 need a get each build
> >>>>
> >>>>                 Option 3:
> >>>>
> >>>>                 notify cross-project-issues that RC3 
> will be late.
> >>>>                 - the only changes are examples and doc (? and
> >>>>                 source bundles)
> >>>>                 -- very unlikely to affect other 
> projects: they can
> >>>>                 use RC2
> >>>>                 - hopefully connectivity will be back 
> within 24 hours
> >>>>
> >>>>                 I favour starting on 3, and see how 
> David Williams
> >>>>                 reacts. I'm sure other projects will stretch too.
> >>>>
> >>>>                     Regards
> >>>>
> >>>>                         Ed
> >>>>
> >>>>
> >>>>                 On 30/05/2011 21:08, Adolfo Sanchez 
> Barbudo wrote:
> >>>>>                 I did the change to the master... it's 
> not really
> >>>>>                 worthy since it is an N build... the 
> point is that
> >>>>>                 now I can't either stop the running job 
> nor start
> >>>>>                 a new one .... :\
> >>>>>
> >>>>>                 Let me know you are able...
> >>>>>
> >>>>>                 Regards,
> >>>>>                 Adolfo.
> >>>>>
> >>>>>
> >>>>>                 2011/5/30 Ed Willink <ed@xxxxxxxxxxxxx
> >>>>>                 <mailto:ed@xxxxxxxxxxxxx>>
> >>>>>
> >>>>>                     Hi Adolfo
> >>>>>
> >>>>>
> >>>>>                         It's now back but slave1 is 
> offline. A job
> >>>>>                         is waiting.
> >>>>>
> >>>>>                     It looks like slave1 has been re-routed to
> >>>>>                     master. Is it even worth letting it run?
> >>>>>
> >>>>>                        Regards
> >>>>>
> >>>>>                            Ed
> >>>>>
> >>>>>
> >>>>>
> >>>>>                     
> _______________________________________________
> >>>>>                     mdt-ocl.dev mailing list
> >>>>>                     mdt-ocl.dev@xxxxxxxxxxx
> >>>>>                     <mailto:mdt-ocl.dev@xxxxxxxxxxx>
> >>>>>                     
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>>>>
> >>>>>
> >>>>>
> >>>>>                 _______________________________________________
> >>>>>                 mdt-ocl.dev mailing list
> >>>>>                 mdt-ocl.dev@xxxxxxxxxxx  
> <mailto:mdt-ocl.dev@xxxxxxxxxxx>
> >>>>>                 
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>>>>
> >>>>>
> >>>>>                 No virus found in this message.
> >>>>>                 Checked by AVG - www.avg.com 
> <http://www.avg.com>
> >>>>>                 Version: 10.0.1375 / Virus Database: 1509/3669 -
> >>>>>                 Release Date: 05/30/11
> >>>>>
> >>>>
> >>>>
> >>>>                 _______________________________________________
> >>>>                 mdt-ocl.dev mailing list
> >>>>                 mdt-ocl.dev@xxxxxxxxxxx
> >>>>                 <mailto:mdt-ocl.dev@xxxxxxxxxxx>
> >>>>                 
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>         _______________________________________________
> >>>>         mdt-ocl.dev mailing list
> >>>>         mdt-ocl.dev@xxxxxxxxxxx  <mailto:mdt-ocl.dev@xxxxxxxxxxx>
> >>>>         https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>>>
> >>>>
> >>>>         No virus found in this message.
> >>>>         Checked by AVG - www.avg.com <http://www.avg.com>
> >>>>         Version: 10.0.1375 / Virus Database: 1509/3669 - Release
> >>>>         Date: 05/30/11
> >>>>
> >>>
> >>>
> >>>         _______________________________________________
> >>>         mdt-ocl.dev mailing list
> >>>         mdt-ocl.dev@xxxxxxxxxxx <mailto:mdt-ocl.dev@xxxxxxxxxxx>
> >>>         https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> mdt-ocl.dev mailing list
> >>> mdt-ocl.dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>>
> >>>
> >>> No virus found in this message.
> >>> Checked by AVG - www.avg.com <http://www.avg.com>
> >>> Version: 10.0.1375 / Virus Database: 1509/3669 - Release 
> Date: 05/30/11
> >>>
> >>
> >>
> >> _______________________________________________
> >> mdt-ocl.dev mailing list
> >> mdt-ocl.dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >>
> >>
> >> No virus found in this message.
> >> Checked by AVG - www.avg.com <http://www.avg.com>
> >> Version: 10.0.1375 / Virus Database: 1509/3669 - Release 
> Date: 05/30/11
> >>
> >
> >
> > _______________________________________________
> > mdt-ocl.dev mailing list
> > mdt-ocl.dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> 
> -- 
> Open Canarias, S.L.
> 	*Adolfo Sánchez-Barbudo Herrera*
> adolfosbh(at)opencanarias(dot)com 
> <mailto:adolfosbh%28at%29opencanarias%28dot%29com>
> C/Elías Ramos González, 4, ofc. 304
> 38001 SANTA CRUZ DE TENERIFE
> Tel.: +34 922 240231
> 
> 

Please consider the environment before printing a hard copy of this 
e-mail. 
 
The information contained in this e-mail is confidential. It is intended 
only for the stated addressee(s) and access to it by any other person is 
unauthorised. If you are not an addressee, you must not disclose, copy, 
circulate or in any other way use or rely on the information contained in 
this e-mail. Such unauthorised use may be unlawful. If you have received 
this e-mail in error, please inform us immediately on +44 (0)118 986 8601 
and delete it and all copies from your system. 
 
Thales Research and Technology (UK) Limited. A company registered in 
England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne 
Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 
774298 
 
Thales UK Limited. A company registered in England and Wales. Registered 
Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, 
Weybridge, Surrey KT15 2NX. Registered Number: 868273 



Back to the top