You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

What is an update GitHub Status Build Event Handler?

The 'Update Github status Build Event handler' is an event handler which interacts with the Github Status API.  This feature allows ContinuaCI to mark commits within a GitHub repository with a success, error, or pending state.  The status can then be reflected in any pull requests involving those commits.

Example use case

This event handler works fantastically as a pre-step within a pull request pipeline.  ContinuaCI can be configured to automatically pull the request, build it, test it, and report back its status.

How to create an update GitHub Status Build Event Handler

  1. Navigate to the events tab within the desired Build Configuration
  2. Click the 'Create' link within the 'Build Event Handlers' section

Select an Event Handler

  1. Enter the name of the event handler (in this case 'Update Github Status')
  2. Enter the sequence in which you wish this event handler to be run.  In our case this is the first event handler so we will leave the default of 1
  3. From the type dropdown select 'Update GitHub Status'

Select Build Event Handler

Event Handler Name

Friendly name for the event Handler (this will be visible in the 'Events' section of the website)

Run order

The order in which the event handler will be run (relevant in the situation where multiple event handlers are present).

Enabled

Whether this specific event handler is able to be run

Type

The type of event handler (Octopus Deploy, Tag Repository Changeset, Update GitHub Status) 

Update GitHub Status

  1. Enter the GitHub API URL.

  2. Enter your GitHub Username / Password.
  3. Enter your access token.
  4. Enter the name of the ContinuaCI repositories that you wish to consider when updating status (these can be found on the 'repositories' page).


    GitHub Url

    The URL of the GitHub API endpoint to be used (more specific details on this can be found: here).

    Username

    The GitHub Username used to login (this user should have access to the repository in question).

    Password

    The GitHub Password used to login (passwords should not contain any of the following characters: !:@).

    Access Token

    The Access Token used to submit information to GitHub (A detailed explanation on how to create and maintain an access token can be found within the github documentation).

    Repositories

    A comma separated list of repository names to apply this status information to.

When To Run

  1. Enter the stage timings when this event handler should be run.


    Start Stage 

    The stage timing when the 'Pending Comment' text will be sent 

    End Stage 

    The stage timing when the 'Pending Comment' text will be sent 

    Complete on Waiting Promotion

    If any stage is awaiting promotion, send the Success or Failure Comment

Comments

  1. Enter the comments that you wish to send to GitHub


    Pending Comment

    The text of the comment that will be sent when the stage hits the specified 'Start Stage' timing.

    Failure Comment

    The text of the comment that will be sent when the stage hits the specified 'End Stage' timing, and the build has failed.

    Success Comment

    The text of the comment that will be sent when the stage hits the specified 'End Stage' timing, and the build has Succeeded.

Comments

  1. Select the build options for this event handler


    Wait for Results

    Should the event handler wait for the result before proceeding. Unchecking this option will run the tagging action in a separate thread.  

    Fail Build on Error

    Whether or not to Fail the build if this event handler fails.

    Log Build Messages

    Whether or not logs for this event handler will be displayed in the build log.

 

 

 

  • No labels