Skip to content

Add CI test environment#32

Open
MitchellThompkins wants to merge 2 commits into
gnu-octave:mainfrom
MitchellThompkins:run-ci
Open

Add CI test environment#32
MitchellThompkins wants to merge 2 commits into
gnu-octave:mainfrom
MitchellThompkins:run-ci

Conversation

@MitchellThompkins

@MitchellThompkins MitchellThompkins commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Description

While working #31 I wanted to run tests but lacked all the tooling locally. I setup a local and CI test environment (both using docker) and wrapped things in makefile calls.

The script to do this is a bit hacky but as a first pass this felt appropriate.

Changes

  • Adds CI jobs that run on PRs to main, pushes, and weekly. The weekly part isn't necessary really but is nice to catch weird regressions in the container. It's a bit pathological so probably not required but overall harmless I felt.
  • Adds a local test environment based on docker/docker compose that lets folks test more easily

@MitchellThompkins

Copy link
Copy Markdown
Contributor Author

I'll also say I think this can be adapted to other octvage packages which I can probably help coordinate if it's welcome.

@MitchellThompkins MitchellThompkins changed the title Add CI Add CI test enviroment Jul 4, 2026
…ile updates to facilitate running all pkg-control tests in CI and localy without installing. Run tests once a week.
@ttl-octave

Copy link
Copy Markdown
Member

Here again, thanks for the contribution. I am going to make the review soon but to be honest, I am not very familiar with the github CI actions. Does the file composer.yaml need to be located in the root directory or can it be moved to devel? If it has to be in the root directory it should be added to .gitattributes with the attribute export-ignore in order to prevent including it into the distributed package archive.

@MitchellThompkins

Copy link
Copy Markdown
Contributor Author

Here again, thanks for the contribution. I am going to make the review soon but to be honest, I am not very familiar with the github CI actions. Does the file composer.yaml need to be located in the root directory or can it be moved to devel? If it has to be in the root directory it should be added to .gitattributes with the attribute export-ignore in order to prevent including it into the distributed package archive.

docker compose looks in the directory from which it is being being run for a compose file, but you can point the tool anywhere with --file. It required a small additional change for it to find the right files but I tested and it worked.

@MitchellThompkins MitchellThompkins changed the title Add CI test enviroment Add CI test environment Jul 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants