Creating ACCDE from ACCDB via GitHub or Azure DevOps Workflow – Any Experience?

Josef P.

Well-known member
Local time
Today, 07:34
Joined
Feb 2, 2023
Messages
1,111
Does anyone have experience in automating the creation of an accde via GitHub/Azure devops workflows?

A workflow to create an accdb from the source files created with msaccess-vcs already works.

My plan:
  1. install Office 64 bit
  2. create accdb from the source
  3. (optional) run tests (64 bit)
  4. create accde (64 bit)
  5. change bit version of Office .. only possible with: uninstall + install?
  6. (optional) run tests (32 bit)
  7. create accde (32 bit)
1+2: done
3/6: still open, but easy to implement, as I can start this via an Access add-in.
4/7: open, but is only one line of code.

5: What is the best way to change the bit version?
Do I have to start an extra workflow for each bit version to create the accde, or can I possibly change the bit version in a workflow?

Note: in my local network I use 2 virtual machines with 32 and 64 bit Office preinstalled. But they are not available via GitHub/Azure devops.

How would you implement this?
 
Note:
Result of my experiments: a self-hosted runner currently seems to be the best option.
1x runner with installed Office 64 bit
1x runner with installed Office 32 bit

This eliminates the long installation time and I feel more comfortable with the license because I can use my own license and not start an unlicensed Office.

This results in this workflow(s):

Workflow 1 - (on runner with 64 bit Office)
  1. create accdb from the source
  2. (optional) run tests
  3. create accde for 64 bit
Workflow 2 - (on runner with 32 bit Office)
  1. create accdb from the source
  2. (optional) run tests
  3. create accde for 32 bit
 
What do you mean by a 'self-hosted runner'?
 
Then I'll continue talking to myself and announce a few interim results. :)

Build scripts are ready: https://github.com/AccessCodeLib/msaccess-vcs-build
Note: The Powershell scripts can also be executed locally without a YAML file for a workflow.

Example GitHub workflow:
=> result: https://github.com/AccessCodeLib/ACLibDeclarationDictionaryAddIn/releases/tag/v0.4.2
The ZIP file and the ACCDA file for this add-in have already been automatically created.

On the subject of 32/64 bit accde: I simply run 2 workflows with different runners in response to a release. I then have one zip file each for 32 and 64 bit accde in the release.


The next step is a script for setting the database properties (AllowBypassKey, ...) etc.

If anyone has any questions, I'll be happy to answer them ... otherwise I'll end this monologue ;)
 

Users who are viewing this thread

Back
Top Bottom