...
[15:03:10 CDT(-0500)] <TonyUnicon> do we have any way of confirming the revision number its based on?
[15:04:11 CDT(-0500)] <dmccallum541> let me check
[15:06:26 CDT(-0500)] <TonyUnicon> like SSP-1271 I thought I had addressed days ago
[15:06:40 CDT(-0500)] <TonyUnicon> and I don't see it locally
[15:07:27 CDT(-0500)] <dmccallum541> the source checkout has the most recent commit
[15:08:00 CDT(-0500)] <dmccallum541> dont have a good way of checking a global rev # on the deployed code… looking to see if that patch was deployed tho
[15:08:53 CDT(-0500)] <dmccallum541> it's got Jim's latest: https://github.com/Jasig/SSP/commit/236e6677765811f153e2b5fe66f8851c776eb486
[15:09:18 CDT(-0500)] <TonyUnicon> hmm
[18:29:33 CDT(-0500)] <dmccallum541> need to bounce linux CI repeatedly to test the liquibase fix
[18:31:19 CDT(-0500)] <JasonElwood> cool
[19:04:20 CDT(-0500)] <dmccallum541> JasonElwood i can no longer reproduce the liquibase lock problem in linux CI. do you want to try to push the latest code to demo?
[19:04:51 CDT(-0500)] <JasonElwood> Not to demo. we've been keeping that on b1 to remain stable. Sinclair is using that for testing
[19:05:39 CDT(-0500)] <JasonElwood> is there a patch that can be done? As soon as we are 110% sure about b2, we'll update the demo site to b2 but not until then.
[19:06:35 CDT(-0500)] <dmccallum541> i think that's feasible
[19:10:04 CDT(-0500)] <dmccallum541> yep. https://github.com/Jasig/SSP/tree/2-0-0-b1-demo