Merge pull request #1942 from coligo/fmo-upd-19Apr22-c

Author: cfsdocs

Diff for: appdeploy-access.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-03-19"
+lastupdated: "2022-04-19"
 
 keywords: applications in code engine, apps in code engine, http requests in code engine, deploy apps in code engine, app workloads in code engine, deploying workloads in code engine, application, app, memory, cpu, environment variables
 
@@ -49,8 +49,8 @@ ibmcloud ce app get --name myapp
 ```
 {: pre}
 
-#### Example output
-{: #access-appdetails-cli-example}
+
+Example output
 
 ```txt
 [...]

Diff for: appdeploy-cr.md

@@ -12,10 +12,10 @@ subcollection: codeengine
 
 {{site.data.keyword.attribute-definition-list}}
 
-# Deploying application workloads from images in {{site.data.keyword.registryshort}}
+# Deploying application workloads from images in {{site.data.keyword.registrylong_notm}}
 {: #deploy-app-crimage}
 
-Deploy your app with {{site.data.keyword.codeengineshort}} that uses an image in {{site.data.keyword.registryshort}}. You can create an app from the console or with the CLI. 
+Deploy your app with {{site.data.keyword.codeengineshort}} that uses an image in {{site.data.keyword.registrylong}}. You can create an app from the console or with the CLI. 
 {: shortdesc}
 
 Before you begin
@@ -51,16 +51,13 @@ Now that you have deployed your application, you can view information about appl
 
 If you want to add registry access to a {{site.data.keyword.registryshort}} instance that is not in your account, see [Adding access to a {{site.data.keyword.registryshort}}](/docs/codeengine?topic=codeengine-add-registry). 
 
-Looking for more code examples? Check out the [Samples for {{site.data.keyword.codeenginefull_notm}} GitHub repo](https://github.com/IBM/CodeEngine){: external}.
-{: tip}
-
 ## Deploying an app with an image in {{site.data.keyword.registryshort}} with the CLI
 {: #deploy-app-crimage-cli}
 
-Deploy an application that uses an image in a container registry with the CLI with the **`ibmcloud ce app create`** command. 
+Deploy an application that uses an image in in {{site.data.keyword.registrylong}} with the CLI with the **`ibmcloud ce app create`** command. 
 {: shortdesc}
 
-Before you can work with a {{site.data.keyword.codeengineshort}} application that references an image in {{site.data.keyword.registryshort}}, you must first add access to the registry, pull the image, and then deploy it. 
+Before you can work with a {{site.data.keyword.codeengineshort}} application that references an image in {{site.data.keyword.registryshort}}, you must first add access to the registry so {{site.data.keyword.codeengineshort}} can pull the image when the app is deployed.  
 
 1. To add access to {{site.data.keyword.registryshort_notm}}, [create an IAM API key](/docs/codeengine?topic=codeengine-add-registry#images-your-account-api-key). To create an {{site.data.keyword.cloud_notm}} IAM API key with the CLI, run the [**`iam api-key-create`**](/docs/account?topic=cli-ibmcloud_commands_iam#ibmcloud_iam_api_key_create) command. For example, to create an API key called `cliapikey` with a description of "My CLI APIkey" and save it to a file called `key_file`, run the following command:
 
@@ -104,8 +101,6 @@ Before you can work with a {{site.data.keyword.codeengineshort}} application tha
     ```
     {: pre}
 
-Looking for more code examples? Check out the [Samples for {{site.data.keyword.codeenginefull_notm}} GitHub repo](https://github.com/IBM/CodeEngine){: external}.
-{: tip}
 
 ## Next steps for apps
 {: #nextsteps-appdeploycr}

Diff for: appdeploy-private.md

@@ -22,7 +22,7 @@ Before you begin
 
 To pull images from a private registry, you must first create a private registry. For example, to create a private Docker Hub registry, see [Docker Hub documentation](https://docs.docker.com/docker-hub/repos/){: external}. After you create a private registry, [push an image to it](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub){: external}. You can also set up an access token. By using an access token, you can more easily grant and revoke access to your Docker Hub account without requiring a password change. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/docker-hub/access-tokens/){: external}.
 
-## Deploying an app that references an image in private registry with the console
+## Deploying an app that references an image in a private registry with the console
 {: #deploy-app-private-console}
 
 Deploy an application that uses an image in a private registry with the {{site.data.keyword.codeengineshort}} console.
@@ -56,9 +56,6 @@ Now that you have deployed your application, you can view information about appl
 
 If you want to add registry access before you create an app, see [Adding access to a private container registry](/docs/codeengine?topic=codeengine-add-registry). 
 
-Looking for more code examples? Check out the [Samples for {{site.data.keyword.codeenginefull_notm}} GitHub repo](https://github.com/IBM/CodeEngine){: external}.
-{: tip}
-
 ## Deploying an app with an image from a private registry with CLI
 {: #deploy-app-private-cli}
 
@@ -76,7 +73,7 @@ Before you can work with a {{site.data.keyword.codeengineshort}} application tha
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     Creating image registry access secret 'privatedocker'...
@@ -101,8 +98,6 @@ Before you can work with a {{site.data.keyword.codeengineshort}} application tha
     ```
     {: pre}
 
-Looking for more code examples? Check out the [Samples for {{site.data.keyword.codeenginefull_notm}} GitHub repo](https://github.com/IBM/CodeEngine){: external}.
-{: tip}
 
 ## Next steps for apps
 {: #nextsteps-appdeploypriv}

Diff for: appdeploy-public.md

@@ -56,7 +56,7 @@ ibmcloud ce application create --name myapp --image icr.io/codeengine/hello
 ```
 {: pre}
 
-**Example output**
+Example output
 
 ```txt
 Creating application 'myapp'...

Diff for: appdeploy-source.md

@@ -29,7 +29,7 @@ You can deploy your application directly from source code with the console.
 
 Before you begin, [plan for your build](/docs/codeengine?topic=codeengine-plan-build). You can also find [tips for creating a Dockerfile](/docs/codeengine?topic=codeengine-dockerfile).
 
-{{site.data.keyword.codeengineshort}} can automatically push (upload) images to {{site.data.keyword.registryshort}} namespaces in your account and even create a namespace for you. To upload images to a different {{site.data.keyword.registryshort}} account or to a private Docker Hub account, see [Adding access to a private container registry](/docs/codeengine?topic=codeengine-add-registry).
+{{site.data.keyword.codeengineshort}} can automatically push (upload) images to {{site.data.keyword.registrylong}} namespaces in your account and even create a namespace for you. To upload images to a different {{site.data.keyword.registryshort}} account or to a private Docker Hub account, see [Accessing container registries](/docs/codeengine?topic=codeengine-add-registry).
 
 1. Open the [{{site.data.keyword.codeengineshort}}](https://cloud.ibm.com/codeengine/overview){: external} console.
 2. Select **Start creating** from **Start from source code**.
@@ -41,8 +41,8 @@ Before you begin, [plan for your build](/docs/codeengine?topic=codeengine-plan-b
 8. Select a source repository, for example, `https://github.com/IBM/CodeEngine`. Because we are using sample source that does not require credentials, select `None` for the Code repo access. You can optionally provide a branch name. If you do not provide a branch name and you leave the field empty, {{site.data.keyword.codeengineshort}} automatically uses the default branch of the specified repository. Click **Next**.  
 9. Select a strategy for your build and resources for your build. For more information about build options, see [Planning your build](/docs/codeengine?topic=codeengine-plan-build). Click **Next**.
 10. Select a container registry location, such as `IBM Registry, Dallas` to specify where to store the image of your build output. If your registry is private, you must [set up access](/docs/codeengine?topic=codeengine-add-registry) to it.
-11. Select an existing **Registry access secret** or create a new one. If you are building your image to a {{site.data.keyword.registryshort}} instance that is in your account, you can select `{{site.data.keyword.codeengineshort}} managed secret` and let {{site.data.keyword.codeengineshort}} create and manage the secret for you.
-12. Select a namespace, name, and a tag for your image. If you are building your image to a {{site.data.keyword.registryshort}} instance that is in your account, you can select an existing namespace or let {{site.data.keyword.codeengineshort}} create and manage the namespace for you.
+11. Provide registry information about where to store the image of your build output. Select an existing **Registry access secret** or create a new one. If you are building your image to a {{site.data.keyword.registryshort}} instance that is in your account, you can select `{{site.data.keyword.codeengineshort}} managed secret` and let {{site.data.keyword.codeengineshort}} create and manage the secret for you.
+12. Select a namespace, name, and a tag for your image. If you are building your image to a {{site.data.keyword.registrylong_notm}} instance that is in your account, you can select an existing namespace or let {{site.data.keyword.codeengineshort}} create and manage the namespace for you.
 13. Click **Done**.
 14. Modify any runtime settings or environment variables for your app. For more information about these options, see [Options for endpoint visibility of apps](/docs/codeengine?topic=codeengine-application-workloads#optionsdeploy) and [Options for deploying an app](/docs/codeengine?topic=codeengine-application-workloads#optionsdeploy).
 15. Click **Create**.

Diff for: appdeploy-update.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-04-14"
+lastupdated: "2022-04-19"
 
 keywords: applications in code engine, apps in code engine, http requests in code engine, deploy apps in code engine, app workloads in code engine, deploying workloads in code engine, application, app, memory, cpu, environment variables
 
@@ -175,7 +175,7 @@ The sample `icr.io/codeengine/hello` image reads the environment variable `TARGE
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     Hello Stranger
@@ -193,7 +193,7 @@ The sample `icr.io/codeengine/hello` image reads the environment variable `TARGE
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     Listing all application revisions...
@@ -226,7 +226,7 @@ In this scenario, update the application that you created in [Deploying an appli
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     Updating application 'myapp' to latest revision.
@@ -245,7 +245,7 @@ In this scenario, update the application that you created in [Deploying an appli
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     [...]
@@ -367,7 +367,7 @@ In this scenario, update the application that you created in [Deploying an appli
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     Updating application 'myapp' to latest revision.
@@ -386,7 +386,7 @@ In this scenario, update the application that you created in [Deploying an appli
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     [...]
@@ -543,7 +543,7 @@ From the previous example, the `myhelloapp` app references the `us.icr.io/myname
 
     The following output displays the details of the build run by using the  [**`ibmcloud ce buildrun get`**](/docs/codeengine?topic=codeengine-cli#cli-buildrun-get) command.
 
-    **Example output**
+    Example output
 
     ```txt
     Getting build run 'helloworld-build-run'...
@@ -582,7 +582,7 @@ From the previous example, the `myhelloapp` app references the `us.icr.io/myname
     ```
     {: pre}
 
-    **Example output**
+    Example output
 
     ```txt
     [...]

Diff for: batch-tutorial.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-04-05"
+lastupdated: "2022-04-19"
 
 keywords: job tutorial, jobs, images for code engine jobs, tutorial for code engine, job log
 
@@ -108,9 +108,27 @@ When the job is in ready state, you can update the job. Let's update the job tha
 ## Next steps for jobs
 {: #nextsteps-deployjobtut}
 
-After you create your job, you can submit it to [run the job](/docs/codeengine?topic=codeengine-run-job). For more information about jobs, see [Working with jobs](/docs/codeengine?topic=codeengine-job-plan).
+After you create your job, you must submit the job to run it. See [Run a job](/docs/codeengine?topic=codeengine-run-job).
 
-Now that you have created your job, you can use event subscriptions to make your jobs event-driven, so that your jobs are triggered by [periodic schedules](/docs/codeengine?topic=codeengine-subscribe-cron#eventing-cron-job) or react to events like [file uploads](/docs/codeengine?topic=codeengine-eventing-cosevent-producer#obstorage_ev_job).
+After you [run your job](/docs/codeengine?topic=codeengine-run-job), to view details of your job and job runs, see [access job details](/docs/codeengine?topic=codeengine-access-job-details).
+
+You can update your job in any of the following ways:
+
+* By accessing and referencing your existing built container image in a [public registry](/docs/codeengine?topic=codeengine-create-job) or [private registry](/docs/codeengine?topic=codeengine-create-job-private). For more information, see [Accessing container registries](/docs/codeengine?topic=codeengine-add-registry).
+
+* By using the [build container images](/docs/codeengine?topic=codeengine-build-image) feature available in {{site.data.keyword.codeengineshort}} to build your image and then access the referenced image from your job run.
+
+* You can choose to let {{site.data.keyword.codeengineshort}} handle the build of your [local source](/docs/codeengine?topic=codeengine-run-job-local-source-code)  or [Git repository source](/docs/codeengine?topic=codeengine-run-job-source-code) for you. The job run can then access the referenced image.
+
+For example, you might choose to let {{site.data.keyword.codeengineshort}} handle the build of your local source while you evolve the development of your source for the job. Then, after the image is "matured", you can update the job to reference the specific image that you want. You can repeat this process as needed.
+
+Each time your job runs, the most current version of your referenced container image is downloaded and run.
+
+For more information about updating jobs, see [Updating a job](/docs/codeengine?topic=codeengine-update-job).
+
+
+
+Now that you have created your job, consider making your jobs event-driven. By using event subscriptions, you can trigger your jobs by [periodic schedules](/docs/codeengine?topic=codeengine-subscribe-cron#eventing-cron-job) or set your job to react to events like [file uploads](/docs/codeengine?topic=codeengine-eventing-cosevent-producer#obstorage_ev_job).
 
 
 Looking for more code examples? Check out the [Samples for {{site.data.keyword.codeenginefull_notm}} GitHub repo](https://github.com/IBM/CodeEngine){: external}.