Feat/build timestamps and history

[vtz]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@vtz has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 54 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5648a666-9861-40aa-992d-609261e47378

📥 Commits

Reviewing files that changed from the base of the PR and between ccb2c0a and cf45f1e.

📒 Files selected for processing (2)

• cmd/bob/list.go
• internal/buildapi/server.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/build-timestamps-and-history

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

builder-operator/internal/buildapi/server.go

Lines 657 to 661 in 1c1d4d7

	switch s {
	case conditionStatusTrue:
	entry.Phase = string(buildv1alpha1.PhaseSucceeded)
	case conditionStatusFalse:
	entry.Phase = string(buildv1alpha1.PhaseFailed)

Handle terminal Unknown PipelineRun statuses in history

This phase mapping only handles Succeeded=True/False; Tekton also uses Succeeded=Unknown for terminal outcomes such as cancellation/timeout, so those runs fall through as Running and are misreported in bob history even after they have completed. In clusters where users cancel or timeout builds, history will show an incorrect active state for finished runs.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".