DevOps Lifecycle Manager

Transcription

1 DevOps Lifecycle Manager version 17.4 Last generated: March 09, 2017

2 CollabNet, Inc. Copyright Information CollabNet, Inc. ("CollabNet") is committed to respecting others' intellectual property rights, and we ask users of our websites (collectively, the "Site") to do the same. CollabNet may, in its sole discretion, terminate the accounts or access rights of users who violate others' intellectual property rights. If you believe that your work has been copied in a way that constitutes copyright infringement on our Site, please deliver the following information to CollabNet's Copyright Agent: 1. An electronic or physical signature of the person authorized to act on behalf of the copyright owner; 2. A description of the copyrighted work that you claim has been infringed; 3. A description of where the material that you claim is infringing is located on our Site; 4. Your address, telephone number and address so that we can contact you; 5. A statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent or the law; and 6. A statement by you, made under penalty of perjury, that the information in your notice to us is accurate and that you are the copyright owner or authorized to act on the copyright owner's behalf. CollabNet's copyright agent for notice of claims of copyright infringement on our Site can be reached by sending an to copyright@collab.net or by mail as follows: CollabNet, Inc. Legal Department Attn: Copyright Agent 4000 Shoreline Court, Suite 300 South San Francisco, CA 94080

3 The Terms were last amended on March 28, 2012.

4 DevOps Lifecycle Manager User Guide PDF last generated: March 09, 2017 Table of Contents Getting Started Overview... 2 Installation Install the DevOps Lifecycle Manager Solution... 3 Setting Up the DevOps Lifecycle Manager Create Workflow Systems Add ActionHub/ActionFlow to TeamForge Projects Create Rules View Action Packs and Action History Work with DevOps Release Packaging ActionHub Admin UI Work with ActionDesigner Tag Archive s DevOps s ActionDesigner s ActionFlow s ActionHub s DevOps Installation s Setting Up DevOps s jmahendran@collab.net i

5 DevOps Lifecycle Manager 17.4 PDF last generated: March 09, 2017 DevOps Lifecycle Manager 17.4 Summary: CollabNet's DevOps Lifecycle Manager solution is here to improve application delivery through integration, automation and continuous feedback. It uses tools such as ActionHub and ActionFlow to create rules and workflow systems to invoke actions based on specific events in your software development life cycle. ActionHub/ActionFlow ActionHub is the next generation platform for integrating and automating software development tools used in the entire software development life cycle. These tools include planning, version control, continuous integration/build, code review, test, deployment, monitoring and more.the ActionHub platform is rules based, so the first thing you must do is create rules to invoke action based on your processes. A few examples of rules to drive process include invoking a build job in Jenkins based on a commit message to a specific branch in a repository, invoking a workflow in CollabNet ActionFlow to deploy a build based on a successful build message from a Jenkins job, and opening a defect in a project based on a health event from a monitoring tool like New Relic. ActionFlow works as the orchestrator on the TeamForge solution. It is integrated with TeamForge and connected on ActionHub for the creation of different workflows. The workflows fire actions that will do almost everything you need to automate your development environment. DevOps Lifecycle Manager User Guide 2

6 Install the DevOps Lifecycle Manager PDF last generated: March 09, 2017 Install the DevOps Lifecycle Manager Summary: ActionHub, a component of CollabNet's DevOps solution, is the next generation platform for integrating and automating software development tools used in the entire software development life cycle. ActionFlow, another piece of CollabNet's DevOps solution, works as the orchestrator on the DevOps solution. ActionFlow is integrated with TeamForge and connected on ActionHub for the creation of different workflows. The workflows fire actions that will do almost everything you need to automate your development environment. Before you begin Before you begin, you must have TeamForge and EventQ 17.1 (or later) installed and running. In this setup, it is assumed that you have TeamForge Application (including the database and datamart) and EventQ (EventQ Application, MongoDB, and RabbitMQ) running on two separate servers. See TeamForge installation requirements and EventQ installation requirements to know what it takes to run TeamForge and EventQ. ActionHub is installed on the TeamForge Application Server and ActionFlow is installed on a seprate server. Also see Port Requirements. Install ActionHub on the EventQ Server 1. Log on to the EventQ Server and download the ActionHub installer RPM: actionhub_installer-17.1-xx.x86_64.rpm. 2. Install ActionHub. Note: Before installing ActionHub, ensure that the EventQ services are up and running. DevOps Lifecycle Manager User Guide 3

