gitee.com/bomy/docker.git@v1.13.1/poule.yml (about)

     1  # Add a "status/0-triage" to every newly opened pull request.
     2  - triggers:
     3        pull_request: [ opened ]
     4    operations:
     5        - type:       label
     6          settings: {
     7              patterns: {
     8                  status/0-triage:     [ ".*" ],
     9              }
    10          }
    11  
    12  # For every newly created or modified issue, assign label based on matching regexp using the `label`
    13  # operation, as well as an Engine-specific version label using `version-label`.
    14  - triggers:
    15        issues:       [ edited, opened, reopened ]
    16    operations:
    17        - type:       label
    18          settings: {
    19              patterns: {
    20                  area/builder:        [ "dockerfile", "docker build" ],
    21                  area/distribution:   [ "docker login", "docker logout", "docker pull", "docker push", "docker search" ],
    22                  area/plugins:        [ "docker plugin" ],
    23                  area/networking:     [ "docker network", "ipvs", "vxlan" ],
    24                  area/runtime:        [ "oci runtime error" ],
    25                  area/security/trust: [ "docker_content_trust" ],
    26                  area/swarm:          [ "docker node", "docker service", "docker swarm" ],
    27                  platform/desktop:    [ "docker for mac", "docker for windows" ],
    28                  platform/freebsd:    [ "freebsd" ],
    29                  platform/windows:    [ "nanoserver", "windowsservercore", "windows server" ],
    30              }
    31          }
    32        - type:       version-label
    33  
    34  # When a pull request is closed, attach it to the currently active milestone.
    35  - triggers:
    36        pull_request: [ closed ]
    37    operations:
    38        - type:       version-milestone
    39  
    40  # Labeling a PR with `rebuild/<configuration>` triggers a rebuild job for the associated
    41  # configuration. The label is automatically removed after the rebuild is initiated. There's no such
    42  # thing as "templating" in this configuration, so we need one operation for each type of
    43  # configuration that can be triggered.
    44  - triggers:
    45        pull_request: [ labeled ]
    46    operations:
    47        - type:       rebuild
    48          settings: {
    49              # When configurations are empty, the `rebuild` operation rebuilds all the currently
    50              # known statuses for that pull request.
    51              configurations: [],
    52              label:          "rebuild/*",
    53          }
    54        - type:       rebuild
    55          settings: {
    56              configurations: [ arm ],
    57              label:          "rebuild/arm",
    58          }
    59        - type:       rebuild
    60          settings: {
    61              configurations: [ experimental ],
    62              label:          "rebuild/experimental",
    63          }
    64        - type:       rebuild
    65          settings: {
    66              configurations: [ janky ],
    67              label:          "rebuild/janky",
    68          }
    69        - type:       rebuild
    70          settings: {
    71              configurations: [ userns ],
    72              label:          "rebuild/userns",
    73          }
    74        - type:       rebuild
    75          settings: {
    76              configurations: [ vendor ],
    77              label:          "rebuild/vendor",
    78          }
    79        - type:       rebuild
    80          settings: {
    81              configurations: [ win2lin ],
    82              label:          "rebuild/win2lin",
    83          }
    84        - type:       rebuild
    85          settings: {
    86              configurations: [ windowsRS1 ],
    87              label:          "rebuild/windowsRS1",
    88          }