Use Github Actions to generate config #51
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I created a very basic PoC how could Github Actions workflow be used in order to have a reliable way to always have the latest config available as an artifact instead of having the generated config in repository.
There are a few advantages/disadvantages to this approach.
Advantages:
dbgore.dll
instead of correctdbgcore.dll
, even though this is fixed in 10_process_access/include_debugging.xml)Disadvantages:
Hopefully these disadvantages will be fixed in foreseeable future (other platforms e.g. GitLab CI/CD support these use-cases). There is a workaround by using eine/tip, which creates one static pre-release and modifies the files for it on successful build, although I haven't tested it.
Example of passing build
Example of failing build (due to missing ending tag)
Not sure if this is necessary or if it will actually help in maintaining the repository, but I think it may open some interesting possibilities, I'm sure there are other ways to extend/improve the pipeline I haven't thought of.