Skip to content
master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
bin
 
 
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 

An example of using CI for Haxe projects.

TravisCI Build Status AppVeyor Build Status Azure Pipelines Build Status

Same procedure is used for setting up both Travis CI, AppVeyor, and Azure Pipelines:

  1. Create a Haxe project if there isn't one.
  2. Create a new repo on GitHub.
  3. Turn on the switches for the GitHub repo on Travis CI/AppVeyor/Azure Pipelines.
  4. Copy and modify the configs:
  5. Commit the configs and push to GitHub.
  6. Watch it build:
    • https://travis-ci.com/${username}/${reponame} for Travis CI
    • https://ci.appveyor.com/project/${username}/${reponame} for AppVeyor
    • https://dev.azure.com/${organization}/${azureproject}/_build for Azure Pipelines
  7. Add badges to README:
    • https://travis-ci.com/${username}/${reponame}.svg?branch=master for Travis CI
    • https://ci.appveyor.com/api/projects/status/github/${username}/${reponame}?branch=master&svg=true for AppVeyor
    • https://dev.azure.com/${organization}/${azureproject}/_apis/build/status/${pipeline}?branchName=master for Azure Pipelines

CC0
To the extent possible under law, Andy Li has waived all copyright and related or neighboring rights to HaxeCI. This work is published from: Hong Kong.

About

An example of using CI for Haxe projects.

Topics

Resources

Releases

No releases published

Packages

No packages published