User guide
Raising work, moving it through a workflow of agents and people, and shipping it.
Getting started
- What is Eido BuildEido Build takes a piece of work from a request to a merged change, through a workflow where agents do some stages, people approve others, and Eido Build does the rest itself.
- Key conceptsThe words Eido Build uses for work, the process it goes through, and the people and agents involved.
- Finding your way aroundThe sidebar, the project picker, search, the Create menu, and what the colours beside a piece of work are telling you.
- Your first work itemRaise an enhancement and follow it through triage, the agent stages, approval and the merge.
Work items
- Raising workHow to raise a bug, an enhancement or a task, and what to put in it so somebody can act on it.
- TriageWhere everything that has been raised is decided once, approved into the plan or turned down with a reason.
- Work items, as a board or a listOne screen for every work item in scope, drawn as a board or a list and filtered by anything.
- Saved filtersKeep a set of conditions, columns and sort order under a name, and share it with a project or with everybody.
- My workWhat has your name on it, what is waiting on you, and how long each thing has been waiting.
- The work item pageA work item's facts, owners, stages, documents, code changes and builds, and how to change each of them.
- TasksWork that is not code, such as ringing a customer back, raised on the same form and tracked on the same screens.
- Discussion and notificationsTalking to colleagues about a work item, following it, and choosing how you are told when something happens.
Workflows
- How a workflow runsThe stages a work item passes through, who has each one, and what each status means.
- Working with an agent stageTalking to the agent on a stage, reading what it produces, finishing the stage, and what to do when it stops.
- ApprovalsHow a stage is signed off, who may do it, and what happens when you reject one.
- Branches, builds and pull requestsWhen a work item gets its branch, how to see its builds and changes, and how the merge stage opens and merges the pull request.
- Acceptance criteria and QAWriting down what done means, testing a change against it with evidence, and deciding what happens to the bugs that turn up.
Releases
- Planning releasesHow work is gathered into releases, why it waits for its release to open, and how the queue and the backlog fit in.
- Cutting a releaseFreezing a release, running its checks, deciding what to do about what they find, and shipping it.
- HotfixesShipping an urgent fix from what is already in production, without disturbing the release being built.
Agents and Odie
- Standing agentsAgents that run on a schedule instead of on a work item, write a report, and raise suggestions for you to decide on.
- OdieThe assistant on every page. It reads everything you can read, and anything it wants to change becomes a card for you to press.