Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typo fixes in prTester readme file #479

Merged
merged 3 commits into from
Mar 11, 2024
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/ARCHITECTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ These are the initial scripts that are the top level jobs that are invoked, this
jobs for each configuration/platform then coordinates deploying the results to GitHub. The majority of the code that
defines this stage is contained within [build_base_file.groovy](https://github.com/adoptium/temurin-build/blob/master/pipelines/build/common/build_base_file.groovy).

#### Indiviual Build Jobs
#### Individual Build Jobs

This are invoked by the parent pipeline job and each build creates the archives/installers for a given platform. The majority
of this code is defined in [openjdk_build_pipeline.groovy](https://github.com/adoptium/temurin-build/blob/master/pipelines/build/common/openjdk_build_pipeline.groovy)
These are invoked by the parent pipeline job and each build creates the archives/installers for a given platform. The majority
of this code is defined in [openjdk_build_pipeline.groovy](https://github.com/adoptium/temurin-build/blob/master/pipelines/build/common/openjdk_build_pipeline.groovy).
8 changes: 4 additions & 4 deletions pipelines/build/prTester/README.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# PR Testers

openjdk-build is an open source project, therefore, we need to ensure the the code that is being deployed to our master branch doesn't break any existing code and actually works as expected.
To achieve this level of testing, we use various jobs to compile, lint and test the code as well as running demo pipelines in a controlled sandbox environment if needs be.
The demo pipelines are colloquially known as "The PR Tester" where the others are generally just referred to as "`checkname` check".
openjdk-build is an open source project, therefore, we need to ensure that the code that is being deployed to our master branch doesn't break any existing code and actually works as expected.
To achieve this level of testing, we use various jobs to compile, lint and test the code as well as running demo pipelines in a controlled sandbox environment if need be.
The demo pipelines are colloquially known as "The PR Tester" and the others are generally just referred to as "`checkname` check".

## When they're used

Expand Down Expand Up @@ -74,7 +74,7 @@ If you're unsure if the tests failed because of your changes or not, check our [

##### `run tests quick`

Simiar to `run tests` but runs a subset of jdk test jobs. Without specific jdk version, it uses 17, otherwise loops over given versions
Similar to `run tests` but runs a subset of jdk test jobs. Without specific jdk version, it uses 17, otherwise loops over given versions
Example:
`run tests quick` is the same as `run tests quick 19`
`run tests quick 11, 19, 8` generates all jobs then runs openjdk pipeline on 8, 11 and 19
Expand Down