WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 17 months ago

Last modified 2 months ago

#42387 closed task (blessed) (fixed)

Trim the Travis CI job matrix even further for older branches

Reported by: johnbillion Owned by: johnbillion
Milestone: 5.2 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:

Description

Previously: #40407

Older branches generally have the following test matrix pattern for jobs on Travis CI (with a reduced number of jobs for very old branches):

  • JS tests
  • Latest PHP version
  • Latest 5.x PHP version
  • Latest 5.x PHP version with object cache
  • PHP 5.2

The Travis CI build process still takes up too much time during the backporting of fixes to older branches. Speeding up (and fixing, see #42385) branch test suites means less stress for committers and less risk taking.

The "Latest 5.x PHP version" job can be removed if there's also a corresponding object cache job. The likelihood of a PHP 5.x issue being introduced into an older branch which doesn't also affect 5.x with an object cache in place is vanishingly small.

I contemplated removing the PHP 5.2 job too, but I'm undecided.

Change History (19)

#1 @jorbin
22 months ago

  • Milestone changed from 5.0 to 5.1

#2 @desrosj
19 months ago

  • Milestone changed from 5.1 to Future Release

Moving to Future Release with #42385.

#3 @johnbillion
17 months ago

In 44991:

Build/Test tools: Trim the test matrix on Travis in order to speed up the 4.9 branch build.

This removes the PHP 7.1, 7.0, 5.5, 5.4, 5.3, and nightly jobs.

See #42387, #40407

#4 @johnbillion
17 months ago

In 44992:

Build/Test tools: Trim the test matrix on Travis in order to speed up the 5.0 branch build.

This removes the PHP 7.2, 7.1, 7.0, 5.5, 5.4, 5.3, and nightly jobs.

See #42387, #40407

#5 @netweb
17 months ago

  • Keywords needs-patch removed
  • Milestone changed from Future Release to 5.2
  • Resolution set to fixed
  • Status changed from new to closed

#6 follow-up: @johnbillion
17 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

I've decided to trim the standard 5.6 job too, leaving just the object cache job for 5.6. See comments above. @netweb any objections?

Version 0, edited 17 months ago by johnbillion (next)

#7 in reply to: ↑ 6 @netweb
17 months ago

Replying to johnbillion:

@netweb any objections?

None, go for it

#8 @johnbillion
17 months ago

  • Owner set to johnbillion
  • Status changed from reopened to accepted

#9 @johnbillion
17 months ago

In 45005:

Build/Test tools: Further trimming of CI jobs on the 5.0 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

See #42387

#10 @johnbillion
17 months ago

In 45006:

Build/Test tools: Further trimming of CI jobs on the 4.9 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

Merges [45005] into the 4.9 branch.

See #42387

#11 @johnbillion
17 months ago

In 45007:

Build/Test tools: Further trimming of CI jobs on the 4.8 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

Merges [45005] into the 4.8 branch.

See #42387

#12 @johnbillion
17 months ago

In 45008:

Build/Test tools: Further trimming of CI jobs on the 4.7 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

Merges [45005] into the 4.7 branch.

See #42387

#13 @johnbillion
17 months ago

In 45009:

Build/Test tools: Further trimming of CI jobs on the 4.6 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

Merges [45005] into the 4.6 branch.

See #42387

#14 @johnbillion
17 months ago

In 45010:

Build/Test tools: Further trimming of CI jobs on the 4.5 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

See #42387

#15 @johnbillion
17 months ago

In 45011:

Build/Test tools: Further trimming of CI jobs on the 4.4 branch.

This removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

Merges [45010] into the 4.4 branch.

See #42387

#16 @johnbillion
17 months ago

  • Resolution set to fixed
  • Status changed from accepted to closed

#17 @SergeyBiryukov
6 months ago

In 47322:

Build/Test Tools: Trim the test matrix on Travis in order to speed up the 5.1 branch build.

This removes the PHP 7.2, 7.1, 5.5, 5.4, and 5.3 jobs.

This also removes the PHP 5.6 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 5.6 environments without an object cache is small.

Merges [44992] and [45005] to the 5.1 branch.
See #42387, #40407.

#18 @SergeyBiryukov
6 months ago

In 47323:

Build/Test Tools: Move the PHP 7.3 Travis job in 5.0 branch after the JS tests, for consistency with other branches.

See #42387, #40407.

#19 @desrosj
2 months ago

In 47928:

Build/Test Tools: Trim the test matrix on Travis in order to speed up the 5.2 branch build.

This removes the PHP 7.2 and 7.1 jobs.

This also removes the PHP 7.3 job which runs without an object cache in place as the likelihood of a change being backported that only breaks 7.3 without an object cache is small.

See #42387, #40407.

Note: See TracTickets for help on using tickets.