Updating Sport library definition from Monticello (file) to Metacello (github) #45
Conversation
Leaving the package definition in place leads to an error with incompatible specs. The error: MetacelloCypressPackageSpec and MetacelloProjectReferenceSpec are not compatible.
|
@tukanos ... it looks like the glass CI runs were disabled less that 5 months ago ... I must have missed the disable workflow mail, or they don't send them anymore ... anyway, I'm going to update the CI lineup with more recent GemStone releases and let you know when I'm done so that you can send another neutral commit to trigger the CI run ... |
|
@tukanos, I've updated the ci lineup and the current glass CI tests are passing ... so please submit a neutral commit to trigger another CI run ... Thanks |
|
@dalehenrich I see. Perhaps Github wanted to save some costs so they disabled it to everyone? I have submitted a commit, hopefully it will trigger CI run. |
|
@tukanos saving money is definitely part of it ... their criteria for disabling actions is currently 60 days of inactivity which is reasonable and they used to send out email when they disabled actions ... and I would dutifully reenable the projects when I would get the email ... looking at my email I don't see any email from github about disabling workflows for the GsDevKit projects, so apparently I have not been notified when the workflows were enabled |
3 participants
Updating baseline for Glass1 in case of Sport compatibility layer to use github instead of Monticello's file.
The main issue addressed here is that the Sport dependency using Monticello can't be influenced by Metacello loading sequence. This update prevents loading the Sport library via http and uses GsDevKit github mirror instead.