Moving current build to prev when a new build is started

[dhillonks]

Issue This PR Addresses

Fixes #2384 (Autodeployment server not remembering previous build info).

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

Assigning the current build to previous in so that the previous build information is not null.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not; N/A for this pr
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[humphd]

@dhillonks you've merged master into your branch, which we don't want. Probably you did a git pull upstream master into your branch? If so, be aware that this will do a fetch and merge.

Let's undo your merge commit like so:

# update your local master branch to what's on the upstream
git checkout master
git pull upstream master

# reset your branch to the commit before you merged
git checkout -B issue-2384-remember-prev-build 0b76fd39ddae5bbba5fc3280c4702d36c0b77416

# rebase onto master, and squash your two commits together
git rebase -i master

# push this updated branch here so we can merge
git push origin issue-2384-remember-prev-build -f

[dhillonks]

@dhillonks you've merged master into your branch, which we don't want. Probably you did a git pull upstream master into your branch? If so, be aware that this will do a fetch and merge.

Let's undo your merge commit like so:

# update your local master branch to what's on the upstream
git checkout master
git pull upstream master

# reset your branch to the commit before you merged
git checkout -B issue-2384-remember-prev-build 0b76fd39ddae5bbba5fc3280c4702d36c0b77416

# rebase onto master, and squash your two commits together
git rebase -i master

# push this updated branch here so we can merge
git push origin issue-2384-remember-prev-build -f

@humphd Yes, that is what I had done before. I didn't realise that it was not needed. However, I have followed the steps highlighted above to rebase and update the branch. Could you please take a look again?

[humphd]

You haven't done it correctly. You have 2 nearly identical commits on this branch, and it's still not rebased onto master.

[dhillonks]

Squashed the commits and rebased it with latest master (wasn't completely in sync in with upstream last time):