Skip to content

Latest commit

 

History

History
82 lines (74 loc) · 3.83 KB

proc_creating-a-content-view.adoc

File metadata and controls

82 lines (74 loc) · 3.83 KB

Creating a Content View

Use this procedure to create a simple Content View. To use the CLI instead of the {ProjectWebUI}, see the CLI procedure.

Prerequisites

While you can stipulate whether you want to resolve any package dependencies on a Content View by Content View basis, you might want to change the default {Project} settings to enable or disable package resolution for all Content Views. For more information, see [Resolving_Package_Dependencies_{context}].

Procedure

  1. In the {ProjectWebUI}, navigate to Content > Lifecycle > Content Views.

  2. Click Create content view.

  3. In the Name field, enter a name for the view. {Project} automatically completes the Label field from the name you enter.

  4. In the Description field, enter a description of the view.

  5. In the Type field, select a Content view or a Composite content view.

  6. Optional: If you want to solve dependencies automatically every time you publish this Content View, select the Solve dependencies checkbox. Dependency solving slows the publishing time and might ignore any Content View filters you use. This can also cause errors when resolving dependencies for errata.

  7. Optional: If you want to designate this Content View for importing from an upstream server, select the Import only checkbox. Import-only content views cannot be published directly.

  8. Click Create content view.

Content View Steps

  1. Click Create content view to create the Content View.

  2. In the Repositories tab, select the repository from the Type list that you want to add to your Content View, select the checkbox next to the available repositories you want to add, then click Add repositories.

  3. Click Publish new version and in the Description field, enter information about the version to log changes.

  4. Optional: You can enable a promotion path by clicking Promote to Select a lifecycle environment from the available promotion paths to promote new version.

  5. Click Next.

  6. On the Review page, you can review the environments you are trying to publish.

  7. Click Finish.

    Note
    		 Remove and Delete are similar but the Delete option deletes an entire Content View and the versions associated with that lifecycle environment. The Remove option allows you to choose which version you want removed from the lifecycle environment.

You can view the Content View in the Content Views window. To view more information about the Content View, click the Content View name. To register a host to your Content View, see {ManagingHostsDocURL}Registering_Hosts_managing-hosts[Registering Hosts] in {ManagingHostsDocTitle}.

CLI procedure

  1. Obtain a list of repository IDs:

    # hammer repository list --organization "My_Organization"

  2. Create the Content View and add repositories:

    # hammer content-view create \
--description "My_Content_View" \
--name "My_Content_View" \
--organization "My_Organization" \
--repository-ids 1,2

    For the --repository-ids option, you can find the IDs in the output of the hammer repository list command.

  3. Publish the view:

    # hammer content-view publish \
--description "My_Content_View" \
--name "My_Content_View" \
--organization "My_Organization"

  4. Optional: To add a repository to an existing Content View, enter the following command:

    # hammer content-view add-repository \
--name "My_Content_View" \
--organization "My_Organization" \
--repository-id repository_ID

{ProjectServer} creates the new version of the view and publishes it to the Library environment.