x
login Signup

Source Code manage Step Code

What are the approaches ElectricFlow/ElectricCommander users are using to manage the Step Code as 'source code'? To version, to ensure code managed like source code?

Do you not embed 'code' in the Step? Do you put all code/script in a file, put it in source control, and then 'call' the script from the Step?

Any thoughts?

avatar image By prgerth 57 asked Mar 21 at 09:11 PM
more ▼
(comments are locked)
10|750 characters needed characters left

1 answer: sort voted first

Putting ElectricdFlow content under source control is a very good best practice. DSL is perfect for doing this. As you pointed out, you have the choice of embedding the step/process code in the DSL or loading a file with the step/process code. I think the latter is preferable for a variety of reasons: source code editors will show coloration better because the file will have the appropriate extension (.sh, .pl, .groovy, etc), you don't have to worry about escaping characters to protect them from the DSL interpreter, and avoid premature expansion of $[] values. The main problem with referencing external files in DSL is that the files have to be accessible by the Flow server. If you use a plugin to manage your code, this issue goes away. Check out https://github.com/electric-cloud/PluginLite.

avatar image By gregm 1.9k answered Mar 22 at 04:55 PM
more ▼
(comments are locked)
10|750 characters needed characters left
Your answer
toggle preview:

Up to 8 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question


Topics:

x997
x154
x28
x9
x2

asked: Mar 21 at 09:11 PM

Seen: 25 times

Last Updated: Mar 22 at 04:55 PM

Related Questions