Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add poule.yml #28143

Merged
merged 1 commit into from
Nov 8, 2016
Merged

Add poule.yml #28143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
81 changes: 81 additions & 0 deletions poule.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
# Add a "status/0-triage" to every newly opened pull request.
- triggers:
pull_request: [ opened ]
operations:
- type: label
settings: {
patterns: {
status/0-triage: [ ".*" ],
}
}

# For every newly created or modified issue, assign label based on matching regexp using the `label`
# operation, as well as an Engine-specific version label using `version-label`.
- triggers:
issues: [ edited, opened, reopened ]
operations:
- type: label
settings: {
patterns: {
area/builder: [ "dockerfile", "docker build" ],
area/distribution: [ "docker login", "docker logout", "docker pull", "docker push", "docker search" ],
area/plugins: [ "docker plugin" ],
area/networking: [ "docker network", "ipvs", "vxlan" ],
area/runtime: [ "oci runtime error" ],
area/security/trust: [ "docker_content_trust" ],
area/swarm: [ "docker node", "docker service", "docker swarm" ],
platform/desktop: [ "docker for mac", "docker for windows" ],
platform/freebsd: [ "freebsd" ],
platform/windows: [ "nanoserver", "windowsservercore", "windows server" ],
}
Copy link
Member

@AkihiroSuda AkihiroSuda Nov 8, 2016 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how about adding more:

area/testing: [ "FAIL: "],
area/plugins: [ "plugin"],
area/kernel: ["Kernel panic - "],
kind/bug: ["panic :"],
platform/arm: ["arm"],

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For plugins I already have:

    area/plugins: [ "docker plugin" ],

They all make sense, but I'm afraid of adding more until we can see these in effect 😉 Right now poule is not yet deployed, I intend to do it tomorrow first thing and see how it goes from there!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also we might need to rethink how matching is done here: I'm using these as regular expression against the lowercase title and body of issues. Something like "arm" is probably too likely to match because of this 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking of incorrect matches; do we have something to prevent Poule from adding the incorrect match again after manually correcting?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thaJeztah No 😢 It will do it again if the issue is edited, or closed/reopened.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@icecrime no worries, i'll open an issue for future enhancements

}
- type: version-label

# When a pull request is closed, attach it to the currently active milestone.
- triggers:
pull_request: [ closed ]
operations:
- type: version-milestone

# Labeling a PR with `rebuild/<configuration>` triggers a rebuild job for the associated
# configuration. The label is automatically removed after the rebuild is initiated. There's no such
# thing as "templating" in this configuration, so we need one operation for each type of
# configuration that can be triggered.
- triggers:
pull_request: [ labeled ]
operations:
- type: rebuild
settings: {
configurations: [ arm ],
label: "rebuild/arm",
}
- type: rebuild
settings: {
configurations: [ experimental ],
label: "rebuild/experimental",
}
- type: rebuild
settings: {
configurations: [ janky ],
label: "rebuild/janky",
}
- type: rebuild
settings: {
configurations: [ userns ],
label: "rebuild/userns",
}
- type: rebuild
settings: {
configurations: [ vendor ],
label: "rebuild/vendor",
}
- type: rebuild
settings: {
configurations: [ win2lin ],
label: "rebuild/win2lin",
}
- type: rebuild
settings: {
configurations: [ windowsRS1 ],
label: "rebuild/windowsRS1",
}