Microsoft 365 Community Community Demos, 21 Mar 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Community demo - DevOps pipelines: Speeding up SPFx solutions packaging by using parallel jobs

Description

This community call demo is taken from the SharePoint General Development Special Interest Group recording on 21st of March 2019.

In this video Velin Georgiev (Pramerica) shows how to speed up SharePoint Framework solution packaging by using parallel jobs.

Presenter - Velin Georgiev (Pramerica) - @VelinGeorgiev

Full details on the community call from https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-dev-community-pnp-general-sp-dev-sig-recording-21st-of-march-2019/

More details on the SharePoint dev community calls from http://aka.ms/sppnp.

A

B

Name is Lorena our SharePoint developer for a very competent, a DML via devil's eyes. Don't try to speed up our build by using a parallel jobs, evasion DevOps. So this is like follow-up on a previous session. So it's not basics. If you want to go from the very beginning, you should visit those URLs, because today we're not covering any basics and.

B

Packages and those packages are all from the source control everything.

B

If you go here, you see that I'm building two separate.

B

I'm doing those two packages in sequence, so after wait a minute 30 23 seconds here so in here over sell all the packages were be able to build the first solution and then have to wait another minute here and all this can be done in parallel. So we don't have to wait all that execution because in case with ten different solution that might take forever. So we have.

B

Like here, I will just open that one to show you how it looks. Basically, we might have three jobs, basically, in parallel and in the tasks.

B

My dramatically speed your milk I'll just do a quick change and I'll try to raise swinging vs. wings because pretty swimming faster in Windows. There was a discussion so today our objects ways those two.

B

And we'll see how this is running and all these swinging I'll also show you how I build up like what we're waiting previously a previous session. That's my.

B

In my previous session, I'll show you how to build it in the sequence and basically you have tasks tasks one after the other, so screed tasks and everything is top to bottom task after task and that's instituted in the sequence. Now, the difference with ABI is a little bit different syntax, where you split the tasks into different groups and on top of those these in different groups, you have just gelled and after the jobs you have that specific job.

B

Underneath you decide what will be your compute virtual machine to do the work, and then you have your task, stop work here and then you have another job to do the other parallel the parallel job. You have tasks there, so they would run at the same time, probably they've already started back to go back to my field and see what's happening, so the build is running and those are running in parallel. So, as you can see, the relief scripts is already done because all I'm doing here with my basket, she likes good money.

B

So that is a very quick thing, but those two now are racing. They start at homes at the same time, and one is using window. The other is using Linux. Let's see what is happening here, we are on an install phase that what is also being in this or face so after these are done.

B

The built will will just create.

B

The two one will be just different packages: okay,.

B

Yeah, so all these the whole definition is in the sample library, so you can grab those and see what is the difference between the jobs running in parallel and running in a sequence you can test it by yourself, because how amusing is I'm using the free tier implementation between get up and use your pipelines. So all that can be test that you just have to find yourself here.

B

Okay, so the jobs completed almost.

B

So we're bundling the packages now that should be dying a few seconds, as you can see the second one complete it so since that the room, the hosted machines can play the faster in the windows, hosted machines and we're seeing waiting the the bubble and the build process here. So we can compare the time he sees like took one minute 49 seconds you could you can put your handsome older years.

A

B

But like come on, meet at 94 for the Windows machine and in two minutes, 18 machine now disclaimer because we're losing the host machine.

A

Version we still support honest.

C

So right now we use to what I was going to say, though, is so. There is a tool rush that we produce. That is effectively specifically for this. It will spider through a large repository notoya packages. Well, it will manage all the no volume references to have only a single set for the entire solution.

C

Total we use for our build tool. That's well lift with other people use how it works. Well, with this.

C

A

C

Chances are it's just removing the checklist, they say what person are using, but wanna make sure that there's no gotcha somewhere in the build tools that.