This video demonstrates how to use a completed pipeline to push a release all the way from QA to production.
- [Narrator] So our code has been deployed to QA, … and our QA team has had a chance to review the site … and they say it looks good. … The heading that we wanted to create is there. … So we're ready to move to the next stage. … We're ready to push our release to staging. … The way to do that is through a merge request. … So I'll open up a new merge request here. … And I want my source branch to be master, … and my target branch to be release. … So I'll click compare branches and continue. … And I'll just call it first release. … I'm going to leave this description blank for now. … And you can see we've got a green check mark here, … because these changes have already passed in QA. … But we also have a merge conflict. … This may or may not happen to you, … but it depends on the way you edited your files … and committed them to the release branch. … So I'm just going to go through it so you can see that process. … So I'll click resolve conflicts, … and I'm going to go to edit in-line. …
- Navigating the GitLab interface
- Using GitLab for collaboration
- Merging requests
- Continuous integration and continuous delivery
- Creating and running a pipeline
- Deploying a project using GitLab
Skill Level Beginner
1. First Steps with GitLab
2. GitLab for Source Control
3. Continuous Integration
4. Continuous Delivery
Next steps1m 57s
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.