You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/11/en/part11b.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ on:
123
123
124
124
jobs:
125
125
hello_world_job:
126
-
runs-on: ubuntu-20.04
126
+
runs-on: ubuntu-latest
127
127
steps:
128
128
- name: Say hello
129
129
run: |
@@ -200,7 +200,7 @@ Before we can run a command to lint the code, we have to perform a couple of act
200
200
201
201
#### Setting up the environment
202
202
203
-
Setting up the environment is an important task while configuring a pipeline. We're going to use an <code>ubuntu-20.04</code> virtual environment because this is the version of Ubuntu we're going to be running in production.
203
+
Setting up the environment is an important task while configuring a pipeline. We're going to use an <code>ubuntu-latest</code> virtual environment because this is the version of Ubuntu we're going to be running in production.
204
204
205
205
It is important to replicate the same environment in CI as in production as closely as possible, to avoid situations where the same code works differently in CI and production, which would effectively defeat the purpose of using CI.
206
206
@@ -218,7 +218,7 @@ on:
218
218
219
219
jobs:
220
220
simple_deployment_pipeline: # highlight-line
221
-
runs-on: ubuntu-20.04# highlight-line
221
+
runs-on: ubuntu-latest# highlight-line
222
222
steps: # highlight-line
223
223
- uses: actions/checkout@v4 # highlight-line
224
224
```
@@ -234,7 +234,7 @@ Secondly, as the application is written in JavaScript, Node.js must be set up to
234
234
235
235
jobs:
236
236
simple_deployment_pipeline:
237
-
runs-on: ubuntu-20.04
237
+
runs-on: ubuntu-latest
238
238
steps:
239
239
- uses: actions/checkout@v4
240
240
- uses: actions/setup-node@v4 # highlight-line
@@ -250,7 +250,7 @@ Lastly, the dependencies of the application must be installed. Just like on your
250
250
```yml
251
251
jobs:
252
252
simple_deployment_pipeline:
253
-
runs-on: ubuntu-20.04
253
+
runs-on: ubuntu-latest
254
254
steps:
255
255
- uses: actions/checkout@v4
256
256
- uses: actions/setup-node@v4
@@ -269,7 +269,7 @@ After the environment has been set up we can run all the scripts from <code>pack
Copy file name to clipboardExpand all lines: src/content/11/es/part11b.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ on:
123
123
124
124
jobs:
125
125
hello_world_job:
126
-
runs-on: ubuntu-20.04
126
+
runs-on: ubuntu-latest
127
127
steps:
128
128
- name: Say hello
129
129
run: |
@@ -200,7 +200,7 @@ Before we can run a command to lint the code, we have to perform a couple of act
200
200
201
201
#### Setting up the environment
202
202
203
-
Setting up the environment is an important task while configuring a pipeline. We're going to use an <code>ubuntu-20.04</code> virtual environment because this is the version of Ubuntu we're going to be running in production.
203
+
Setting up the environment is an important task while configuring a pipeline. We're going to use an <code>ubuntu-latest</code> virtual environment because this is the version of Ubuntu we're going to be running in production.
204
204
205
205
It is important to replicate the same environment in CI as in production as closely as possible, to avoid situations where the same code works differently in CI and production, which would effectively defeat the purpose of using CI.
206
206
@@ -218,7 +218,7 @@ on:
218
218
219
219
jobs:
220
220
simple_deployment_pipeline: # highlight-line
221
-
runs-on: ubuntu-20.04# highlight-line
221
+
runs-on: ubuntu-latest# highlight-line
222
222
steps: # highlight-line
223
223
- uses: actions/checkout@v4 # highlight-line
224
224
```
@@ -234,7 +234,7 @@ Secondly, as the application is written in JavaScript, Node.js must be set up to
234
234
235
235
jobs:
236
236
simple_deployment_pipeline:
237
-
runs-on: ubuntu-20.04
237
+
runs-on: ubuntu-latest
238
238
steps:
239
239
- uses: actions/checkout@v4
240
240
- uses: actions/setup-node@v4 # highlight-line
@@ -250,7 +250,7 @@ Lastly, the dependencies of the application must be installed. Just like on your
250
250
```yml
251
251
jobs:
252
252
simple_deployment_pipeline:
253
-
runs-on: ubuntu-20.04
253
+
runs-on: ubuntu-latest
254
254
steps:
255
255
- uses: actions/checkout@v4
256
256
- uses: actions/setup-node@v4
@@ -269,7 +269,7 @@ After the environment has been set up we can run all the scripts from <code>pack
Copy file name to clipboardExpand all lines: src/content/11/zh/part11b.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,7 +170,7 @@ on:
170
170
171
171
jobs:
172
172
hello_world_job:
173
-
runs-on: ubuntu-20.04
173
+
runs-on: ubuntu-latest
174
174
steps:
175
175
- name: Say hello
176
176
run: |
@@ -266,8 +266,8 @@ jobs:
266
266
267
267
#### Setting up the environment
268
268
269
-
<!-- Setting up the environment is an important task while configuring a pipeline. We're going to use an <code>ubuntu-20.04</code> virtual environment because this is the version of Ubuntu we're going to be running in production.-->
<!-- Setting up the environment is an important task while configuring a pipeline. We're going to use an <code>ubuntu-latest</code> virtual environment because this is the version of Ubuntu we're going to be running in production.-->
<!-- It is important to replicate the same environment in CI as in production as closely as possible, to avoid situations where the same code works differently in CI and production, which would effectively defeat the purpose of using CI.-->
0 commit comments