From the course: Software Design: From Requirements to Release
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Solution: From dev to deploy
From the course: Software Design: From Requirements to Release
Solution: From dev to deploy
(upbeat music) - [Instructor] In this challenge you were to print the number of nutrients in database. So for that I have added this one more statement, printing the size of the nutrient map. And to test it out, I go back to my local host and refresh, you can see, it is printing the number of nutrients. Now I need to push this change to Git, so for that I go to Git staging, you can see it is showing up as unstaged, so I stage it, you can also see that I'm adding it to a branch 02-09, just so that I can keep it separate, I will add the comment 02-09e, you'll see it changed. Then I commit and push, next, and it is done. Now Jenkins is going to pull the code from master, which means the branch needs to be merged to the master, so that Jenkins can pull the changes. For that I'll go to my command line and I am in my Git folder, so I'll say Git, checkout master, Git pull origin master. Then I'll say Git merge 02-09e and…
Contents
-
-
-
Define problem and vision statements4m 58s
-
(Locked)
Elicit and specify requirements5m 51s
-
(Locked)
Requirement validation6m 31s
-
(Locked)
Technology validation7m 45s
-
(Locked)
Proof of concept (POC) setup5m 28s
-
(Locked)
POC implementation8m 29s
-
(Locked)
POC deployment7m 16s
-
(Locked)
Challenge: From dev to deploy31s
-
(Locked)
Solution: From dev to deploy2m 4s
-
-
-
-