Hi Mats, I believe Ibrahim was working on this (CC'd). If you have the time to pitch in, I can send you an invite to the sandbox[1] user group so you can test jobs.
Definitely a +1 from me on phasing out 2013 builds. Perhaps this is something we could make as part of the 1.4 release (As in 1.4 being the last release to support vs2013). [1] http://docs.releng.linuxfoundation.org/en/latest/jenkins.html#jenkins-sandbox Regards, Trevor Bramwell On Thu, Apr 19, 2018 at 09:44:36AM -0600, Mats Wichmann wrote: > > Currently, the CI infrastructure provisions three generations of Visual > Studio: 2013, 2015, 2017. Jenkins builds happen against the 2013 and > 2015 versions in both 32-bit and 64-bit mode, which contribute to the > "verified" vote; 2017 exists but is not used. Is there a transition plan > to enable 2017 and phase out 2013 (which feels like it would not be as > useful any longer - of course Microsoft's official public recommendation > is to use VS2017)? If there isn't, should we make such a plan? > > _______________________________________________ > iotivity-dev mailing list > [email protected] > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
signature.asc
Description: PGP signature
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
