Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build: show build step #102

Open
2 tasks
agjohnson opened this issue Mar 15, 2022 · 2 comments
Open
2 tasks

Build: show build step #102

agjohnson opened this issue Mar 15, 2022 · 2 comments
Labels
Accepted Accepted issue on our roadmap Feature New feature Status: blocked Issue is blocked on another issue

Comments

@agjohnson
Copy link
Contributor

We will have additional build steps soon, for pre/post builds, etc. We may want to show the explicit step names somewhere in the UI.

Two big options here:

  • Show metadata like a label on each build command
  • Group commands by the build step instead of just sequentially listing

Show metadata

Perhaps this is a small label or inverted label on the build command. This could overwhelm the listing though, so would need to find a minor addition here

This could lead to also wanting some balance on the UI and also showing labels for our existing commands -- for example "build", "install:default", "install:custom", etc.

Group commands by step

This might be a better UX altogether. With this method, build commands would be listed sequentially under an expanded section for each build step.

So instead of seeing the build commands listed on the build output page, the build output page would show:

  • Cloning repository
  • Running pre-install
  • Installing dependencies
  • Running post-install
  • Building
  • ..

Those sections could be dropped down to see the commands in each group.

We'd probably want to store the build step/substep (install:pre) on each command for easy grouping.


  • Play with UI, experiment with both options
  • If changing modeling separate out modeling changes
@agjohnson agjohnson added the Needed: design decision A core team decision is required label Mar 15, 2022
@agjohnson agjohnson added Accepted Accepted issue on our roadmap Feature New feature and removed Needed: design decision A core team decision is required labels Feb 7, 2023
@agjohnson agjohnson removed this from the Template public beta - community milestone Feb 7, 2023
@agjohnson
Copy link
Contributor Author

I'm going to call this a new improvement, for after the beta process probably. The UX here would be great though! I think we need to add a field or two to the build command model to satisfy a few build detail page features we'd like.

@agjohnson agjohnson added this to the New dashboard features milestone Dec 8, 2023
@agjohnson
Copy link
Contributor Author

Lots of duplicate discussion here in #171

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Feature New feature Status: blocked Issue is blocked on another issue
Projects
None yet
Development

No branches or pull requests

1 participant