GitLab 12.4 Release Kickoff, 13 Sep 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Ecosystem 12.4 Kickoff

Description

Slides: https://docs.google.com/presentation/d/1ZRbIymvtg8cLC35TbuMV7TPtpUwSOcjIZGfRsgSy0Bc/edit?usp=sharing

Ecosystem Direction: https://about.gitlab.com/direction/ecosystem/

12.4 Issues: https://bit.ly/2m8tksO

Ecosystem board: https://bit.ly/2m5Cjej

Questions? Comments? Send thoughts to pdeuley@gitlab.com or mention me on GitLab.com using @deuley

A

Hi I'm Patrick Dooley I'm, the Senior Product Manager for the gitlab ecosystem group for the 12.4 kickoff I, wanted to take a few minutes to talk about what ecosystem will be doing. The new team members that we have on the ecosystem team and then what we'll be working on for the 12.4 kickoff.

A

Ecosystem is going to be supporting our integrations with third party systems and our API is and SDKs. So today our priorities are going to be around the integrations that enable customers who are looking to operate get lab at large scale. So these are primarily enterprise customers who are looking to integrate with JIRA and Jenkins, but those integrations will also cover things, like slack will be responsible for the internal development and maintenance of those integrations and the expansion into new integrations over time.

A

We're also going to be responsible for the API and SDK development, so will be the primary maintainer, x' and developers of the gitlab ap is the get lab, client, libraries and the overall developer experience.

A

We really want developers who are looking to build on top of get lab to have an incredible developer experience. So it's really easy for you to just dive in and start coding. You can learn more about where we're headed on the git lab website under direction. Ecosystem I'll leave a link in the comment below so we've got a new team. I just started a couple months ago and Nick when and our Toro Herrero started last week on September 2nd.

A

We've also got a shared researcher for the with the rest of the enablement stage, Eileen and then coming soon. We've got a front-end engineer, starting at the end of the month, back in engineer in November, and then we have an opening for a product designer that'll come up in November. If you have any candidates that you think would be a great fit for this team, please send them my way. It'd be greatly appreciated.

A

So let's talk about 12 for so for twelve four we've got five issues that we've pulled out for Arturo and Nick to start working on so the first one we're going to talk about is G or integrations, not transitioning correctly from merge request. So you can see in this example that Ryan here has created the M. R has been accepted, it was merged and it says that it closes en nine there. But if you go over to JIRA it hasn't successfully closed, so we need to go trap down.

A

What's causing that and go figure that out.

A

We've also got wrong, merge, request, title after created from proposal, so that's referring to when you hit create merge request. It should grab the task in JIRA, which should look like this, the all-caps number and instead it's creating it with lower case and no.

A

There is a broken favicon when you use a relative URL and what that means is, if you have it set up. So it's your your get lab instance is something comm slash get lab. So if you do that, it doesn't correctly set up the URL for the favicon and it looks like it's adding an extra slash gitlab in there. So if you look at the example URL that they've they've provided here, it's got these two get labs instead of only one get lab, so we need to go track that one down.

A

Russell Dickinson who's, an awesome tech writer is working on updating some outdated juror configuration info linking to your projects with keys. That start with a number doesn't work. So this is pretty straightforward. If you've got a project, that's got a key. That's ABC works fine. If your key is instead one two three, it does not work. Fine, our.

A

We have a regular expression. That is testing for the key name and it doesn't seem to be picking up key names, starting with numbers correctly and then finally, merge request process breaks if an integration endpoint is unreachable, that's pretty straightforward! If the. If the integration endpoint is unreachable, it looks like the JIRA product. The JIRA project service does not catch the error correctly. If it's unable to hit that.

A

So that's it for 12:4. If you have any any questions, any feedback, please contact me directly at p. Dually Atget lab comm and you can always hit me up at Dooley on any issues on get lab. Comm, please mention me so I can take a look at things and if you create any new issues- or you see an issue- that's already there that needs our attention, please make sure to label them as group ecosystem, so they show up on our board thanks a lot have a great day.