diff --git a/docs/images/hello-world_deployments.png b/docs/images/hello-world_deployments.png index 0d790bc..cb0f5be 100644 Binary files a/docs/images/hello-world_deployments.png and b/docs/images/hello-world_deployments.png differ diff --git a/docs/images/hello-world_john.png b/docs/images/hello-world_john.png index 4dcf31c..d63f91b 100644 Binary files a/docs/images/hello-world_john.png and b/docs/images/hello-world_john.png differ diff --git a/docs/images/openshift_online_console.png b/docs/images/openshift_online_console.png deleted file mode 100644 index b1d622c..0000000 Binary files a/docs/images/openshift_online_console.png and /dev/null differ diff --git a/docs/images/openshift_online_deployments.png b/docs/images/openshift_online_deployments.png new file mode 100644 index 0000000..6cb0fad Binary files /dev/null and b/docs/images/openshift_online_deployments.png differ diff --git a/docs/images/oso_projects.png b/docs/images/oso_projects.png index 4b9ec64..8bdf59a 100644 Binary files a/docs/images/oso_projects.png and b/docs/images/oso_projects.png differ diff --git a/docs/images/pipeline_firstrun.png b/docs/images/pipeline_firstrun.png index ec991ee..94add22 100644 Binary files a/docs/images/pipeline_firstrun.png and b/docs/images/pipeline_firstrun.png differ diff --git a/docs/images/pipeline_jenkins.png b/docs/images/pipeline_jenkins.png index 3397340..5ca2485 100644 Binary files a/docs/images/pipeline_jenkins.png and b/docs/images/pipeline_jenkins.png differ diff --git a/docs/images/proj_gh.png b/docs/images/proj_gh.png index 9959e77..4dd149a 100644 Binary files a/docs/images/proj_gh.png and b/docs/images/proj_gh.png differ diff --git a/docs/images/promote.png b/docs/images/promote.png index 6a1ccd8..69e8ea9 100644 Binary files a/docs/images/promote.png and b/docs/images/promote.png differ diff --git a/docs/images/rollout_to_run.png b/docs/images/rollout_to_run.png index 5cd687d..bfc792d 100644 Binary files a/docs/images/rollout_to_run.png and b/docs/images/rollout_to_run.png differ diff --git a/docs/images/vertx_stage.png b/docs/images/vertx_stage.png index aa1e8c3..10f8b02 100644 Binary files a/docs/images/vertx_stage.png and b/docs/images/vertx_stage.png differ diff --git a/docs/topics/hello_world_developers.adoc b/docs/topics/hello_world_developers.adoc index 7026474..c44cf3a 100644 --- a/docs/topics/hello_world_developers.adoc +++ b/docs/topics/hello_world_developers.adoc @@ -9,19 +9,19 @@ include::modules/about_application_codebases.adoc[leveloffset=+1] include::modules/creating_new_application.adoc[leveloffset=+1] -include::modules/about_stage_run.adoc[leveloffset=+1] +include::modules/about_pipelines_stage_and_run.adoc[leveloffset=+1] -include::modules/working_with_pipelines.adoc[leveloffset=+1] +include::modules/reviewing_your_staged_application.adoc[leveloffset=+1] -include::modules/viewing_build_pipeline_oso.adoc[leveloffset=+1] +include::modules/approving_your_application.adoc[leveloffset=+1] -include::modules/approving_build_pipeline.adoc[leveloffset=+1] +include::modules/viewing_build_pipeline_logs.adoc[leveloffset=+1] -include::modules/optional_detailed_views.adoc[leveloffset=+1] +include::modules/viewing_codebase_github.adoc[leveloffset=+1] -include::modules/viewing_project_github.adoc[leveloffset=+1] +include::modules/viewing_application_deployment_details.adoc[leveloffset=+1] -include::modules/viewing_projects_oso.adoc[leveloffset=+1] +include::modules/viewing_oso_projects.adoc[leveloffset=+1] include::modules/about_workspaces.adoc[leveloffset=+1] diff --git a/docs/topics/modules/about_pipelines.adoc b/docs/topics/modules/about_pipelines.adoc index 026ff3e..636707c 100644 --- a/docs/topics/modules/about_pipelines.adoc +++ b/docs/topics/modules/about_pipelines.adoc @@ -3,4 +3,4 @@ _Pipelines_ define how your application is deployed. Each pipeline has multiple stages with a varying set of capabilities. They are crucial to ensure a continuous delivery system that test and deploy the code at each step to provide feedback to the user. Examples of such steps are unit testing, performance, integration, and deployment. Each step of the pipeline implements a different level of testing and deployment tasks, provides results, and then passes the code on to the next step. -In {osio}, you configure a pipeline build when creating or importing a project. The pipeline build is triggered when a collaborator commits a change to the code repository. +In {osio}, you initiate a pipeline build when creating or importing a project. The pipeline build is triggered when a collaborator commits a change to the code repository. diff --git a/docs/topics/modules/about_pipelines_stage_and_run.adoc b/docs/topics/modules/about_pipelines_stage_and_run.adoc new file mode 100644 index 0000000..35ed19e --- /dev/null +++ b/docs/topics/modules/about_pipelines_stage_and_run.adoc @@ -0,0 +1,11 @@ +[id="about_pipelines_stage_run"] += About pipelines and the stage and run environments + +When you create a codebase, a pipeline build is initiated. Pipelines are automated, continuous integration and deployment processes, powered by Jenkins, which define how your application is deployed. + +The free OpenShift Online Starter subscription, included with your {osio} subscription, provides two environments named _Stage_ and _Run_ to deploy your applications. + +Initially, the build pipeline deploys the application to _Stage_, which is accessible to stakeholders for review through a public URL provided by OpenShift Online. If approved and promoted, the pipeline deploys it to the _Run_ environment. This simulates the workflow of pushing an application to a staging environment and reviewing it, before promoting it to production. + +The _Run_ environment is similar to a production environment but is another staging area. The reason _Run_ is not named _Production_ is that the OpenShift Online Starter subscription does not support running production applications. +//See link:https://www.openshift.com/pricing/index.html[purchasing an OpenShift Online Pro subscription] for information about support for running production applications. diff --git a/docs/topics/modules/about_stage_run.adoc b/docs/topics/modules/about_stage_run.adoc deleted file mode 100644 index 1c87f5f..0000000 --- a/docs/topics/modules/about_stage_run.adoc +++ /dev/null @@ -1,11 +0,0 @@ -[id="about_stage_run"] -= About the stage and run environments - -Next, you will learn about pipelines and staging environments in {osio}. After you create or add an application to your space, a pipeline is created to publish your application. - -When you get an {osio} subscription, you also get an OpenShift Online Starter subscription, which includes two environments named *Stage* and *Run* to deploy your applications. Initially, applications deploy to *Stage*, which is accessible to stakeholders for review using a public URL. If approved and promoted, the application deploys to *Run*, which is similar to a production environment but is another staging area. - -The reason *Run* is not named *Production* is that the OpenShift Online Starter subscription does not support running production applications. Currently, we recommend using OpenShift Online with {osio} and not OpenShift Online Pro. -//See link:https://www.openshift.com/pricing/index.html[purchasing an OpenShift Online Pro subscription] for information about support for running production applications. - -{osio} includes a *Stage* and *Run* environment to allow developers to experience the modern workflow of pushing an application to a staging environment before production. As a result, *Run* is a pseudo-production environment for educational purposes. diff --git a/docs/topics/modules/approving_build_pipeline.adoc b/docs/topics/modules/approving_build_pipeline.adoc deleted file mode 100644 index 50cccd6..0000000 --- a/docs/topics/modules/approving_build_pipeline.adoc +++ /dev/null @@ -1,43 +0,0 @@ -[id="approving_build_pipeline"] -= Approving the build pipeline - -Several minutes after starting, your build pipeline is ready to be promoted to _Stage_. - -The build pipeline includes steps for a _Stage_ build and a _Run_ build. _Stage_ is a production staging area to review and test your application before finalizing it and deploying the build on _Run_. - -To stage your application and review it on _Stage_: - -. If you are not on the *Pipelines* view, click *Create* from the options at the top of the screen and then click *Pipelines*. -. Click the icon (image:rollout_icon.png[title="Rollout"]) next to *Rollout to Stage* in the displayed pipeline. OpenShift Online provides this public URL to access the staged quickstart application. -+ -image::rollout_stage.png[Rollout to stage] -+ -. In a new browser tab, the HTTP Booster application runs on _Stage_. The Vert.x HTTP booster quickstart produces a simple API behind a REST endpoint over HTTP with a minimalist user interface. -+ -image::vertx_stage.png[Test the Application] -+ -NOTE: If the application does not load, see <> for troubleshooting information. -+ -. In the application, enter a name in the *Name* field and click btn:[Invoke] to test the application. The *Result* field displays the JSON result returning -from the API. -+ -image::hello-world_john.png[Test the Application] - -If the quickstart application on the _Stage_ build runs as expected, return to the {osio} browser tab and promote your application and build on _Run_: - -. Return to the {osio} tab which displays the *Pipeline* view. -. Click btn:[Input Required] at the *Approve* stage of the pipeline. -+ -image::pipeline_firstrun.png[Input Required] -+ -. Click btn:[Promote] to promote the build from the _Stage_ environment to the _Run_ environment. The rollout process from _Stage_ to _Run_ requires several minutes. -+ -image::promote.png[Promote build] -+ -. Optionally, click *Build #1* to view the detailed progress in the OpenShift Online console view as your build is promoted to _Run_. -+ -image::build1.png[Build #1 link] -+ -. When the *Pipeline* view indicates that the project is available in the _Run_ environment, click the icon (image:rollout_icon.png[title="Rollout"]) next to *Rollout to Run* to view the project in a new tab and test the application. -+ -image::rollout_to_run.png[Rollout to Run] diff --git a/docs/topics/modules/approving_your_application.adoc b/docs/topics/modules/approving_your_application.adoc new file mode 100644 index 0000000..56750a6 --- /dev/null +++ b/docs/topics/modules/approving_your_application.adoc @@ -0,0 +1,14 @@ +[id="approving_your_application"] += Approving your application + +If the quickstart application in the _Stage_ environment runs as expected, approve your application and promote it to the _Run_ environment: + +. Return to the {osio} tab which displays the *Pipeline* view and click btn:[Input Required] at the *Approve* stage of the pipeline. + +. Click btn:[Promote] to promote the application from the _Stage_ environment to the _Run_ environment. This process requires a few minutes. ++ +image::promote.png[Promote application] +. Optionally, as your application is promoted to _Run_, click *helloworldvertx* or *Build #1* to view the detailed progress of the pipeline or build in your OpenShift Online console, respectively. +. When the *Pipeline* view in {osio} indicates that the application is available in the _Run_ environment, click the icon (image:rollout_icon.png[title="Rollout"]) next to *Rollout to Run* to view the application in a new tab. ++ +image::rollout_to_run.png[Rollout to Run] diff --git a/docs/topics/modules/creating_new_application.adoc b/docs/topics/modules/creating_new_application.adoc index b7bfe1c..203d0fa 100644 --- a/docs/topics/modules/creating_new_application.adoc +++ b/docs/topics/modules/creating_new_application.adoc @@ -48,7 +48,7 @@ ifeval::["{context}" == "user-guide"] + image::choose_mission_runtime.png[Choose mission and runtime] + -. In the *Select Pipeline* section, select the appropriate option, then click the blue arrow to continue to the next step. The first option is suggested for most use cases because it provides stages to test your changes for each pipeline build. For more information see <>. +. In the *Select Pipeline* section, select the appropriate option, then click the blue arrow to continue to the next step. The first option is suggested for most use cases. For more information see <>. + image::select_pipeline.png[Select a pipeline] diff --git a/docs/topics/modules/creating_new_space_and_vertx_quickstart_project.adoc b/docs/topics/modules/creating_new_space_and_vertx_quickstart_project.adoc index 0abadd8..52b7a20 100644 --- a/docs/topics/modules/creating_new_space_and_vertx_quickstart_project.adoc +++ b/docs/topics/modules/creating_new_space_and_vertx_quickstart_project.adoc @@ -9,14 +9,14 @@ include::modules/creating_new_space.adoc[leveloffset=+1] include::modules/creating_new_project.adoc[leveloffset=+1] -include::modules/working_with_pipelines.adoc[leveloffset=+1] +include::modules/reviewing_your_staged_application.adoc[leveloffset=+1] include::modules/viewing_build_pipeline_oso.adoc[leveloffset=+1] -include::modules/approving_build_pipeline.adoc[leveloffset=+1] +include::modules/approving_your_application.adoc[leveloffset=+1] include::modules/optional_detailed_views.adoc[leveloffset=+1] include::modules/viewing_project_github.adoc[leveloffset=+1] -include::modules/viewing_projects_oso.adoc[leveloffset=+1] \ No newline at end of file +include::modules/viewing_projects_oso.adoc[leveloffset=+1] diff --git a/docs/topics/modules/next_steps.adoc b/docs/topics/modules/next_steps.adoc index 2f4f484..85ba60d 100644 --- a/docs/topics/modules/next_steps.adoc +++ b/docs/topics/modules/next_steps.adoc @@ -8,7 +8,7 @@ If you followed the instructions in this document, you have now learned about {o * Create new projects using the quickstart wizards and test them. See <> for a Vert.X project. //and <> for a Spring Boot project. * Plan your work by creating work items and execute them using iterative development cycles. See <>. -* Use the build pipelines to stage reviews in the *Stage* and *Run* environments. See <>. +* Use the build pipelines to stage reviews in the *Stage* and *Run* environments. See <> and <>. * Create Che workspaces to edit your project code and commit the changes to GitHub. See <> and <>. * Optimize the memory usage for your projects to use your OpenShift Online resources more efficiently. See <>. // and <>. diff --git a/docs/topics/modules/optional_detailed_views.adoc b/docs/topics/modules/optional_detailed_views.adoc index 3d645a1..ac72d59 100644 --- a/docs/topics/modules/optional_detailed_views.adoc +++ b/docs/topics/modules/optional_detailed_views.adoc @@ -1,7 +1,7 @@ [id="optional_detailed_views"] = (Optional) Detailed views -Optionally, you can see an experimental detailed *Deployments* view for the *Test*, <> environments. This view displays the environment deployments, pods, events, and other information. +Optionally, you can see an experimental detailed *Deployments* view for the *Test*, <> environments. This view displays the environment deployments, pods, events, and other information. View the details for the *Deployments* as follows: diff --git a/docs/topics/modules/reviewing_your_staged_application.adoc b/docs/topics/modules/reviewing_your_staged_application.adoc new file mode 100644 index 0000000..ef93176 --- /dev/null +++ b/docs/topics/modules/reviewing_your_staged_application.adoc @@ -0,0 +1,26 @@ +[id="reviewing_your_staged_application"] += Reviewing your staged application + +When you create a new codebase, the selected pipeline pushes version 1.0.1 of your new application into the _Stage_ environment, and then awaits your approval to deploy into the _Run_ environment. + +<> are individual OpenShift projects. _Stage_ is a production staging area to review and test changes before they are finalized and then staged on _Run_. + +To review your application on _Stage_: + +. At the top of the page, click *Create*, and then click *Pipelines* to see the build pipelines for your new application. When you create a new codebase, the selected pipeline is triggered. In the *Build Release* stage of the pipeline, the build server is set, the build is started, and then released. Next, the pipeline build pushes the application to stage and it displays at the *Approve* stage. This process takes a few minutes. ++ +image::pipeline_firstrun.png[Pipeline First Run] ++ +NOTE: If your pipeline build does not start for more than ten minutes, you can manually start a pipeline build using the instructions at <>. + +. Click the icon (image:rollout_icon.png[title="Rollout"]) next to *Rollout to Stage* in the displayed pipeline. OpenShift Online provides this public URL to access the staged quickstart application. ++ +A new browser tab displays the HTTP Booster application running on _Stage_. The Vert.x HTTP booster quickstart produces a simple API behind a REST endpoint over HTTP with a minimalist user interface. ++ +image::vertx_stage.png[Staged Application] ++ +NOTE: If the application does not load, see <> for troubleshooting information. + +. To test the application, enter a name in the *Name* field and click btn:[Invoke]. The *Result* field displays the JSON result returning from the API. ++ +image::hello-world_john.png[Test the Application] diff --git a/docs/topics/modules/viewing_application_deployment_details.adoc b/docs/topics/modules/viewing_application_deployment_details.adoc new file mode 100644 index 0000000..6101ec8 --- /dev/null +++ b/docs/topics/modules/viewing_application_deployment_details.adoc @@ -0,0 +1,15 @@ +[id="viewing_application_deployment_details"] += Viewing your application deployment details + +You can see a detailed view of your application pods in the <> environments, resources consumed in the two environments, and the overall resources used by the application in the *Deployments* view as follows: + +. At the top of the page, click *Create* and then click *Deployments* to see the deployment details. +. In *Applications*, expand *helloworldvertx* to see the application pods and the resources consumed in the *stage* and *run* environments respectively. The *Resource Usage* at the bottom of the screen displays the overall resources used by your applications in {osio}. ++ +image::hello-world_deployments.png[Deployments page] +. To see further deployment details in your OpenShift Online console, in either the *Stage* or *Run* environments, click the options (image:kabob.png[title="Options"]) icon and then click *View OpenShift Console*. + +. If prompted, click btn:[LOGIN WITH RED HAT] to log in to your OpenShift Online account. When logged in, the OpenShift Online console displays an overview of your application. +. In the left pane, click *Applications* > *Deployments* to view details about the application deployment in the appropriate environment. ++ +image::openshift_online_deployments.png[OpenShift Online Deployments] diff --git a/docs/topics/modules/viewing_build_pipeline_logs.adoc b/docs/topics/modules/viewing_build_pipeline_logs.adoc new file mode 100644 index 0000000..68c0de0 --- /dev/null +++ b/docs/topics/modules/viewing_build_pipeline_logs.adoc @@ -0,0 +1,14 @@ +[id="viewing_build_pipeline_logs"] += (Optional) Viewing the build pipeline logs + +Optionally, while you wait for the pipeline build, you can view the build details in the Jenkins log. For experienced users, these logs are useful when troubleshooting problems with builds if required. + +. In the *Pipeline* page, click *View Log* for the build pipeline in progress. +. When prompted, log into Jenkins with your OpenShift Online account. If the page does not display, wait for a few minutes for the Jenkins instance to initialize and try again. +Once you are logged in, the page displays the logs for your pipeline build. ++ +image::pipeline_jenkins.png[Pipeline Build Logs in Jenkins] ++ +WARNING: Do not click the *Proceed* or *Abort* options at the end of the logs. + +You can now examine the log output to troubleshoot build problems if needed. diff --git a/docs/topics/modules/viewing_build_pipeline_oso.adoc b/docs/topics/modules/viewing_build_pipeline_oso.adoc deleted file mode 100644 index 59abe32..0000000 --- a/docs/topics/modules/viewing_build_pipeline_oso.adoc +++ /dev/null @@ -1,20 +0,0 @@ -[id="viewing_build_pipeline_oso"] -= Viewing the build pipeline logs - -Optionally, while you wait for the pipeline build, you can view the build details in the Jenkins log. For experienced users, these logs are useful when troubleshooting problems with builds if required. - -. In the *Pipeline* page, click *View Log* for the build pipeline in progress. -+ -image::view_log_link.png[View log link] -+ -. When prompted, log into Jenkins with your OpenShift Online account. If an error appears instead of the log in page, wait several minutes for the Jenkins instance to initialize and then try again. -+ -image::jenkins_login.png[Logging into Jenkins] -+ -. When logged in, the page displays the logs for your pipeline build. -+ -image::pipeline_jenkins.png[Pipeline Build Logs in Jenkins] -+ -WARNING: Do not click the *Proceed* or *Abort* options at the end of the logs. -+ -. After examining the logs to familiarize yourself with the log output, you can close the browser tab and return to the {osio} browser tab. diff --git a/docs/topics/modules/viewing_codebase_github.adoc b/docs/topics/modules/viewing_codebase_github.adoc new file mode 100644 index 0000000..a256817 --- /dev/null +++ b/docs/topics/modules/viewing_codebase_github.adoc @@ -0,0 +1,11 @@ +[id="viewing_codebase_github"] += Viewing your codebase in GitHub + +After reviewing your pipeline build running in {osio} and OpenShift Online, view your application <> in GitHub as follows: + +. Return to the *Pipeline* view in {osio}, the *Source Repository* provides the link to the codebase of your application. Right click the link and open it in a new tab to see your codebase in GitHub. +. In the repository, click the *Jenkinsfile* to view details on staging and rolling out of the pipelines. ++ +image::proj_gh.png[Project Code in GitHub] + +Use the codebase link to review code commits and details in your GitHub repository. diff --git a/docs/topics/modules/viewing_projects_oso.adoc b/docs/topics/modules/viewing_oso_projects.adoc similarity index 68% rename from docs/topics/modules/viewing_projects_oso.adoc rename to docs/topics/modules/viewing_oso_projects.adoc index eec0e66..e8d058f 100644 --- a/docs/topics/modules/viewing_projects_oso.adoc +++ b/docs/topics/modules/viewing_oso_projects.adoc @@ -1,7 +1,7 @@ -[id="viewing_projects_oso"] -= Viewing projects in OpenShift Online +[id="viewing_oso_projects"] += Viewing your OpenShift Online projects -To view the OpenShift Online projects that support the pipeline for your project, navigate to your link:https://console.starter-us-east-2.openshift.com/console/projects/[OpenShift Online Console]. +To view all the OpenShift Online projects that support your application, navigate to link:https://console.starter-us-east-2.openshift.com/console/projects/[*My Projects*] in the OpenShift Online Console. image::oso_projects.png[OpenShift Online Projects] @@ -9,6 +9,6 @@ This page displays the following projects and namespaces that are created in Ope * The *_username_* project is where your pipelines run. Your OpenShift Online user name is the name of your project. * The *_username-che_* project represents your <>. -* The *_username-jenkins_* project represents your Jenkins Master or your Jenkins Slaves. Click *Monitoring* after clicking this project to access your Jenkins console. +* The *_username-jenkins_* project represents your Jenkins Master for your Jenkins Slaves. Click this project, and then click *Monitoring* in the left pane to access your Jenkins console. * The *_username-run_* project is identical to the *_username-stage_* project and is an environment for experimenting with your OpenShift pods and monitoring the memory usage for your application. * The *_username-stage_* project is for your personal use. Use this project to see the pods that are created when pipelines are triggered in {osio}. For maintenance, select this project and power down individual pods as required. diff --git a/docs/topics/modules/viewing_project_github.adoc b/docs/topics/modules/viewing_project_github.adoc deleted file mode 100644 index 1575568..0000000 --- a/docs/topics/modules/viewing_project_github.adoc +++ /dev/null @@ -1,17 +0,0 @@ -[id="viewing_project_github"] -= Viewing your project in GitHub - -After reviewing your pipeline build running in {osio} and OpenShift Online, view your project <> in GitHub as follows: - -. Return to your space dashboard. -. In the *Codebases* panel, click the GitHub link to the project code. -+ -image::gh_link.png[GitHub Code Link] -+ -A new browser tab displays your project code in GitHub. -+ -image::proj_gh.png[Project Code in GitHub] -+ -. Click *Jenkinsfile* to view the details for the staging and rollout of the pipelines. - -Use this link to review code commits and details in your GitHub repository. diff --git a/docs/topics/modules/viewing_your_detailed_oso_quota_usage.adoc b/docs/topics/modules/viewing_your_detailed_oso_quota_usage.adoc index e8dba51..0d1b820 100644 --- a/docs/topics/modules/viewing_your_detailed_oso_quota_usage.adoc +++ b/docs/topics/modules/viewing_your_detailed_oso_quota_usage.adoc @@ -9,7 +9,7 @@ After committing your changes, view the resource details for your project again + image::optimize_memory.png[Optimizing Hello World Memory Usage] + -. <> to the *Run* environment. +. <> to the *Run* environment. + You can now compare these details to the details in <> to see the resource usage improvements. diff --git a/docs/topics/modules/working_with_pipelines.adoc b/docs/topics/modules/working_with_pipelines.adoc deleted file mode 100644 index 5b145fe..0000000 --- a/docs/topics/modules/working_with_pipelines.adoc +++ /dev/null @@ -1,25 +0,0 @@ -[id="working_with_pipelines"] -= Working with pipelines - -When you create a new quickstart project, a new build executes. In a build pipeline, <> are individual OpenShift projects. _Stage_ is a production staging area to review and test changes before they are finalized and then staged on _Run_. - -//After you create a new Quickstart project, you can see the new project build pipelines running in the *Applications* panel on your space dashboard: - -//image::hello-world_applications.png[Applications view] - -. At the top of the page, click *Create*. - -. In the sub-menu options, click *Pipelines*. The build pipelines for your new application display on this page. Initially, the build status is *No stages have started*. -+ -image::hello-world_build1_nostages.png[VertX Build 1 No Stage] -+ -When the pipeline build is ready, it displays at the *Approve* stage: -+ -image::pipeline_firstrun.png[Pipeline First Run] - -For your new quickstart project, the new build pipeline pushes version 1.0.1 into _Stage_ and then, after user approval, it pushes the changes to _Run_. - -[NOTE] -==== -If your pipeline build does not start for more than ten minutes, you can manually start a pipeline build using the instructions at <>. -==== diff --git a/docs/topics/working_with_pipelines.adoc b/docs/topics/working_with_pipelines.adoc index 83af8b7..1c01b8a 100644 --- a/docs/topics/working_with_pipelines.adoc +++ b/docs/topics/working_with_pipelines.adoc @@ -13,7 +13,7 @@ include::modules/staging_the_application.adoc[leveloffset=+1] include::modules/promoting_the_application.adoc[leveloffset=+1] -include::modules/viewing_build_pipeline_oso.adoc[leveloffset=+1] +include::modules/viewing_build_pipeline_logs.adoc[leveloffset=+1] include::modules/configuring_pipelines.adoc[leveloffset=+1]