Temporary Fix for the deadlink for user guide documentation of setting up jenkins on google cloud

[yashpal2104]

fixes #7589. Fixed the broken link for the tutorial to setup Jenkins on google cloud by inserting a video in place of the deadlink. It can be modified later if someone wants to take the next step of creating text that describes how to use Jenkins on Google Cloud.

[zbynek]

Please make sure the PR contains only the relevant commit(s), in this case just 991929e

Maybe besides the video you could also add a link to https://cloud.google.com/blog/products/gcp/using-jenkins-on-google-compute-engine-for-distributed-builds which contains some text + images from the deleted tutorial.

[yashpal2104]

I don't know why but all the previous commits keep adding on my PR although I created a new branch. Same is happening here #7600 can you like tell me what am I doing wrong?

[krisstern]

Hi @yashpal2104 I think you may have created a new branch based off of a feature branch and not the master branch. To correct this you will need to rebase against the master branch. Also, moving forward you should first switch to the most up-to-date master branch before you create a new feature branch off this.

[krisstern]

If you need help with the steps do let us know.

[yashpal2104]

Oh ok now I understand what my mistake was I will try it myself first if I need some help I will definitely reach out to you. Thank you again for your help

[yashpal2104]

Hey @krisstern can you help me understand the rebase thing you were talking about like what I understand was the commits I make are forwarded again when I do git rebase and after that all the commits are added on top of the other right? also how do I know which one is good 'rebase' or 'merge' -> 'fast forwarding' or 'no-ff'
How do I get my master branch clear of my commits in my local repo and up to date along with the original repo of jenkins' master branch clone

[krisstern]

Duplicated in #7602

[krisstern]

Hi @yashpal2104, by rebasing I meant something like the below steps (note there can be variations based on the setup):

git switch master
git pull origin master
git fetch origin
git switch feature-branch-name
git rebase origin/master

If you do this your feature branch would be rebased to the latest commit of the master branch.

[yashpal2104]

And what if when I git pull origin master what if my origin is where I pushed the wrong changes which is my remote repo wouldn't it then change or say contaminate my master branch, does that happen?
And git fetch origin then fetches all the new updates from the remote repo origin which if it gets contaminated(I don't know if it gets contaminated )when I push from my local branch to my remote repo origin