Skip to content

Commit a9e9185

Browse files
committed
minor updates
1 parent 1f463c3 commit a9e9185

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

articles/spring-apps/enterprise/how-to-manage-job.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This article shows you how to manage the lifecycle of a job and run it in the Az
2727

2828
### [Azure CLI](#tab/azure-cli)
2929

30-
Use the command `az spring job create` to create job and deploy the job with source code or artifacts of the application.
30+
Use the following commands to create and deploy a job:
3131

3232
```azurecli
3333
az spring job create \
@@ -40,7 +40,7 @@ az spring job deploy \
4040

4141
### [Azure portal](#tab/azure-portal)
4242

43-
Use the following steps to create a job using the Azure portal:
43+
Use the following steps to create and deploy a job:
4444

4545
1. Open your Azure Spring Apps service instance.
4646

@@ -114,20 +114,22 @@ az spring job execution list \
114114

115115
### [Azure portal](#tab/azure-portal)
116116

117-
In the **Executions** section of the **Jobs** overview page, find the latest job execution and select **View execution detail** to see the configuration both in the job level and the execution level.
117+
1. Go to the **Executions** section of the **Jobs** overview page.
118+
119+
1. Find the latest job execution and select **View execution detail** to see the configuration both in the job level and in the execution level.
118120

119121
---
120122

121-
For the public preview, the latest 10 completed or failed job execution records per job in the history are retained.
123+
For the public preview, the latest 10 completed or failed job execution records per job are retained in history.
122124

123125
## Query job execution logs
124126

125127
For the history of job executions in the Azure portal, use the following command to query the logs in the Azure Log Analytics:
126128

127129
```SQL
128-
AppPlatformLogsforSpring
129-
| where AppName == '<job-name>' and InstanceName startswith '<execution-name>'
130-
| order by TimeGenerated asc
130+
AppPlatformLogsforSpring |
131+
where AppName == '<job-name>' and InstanceName startswith '<execution-name>' |
132+
order by TimeGenerated asc |
131133
```
132134

133135
For more information, see [Set up log analytics workspace](../basic-standard/quickstart-setup-log-analytics.md?tabs=Azure-Portal#prerequisites).
@@ -140,7 +142,7 @@ az spring job logs \
140142
--execution <execution-name> \
141143
```
142144

143-
If there are multiple instances for the job execution, specify `--instance <instance-name>` to view the logs of only one instance.
145+
If there are multiple instances for the job execution. Specify `--instance <instance-name>` to view the logs of only one instance.
144146

145147
## Rerun job execution
146148

@@ -157,13 +159,13 @@ az spring job start \
157159

158160
### [Azure portal](#tab/azure-portal)
159161

160-
Use the following steps to rerun the job execution:
162+
Use the following steps to rerun a job execution:
161163

162164
1. Open the **Executions** section of the **Jobs** overview page.
163165

164166
1. Select **Rerun** to trigger a new job execution with the same configuration as the previous one.
165167

166-
A new job execution is shown in the **Executions** section.
168+
1. A new job execution is shown in the **Executions** section.
167169

168170
---
169171

@@ -173,7 +175,7 @@ For the public preview, jobs are enabled to integrate seamlessly with Spring Clo
173175

174176
### Spring Cloud Config Server
175177

176-
With the Spring Cloud Config Server, configurations or properties required by the job can be managed externally on GitHub repos and then loaded into the job accordingly. After setting up GitHub repo configurations on Spring Cloud Config Server, you need to bind the jobs with it.
178+
With the Spring Cloud Config Server, configurations or properties required by the job can be managed externally on GitHub repositories and then loaded into the job accordingly. After setting up GitHub repo configurations on Spring Cloud Config Server, you need to bind the jobs to it.
177179

178180
#### [Azure CLI](#tab/azure-cli)
179181

0 commit comments

Comments
 (0)