Projects
A project is a place to separate management activity. All Rundeck activities occur within the context of a project. Multiple projects can be maintained on the same Rundeck server. Projects are independent from one another, so you can use them to organize unrelated systems within a single Rundeck installation. This can be useful for managing different teams, infrastructures, environments or applications.
Projects can be archived and imported to other Rundeck servers to help promote changes between environments.
A new installation will not contain any projects so Rundeck will present you with a dialog to create one.
Creating A Project
Creating a New Project: Setting the name
In the Execution History Clean Settings, you can set the length of time you would like to keep execution history:
Jobs are set to run automatically, this can be disabled as well as scheduling jobs can be disabled via the Execution Mode tab:
The user interface setting within the project allows for view settings such as the Job Group Expansion Level, Showing the Project Readme/Homepage, and the MOTD
Node Executor settings deal with how commands are executed on remote nodes, note there is a local setting to run rundeck strictly on the local machine, and the script execution setting which delegates command execution to an external script:
The File Copier is responsible for copying scripts to the remote nodes before they are executed, this means the scripts will be copied to the remote machine before being run (note the default locations for any files being copied is c:\windows\temp on windows systems and /tmp on linux based systems:
Git Configuration with Projects
Note with SCM Configurations there is an ability to both export jobs to a Git Repository and an Import setting for projects: Configuring these
Archiving a Project
Maybe a project needs to be archived. When creating an archive, there are some settings that can be modified to select just what is needed on the archive. Some of these include: Jobs/Executions/Configuration/Readme/MOTD/ACL Policies/SCM Configuration/Webhooks
On the other side of this Importing an Archive can also be done. Some settings to note when importing include: Preserving UUIDs on the imported Jobs, Importing Executions and History, The Project Configuration, Node Sources, ACL Policies, SCM Configuration, Referenced Job Validations, and Webhooks
Deleting a Project
Maybe you are done with the project, deleting a project can be done via the GUI via:
No Comments