![]() ![]() In such a case, they may like to use tools which easily capture all changes that have occurred to source code. A planned future Git-related custom step will also facilitate "pulling" / updating existing code repos, so stay tuned for the same.Īcknowledging the dynamism of many analytics programs (especially if they are at early stages of development / production), it may sometimes be necessary for analysts to change parts of the source (SAS) code. You may still like to have the log persisted in an alternative location so that you can access it as a matter of record. While there are different approaches (such as pulling new code) to address this, in ephemeral environments, one option is to remove the source code once it has served its purpose (i.e. ![]() But, the presence of an earlier version of the code on the Viya environment is highly likely to mislead analysts into thinking that they are running the latest code. It's likely that the code / process you ran today may have already been updated on the central Git repository. As this article (and other similar articles) points out, applying the wrong process is a cause of analytics projects failing, and updated code becomes even more important when following modern collaborative analytics processes. Successful run of the Git Clone Custom Step at the top of the repository paves the way for subsequent code assets being made available and executable!Īn advantage to separating code from the runtime environment is that you can address problems occurring due to stale code. Here's a suggestion which can make the whole process even more portable : what if, in addition to your source code assets, you also have a SAS Studio Flow which contains your entire source code, linked together in the form of a process, neatly organised within swim lanes as shown in the below GIF? This Flow already has code placeholders which are linked together to a local repository (saved in a predetermined path as dictated by your business process). Choose the execution method most convenient for you (run the code standalone, pull them into a flow, or include within other programs). The animated GIF below shows these steps.Īs a result of the steps above, you now have your source code (SAS programs and other related content) available within your SAS Studio environment, ready to run.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |