Skip to content

Add multi-module support to project infrastructure #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 23, 2021
Merged

Add multi-module support to project infrastructure #71

merged 1 commit into from
Aug 23, 2021

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Aug 23, 2021

Projects may contain multiple Go modules in subfolders of the repository. In order to support checks on these modules,
it's necessary to configure the commands to run from their path. This is passed to the task via the GO_MODULE_PATH
environment variable. If this variable is not defined, the default root module path is used as default, preserving the
previous task behavior.

The workflows use a job matrix to allow easy configuration for any number of module paths and a dedicated parallel job
for each module.

Although this particular repository does not contain multiple modules, at the moment, and though there may be no plans to
add them at the moment, these are intended to be general-purpose assets that can be applied to any project. Since other
projects do contain multiple modules, the capability is necessary and this project inherits such.

Projects may contain multiple Go modules in subfolders of the repository. In order to support checks on these modules,
it's necessary to configure the commands to run from their path. This is passed to the task via the GO_MODULE_PATH
environment variable. If this variable is not defined, the default root module path is used as default, preserving the
previous task behavior.

The workflows use a job matrix to allow easy configuration for any number of module paths and a dedicated parallel job
for each module.

Although this particular repository does not contain multiple modules, at the moment, and though there may be no plans to
add them at the moment, these are intended to be general-purpose assets that can be applied to any project. Since other
projects do contain multiple modules, the capability is necessary and this project inherits such.
@per1234 per1234 added type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Aug 23, 2021
@per1234 per1234 merged commit e709fb5 into arduino:main Aug 23, 2021
@per1234 per1234 deleted the multi-module-support branch August 23, 2021 14:32
@per1234 per1234 self-assigned this Nov 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants