1
00:00:02,650 --> 00:00:07,580
In this short lecture, we're going to have a look at pipelining, triggers, how we can retry failed

2
00:00:07,630 --> 00:00:11,020
jobs and now we can start the pipeline without making a comment.

3
00:00:13,980 --> 00:00:20,340
Now, it may happen that your pipeline fails for no apparent reason, and especially if the job that

4
00:00:20,340 --> 00:00:25,440
failed is really like the last one or one of the last jobs and the previous one really took a long time

5
00:00:25,440 --> 00:00:28,800
to execute, it might be worth retrying jobs.

6
00:00:29,220 --> 00:00:35,310
So in order to do that, you can simply click on this button on retrial and Giddyap will retry the job

7
00:00:35,310 --> 00:00:35,630
for you.

8
00:00:35,640 --> 00:00:39,330
And if it's successful, then the entire pipeline would be marked as successful.

9
00:00:40,450 --> 00:00:46,270
The same goes for pipelines, if the entire pipeline failed, you can simply click on retry and it will

10
00:00:46,270 --> 00:00:52,000
restart to the same pipeline with the same code that has been executed there and tried to rebuild it

11
00:00:52,000 --> 00:00:52,330
again.

12
00:00:53,300 --> 00:00:59,470
Sometimes temporary problems do occur and simply retrying the pipeline or retrying a job is a good way

13
00:00:59,470 --> 00:00:59,910
to do it.

14
00:01:02,310 --> 00:01:08,940
On other occasions, it might be just necessary to start a pipeline without actually making changes

15
00:01:08,940 --> 00:01:15,210
to your code, and one way to do it is to simply manually click on one pipeline.

16
00:01:16,610 --> 00:01:20,600
And this will open this interface, you have the possibility of selecting for which branch would like

17
00:01:20,600 --> 00:01:21,470
to run the pipeline.

18
00:01:22,130 --> 00:01:27,020
If there are any variables, you can simply input some data and click on one pipeline, and that would

19
00:01:27,020 --> 00:01:28,130
be good as well.

20
00:01:29,240 --> 00:01:34,130
It may also happen that you want to run your pipelines based on a schedule.

21
00:01:34,970 --> 00:01:40,250
So let's say you're not constantly working on a project, but you still want to make sure that whatever

22
00:01:40,250 --> 00:01:44,420
you're doing here, all the dependencies that you have, they are still properly working.

23
00:01:44,900 --> 00:01:48,440
And maybe you want to build them daily or you might to build them once a week.

24
00:01:48,770 --> 00:01:50,000
That's totally your decision.

25
00:01:50,360 --> 00:01:53,440
And there's the possibility of doing that from Gitlow.

26
00:01:53,480 --> 00:01:57,290
And this is being configured here under SkyCity schedules.

27
00:02:00,680 --> 00:02:03,200
So here you have the possibility of creating a schedule.

28
00:02:05,980 --> 00:02:08,229
Let's say that we want to run this pipeline daily.

29
00:02:11,650 --> 00:02:18,940
You can run it every day at 4:00 a.m. and you can even define your own currency index if this is something

30
00:02:18,940 --> 00:02:25,450
that you like, but I have just used one of the predefined options that are available here tend to select

31
00:02:25,450 --> 00:02:29,950
the branch, specify any variables if that's needed, and simply save the pipeline.

32
00:02:32,590 --> 00:02:38,650
Now, you can wait for this pipeline to run, but if you want to simply trigger it manually, you can

33
00:02:38,650 --> 00:02:39,730
do it from here as well.

34
00:02:43,250 --> 00:02:44,090
So that's about it.

35
00:02:44,120 --> 00:02:48,600
These are different ways on how we can run your pipeline in catalepsy.