Skip to content

Functions

Jump to bottom
devonfw-core edited this page Aug 13, 2021 · 44 revisions

Functions

The following functions are already implemented:

installDevonfwIde

This function allows you to install devonfw-ide in your environment.

parameter

This function consist of two parameter.

  1. First parameter:
    • Required
    • Type- String[] or Array of String
    • Description-The tools you want to install within the devonfw-ide. You can pass every tool that can be installed with the devonfw-ide. In this parameter, the tools you can pass are: java, mvn, node, npm, gradle, ionic jasypt, jenkins, ng, sonar and yarn. You can pass any tool based on your requirement.

Note: You can also pass the IDEs: eclipse, intellij, and vscode. But are not needed in the Katacoda environment and they might create some errors.

  1. Second parameter:
    • Optional
    • Type- devon-ide version
    • Description-It is the version of the ide to install. If you don't use the second parameter, it will always install the newest devonfw-ide release.

example

installDevonfwIde(["java","mvn"], "2020.08.001")

details

  1. You should not use it when you want to show Katacoda user the installation process of the devonfw-ide.
  2. There are scripts that can run in the Katacoda background before first step.

restoreDevonfwIde

parameter

  1. The tools you want to install within the devonfw ide: string array
  2. Optional: The version of the ide to install

example

restoreDevonfwIde(["java","mvn"], "2020.08.001")

details

In the Katacoda environment the installation of the devonfw IDE is executed in a startup script.

restoreWorkspace

parameter

  1. (Optional) Name of the workspace repository {"workspace": string} (Default is the playbook-name)

arguments

User(Optional) flag: --user value: GitHub-username (Default is 'devonfw-tutorials')

You can use a forked workspace-repository, if you add the username as argument. If the runner cannot find the workspace repository in the your repositories, it will use devonfw-tutorials instead.

Branch(Optional) flag: --branch value: the working branch (Default is its default-branch)

You can use a different branch, if you add the working branch as argument. If the runner cannot find the branch in the cloned repository, it will use the default branch instead.

buildRun.sh --user [username] --branch [branch]

example

restoreWorkspace() will clone "https://github.com/devonfw-tutorials/[playbook-name]" into the workspace directory.

restoreWorkspace({"workspace": [name]}) will clone "https://github.com/devonfw-tutorials/[name]" into the workspace directory.

buildRun.sh --user [GitHub-name] --branch [branch] restoreWorkspace() will run "git clone https://github.com/[GitHub-name]/[playbook-name]" and checkout in branch [branch]

details

workspace The default name of the workspace repository is a concatenation of "workspace-" and the name of your playbook-folder. If you want to use another repository as workspace, you can specify the ending with {"workspace": [name]}. example "workspace-devon4ng" -> {"workspace" : "devon4ng"}

local repository You can use a local repository as workspace in the console environment for your tutorial. Clone the forked repository next to the tutorial-compiler folder. Before cloning the GitHub repository, the console runner will always check, if there is a 'workspace-[name]'-folder next to the tutorial compiler first, and will use it instead.

Keep in mind, that it is a feature only implemented in the console environment. Other runners will clone the environment from GitHub.  

|--tutorial-compiler
|--tutorials 
|--workspace-devon4ng

workspace directory

If you call 'restoreDevonfwIde' or 'installDevonfwIde' before the 'restoreWorkspace'-function the workspace directory remains: 

    `'/root/workspaces/main'`

If you don't call them, the workspace is changed to:

    `'/root/workspaces'`

Learn more about the workspace directory and working directory on Structure

changeWorkspace

parameter

  1. path to a new workspace (relative to working directory)

example

changeWorkspace("devonfw/workspaces/project") will set the workspace directory to "[working directory]/devonfw/workspaces/project"

Learn more about the workspace directory and working directory on Structure

executeCommand

parameter

  1. The command that will be executed on Windows
  2. The command that will be executed on Linux
  3. Json-object with optional fields
    • (Optional) Directory where the command will be executed, if not in current directory (relative to workspace){"dir": string}
    • (Optional) Synchronous or asynchronous process. Use asynchronous when starting a server. Default is synchronous. {"asynchronous": boolean}
    • (Optional) Array of arguments {"args": string[]}
  4. Assert information needed if you start a server to check server availability. Only required when you start a asynchronous server.

Commands

It is needed to pass a command for Windows and also for Linux-based systems because both systems will always be tested.

