Upload application to Actcast and test #

In this chapter, using applications under development incurs fees. For more details, see Fees to use applications under development by your group.

Uploading application #

You can upload and register your built image and trained models onto Actcast. The uploaded image is the one built for release.

Before uploading, create a file .actdk/long_description.md in the working directory. Write a full description of the application in Markdown format (see below) in the file.

The following command uploads the application.

$ actdk upload

If the upload succeeds, the following strings appear some time after the execution of the command.

start uploading
Build Submission ID: XX
Build ID for Raspberry Pi: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

“Build Submission ID” and “Build ID” are corresponding build IDs issued by Actcast.

If you want to use another Markdown file for the full description, you can use the -d option like the following:

$ actdk upload -d <DESCRIPTION_FILE>

where <DESCRIPTION_FILE> is a path to the Markdown file.

About Markdown file #

You must write a full description file of your application in Markdown-formatted text. This Markdown format is compliant with CommonMark, except for some restrictions, e.g., you cannot use HTML tags directly. For details, see here.

Build status #

You can check the build status ActDK with the following command:

$ actdk check status

By this command, you can check the build status corresponding to the latest upload. If the command succeeds, the following output is displayed.

Succeeded at 2019-06-07 10:27:26.682066134 UTC

The lead part Succeeded represents the current build status, followed by its issued date. Actcast build has four statuses:

Submitted (Waiting to start building)
Running (Currently building)
Succeeded (Build succeeded)
Failed (Build failed)

You can also check the build status of the <POS>th-to-last upload, where <POS> must be a number between 0 and 4.

$ actdk check status <POS>

Alternatively, you can specify a build ID directly to check the corresponding build status, like the following:

$ actdk check status <BUILD_ID>

Checking the build artifact #

If Actcast succeeds in rebuilding an uploaded image online, the developer can check its operation as an Act; you can download it to your Raspberry Pi and try it.

Go to Vendor Console > Applications.
Select the uploaded application.
Create an Act from Builds > Test

You must use a micro SD card with the ordinary Actcast client image. Please note that this image is different from the one used offline in the previous steps. For practical use, it is convenient to use two micro SD, one for offline development and the other as an Actcast client.

Next: Release an application

Previous: Test on local device