Distributing compiled outputs for embedded controllers

[GaryL]

I have a slightly atypical use case.  We program controllers for embedded systems that use a proprietary programming language.  The plan is to version control the source code in BitBucket.  We (the developers) will manage this.  When we "release" a new version, we will compile the code and have a hex file that our operations folks download to the controllers.

Right now my idea is that I will manually place the compiled output on a network server for the ops guys to grab the file and download to the controllers.  It seems like there must be a better way!!  What is the better way?

[Daniil Penkin]

Hello @GaryL,

Thanks for reaching out!

You might be able to automate the pipeline you described, or at least some of its steps:

1. Build the binary artifacts of your project using Bitbucket Pipelines. To make it easier: if you can configure a Docker container to build your project, you can move such build into Bitbucket Pipelines.
2. Upload the binaries to a FTP/SFTP/SCP server / AWS / some other artifact storage. There might be an existing Pipe for that, which would simplify the configuration. You might find Deployments useful for your delivery process.
3. Alternatively, you can upload the binaries into Downloads section of your repository in Bitbucket. This can be done using Bitbucket REST API call from your pipeline script.

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil