Fold all updates since May from master and internal repo into v1 #437
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uments in module.xml Fixes #367
Fixes #416 This just changes tar generation, so it's actually backward-compatible with old IPM versions loading the package. (Which is neat.)
Update readme to add one-liner to install IPM
Use prefix to work around filename length limits
Fix install for certain non-enuw locales
Fix broken `exec` command
fixed installing python dependencies for ipm dependencies
Set up for `intersystems-community.testingmanager` VS Code extension
Set the ^UnitTestRoot node when building the container
add zpm version and current registry on entrance
EnableEnsemble for Verify stage
Eventually...
Strip newlines
Move packages to attribute?
Change quoting approach to see if this works better?
This reverts commit f16a6af.
Maybe needs else?
Raise threshold while in testing
|
@isc-shuliu in case you get to the CI failures before I do, there are three classes of issues:
Also, we only want the highest value of z among builds (year.x.y.z) |
e.g. with: act -j "build" --input IMAGE="[\"iris-community:latest-em\"]"
Easier to run via act for testing. We now omit old previews and no longer truncate valid tags containing dashes
Running locally on act, would previously leave the registry and zpm network after failure.
Mounts don't seem to work properly in act, so copying files instead. Fix Default.Document resource processor to not force a category subdirectory
Update CI for packages.yml
ci: parameterize minVersionCount for packages.yml
ci: bug fix
|
@isc-shuliu here's an updated checklist after the work I did earlier this week:
|
Update packages.yml
Add CI to test major packages on v1-jan-2024-updates branch
ModuleItem is the table name; should have checked for Module class.
Looking at history these were added fairly recently and it's failing here, so maybe removing them will fix it.
|
All changes since the last approving reviews have been CI-related. There's still some preexisting tech debt there; captured it in #451 but merging this now so we can keep targeting v1 with more granular changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This also includes some in-progress changes to the packages workflow (will be handled separately, this at least moves the ball forward there although it isn't done yet).
This includes through internal revision 6487010.