7 Install the DevOps Lifecycle Manager PDF last generated: March 09, 2017 /etc/init.d/eventq status yum install actionhub_installer 3. Run the enableactionhub utility. This is to create the RabbitMQ account for ActionHub to use. /opt/collabnet/teamforge/bin/enableactionhub Install ActionHub on the TeamForge Application Server 1. Log on to the TeamForge Application Server and download the ActionHub installer RPM: CN-actionhub-17.1.X.XX.rpm. 2. Install ActionHub. yum install CN-actionhub 3. Run the enableactionhub utility. This is to update the site-options.conf file with the ActionHub services and database information. /opt/collabnet/teamforge/bin/enableactionhub 4. Make sure the PUBLIC_FQDN site-options.conf token is set as follows: localhost:public_fqdn = <IP address of TeamForge Application Server> 5. Stop TeamForge. /opt/collabnet/teamforge/bin/teamforge stop DevOps Lifecycle Manager User Guide 4

8 Install the DevOps Lifecycle Manager PDF last generated: March 09, Deploy services. /opt/collabnet/teamforge/bin/teamforge provision Note: It will take a few minutes for TeamForge to start up. 7. Bootstrap ActionHub. /opt/collabnet/teamforge/bin/teamforge bootstrap -s actionhub 8. Bootstrap ActionHub database. /opt/collabnet/teamforge/bin/teamforge bootstrap -s actionhu b-database 9. Start TeamForge. /opt/collabnet/teamforge/bin/teamforge start 10. Open the site in your browser ( and verify that TeamForge is up and running. Enter the TeamForge DevOps license key 1. Enter the DevOps license key. Select Projects > License Info, click Enter License Key, paste the TeamForge DevOps license key and click Save. Note: Click Get License Key if you want to get the TeamForge DevOps license key. You can now assign the DevOps license to users. DevOps Lifecycle Manager User Guide 5

9 Install the DevOps Lifecycle Manager PDF last generated: March 09, Assign DevOps license to the TeamForge Administrator. a. Select Projects > Users. b. Select TeamForge Administrator. c. Click Edit. d. Select DevOps from the License Type drop-down list. e. Click Update. This concludes setting up ActionHub with TeamForge. You can now add ActionHub to projects (page 14), create and integrate new workflow systems (page 12) and create new rules (page 15) to automate your processes. Install ActionFlow and ActionDesigner: Do this on a separate server Requirements A workflow system created for ActionFlow in TeamForge. If not created already, see Create Workflow Systems (page 12). WorkFlow Queue, Action Queue, AMQP User and AMQP Password for ActionFlow. See Create Workflow Systems (page 12). Hardware/Software requirements for ActionFlow Server: RHEL/ CentOS 7.x, Quad-core CPU with 16GB RAM, 40GB storage (recommended EC2: m4.xlarge). DevOps Lifecycle Manager User Guide 6

10 Install the DevOps Lifecycle Manager PDF last generated: March 09, 2017 Downloaded ActionFlow, ActionDesigner installer and CN-st2web RPMs. Node.js v6.x (for ActionDesigner) 1. Log on to the TeamForge Application Server, copy the values of WorkFlow Queue, Action Queue, AMQP User and AMQP Password for ActionFlow from the UI and keep them handy. For more information, see Create Workflow Systems (page 12). 2. Log on to the ActionFlow Server. 3. Install the ActionFlow RPM. yum install -y CN-actionflowst xx.rpm 4. Update the ActionFlow site-options.conf file with ActionFlow username and password. Note: You will be using this username and password to log on to ActionFlow post installation. vi /opt/stackstorm/installer/site-options.conf ACTIONFLOW_USER=<username> ACTIONFLOW_PASSWORD=<password> ST2_HOSTNAME=<The IP Address or fully qualified domain name of the ST2 host> EVENTQ_HOST=<IP where TeamForge is hosted or IP where eventq is hosted if EventQ is running on a separate server> DevOps Lifecycle Manager User Guide 7

11 Install the DevOps Lifecycle Manager PDF last generated: March 09, 2017 WORKFLOW_QUEUE=<ws.plug#### copied previously from TeamForge> ACTION_QUEUE=<actions.plug#### copied previously from TeamForge> AMQP_USER=<AMQP user copied previously from TeamForge server> AMQP_PASSWORD=<AMQP password copied previously from TeamForge server> 5. Run the ActionFlowSt2Install.sh script../actionflowst2install.sh 6. Once the installation is complete, you will be prompted to press Enter to restart the server. 7. Install the ActionDesigner RPM. yum install -y CN-actiondesigner xx.rpm 8. Edit the config.js file with the required information for ActionDesigner to connect with ActionFlow. vi /opt/actiondesigner/config.js "use strict"; var config = { "workflowhost": "<the URL for the ActionFlow instance>" }; Object.defineProperty(exports, " esmodule", { value: true }); exports.default = config; 9. Start ActionDesigner. DevOps Lifecycle Manager User Guide 8

12 Install the DevOps Lifecycle Manager PDF last generated: March 09, 2017 systemctl start actiondesigner 10. Run the CN-st2web RPM. rpm -ivh --force --nodeps --replacepkgs --replacefiles CN-st2 web x.rpm 11. Configure SSL for ActionFlow, if required. For more information, see StackStorm Authentication. In /etc/ssl/st2/ copy the.crt file to be used as st2.crt. In /etc/ssl/st2/ copy the.key file to be used as st2.key. Edit the /etc/st2/st2.conf file. Look for the use_ssl setting, set it to True and append the path to cert and key files as shown below. use_ssl = True cert = /etc/ssl/st2/st2.crt key =/etc/ssl/st2/st2.key 12. Restart Stackstorm and Nginx services. st2ctl restart service nginx restart 13. Configure SSL for ActionDesigner, if required. In /opt/actiondesigner/ssl/ copy the.crt file to be used as ca.crt. In /opt/actiondesigner/ssl/ copy the.crt file to be used as server.crt. In /opt/actiondesigner/ssl/ copy the.key file to be used as server.key. DevOps Lifecycle Manager User Guide 9

13 Install the DevOps Lifecycle Manager PDF last generated: March 09, Verify ActionFlow installation. a. Add ActionFlow to TeamForge projects. See Add ActionHub/ ActionFlow to TeamForge projects (page 14). b. Create a test rule targetting ActionFlow and save the rule. See Create Rules. For example, create a test rule as follows: Rule Name: TestActionFlow Rule Source: Work Item > Defects Target: ActionFlow Criteria: leave defaults Action: helloworld Parameters: blank Save the rule. c. Go to Trackers > Defects and add a comment to a defect. d. Select ActionHub from the tools menu, go to Rule Execution History tab and verify that the test rule has been executed. e. Select ActionFlow from the tools menu and log on to ActionFlow. f. In the History tab, you should see two processes: actionhub.msg_handler and collabnet-generic-flows.helloworld. Watch for the status circle in front of these processes to turn green indicating that the processes ran successfully. 15. Verify ActionDesigner installation. Open the following URL in a browser: (for example, and log on to ActionDesigner DevOps Lifecycle Manager User Guide 10

14 Install the DevOps Lifecycle Manager PDF last generated: March 09, 2017 using your ActionFlow credentials. DevOps Lifecycle Manager User Guide 11

15 Create Workflow Systems PDF last generated: March 09, 2017 Create Workflow Systems Summary: Workflow systems, like ActionFlow and TeamForge Action Server, monitor the system for certain conditions defined in one or more rules. When the condition set in a rule match the system conditions, the associated rule is executed. The Actions defined in the rule can then perform a workflow that in turn can consist of a sequence of predefined Actions. Follow these instructions to set up integrations with such workflow systems. 1. Log on to TeamForge web UI with site administrator credentials. 2. Select My Workspace > Admin. 3. Select Projects > Integrated Apps. 4. Select ActionHub and click Administer. 5. Select Workflow Systems from the Administration pane. 6. Click Create. The Create WorkFlow Integration page appears. 7. Type the workflow system name and base URL (the URL where the workflow system is hosted. Use if using SSL). 8. Click Create. DevOps Lifecycle Manager User Guide 12

16 Create Workflow Systems PDF last generated: March 09, 2017 Important: Once the workflow system is created in TeamForge, copy the values of WorkFlow Queue, Action Queue, AMQP_User and AMQP_Password for the workflow system you just created and keep it handy to be used during installation and configuration of the workflow system, for example installation of ActionFlow. DevOps Lifecycle Manager User Guide 13

17 Add ActionHub/ActionFlow to TeamForge projects PDF last generated: March 09, 2017 Add ActionHub/ActionFlow to TeamForge projects Summary: Log on to TeamForge as a Project Admin, create a TeamForge project, and add ActionHub as a tool to that project. You can also add ActionHub to existing TeamForge projects. 1. Select Project Home > Project Admin. 2. Select Tools from the Project Admin menu. 3. In Project Tools tab, click Add Tool. 4. Select ActionHub or ActionFlow from the Select Tool Type drop-down list and Save. Now, you should be able to view ActionHub/ActionFlow as one of the tools in the TeamForge tools menu. 5. Select Project Home > ActionHub or Project Home > ActionFlow. The Rules page appears. You can now create rules to invoke actions based on specific events. DevOps Lifecycle Manager User Guide 14

18 Create Rules PDF last generated: March 09, 2017 Create Rules Summary: The ActionHub/ActionFlow platforms are rule-based, so the first thing you must do is create rules to invoke action based on your processes. A few examples of rules to drive process include invoking a build job in Jenkins based on a commit message to a specific branch in a repository, invoking a workflow in CollabNet ActionFlow to deploy a build based on a successful build message from a Jenkins job, and opening a defect in a project based on a health event from a monitoring tool like New Relic. You can create simple rules that check for one particular condition or complex nested rules that have more than one condition to check. Create simple rules with just one condition 1. Log on to TeamForge and select a project from the menu. 2. From the TeamForge tools menu, choose Project Home > ActionHub or Project Home > ActionFlow. The Rules page appears. 3. In the Rules section, click Create. The Create Rule page appears. DevOps Lifecycle Manager User Guide 15

19 Create Rules PDF last generated: March 09, In the Rule Name field, enter the name given to the rule that will be displayed in the rules list and in notifications generated by the rule. Enter meaningful attributes into this field to describe what the rule does. This will make it easier to understand in lists and notifications. 5. For the Rule Enabled option, click the checkbox to enable or disable the rule. Disabling a rule prevents it from being processed by the ActionHub rules engine. 6. In the Rule Description field, enter a detailed description describing the purpose of the rule. Include as much detail as possible to help another person understand the rule. For example, the description may include details about the parameters defined for the action on the target system. 7. Click Source, select the source from where the event will be generated and click Save. The SOURCE page shows a list of all sources defined in TeamForge EventQ. These source systems generate events which may match the rule being defined. Selecting the source also DevOps Lifecycle Manager User Guide 16

20 Create Rules PDF last generated: March 09, 2017 tells the editor the type of event generated by the system such as commit, workitem, build, deploy, review, health and more. This allows the editor to understand the format of the message and make it easy to create the criteria for the rule. 8. In the Criteria field, define the criteria for what events should match the rule. When a rule is first created it has a default criteria of Matches Any condition. This means it will match any event generated by the source system. To modify the condition, click the Matches Any link and select Edit Condition from the menu. The Add Condition dialog box appears allowing you to modify the condition. a. Select a message property that should be evaluated. The Property list displays a list of all properties defined for the message type specified by the Source system. For example, a source control system will show properties for a commit message. A tracker system will show properties for a work item message. b. From the Operator list, select the operator that will determine how DevOps Lifecycle Manager User Guide 17

21 Create Rules PDF last generated: March 09, 2017 the property will be evaluated. c. In the Value field, specify the value to evaluate against the property. d. Click Save. Create complex rules with multiple nested conditions If you want to create a criteria that evaluates more than one condition such as (work_item.created_by Contains user123 AND work_item.updated_by Contains userqa) OR (work_item.status_id Equals Ready for Deploy), you can create a nested criteria as follows. To create a rule that checks for more than one condition, click the Matches Any link and select Convert to Group from the shortcut-menu. You now have two Matches Any conditions linked together by an AND operator. You can toggle between AND and OR operators by clicking the AND or OR operator. Now, you can modify the conditions by clicking the Matches Any link and selecting Edit Condition from the menu. The Add Condition dialog box appears allowing you to modify the condition. Click Add New to add (nest) more conditions. 1. From the TARGET drop-down list, select the target system. DevOps Lifecycle Manager User Guide 18

22 Create Rules PDF last generated: March 09, 2017 The TARGET drop-down list shows a list of all target workflow systems. Selecting a target system populates the Action dropdown list with actions available for the event type defined by the Source system. 2. From the Action drop-down list, select the action to take for the defined event. The Action drop-down list shows all available actions on the target workflow system based on the event type of the Source system. Selecting an action populates the PARAMETERS table with all the available parameters for the action. Refer to the documentation for the action in the target workflow system for purpose of each parameter. If the selected action requires input, the PARAMETERS table will be populated with the required parameters. 3. In the PARAMETERS table, specify the appropriate value for each parameter. As each action is different, refer to the documentation for the action in the target workflow system for the purpose of each input parameter. 4. Click Save. The new rule is created. Create as many rules you want. You can now go to the Rule Execution History tab (Project Home > ActionHub) to view the history of rules that are executed. Create and execute Manual Rules The Manual Rule feature allows you to create rules that will be manually executed on demand from the Release Console page. DevOps Lifecycle Manager User Guide 19

23 Create Rules PDF last generated: March 09, From the Project Home menu, choose ActionHub. 2. Click the Create Rule button. 3. Enter all appropriate informaiton about the rule you wish to create while clicking Manual from the Source list. 4. In the Rule Parameters section, enter the Environment ID corresponding with the environment that packages should be deployed to when this rule is executed. 5. On the Release Console page, select the radio button next to the package you want to execute a Manual Rule for. 6. Click the button corresponding to the Manual Rule that you would like to execute. Audit information for rules Within ActionHub, you can view a rule s general information, scope, change log and the rule execution history. From the Project Home menu, choose ActionHub and select a rule. General tab: View general rule information. Scope tab: View the scope of the rule. DevOps Lifecycle Manager User Guide 20

24 Create Rules PDF last generated: March 09, 2017 Execution History tab: Lists the rule execution history. Change Log tab: Shows the change log for a rule. DevOps Lifecycle Manager User Guide 21

25 View Action Packs and Action History PDF last generated: March 09, 2017 View Action Packs and Action History Summary: Log on to ActionFlow to view the available Action Packs and historical information of actions. The History page lists all the actions that have a history sorted by execution date. Action History Log on to ActionFlow. The History page is displayed. DevOps Lifecycle Manager User Guide 22

26 View Action Packs and Action History PDF last generated: March 09, 2017 You can sort the list by Status, Action, Trigger Type, or Rule. To view general information for an action, select the date the action ran, then click the action. The General tab shows the following information: Status - the current status of the action (Succeeded or Failed) Execution ID- the unique ID assigned to the execution of the action Trace Tag - the unique tag attached to the action for history filtering Started - the time the action launched DevOps Lifecycle Manager User Guide 23

27 View Action Packs and Action History PDF last generated: March 09, 2017 Finished - the time the action completed Execution Time - the time the action was executed Action Output - the output received from the action DevOps Lifecycle Manager User Guide 24

28 Work with DevOps Release Packaging PDF last generated: March 09, 2017 Work with DevOps Release Packaging Summary: A package is a folder into which one or more related releases are published. For example, you might create a package to represent a product deliverable or major component. A package must exist before you create the releases and individual files that will go into the package. Before you can define an application, environment and release package, you must install a valid TeamForge license, create a TeamForge Project and Planning Folder. 1. Install TeamForge license. See: How do TeamForge licenses work? Supply your TeamForge license key from Teamforge user interface Supply your TeamForge license key as a text file 2. Create a TeamForge project. See Create a TeamForge project. 3. Create a Planning Folder. See Create a planning folder. Define the Application 1. From My Workspace, navigate to your project. 2. Choose Project Home > Project Admin. The Project Settings page appears. 3. From the Project Admin menu, choose Application Settings. The Applications Settings page appears. DevOps Lifecycle Manager User Guide 25

29 Work with DevOps Release Packaging PDF last generated: March 09, Click the Statuses tab to define the application status. 5. Click Create. 6. Click Create New. The Create Application page appears. 7. Enter a name to identify this application. 8. Optionally, specify a description of this application. 9. Select the status of the application. Development The status is currently in development New Status Select to add a new status DevOps Lifecycle Manager User Guide 26

30 Work with DevOps Release Packaging PDF last generated: March 09, 2017 Add New Status Select to create a new status 10. Select FRS or Planning Folder. 11. Select the Planning Folder or File Package. This list populates depending upon the selection of the planning model. 12. Click Save. The View Application page appears. This page contains three tabs: Application Attributes, Components and Package Attributes. 13. Click the appropriate tab, then click Add to add a row. 14. Enter the required information, then click Save. 15. Repeat these steps to add a new component and a new attribute. Define the Environment Infrastructure 1. From the Project Admin menu, choose Environment Settings. The Environment Settings page appears. 2. Click the Types tab to define the environment types. 3. Click New Type. The Add New Environment Type dialog appears. DevOps Lifecycle Manager User Guide 27

31 Work with DevOps Release Packaging PDF last generated: March 09, Enter the name for the type, choose the display order and then choose the class. 5. Click Add New Type. The new type appears on the Types tab. 6. Click the Environments tab. 7. Click New Environment. The Add New Environment page appears. 8. Enter a name for the new environment, then select the type (user defined). DevOps Lifecycle Manager User Guide 28

32 Work with DevOps Release Packaging PDF last generated: March 09, Click Save. The new environment is added. Create a Package 1. Choose Project Home > Release Console. The Release Console page appears. 2. Click CreatePackage. The Create Package page appears. 3. Enter a title for the new package. 4. Choose an application you want associated with the new package. 5. Select the status of the application. Development The status is currently in development DevOps Lifecycle Manager User Guide 29

33 Work with DevOps Release Packaging PDF last generated: March 09, 2017 New Status Select to add a new status Add New Status Select to create a new status 6. Select the appropriate release folder. This list populates depending upon the selection of the planning mode. 7. Optionally specify a description of this package. 8. Click Save. DevOps Lifecycle Manager User Guide 30

34 ActionHub Admin UI PDF last generated: March 09, 2017 ActionHub Admin UI Summary: You can use the ActionHub Admin user interface to verify the Daemon and Workflow System statuses. Select Project Home > ActionHub and click Admin. DevOps Lifecycle Manager User Guide 31

35 Work with ActionDesigner PDF last generated: March 09, 2017 Work with ActionDesigner Summary: CollabNet ActionDesigner acts as the workflow editor for ActionFlow. You can create new workflows, edit and run existing workflows in CollabNet ActionDesigner. It has a yaml editor that lets you edit a particular workflow's yaml file. 1. Open the following ActionDesigner URL in a browser: actiondesigner (for example, actiondesigner) and log on to ActionDesigner using your ActionFlow credentials. 2. Edit or run an existing workflow. a. Click the workflow you want to edit. ActionDesigner s yaml editor opens up. b. Edit the workflow and click Save. c. Click Run to run the workflow. 3. Add a new workflow. DevOps Lifecycle Manager User Guide 32

36 Work with ActionDesigner PDF last generated: March 09, 2017 a. Click the + button. The Workflow dialog box appears. b. Select a pack from the Pack drop-down list. c. Type a name and description for the workflow. d. Click the + button to add parameters. e. Type a name, description, Enum, and default value for the parameter, and select its type from the drop-down list. f. Add as many parameters as you want and click Save. DevOps Lifecycle Manager User Guide 33

37 DevOps pages PDF last generated: March 09, 2017 DevOps pages The following pages and posts are tagged with devops Title Type Excerpt Work with ActionDesigner (page 32) Add ActionHub/ActionFlow to Team- Forge projects (page 14) ActionHub Admin UI (page 31) Work with DevOps Release Packaging (page 25) Create Rules (page 15) Create Workflow Systems (page 12) View Action Packs and Action History (page 22) CollabNet ActionDesigner acts as the workflow editor for ActionFlow. You can create new workflows, edit and run existing workflows in CollabNet ActionDesigne... Log on to TeamForge as a Project Admin, create a TeamForge project, and add ActionHub as a tool to that project. You can also add ActionHub to existing TeamF... You can use the ActionHub Admin user interface to verify the Daemon and Workflow System statuses. A package is a folder into which one or more related releases are published. For example, you might create a package to represent a product deliverable or ma... The ActionHub/ActionFlow platforms are rulebased, so the first thing you must do is create rules to invoke action based on your processes. A few examples of... Workflow systems, like ActionFlow and Team- Forge Action Server, monitor the system for certain conditions defined in one or more rules. When the condition set... Log on to ActionFlow to view the available Action Packs and historical information of actions. The History page lists all the actions that have a history sor... DevOps Lifecycle Manager User Guide 34

38 DevOps pages PDF last generated: March 09, 2017 Title Type Excerpt DevOps Lifecycle Manager 17.4 (page 2) Install the DevOps Lifecycle Manager (page 3) CollabNet's DevOps Lifecycle Manager solution is here to improve application delivery through integration, automation and continuous feedback. It uses tools... ActionHub, a component of CollabNet's DevOps solution, is the next generation platform for integrating and automating software development tools used in the... DevOps Lifecycle Manager User Guide 35

39 ActionDesigner pages PDF last generated: March 09, 2017 ActionDesigner pages The following pages and posts are tagged with action_designer Title Type Excerpt Work with ActionDesigner (page 32) Install the DevOps Lifecycle Manager (page 3) CollabNet ActionDesigner acts as the workflow editor for ActionFlow. You can create new workflows, edit and run existing workflows in CollabNet ActionDesigne... ActionHub, a component of CollabNet's DevOps solution, is the next generation platform for integrating and automating software development tools used in the... DevOps Lifecycle Manager User Guide 36

40 ActionFlow pages PDF last generated: March 09, 2017 ActionFlow pages The following pages and posts are tagged with action_flow Title Type Excerpt Add ActionHub/ActionFlow to Team- Forge projects (page 14) Work with DevOps Release Packaging (page 25) Create Rules (page 15) Create Workflow Systems (page 12) View Action Packs and Action History (page 22) DevOps Lifecycle Manager 17.4 (page 2) Install the DevOps Lifecycle Manager (page 3) Log on to TeamForge as a Project Admin, create a TeamForge project, and add ActionHub as a tool to that project. You can also add ActionHub to existing TeamF... A package is a folder into which one or more related releases are published. For example, you might create a package to represent a product deliverable or ma... The ActionHub/ActionFlow platforms are rulebased, so the first thing you must do is create rules to invoke action based on your processes. A few examples of... Workflow systems, like ActionFlow and Team- Forge Action Server, monitor the system for certain conditions defined in one or more rules. When the condition set... Log on to ActionFlow to view the available Action Packs and historical information of actions. The History page lists all the actions that have a history sor... CollabNet's DevOps Lifecycle Manager solution is here to improve application delivery through integration, automation and continuous feedback. It uses tools... ActionHub, a component of CollabNet's DevOps solution, is the next generation platform for integrating and automating software development tools used in the... DevOps Lifecycle Manager User Guide 37

41 ActionFlow pages PDF last generated: March 09, 2017 DevOps Lifecycle Manager User Guide 38

42 ActionHub pages PDF last generated: March 09, 2017 ActionHub pages The following pages and posts are tagged with action_hub Title Type Excerpt Add ActionHub/ActionFlow to Team- Forge projects (page 14) ActionHub Admin UI (page 31) Work with DevOps Release Packaging (page 25) Create Rules (page 15) Create Workflow Systems (page 12) View Action Packs and Action History (page 22) DevOps Lifecycle Manager 17.4 (page 2) Log on to TeamForge as a Project Admin, create a TeamForge project, and add ActionHub as a tool to that project. You can also add ActionHub to existing TeamF... You can use the ActionHub Admin user interface to verify the Daemon and Workflow System statuses. A package is a folder into which one or more related releases are published. For example, you might create a package to represent a product deliverable or ma... The ActionHub/ActionFlow platforms are rulebased, so the first thing you must do is create rules to invoke action based on your processes. A few examples of... Workflow systems, like ActionFlow and Team- Forge Action Server, monitor the system for certain conditions defined in one or more rules. When the condition set... Log on to ActionFlow to view the available Action Packs and historical information of actions. The History page lists all the actions that have a history sor... CollabNet's DevOps Lifecycle Manager solution is here to improve application delivery through integration, automation and continuous feedback. It uses tools... DevOps Lifecycle Manager User Guide 39

43 ActionHub pages PDF last generated: March 09, 2017 Title Type Excerpt Install the DevOps Lifecycle Manager (page 3) ActionHub, a component of CollabNet's DevOps solution, is the next generation platform for integrating and automating software development tools used in the... DevOps Lifecycle Manager User Guide 40

44 DevOps installation pages PDF last generated: March 09, 2017 DevOps installation pages The following pages and posts are tagged with devops_installation Title Type Excerpt Install the DevOps Lifecycle Manager (page 3) ActionHub, a component of CollabNet's DevOps solution, is the next generation platform for integrating and automating software development tools used in the... DevOps Lifecycle Manager User Guide 41

45 Setting up DevOps pages PDF last generated: March 09, 2017 Setting up DevOps pages The following pages and posts are tagged with setting_up_devops Title Type Excerpt Work with ActionDesigner (page 32) Add ActionHub/ActionFlow to Team- Forge projects (page 14) Work with DevOps Release Packaging (page 25) Create Rules (page 15) Create Workflow Systems (page 12) View Action Packs and Action History (page 22) CollabNet ActionDesigner acts as the workflow editor for ActionFlow. You can create new workflows, edit and run existing workflows in CollabNet ActionDesigne... Log on to TeamForge as a Project Admin, create a TeamForge project, and add ActionHub as a tool to that project. You can also add ActionHub to existing TeamF... A package is a folder into which one or more related releases are published. For example, you might create a package to represent a product deliverable or ma... The ActionHub/ActionFlow platforms are rulebased, so the first thing you must do is create rules to invoke action based on your processes. A few examples of... Workflow systems, like ActionFlow and Team- Forge Action Server, monitor the system for certain conditions defined in one or more rules. When the condition set... Log on to ActionFlow to view the available Action Packs and historical information of actions. The History page lists all the actions that have a history sor... DevOps Lifecycle Manager User Guide 42