Does anyone have a good workflow for testing new L...
# lucee
d
Does anyone have a good workflow for testing new Lucee builds? @bdw429s sent me something a while ago that worked well with CommandBox, but I've somehow misplaced those instructions. I'm really wanting to fire up the testbox tests to run a specific test suite, preferably in the browser so I can do some tracking.
z
d
@zackster how do you run script-runner locally from the CLI?
z
i have written up docs about usage on the repo https://github.com/lucee/script-runner
b
I found it first try in the Slack search by searching for "Lucee compile" šŸ™‚
d
I was thinking you sent me something much longer ago where I could point commandbox to a specific JAR/lco file.
So I would just spin up any version of Lucee and the idea is that script compiles the code, then puts the updated lco in the deployment folder, correct?
b
To be clear, that's precisely the instructions I sent you last time
They • run the build • copy the lco file to Lucee's deploy folder • and then the bit of CFML code you put at the top of your test page forces Lucee to check the deploy folder
@dswitzer
d
@bdw429s Sorry about that. I really thought you had sent me something that would work with the server start command, where you could specify the JAR/LCO in the cfengine path somehow, but that wasn't working (because I was obviously wrong!) 😃
b
Nope. CommandBox can be pointed to a war file anywhere, but a CommandBox server can't be pointed at a jar or lco file-- those go inside the war
You may be thinking of the ability to run any Lucee snapshot
Copy code
start cfengine=<http://update.lucee.org/blah/blah>
back before we started publishing all snapshots directly to ForgeBox
Now you could make a simple process in a task runner or something that takes a jar and wraps it up in a war, but it's really much simpler to just have Lucee running an swap out the lco on the fly, which is can do without restarting.