Files and history
Project history and recovery
Buildryn records source history associated with generation and builds. Use the recovery action that matches what you want to restore, and preserve current work before a rollback.
Choose the appropriate action
Section titled “Choose the appropriate action”| Goal | Action |
|---|---|
| Reject the latest generated result | Undo all in pending change review. |
| Return to a source state associated with a message | Revert to this message, when available. |
| Restore source associated with an earlier build | Revert to this commit from build history, when available. |
| Package an older source state | Rebuild from the historical build/commit. |
| Keep current source and try a different direction | Duplicate the project. |
| Recover an older downloadable version | Download its successful historical build, when reconstructable. |
A source restore and an artifact download are different. Downloading an old JAR does not change the project files. Restoring old source does not change an existing deployment.
Preserve your current work
Section titled “Preserve your current work”- Wait for active generation and builds to finish.
- Save or copy manual edits.
- Download any artifact you need to retain.
- Duplicate the project if you want an independent copy of current source.
- Tell collaborators before replacing shared project state.
Duplication preserves source for an experiment but does not copy the original’s full conversation, build, and membership history.
Revert to a message
Section titled “Revert to a message”- Find the relevant generated message in its chat history.
- Check that it represents the source state you want.
- Use Revert to this message if that action is available.
- Read and complete any confirmation.
- Inspect the restored files and build them before testing.
This requires suitable managed project history associated with the message. A discussion-only response or a message without a usable source snapshot may not offer restoration.
Restore from build history
Section titled “Restore from build history”- Open Build history.
- Identify the build number, date, version, and source commit.
- Open More actions for an eligible entry.
- Choose Revert to this commit.
- Complete the confirmation, then inspect the restored source.
- Build and deploy the restored version if you want to test it.
Restoring source from a previous build can replace later work. Check the build number and commit before confirming; restoration does not merge the old source with your later changes.
Rebuild a historical version
Section titled “Rebuild a historical version”Use the historical entry’s rebuild action when you want an artifact from its recorded source. Check which build or commit the action names so you do not accidentally build current source instead.
A historical Java artifact may need recompilation. A historical datapack may need repackaging. These operations depend on available source history and can fail if that version can no longer be reconstructed or built.
Download a historical artifact
Section titled “Download a historical artifact”- Open the desired successful build entry.
- Use its download action.
- Wait if reconstruction is required.
- Check the downloaded file name and version against the chosen build.
Buildryn stores the latest packaged artifact for a project and reconstructs historical downloads from source when possible. Keep local copies of releases you rely on.
After a rollback
Section titled “After a rollback”Review metadata, configuration, dependency requirements, and feature behavior. If you changed the deployment’s live configuration separately, a project rollback may not reverse those runtime edits.
Build the restored source and launch the matching artifact. Use your previous acceptance checklist to confirm that the recovered version is the one you intended.
History is not a general Git interface
Section titled “History is not a general Git interface”Use the exposed message and build controls for recovery. Buildryn manages project history through these controls. User-controlled branches, pull requests, and external-repository connections are outside this workflow.
For recording team actions, see project activity.