Assertion information

startupTime = Time in seconds to wait before checking if the server is running port: Port on which the server is running path: The URL path on which is checked if the server is running interval: The availability of the server is checked in the given interval

  • (Required) port: will throw error if no port is given.
  • (Optional) path: subpath which should be pinged, i.e: if localhost:8081/jumpthequeue should be checked path should be "jumpthequeue". DEFAULT: ""
  • (Optional) interval: interval in seconds in which the server should be pinged until it is available or timeouted. DEFAULT: 5 seconds
  • (Optional) startupTime: seconds until a timeout will occur and an error will be thrown. DEFAULT: 10 minutes

example

executeCommand("node", "node" ,{"args": ["-v"]}) Will create a command for executing node -v .

executeCommand("somePollingScript.ps1","bash somePollingScript.sh", {"dir": "data/setup","asynchronous": true, "args": ["--params 5"]}) Will create a command to execute the script in the directory with the parameter --params 5 and in a new terminal.

executeCommand("someServerScript.ps1","bash someServerScript.sh", {"asynchronous": true, "args":["-port 8080"] },{"port":8080 , "startupTime": 20, "path": "some/path/", "interval": 2}) Starting a server in a new terminal. You have to specify the port for testing, the other parameters are optional. The startupTime can specify how long the runner will wait for a response from the server process and with interval you can set the frequenzy for the server testing. The path is the subpath from your server that should be reached.

installCobiGen

parameter

  • No parameters

example

installCobiGen()

cobiGenJava

This function is used for code generation inside Java file i.e. Entity class in Java.

parameter

This function consist of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- The path to the Java file you want to generate code for.
  2. Second parameter:
    • Required
    • Type- Array of Integers
    • Description- It is the array of numbers that represent the templates that CobiGen uses to generate code.

example

cobiGenJava("path/to/java/file/MyEntity.java",[1,3,5,6,8])

details

Number Description
1 CRUD logic: Generates the logic layer and implementations for some use cases.
3 CRUD REST services: Generates the service layer with CRUD operations for using in REST services.
5 TO's: Generates the related Transfer Objects.
6 Entity infrastructure: Creates the entity main interface and edits (by a merge) the current entity to extend the newly generated classes.
8 CRUD SpringData Repository: Generates the entity repository (that contains the CRUD operations) in the data access layer.

Note:

  1. User needs to execute this command manually.

  2. You need to add installCobiGen() and adaptTemplatesCobiGen() functions before adding this function for CobiGen installation and adapting the Cobigen Templates respectively.

  3. CobiGen CLI is used for execution of these functions. You can find more information related to CobiGen CLI click here.

  4. To execute this function, devonfw-ide must be installed.

createDevon4jProject

parameter

  1. The base package name

example

createDevon4jProject("com.mycustomer.myapplication")

buildJava

This function will build your java project.

parameter

This function consist two parameter .

  1. 1st Parameter:
    • Required
    • Type- String
    • Description- The project directory, relative to workspace.
  2. 2nd Parameter:
    • Optional
    • Type- Boolean
    • Description- Indicator whether tests should be run. Default is false.

example

buildJava("cobigenexample", true) Note:

  1. To execute this function, devonfw-ide must be installed.

createFile

This function creates a new file with a specified content. If no content is specified, an empty file is created.

parameter

This functions consists of two parameter.

  1. 1st Parameter:
    • Required
    • Type- String
    • Description- Path of the file to be created (relative path to the workspace directory).
  2. 2nd Parameter:
    • Optional
    • Type- String
    • Description- Path of the file to get the content from. Relative to the playbook directory.

example

createFile("cobigenexample/core/src/main/java/com/example/application/cobigenexample/customermanagement/dataaccess/api/CustomerEntity.java", "files/CustomerEntity.java")

Note: This function will work without a devonfw-ide installation.

changeFile

parameter

  1. Path of the file to be changed (relative path to the workspace directory)
  • Path of the file to get the content from or a string, that should be inserted.(relative path to the playbook directory)
  • (Optional) Name of a placeholder
  • (Optional) Line number where u want to insert your code. (Possible lines are: 1...n+1 for N = number of existing lines. File cant be empty)

example

changeFile("cobigenexample/core/src/main/java/com/example/application/cobigenexample/customermanagement/dataaccess/api/CustomerEntity.java", { "file": "files/Placeholder.java", "placeholder": "private static final long serialVersionUID = 1L;" })

