Fossil SCM
"Raw TH1 commands" work, while "transfer" commands don't
fd02d0b67b935a6…
· opened 5 years, 11 months ago
- Type
- Code_Defect
- Priority
- Immediate
- Severity
- Important
- Resolution
- Not_A_Bug
- Subsystem
- —
- Created
- May 5, 2020 1:35 p.m.
In this forum post I detail my issues getting "transfer" scripts to work.
The short of it is, in my current setup:
- If I enter the TH1 code in the "Raw TH1 commands" my script executes, but
- If I have that same exact code in the transfer (e.g. commit or push) boxes, the script doesn't execute
Note that I do have the 'tcl' and 'th1-hooks' enabled in the settings.
This is a problem for me, because I want a bash script to execute and update a web site every time someone commits a change, and I don't want to give access to the web site itself to the developers.
Comments (2)
In this forum post I detail my issues getting "transfer" scripts to work.
The short of it is, in my current setup:
- If I enter the TH1 code in the "Raw TH1 commands" my script executes, but
- If I have that same exact code in the transfer (e.g. commit or push) boxes, the script doesn't execute
Note that I do have the 'tcl' and 'th1-hooks' enabled in the settings.
This is a problem for me, because I want a bash script to execute and update a web site every time someone commits a change, and I don't want to give access to the web site itself to the developers.
Figured out the problem: you need the & after the tclInvoke command or it never returns to Fossil.