GitLab 13.2 Release Kickoff, 15 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.2 Kickoff - Create:Editor

Description

Board for the GitLab 13.2 Release: https://gitlab.com/groups/gitlab-org/-/boards/1131977?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aeditor&milestone_title=13.2

- Snippets with Multiple Files: https://gitlab.com/groups/gitlab-org/-/epics/2829
- Realtime feedback for editing .gitlab-ci.yml: https://gitlab.com/gitlab-org/gitlab/-/issues/218472
- Example Project: https://gitlab.com/jramsay/monaco-gitlab-ci/-/blob/master/examples/react-webpack/index.jsx
- Schemastore GitLab CI: https://json.schemastore.org/gitlab-ci
- Example contribution to Schemastore GitLab CI: https://github.com/SchemaStore/schemastore/pull/1064

A

Hi, my name is kai armstrong, I'm the product manager for the editor group in the create stage of the devops lifecycle at gitlab, and I'm here to talk about the 13.2 release and what we're going to be working on for that. So uh let me share my screen, really quick and then we'll start jumping through some items.

A

So, first up uh you're seeing the board that we use for planning here uh what you'll notice is a lot of issues that sort of seem like they're, backstage or building up to something, and a lot of that is because what we're going to continue to be working on in 13.2 is multiple file support for snippets.

A

So um if you think back a couple releases in 13.0, we released version control for snippets, and so once we did that the next logical step and the next things we began working on were multiple files, and so um there's an epic I'll link that in the video notes below. But you can come to the epic and take a look, uh there's screenshots of what we expect this to look at, and here's just a couple.

A

So when you're editing a snippet you'll see that you'll be able to place multiple files, there'll be a button to add additional files, and when that gets rendered out, you might see something like this. Where you've got markdown, you know comments or description of what the snippet does or other things like that, and then you'll see uh the multiple files render that below. So we'll be working on that in 13.2 we were working on 13.1.

A

um We expected to take a few more releases to materialize and get to a point where we can start turning bits and pieces of this on or enabling multiple files in certain use cases so stay tuned to the epic and keep an eye on that.

A

The next feature that I want to talk about, which I'm really excited about, is real-time feedback for editing. The gitlab ci aml file inside of the web ide, and so um the gitlab ciemo file is a really important configuration file for using ci with gitlab. It tells the ci runners what to do what jobs to execute. What to what's. You know task and other things need to be executed in each of those jobs. How those results work.

A

It can have build steps, it can have deployment steps, and so all of these things you know the downside is- is that that file is really complicated. It's got a lot of different configuration parameters and you really have to know how each of those different parameters work to make sure that your files, valid and so inside of the web ide we're going to add some linting and kind of real-time feedback capabilities and um if you I'll link this issue down below in the video notes.

A

But if you take a look at it, there's a link to a demo project, and so this demo project's got um a sample. Monaco editor, that'll load up and it actually loads.

A

The schema that we're going to be using from schema store, so schema store, hosts a variety of schemas for a bunch of different services across the board and there's a community contributed gitlab ci schema, so we're gonna start with that, um we'll see if we need to continue building on that or what kind of issues we might run into, but we're gonna start with that as a way to sort of prove the concept and see what users think of this. um So you can click into this project.

A

You can see how we're defining that what's loading and then I actually, I thought a quick demo would be cool, and so um this is a the default template that we have for a go project if you were writing a ci file for that sort of some default things that you might do um and you'll notice that this is perfectly valid.

A

There's nothing interesting in here yet, but if I start typing that you'll see that it sort of gives me the autocomplete that, like stages, is probably what I'm looking for, because I started typing that and I can tab to complete that and then you'll notice that I'm getting these underlying error feedback places. So let me get rid of that line. We'll just take a letter out of here.

A

If we look at this it'll say: oh, it's an incorrect type expected an object, so this will help you, while you're writing these files to either autocomplete the stages or the other settings or configuration parameters that you're looking for and also make sure that you know this file doesn't have any lines in it when you're done editing it.

A

So we're really excited to add this in the web ide, we think it'll be very valuable for getting started with your product or when you're, making those changes to just make sure that you've got that real-time feedback without needing to commit copy and paste it into another validator or see. What's going on there so we're um you know, let us know what you think of this one once we ship this and then I'll just finally show you that the schema store json that we'll be using is here, you can see everything that's defined.

A

You can also go to store.org. Take a look at some of the other json schemas they provide. So, like I said the gitlab ci schema is community, contributed to this project, um we'll look at maybe contributing some additional pieces to it or bringing a version in-house and kind of syncing them back and forth. So that way we have the latest versions, but if you're interested in contributing to this project and making sure that that's up to date, you can also I'll make sure we link that out.

A

So you can see, what's been done in the past, so um we're really excited about gitlab 132. We think um the path to multiple files for snippets is going to be great, and we think this really solid cross stage workflow that we're going to have with editing.

A

You know that gitlab ci file and getting sort of that better editing experience than you would get anywhere else in the gitlab application is going to be really valuable to users. So let us know what you think I'll link all of this below, but thanks for chatting with us today, we'll see.