details

Path of the file to get the content from or a string, that should be inserted.

If you want to add content from a file: {"file": "[path]"} If you want to add a string to a file: {"content": "[string]"} If you want to add different contents for the katacoda and console runner, then use the properties "fileConsole" and "fileKatacoda" or "contentConsole" and "contentKatacoda": {"fileConsole": "[pathToConsoleFile]", "fileKatacoda": "[pathToKatacodaFile]"} If you want to insert some content at a specific line, then use "lineNumber" and dont use a placeholder: {"lineNumber": "[Line]"}

example:{...,"placeholder": "private int age;"}

Before Content or File After

private int age;

public String getFirstname() {
return firstname;
}

private int age;

private String company;
public String getCompany() {
return firstname;
}
public void setCompany(String company) {
this.company = company;
}

private int age;

private String company;
public String getCompany() {
return firstname;
}
public void setCompany(String company) {
this.company = company;

public String getFirstname() {
return firstname;
}
Prerequisite

The usage of the line number function requires having VSCode installed on your System. Not having VSCode installed will not create any output for Katacoda.

Name of the placeholder

If you want to insert content into your code between two existing lines, take the previous line as your placeholder or use the option to insert at a line number. Add your placeholder into the new file or string, otherwise it will be replaced entirely.

A placeholder is optional. If you do not define a placeholder, the content in the existing file will be simply replaced by the new content.

Please try not to use custom placeholders. Keep in mind that you might want to build the project before changing them. Custom placeholders with a comment-syntax (e.g. "//PLACEHOLDER") will be removed by the console-environment and others might cause errors.

The option to insert at a linenumber uses a placeholder inserted by a script and just adds it at the step you also insert the content.

createFolder

This function is used to create a new folder.

parameter

This function consist of one parameter.

  1. First parameter:
    • Required
    • Type- String
    • Description- Path of the folder to be created (relative to working directory). Subdirectories are also created.

example

createFolder("directoryPath/subDirectory")

Note:

  1. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

  2. It can be used before any command which needs to be executed in such folder which doesn't exist.

cloneRepository

This function is used when you want to clone a repository into a particular directory.

parameter

This function consist of two parameter.

  1. First parameter:

    • Required
    • Type- String
    • Description- It is path into which the repository is to be cloned, relative to workspace.

  2. Second parameter:

    • Required
    • Type- String
    • Description-It is the Git repository URL.

example

  1. cloneRepository("", "https://github.com/devonfw-tutorials/tutorial-compiler.git") Repository will be cloned directly into the workspace directory.

  2. cloneRepository("devonfw-tutorials", "https://github.com/devonfw-tutorials/tutorial-compiler.git") Repository will be cloned into a newly created subdirectory "devonfw-tutorials".

Note:

  1. No scripts will run in the background.

  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

runServerJava

parameter

  1. Path to the server directory within the java project.
  2. Assertion information. Only needed for the console runner to check if the server was started properly.

example

runServerJava("devonfw/workspaces/main/jump-the-queue/java/jtqj/server", { "startupTime": 40, "port": 8081, "path": "jumpthequeue" })

Assertion information

startupTime = Time in seconds to wait before checking if the server is running port: Port on which the server is running path: The URL path on which is checked if the server is running

If the tutorial should be tested on the console environment, you have to specify a port.

npmInstall

npmInstall is used for installing packages from node package mangager, for example used in Node.js or Angular projects.

parameter

This function consist of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- It is the path to the project where the dependencies from the package.json file are to be installed.
  2. Second parameter:
    • Optional
    • Type- JSON object
    • Description- It is the array of JSON-objects which contains name of a package, global or local installation, or array of npm arguments.

Details

In second parameter, you can add 3 attributes.

  • Frist attribute: It is optional and it is the name of a package.

    Example: {"name": string }

  • Second attribute: It is optional and it is for global or local installation. Default is local, therefore false.

    Example: {"global" : boolean }

  • Third attribute: It is optional and it is the array of npm arguments.

    Example: {"args": string[]}

example

  • npmInstall("jump-the-queue/angular", {"name": "@angular/cli", "global": true, "args": ["--save-dev"]}) will run 'npm install -g --save-dev @angular/cli' in the directory 'jump-the-queue/angular'.

  • npmInstall("my-thai-star/angular") will run 'npm install' in the directory 'my-thai-star/angular'

Note:

  1. Existing project is required to execute this command.
  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

dockerCompose

parameter

  1. Path to the directory where the docker-compose.yml file is located, relative to workspace.
  2. Assertion information. Only needed for the console runner to check if the server was started properly.

example

dockerCompose("my-thai-star", { "startupTime": 600, "port": 8081, "path": "" })

Assertion information

startupTime = Time in seconds to wait before checking if the server is running port: Port on which the server is running path: The URL path on which is checked if the server is running

If the tutorial should be tested on the console environment, you have to specify a port.

downloadFile

parameter

  1. URL of the file to be downloaded.
  2. Name of file.
  3. (Optional) Downloads file to a given directory relative to workspace. Directory is created, if its not existing.

example

downloadFile("https://bit.ly/2BCkFa9", "file", "downloads")

buildNg

parameter

  1. Path to the angular project, relative to workspace
  2. (Optional) Custom output directory.

example

buildNg("exampleAngularProject") Will build the angular project to default output directory defined in angular.json outputPath key, normally set to dist/.

buildNg("exampleAngularProject", "testOutput") Will build the angular project to output directory testOutput.

runClientNg

parameter

  1. Path to the angular project from which the frontend server is to be started.
  2. Assertion information. Only needed for the console runner to check if the server was started properly.

example

runClientNg("jump-the-queue/angular", { "startupTime": 200, "port": 4200, "path": "" })

Assertion information

startupTime = Time in seconds to wait before checking if the server is running port: Port on which the server is running path: The URL path on which is checked if the server is running

If the tutorial should be tested on the console environment, you have to specify a port.

displayContent

parameter

  1. The title of the step.
  2. An array of json objects with files, content, or images to be rendered within the Katacoda step. The use for this function is to display an image and some descriptive text. No Katacoda syntax is allowed in the files or the content!
  3. (Optional) Path to the current directory where the user is located (relative to the workspace directory). Only needed if the directory is changed within this step.

example

display("Step title", [{ "file": "files/description.asciidoc" }, { "content": "This is just plain content." }, { "image": "files/image.png" }])

Details

Available attributes in the json objects:

  1. file: Path to a file whose content is to be displayed in the Katacoda step (e.g. .asciidoc or .txt file). The file should be following the formating of asciidoc files.
  2. content: Plain text to be displayed in the Katacoda step. This Text should be following the formating of asciidoc files.
  3. image: Path to an image to be displayed in the Katacoda step.

Formatting rules for content and .asciidoc or .txt files.

  • You can add headers to structure your text. The generated headers are shown in the examples below. The headers should fit into the overall structure of the generated wiki so level 1 header are not allowed, but the other header can be used at your judgement.
  • A list always needs an empty newline between the last row and the list.
  • Use asciidoc style of links

examples

Existing header structure
= Level 1: tutorial title
== Level 2: subtitle
=== Level 3: prerequisites and learning goals
== Level 2: steptitle
=== Level 3: titles from functions 
==== Level 4: subtitles from functions
== Level 2: conclusion

List:
This an unordered List (The empty line is necessary)

* First Item
* Second Item

Link:
The tutorials repository can be found https://github.com/devonfw-tutorials/tutorials/issues[here].

adaptTemplatesCobiGen

parameter

  • No parameters

example

adaptTemplatesCobiGen()

createDevon4ngProject

parameter

  1. Name of the Project.
  2. Path to where the Project should be created (relative to workspace). Folder should exist.
  3. (Optional) String array of parameters, according to https://angular.io/cli/new.

example

createDevon4ngProject("exampleAngularProject", "") Will create the angular project to the current workspace with the name exampleAngularProject.

createDevon4ngProject("exampleAngularProject", "projects", ["--verbose"]) Will create the angular project to the directory projects within the current workspace and adds more details to output logging.

Details

This command also works if the devonfw IDE is not installed, but then you have to make sure that the Angular cli is installed.

addSetupScript

parameter

  1. Path of the script (Linux). Relative to the playbook directory
  2. Path of the script (Windows). Relative to the playbook directory

example

addSetupScript("assets/createProjectScript.sh", "assets/createProjectScript.ps1")

openFile

parameter

  1. Path of the file to be opened (relative path to the workspace directory)

example

openFile("cobigenexample/core/src/main/java/com/example/application/cobigenexample/customermanagement/dataaccess/api/CustomerEntity.java")

Clone this wiki locally