Deployment detail page with the full log

Open
  • Is something wrong?
#265 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, typescript
Domain
devops, full-stack

Research direction

Start with the design preview for Screen 15 and trace the deployment detail page in the web UI and control plane. Check the dependencies M3.3 and M6.1 before starting. Done means one deployment shows per-step timings and a live build and release log that remains readable afterward, with secrets excluded.

Written by the indexing model from the issue text.

Description

priority:P1 task track:control-plane track:web
Track

C: control plane, W: web UI

Scope
  • Screen 15 of the design (preview): per-step timings and the build and release log of one deployment, streamed while it runs.
Acceptance criteria

A running deployment's log appears live and stays readable afterwards; secrets never appear in it.

Depends on

M3.3, M6.1

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.