13:00:10 <bh526r> #startmeeting Weekly Technical Discussion
13:00:10 <collabot`> Meeting started Mon Jul  1 13:00:10 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:10 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:10 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
13:00:22 <bh526r> #topic Roll Call
13:00:36 <bh526r> #info Bin Hu
13:01:16 <bh526r> #info Mark Shostak
13:01:37 <bh526r> #info Daniel Balsiger
13:01:56 <mbuil> #info Manuel Buil
13:02:15 <bh526r> #info Al Morton
13:03:55 <bh526r> #info Trevor Cooper
13:04:47 <bh526r> #topic Infrastructure Evolution (GitHub and CircleCI etc.)
13:06:40 <acmacm> #info Al Morton
13:06:55 <trevor_intel> #info Trevor Cooper
13:13:45 <bh526r> #info Georg Kunz
13:14:42 <bh526r> #info Yang Guangzhi
13:39:12 <bh526r> #info Trevor asked if we are mandating every project to use CircleCI
13:40:10 <bh526r> #info Bin responded that it is still at experimental stage. It would be too radical if we mandate every project to use CircleCI.
13:42:41 <bh526r> #info Although TAC has recommended and TSC agreed to move to it in long term, we are still experimenting it. So we encourage project to start to try, get experience, and pass through learning curve. But it is premature to mandate every project to use it.
13:43:21 <bh526r> #info Trevor further asked if everyone has known the benefit of moving to CircleCI.
13:44:36 <bh526r> #info Bin said that he believed not everyone has realized the benefits. Once he and Alec (NFVBench) have gained enough experience, he and Alec will prepare a presentation for it.
13:45:16 <bh526r> #info Today's expert Ed doesn't have time for presentation, but would be happy to help for any technical question and challenge.
13:45:42 <bh526r> #info He encourages everyone to just do it, just play with it.
13:46:10 <bh526r> #info Bin also indicated that from his limited experience, he sees 2 benefits:
13:49:05 <bh526r> #info (1) Control at project's hand. Configuration of CI is done at .circleci/config.yml in project's repo (client side). So project totally controls its configuration (compared to jjb on server side in Jenkins). Then project's CI configuration only relies on project itself instead of releng resources on server side. The challenge of insufficient releng resources is thus mitigated.
13:50:34 <bh526r> #info (2) When we pay for CircleCI, we will get professional service, and theoretically it will be more responsive, and support us 24x7 regardless of our time zones.
13:51:20 <bh526r> #info Manuel asked if we need a lfntac account for experimenting
13:52:57 <bh526r> #info Bin answered that it is not necessary. At the beginning he thought we needed. Then it turned out that he can logged in CircleCI with his Github account, and set up projects for any repo he has under his personal account of Github.
13:53:40 <bh526r> #info So for experimental purpose, he can use personal Github account, and free for Github and CircleCI. Of course, the support is very limited.
13:54:40 <bh526r> #info Once we decide to move to Github and CircleCI officially, we will use enterprise account and pay for it. Then we will get professional service because we pay for it.
13:55:29 <bh526r> #info Manuel also asked if we can see debug information
13:56:25 <bh526r> #info Bin said yes. Bin shared his screen and showed the group the console output of error information from one of the failed build in his setup
13:57:45 <bh526r> #info Bin also showed the simplest .circleci/config.yml for his IPv6 project (but Gulon code), and a more comprehensive .circleci/config.yml of VPP project that uses C code.
13:58:18 <bh526r> #info No further question
13:58:34 <bh526r> #topic AOB
13:58:49 <bh526r> #info No other topic. Meeting adjourned
13:58:53 <bh526r> #endmeeting