![]() ![]() In dynamic mode, CatLight requests the status of the specific build definitions from the server, and server returns only them.īoth modes use the same data model. It is easy to implement, but the amount of generated and returned data can be quite large. In basic mode, server returns all the build information on each polling cycle. Your server should implement one of them. ImplementationĬatLight protocol support two modes - basic and dynamic. Z at the end means that the time is in UTC time zone. When the build contains changes from multiple user, additional contributors can be placed here.ĬatLight will use "triggeredByUser" and "contributors" field to determine if this build is related to current user.īuild status can be one of the following:ĭateTime is represented in ISO date format. If the build started automatically after new commit, this should be the user that committed the code. ![]() ![]() (Optional) User that requested the build. Should be present for completed builds, but can be absent for running builds. Build Propertyīuild status, see below for the list of possible valuesĭate and time when this build was started. Note: if you don't see the branch in CatLight app UI, make sure that it has recent builds. For example, "refs/heads/master" will be transformed into "master". refs/remotes/origin/features/test-feature-branchĬatLight will cleanup branch id and use it as a display name for the branch.refs/heads/features/test-feature-branch.Return 5-10 builds for each branch.īranch id can be taken from source control. Last build in the array should be the newest. Id should be unique within the parent build definition. If your system cannot separate builds into branches, add a single branch to this array with id = "~all" BuildBranch Property Active feature branches that had builds in the past 30 days.Primary branches (master, develop, etc.).(Optional) path to the build definition, e.g. (Optional) Webpage that provides user with detailed information about this build definition. If your server has thousands of build definitions, put them into separate spaces to avoid performance problems. For most servers, space will map to a project or source control repository.ĬatLight apps exchange information about build investigations on space level. Space is a logical container of build definitions. Read more about basic and dynamic modes below. Protocol value can be one of the following: If your server has a built-in unique id that is very long, you can use a hash sum of it that should be shorter. Try to keep the id shorter than 100 symbols. If your server does not have unique id, you can generate a GUID during installation and save it to configuration file. For installed servers, use your domain or product name + unique installation id. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |