A project is a top-level container within CloudBees Flow. Most information about software production processes, such as procedures, schedules, jobs, and workflows are contained within a project.
Projects let you create separate work areas for different purposes or groups of people so they do not interfere with each other.
For example, different projects can reuse the same names internally without conflict, and each project has its own access control that determines who can use and modify the project.
In a small organization, you might choose to keep all work in a single project, but in a large organization, you might want to use projects to organize information and simplify management.
Projects simplify sharing.
You can create library projects containing shared procedures and invoke these procedures from other projects. After creating a library project, you can copy it easily to other CloudBees Flow servers to create uniform processes across your organization.
CloudBees Flow includes the following projects:
EC-Utilities—Contains procedures that you can use to perform basic CloudBees Flow tasks.
Also, you can use these procedures as templates by copying them to another project and then modifying them for your purpose. By default, only the “admin” user has execute privileges on the EC-Utilities project. The admin user can enable privileges for additional users or groups.
EC-Examples—Contains templates for procedures that perform basic CloudBees Flow tasks.
CloudBees—Contains procedures to manage the ElectricSentry Sentry Monitor for schedules and also contains CloudBees Flow global reports.
Procedures in each of these projects are maintained by CloudBees.
You can create or edit a project through either the Deploy web UI or the Automation Platform web UI. For details, see