Home
Contribute Contact Us Browse all meetings
Home Contribute Contact Us Browse all meetings
GitLab / Feature Walkthroughs / 16 Mar 2020
GitLab / Feature Walkthroughs / 16 Mar 2020
Previous Meeting Next Meeting
⏯
Add meeting Rate page Subscribe
youtube image
►
From YouTube: Set dynamic environment URLs after a job finished

Description

https://gitlab.com/gitlab-org/gitlab/issues/17066
https://docs.gitlab.com/ee/ci/environments.html#example-of-setting-dynamic-environment-urls

A

Hi, everyone I'm a back-end, a engineer and gives laughs today, I'd like to introduce you our cool future. It's included in love. 2.9.

A

This feature is about set dynamic environment URLs after job finished, so that today's problem is that when you create a Raby app when you set up regular blood flow in your pipeline today, you can only set static URLs to the environment URL, but sometimes it's problematic when you deploy to samir cloud hosting service such as AWS, which generates random URL and the returns run wll to the JavaScript.

A

You have no idea how to set that dynamically created the URL to get love this issues about to resolve this problem.

A

So, let's take a look there demo.

A

Now, let's take a look at this killer mo file. This is our pipeline. There are two jobs: one is Revie job which it deploys a new review app and it's that regular job, which starts a running graveyard.

A

Now, let's take a look look at the rebel job. This is very traditional specification. You set up environment name as review / branch name in the you ll is here the static part, HTTP development branch name, calm a non-stop sophistication, but today you can do differently. So, for example, you get a dynamic, dynamic, dynamic link in JavaScript. In the JavaScript example,.

A

Url.

A

Here this lying, let's say you.

A

You execute people on the script here and diplomate script in the shell, it returns the run WOL and we set it as a environment, ul local environment, you ll a local environment variable and we export this variable trivia. According to.

A

Dot M file deploy and you can specify any dot, add file name in this case. We name it as deployed at M file and the next step is you actually have to specify this dot M file as artifact, so adverts.

A

Reports that I'm and the dis purpose.

A

This means that.

A

Runners is going to fetch this diploid M file and then report it back to gillip, so you love parties, environment, lists and then projects into the database and then, lastly, we change this line. Since we have this dynamically generated, you are in this variable. We can just set this dynamic, amber, yellow, as is ok, let's commit this change.

A

Now we create a module request.

A

Whatever module requests future.

A

Okay, now the pipeline has started and it's currently running Rippy Rippy job and it's just finished. Let's reload this page and then the latest pipeline has finished a diplomatic job. You can see that deployed to review / brush name, and this is deployed- and here you see that beer this actually points to a varmint ulo which we just set.

A

Let's take a look this since I haven't set up actual review app environment. It shows as the set can be reached, but let's take a look. This URL it's indicates its point to the exact URL we specified in biloxi mo file.

A

Yes, sir. Yes, that part and then here say, say a much reduced iid in this case, 5 five. It said yes, so.

A

This picture lets you set that environment you ll dynamically, even if the URL is generated during a JavaScript, you can get that you can expose it as Caleb environment.

A

Six.