-
Notifications
You must be signed in to change notification settings - Fork 48
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.
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
fix release filtering and RBAC for releases #1023
Conversation
With the old implementation, when using more than one tag in the filter, or when using role which grants access to releases with given tag (and more than one tag was specified), deployments will present only releases containg ALL the tags each. With the new behavior, deployments will retrun all the releases containg ANY of the tags. Changelog: All Ticket: MEN-7272 Signed-off-by: Krzysztof Jaskiewicz <krzysztof.jaskiewicz@northern.tech>
Merging these commits will result in the following changelog entries: Changelogsdeployments (men-7272)New changes in deployments since master: Bug Fixes
|
@kjaskiewiczz, Let me know if you want to start the integration pipeline by mentioning me and the command "start pipeline". my commands and optionsYou can trigger a pipeline on multiple prs with:
You can start a fast pipeline, disabling full integration tests with:
You can trigger GitHub->GitLab branch sync with:
You can cherry pick to a given branch or branches with:
|
@mender-test-bot start pipeline --fast |
Hello 😺 I created a pipeline for you here: Pipeline-1307447514 Build Configuration Matrix
|
Hello 😺 This PR contains changelog entries. Please, verify the need of backporting it to the following release branches: |
With the old implementation, when using more than one tag in the filter, or when using role which grants access to releases with given tag (and more than one tag was specified), deployments will present only releases containg ALL the tags each.
With the new behavior, deployments will retrun all the releases containg ANY of the tags.
Ticket: MEN-7272