Closed hjmjohnson closed 4 years ago
Correct me if I'm wrong Hans, but I would say that we will usually want to test remotes against stable/release versions of ITK. I assume you want to make sure that this builds against the pointed version of ITK.
Another change will be needed when the new release is tagged I guess.
I don't know how to test this "chicken & egg" problem in another way.
Not sure why but looks like Azure CI did not like the commit hash.
Not sure why but looks like Azure CI did not like the commit hash.
The git clone command for checking out shallow named branches does not work with hashes. I think it is a git server issue in that the hashes are not exposed at that level.
A newer version of ITK is needed for build to succeed.