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

Fix capitalization errors and minor phrasing errors #334

Merged
merged 2 commits into from
Dec 14, 2023
Merged
Show file tree
Hide file tree
Changes from all 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
12 changes: 8 additions & 4 deletions .github/labeler.yml
Original file line number Diff line number Diff line change
@@ -1,11 +1,15 @@
skip-changelog:
- any: [ '.gitattributes', '.github/**/*', '.gitignore', 'crowdin.yml', '.mvn/**/*' ]
- changed-files:
- any-glob-to-any-file: [ '.gitattributes', '.github/**/*', '.gitignore', 'crowdin.yml', '.mvn/**/*' ]

dependencies:
- any: [ 'pom.xml' ]
- changed-files:
- any-glob-to-any-file: [ 'pom.xml' ]

documentation:
- any: [ '*.adoc', '*.md', '*.txt', '**/*.html', '**/*.png', 'LICENSE*' ]
- changed-files:
- any-glob-to-any-file: [ '*.adoc', '*.md', '*.txt', '**/*.html', '**/*.png', 'LICENSE*' ]

tests:
- any: [ 'src/test/**/*' ]
- changed-files:
- any-glob-to-any-file: [ 'src/test/**/*' ]
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Then, this is the right plugin for you.

Jenkins is an excellent tool for several continuous integration tasks, but it is still in the early stages for helping you to create your own personal cloud of computers.
The multi configuration job helps you running a task over a fixed number of computers, but the standard axis has several drawbacks for this kind of task.
If you have tenths of computers to run several jobs in your personal array of computers, for example, you have to configure each job and include every node individually.
If you have many computers to run several jobs in your personal array of computers, for example, you have to configure each job and include every node individually.
And you'll have to do it again, when you create new jobs.
If that's not tedious enough, when you add a new node to your cloud, you have to reconfigure every job to start receiving the new node's contribution.

Expand All @@ -23,13 +23,13 @@ So, this plugin address these two flaws of the standard label axis.

## Running over an Elastic Axis

When you create an Elastic Axis, you specify one or more labels where you want to run your job.
When you create an elastic axis, you specify one or more labels where you want to run your job.
That is, instead of specifying a fixed number of computers, you let the axis find out on the fly all the computers in that label to run your job.
By doing this, you avoid the problem of the standard label, because new nodes are added to the label and not to the jobs.
As soon as you add a new computer to the labels, jobs configured to used the Elastic Axis over this label will immediately benefit.
As soon as you add a new computer to the labels, jobs configured to used the elastic axis over this label will immediately benefit.

Another issue addressed by the Elastic Axis is the offline nodes.
Sometimes, the computers in your cloud might end up in maintenance or go offline for some reason. With the Elastic Axis, you can check an option instructing it to skip these nodes if they are not available, and therefore, your tasks may take longer, but the job will complete without hanging out because of offline nodes.
Another issue addressed by the elastic axis is the offline nodes.
Sometimes, the computers in your cloud might end up in maintenance or go offline for some reason. With the elastic axis, you can check an option instructing it to skip these nodes if they are not available, and therefore, your tasks may take longer, but the job will complete without hanging out because of offline nodes.

## A Massive Test Case

Expand All @@ -41,7 +41,7 @@ By using Jenkins multi-configuration jobs, automatically running the tests over
Now, we have several production branches of our product, all of them with the same 25k tests that should run as often as possible to make sure the fixes are not causing regression.
And they all share the same grid of computers on Jenkins to run the tests.

This is where the Elastic Axis plugin becomes a great tool.
This is where the elastic axis plugin becomes a great tool.
By using the plugin, we are able to easily manage the computing resources and change it without ever reconfiguring the jobs.
The kind of task we run doesn't care whether you have 20 or 50 computers, it will complete even with a single unit.
But by adding more computers, we can speed it and even the daunting task of running 25k functional tests that access databases turns out to run on acceptable time for continuous integration purposes.
Expand Down