Hi Uze, Sorry for not responding to this sooner, as it was the Thanksgiving holiday in the US.
I have updated Jenkins to build master, 1.1-rel, and 1.2-rel twice a day, I believe the timing needs to be modified, but my idea is to have branches verified before the start of work days in each timezone (PST/KST) so any blocking issues can be addressed ASAP. I'll work with Phillipe to address any discrepancies he may find in what needs to be cached on the build server. Regards, Trevor Bramwell On Wed Nov 23 21:02:36 2016, uzchoi at samsung.com wrote: > Two activities we can think about. > > - From the Jenkins we need to trigger the build verification > periodically for released version. (Trevor, Could you help it) > - External library dependency with exact version. It should be done > from 1.2.1 release [https://jira.iotivity.org/browse/IOT-1600] > > BR, Uze Choi > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Thursday, November 24, 2016 2:43 AM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] 1.2.0 build failure > > On ter?a-feira, 22 de novembro de 2016 15:39:54 PST Nivedita Singhvi > wrote: > > * It does not matter if it was working when first released, if 48hrs > > later > > is subsequently breaks with the existing code. And all subsequent > > users are affected going forward, for ever, as you point out, as > > it is > > not removed or replaced. Most projects rev their release when > > something > > like that happens, or provide some mitigation for users. > > Yes, we need an update that fixes it. That's 1.2.1 and it's coming.
