6.2.8.20

v6.2.8.20 has been added to the download page, but because there wasn’t an announcement here I didn’t see it to begin testing it.

It seems to be missing the normal lucee/lucee:6.2.8.20-nginx Docker image we base our deploys on, and the Windows install at https://cdn.lucee.org/lucee-6.2.8.20-windows-x64-installer.exe is also noted in other threads as missing, for weeks now.

There also seems a serious bug where the sort-of-released version doesn’t correctly pick up new changes to files, but no one has fix it or acknowledged it yet ??

1 Like

Anyone from Lucee team able to take ownership of the download page issues ?

I have 2 nodes on v6.2.8.20 and neither pick up changes to deployed files reliably. the other nodes on 6.2.7.16 work fine. They all have the same performance caching settings.
A restart of Lucee will fix the issue. Can reproduce this pretty reliably. for example, if I alter a heartbeat cfm page to send an error to bleed off connections and then fix the error after the lucee restart, the heartbeat cfm change will stay in error state.
Also deployed various cfm and cfc changes the last few days and the changes were not picked up until a restart.

Thanks. Guess we shouldn’t upgrade to the was-it-really-meant-to-be-released v6.2.8.20 then…

I am planning to roll back to 6.2.7.16 today. 6.2.8.20 causing too many deployment issues for me. Thanks for the original post TF. It helped me figure this out much faster.

because of the switch to the new download page that now mainly depend directly on maven one deployment step was missing, sorry for that.
all downloads should be back to normal.

On the “doesn’t pick up file changes” reports: confirmed regression from LDEV-6358, tracked and in development as LDEV-6482: Jira

Workaround for now: set Inspect Templates to “Once” (or “Always”) instead of Auto. Downloads/Docker for 6.2.8.20 should already be back after the Maven download-page fix. We’ll also add test cases so this whole inspect-Auto / file-change path stays covered.

Update on the file-change / Inspect Templates Auto issue: fixed in Lucee 6.2.9.3. Details: Jira

The same fix will follow for Lucee 7.

1 Like

@anderslars27 quick update: the “doesn’t pick up changes to deployed files” problem on 6.2.8.20 (Inspect Templates “Auto”) is fixed in 6.2.9.4-RC, which is out now: Lucee 6.2.9.4-RC available for testing.

The fix (PR #2809) and a regression test are merged into 6.2, tracked as LDEV-6482.

It would be great if you could try the RC on one of your nodes with “Auto” and let us know if deployed changes show up again without a restart.

Will do.

@anderslars27 thanks! Looking forward to hearing how the RC does on your node with Inspect Templates set to “Auto”.

I have only made one deployment so far to a single prod node on 6.2.9.4-RC with inspect templates auto - ON.
I had no issues and the changes were picked up. So - thus far - looking good.
I will do more in the next 2 days and confirm. Didn’t want to reply - ''all good" with such a small sample set.

1 Like

@anderslars27 thanks for the update and for taking the time to test it on a prod node, that’s good to hear.

Deployed multiple times today on 2 prod nodes and no problem detecting changes on 6.2.9.4-RC with inspect templates auto - ON.
So it is looking good to me. Thanks!

@anderslars27 thanks for testing it across several deployments on two production nodes and for reporting back, that’s exactly the confirmation we were waiting for. Thanks for taking the time to help improve Lucee.

We’ve updated an Internet facing pre-live site today, and will probably do a change-the-files-while-it’s-running deploy several times.

I’ve asked the team to keep a special eye out that changes appear right away.