-
Notifications
You must be signed in to change notification settings - Fork 21
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
Build process is now broken #662
Comments
ok I found how to enable it why did you release breaking change? I'll need to fix all builds to older version now |
For the short term: we'll fix this and get 0.9.1 out ASAP. For the longer term: CI that says "download the current latest version of a dependency, whatever that happens to be, irrespective of semantic versioning" is fragile and wouldn't be a good idea in any other open-source ecosystem. I know we've directed people that way for a long time but it paints us into a corner. |
@daimor if you can point to a CI process that fails this way, that would be helpful. In my observation most things seemed to be using the Developer Community containers which is why we filed intersystems-community/zpm-dockerhub#43 before release. |
We used zpm in our corporate builds. It we were using the latest version in the build, and with the release 0.9.0, our build ate broken, because it now requires additional steps, enable zpm globally and add removed public repository. Previously just installing zpm from xml were enough. I'm not going to change our build process to adjust to the new behavior, I'm going to use one of the previous releases. So, we will get stability in the builds |
git blame for this: 5c8f4e9#diff-3f2db197477147c00fdfc3242d2cd3e309d30861f50232f98ffebf8e6ba4f3c3R70 On further consideration, this is actually intentional, and given that there are other necessary backwards-incompatible changes in 0.9.0 (esp. class naming) it makes sense to lump them all together. The road here is to inclusion of IPM with IRIS, and from a software supply chain security perspective we don't want to have the community repo enabled by default out of the box in IRIS (though we do want to make it easy to enable). We also want the ability to have different IPM versions in different namespaces to support multi-tenant use cases (different applications with different requirements in different namespaces). Steps to reproduce on a clean installation (really the only case as an upgrade will migrate repos):
zpm "repo -reset-defaults" will still enable the community registry. Things to do:
|
One should not be shocked that an open source project with semantic versioning on major version 0 introduces backwards incompatible changes. I think it's a widely agreed convention semantic versions < 1.0.0 are considered unstable and only versions since 1.0.0 indicate stable public API. I don't know how strictly this convention is used in InterSystems' ecosystem thought. |
@janihur that's spot-on and would be my expectation for use of semantic versioning of packages in this ecosystem. |
I filed intersystems-community/zpm-registry#119 which would let us have a better one-liner to recommend for CI. |
The steps to get back to previous behavior are simplified (and properly documented) in 0.9.1: |
I don't want workarounds, show just work as before |
We are using IPM in our CI, and now it does not work
How it supposed to be enabled?
Why the message does not suggest, how to do it?
The text was updated successfully, but these errors were encountered: