Skip to content

Commit af96a19

Browse files
authored
Merge branch 'main' into patch-16
2 parents 0b967f7 + e5949a7 commit af96a19

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,15 @@ For more information, see "[Core concepts for {% data variables.product.prodname
3333

3434
Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
3535

36-
Similiarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}.
36+
Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}.
3737

3838
| Jenkins | {% data variables.product.prodname_actions %} |
3939
| ------------- | ------------- |
4040
| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners) <br> [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners)|
4141

4242
#### Using sections to organize pipelines
4343

44-
Jenkins splits its Declarative Pipelines into multiple sections. Similiarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
44+
Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
4545

4646
|Jenkins Directives | {% data variables.product.prodname_actions %} |
4747
| ------------- | ------------- |

package.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@
77
"name": "GitHub",
88
"url": "https://github.com/github/docs"
99
},
10+
"license": "(MIT AND CC-BY-4.0)",
1011
"dependencies": {
1112
"@babel/core": "^7.8.3",
1213
"@babel/plugin-transform-runtime": "^7.11.0",

0 commit comments

Comments
 (0)