Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#44276 closed task (blessed) (fixed)

Add AppVeyor Windows-based CI (Continuous Integration) Service

Reported by: netweb's profile netweb Owned by: pento's profile pento
Milestone: 5.1 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: has-patch commit
Focuses: Cc:

Description

AppVeyor is a Windows-based CI (Continuous Integration) Service https://www.appveyor.com/

With issues arising such as #44262 (Build tools: "grunt watch" throws fatal error on Windows)

By adding AppVeyor we can hopefully prevent some basic issues when running WordPress' build tools on Windows-based platforms.

In future iterations, we can investigate further build tools testing, be it Grunt tasks, Webpack, PHPCS, or PHPUnit


Once the forthcoming patch has been committed the following is required to set up the GitHub and Slack integrations for the https://github.com/WordPress/wordpress-develop repo :


Here is the latest CI build from my mirror: https://ci.appveyor.com/project/ntwb/wordpress/build/1.0.3

Attachments (1)

44276.diff (542 bytes) - added by netweb 6 years ago.

Download all attachments as: .zip

Change History (7)

@netweb
6 years ago

#1 @jorbin
6 years ago

  • Milestone changed from 5.0 to 5.1

#2 @pento
6 years ago

  • Owner set to pento
  • Status changed from new to assigned

#3 @pento
6 years ago

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

In 44594:

Build Tools: Add AppVeyor integration.

AppVeyor allows us to test in a Windows environment. This first iteration tests that building works correctly.

Props netweb.
Fixes #44276.

#4 @pento
6 years ago

In 44595:

Build Tools: Tweak AppVeyor settings.

  • Set grunt build as the build script
  • Disable testing and deployment options
  • Customise the Slack integration message
  • Only show the Slack message when the status changes

See #44276.

#5 @pento
6 years ago

In 44599:

Build Tools: Don't send AppVeyor notifications on Slack on repeated successful builds.

See #44276.

This ticket was mentioned in Slack in #core by desrosj. View the logs.


6 years ago

Note: See TracTickets for help on using tickets.