mait.sh1.142.0

Private beta: features and content may change. No warranty; use at your own risk.

AIDC Pack

Turns a tool you have installed into a package you can look inside, check, and share with your team, with a record of its identity and the checks you performed.

Start here: what it does, why use it, and how it fits.

Beta
OverviewInstallWorkflowsOperateCustomizeInsideProblems and fixesAll components
What it does

Turn an installed tool into a package you have looked at and checked.

Say you keep a tool that your whole team installs, such as a language runtime. Before you share a new version, you want to know that the package holds what you intend and nothing else. AIDC Pack prepares a tool installation in the chosen capture environment and wraps its files into a package, together with a small record of what the package is: the tool, its version, its size and the commands it gives you.

You can then look inside the package, run a set of checks on it, and send it to the MAIT Hub of your release channel. An interrupted upload can reuse eligible progress when you retry the unchanged archive. Looking, checking and packaging all work on your own computer with no sign-in. Only sharing the package needs your MAIT credentials.

aidc-packmait4.1.5the package builder
Choose targetBuildReview andverifyPublishConfirmavailability1234Choose targetBuildReview and verifyPublishConfirm availability1234
  1. Step 1: Choose target to Build.
  2. Step 2: Build to Review and verify.
  3. Step 3: Review and verify to Publish.
  4. Step 4: Publish to Confirm availability.
Why use it

What you gain over zipping a folder by hand.

Zipping an installed tool gives you a file and nothing that says what is in it. Here the package travels with a record of what it is, and it is checked before anyone downloads it.

Reliability

The package carries its own record

Reviewers can compare the recorded identity with the package they received

Typical alternative
A zip file with a name and a hope
Here
Every package is saved with a small record of the tool, its version, the system it is for, its size and the commands it provides
Usability

You see the contents before they leave

A package that is far too big, or missing the main program, shows up at once

Typical alternative
Unpacking the file to look around
Here
You can ask for a summary of the package, or a full list of what is inside
Reliability

A check on your own machine first

You can detect supported consistency failures before sharing

Typical alternative
Trusting that the packing step worked
Here
Every completed build performs local package checks; a separate verification can also compare an available Hub baseline
Speed

Uploads survive interruptions

Eligible progress can reduce repeated transfer

Typical alternative
Starting a large upload over from zero
Here
The upload is sent in pieces, failed pieces have bounded retries, and a repeat run may reuse eligible progress
Security

Sign-in only where it is needed

You can keep publishing credentials out of build-only jobs

Typical alternative
A publishing key sitting in every build job
Here
Only publication requires publishing credentials; an optional verification comparison can use credentials
Operability

A predictable place for everything

Each step finds the same package without you pointing at it

Typical alternative
Archives saved wherever the author happened to be
Here
Packages are saved in one tidy folder per tool and version, named after the system they are for
Out of the box

Already in the MAIT image.

AIDC Pack is already part of the MAIT image, so a project container has it from the start, and a newer image brings a newer version. Environments without the image can get a standalone copy from The MAIT Team or from your environment owner. By default it packages the tool inside a separate capture container; it can also do it in place on your machine.

Sharing always goes to the MAIT Hub of your release channel. If your team runs its own hub, you can still use AIDC Pack to build and check the package, then hand it over through that hub's own interface, as described in AIDC Server.

Where it fits

Where it sits in the MAIT toolkit.

Included inThe MAIT image from mait-image
NeedsAIDC, which installs the tool that gets packaged
Hands toThe AIDC Server of your release channel, or your own AIDC Server through its own interface
Used byPeople who install the published tool with AIDC; they never need AIDC Pack
Learn more

Where to read on.