Actions for the gCubeActionExecutor pipeline.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Roberto Cirillo 834c72a24c add grep-log4j-core script 1 month ago
24-01-2021-AddLicenseToAllRepos Add messages to License action. 12 months ago
24-01-2021-CreateTestFile Test action to create and add a file. 1 year ago
27-01-2021-grepString add grep-log4j-core script 1 month ago
repos Upload files to 'repos' 3 months ago Fix typos. 11 months ago Add more comments. 10 months ago

Actions for the gCubeActions Pipeline

Container for Actions executed with the gCubeActionExecutor pipeline.


An Action is a script that is executed on a selected git repository. Every command in the Action must be written assuming the root folder of the repository as working folder.

Exit Code

An Action is successful if it returns 0 as exit code. Any code different from 0 makes the Action fails and halts the execution of the pipeline process.

An exit code can be returned at any point of the Action by invoking the exit code command. Unless exit is used, the exit code of the Action is the one returned by the last command of the Action.

List of Repositories

Each action is executed on a list of repositories. The expected format of the file with the list on repo name per file.

For example:


The URL of the Gitea organization where to find these repositories is passed as parameter of the gCubeActionExecutor pipeline.

How to Generate the List

The script can be executed any time to generate an up-to-date list of repositories in the gCubeSystem organization. If a different organization has to be scanned, we can easily change the script or make it parametric.

The output of the script is a file named gCubeSystem_all_sorted_$timestamp.txt. The list in the output file is alphabetically ordered.