3. Make modifications and click "Run". In this example, we changed "ruby-2.3" to "ruby-2.4". 4. Check the results of changes • Can be called multiple times on the same run  - allows for easy parallel testing of different changes. • Can also be called on Pipeline runs that are still in-progress  - As long as a Pipeline contained syntactically correct Groovy and was able to start, it can be Replayed. • Referenced Shared Library code is also modifiable  - If a Pipeline run references a Shared Library, the code from the shared library will also be shown and modifiable as part of the Replay page. • Pipeline runs with syntax errors cannot be replayed  - meaning their code cannot be viewed and any changes made in them cannot be retrieved. When using Replay for more significant modifications, save your changes to a file or editor outside of Jenkins before running them. See JENKINS-37589 • Replayed Pipeline behavior may differ from runs started by other methods  - For Pipelines that are not part of a Multi-branch Pipeline, the commit information may differ for the original run and the Replayed run. See JENKINS-36453 79 Limitations Features Once you are satisfied with the changes, you can use Replay to view them again, copy them back to your Pipeline job or  Jenkinsfile , and then commit them using your usual engineering processes.