Skip to content

Set buildDiscarder #640

Set buildDiscarder

Set buildDiscarder #640

Workflow file for this run

name: "Comment Bot"
on:
pull_request_target:
types: [ opened ]
permissions:
contents: read
jobs:
Comment:
permissions:
issues: write # for peter-evans/create-or-update-comment to create or update comment
pull-requests: write # for peter-evans/create-or-update-comment to create or update comment
name: Add Comment
runs-on: ubuntu-latest
steps:
- name: Create comment
uses: peter-evans/create-or-update-comment@23ff15729ef2fc348714a3bb66d2f655ca9066f2 # v3.1.0
with:
issue-number: ${{ github.event.pull_request.number }}
body: |
# Thank you for creating a pull request!
Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).
## Code Quality and Contributing Guidelines
If you have not done so already, please familiarise yourself with our [Contributing Guidelines](https://github.com/adoptium/ci-jenkins-pipelines/blob/master/CONTRIBUTING.md) and [Code Of Conduct](https://github.com/adoptium/ci-jenkins-pipelines/blob/master/CODE_OF_CONDUCT.md), even if you have contributed before.
## Tests
Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our [testing documentation](https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/prTester/README.md).
In order to run the advanced [pipeline tests](https://github.com/adoptium/ci-jenkins-pipelines/tree/master/pipelines/build/prTester#openjdk-build-pr-tester) (executing a set of mock pipelines), it requires an admin to post `run tests` on this PR.
If you are not an admin, please ask for one's attention in [#infrastructure on Slack](https://adoptium.slack.com/archives/C53GHCXL4) or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"