Improved build log page for issue 2622

[nguyenhung15913]

Issue This PR Addresses

fixes #2622

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

• Made the message more clear if there is no current or previous build
• Displaying the previous build if there is one and there is no current build

Screenshot

• No current or previous build
  
• No current build but there is a previous build
  
• If there is a current build
  

How to test locally

From the root directory

• Fetch these links https://dev.telescope.cdot.systems/deploy/status or https://telescope.cdot.systems/deploy/status instead of autodeploymentUrl('status') in thecheckBuildStatus() in src/api/status/public/js/build-log/api.js
• Copy the chosen link above to the array of connectSrc in src\api\status\src\server.js so that it won't have error related to CSP
• cd ./src/api/status and pnpm run dev. Then go to http://localhost:1111/v1/status/build.

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
• 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)

[gitpod-io]

[humphd]

I'm reworking this code in #2653 too, so we can take this and I can incorporate it into mine.

[DukeManh]

I think this and #2665 will be improved in @humphd's PR.

[TDDR]

Just needs a rebase and you are good to merge

[nguyenhung15913]

Hi everyone, I just pressed the "update branch" something and it create this commit "23b0064", "Merge branch 'master' into issue-2622". is there any issue with it ? @humphd @DukeManh @TDDR

[humphd]

@nguyenhung15913 correct, we don't want to do this. It creates a new merge commit, merging master into your branch. We never want to do this. We want to merge your branch into master. To do this, we prefer rebasing and squashing.

[humphd]

See https://github.com/Seneca-CDOT/telescope/blob/master/docs/git-workflow.md#squashing-commits

[nguyenhung15913]

@nguyenhung15913 correct, we don't want to do this. It creates a new merge commit, merging master into your branch. We never want to do this. We want to merge your branch into master. To do this, we prefer rebasing and squashing.

So now I have to revert the commit and rebase right ?

[humphd]

If you rebase, it should get rid of the merge commit. But yes, you could also revert and then rebase.

[nguyenhung15913]

awesome

[humphd]

Nice job