docs
docs copied to clipboard
Fix Jenkins migration: Using steps to execute task
Why:
To fix the "Using steps to execute tasks" section that uses the wrong Jenkins keyword, IMO.
What's being changed (if available, include any code snippets, screenshots, or gifs):
In the "Using steps to execute task" section of the "Migrate from Jenkins" page, the script
entry is replaced by steps
, which sounds more relevant in this case. Indeed, script
is one particular type of step whereas the paragraph is about groups of steps, handled in Jenkins by the steps
element of a declarative Pipeline.
Check off the following:
- [x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
- [x] For content changes, I have completed the self-review checklist.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Automatically generated comment ℹ️
This comment is automatically generated and will be overwritten every time changes are committed to this branch.
The table contains an overview of files in the content
directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data
directory will not show up in this table.
Content directory changes
You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
Source | Preview | Production | What Changed |
---|---|---|---|
actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md |
fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae |
fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae |
fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server ghae: GitHub AE
@ataillefer Thanks so much for opening a PR! I'll get this triaged for review :zap:
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues :zap: