[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Parichay Barpanda updated JENKINS-61020 Jenkins / JENKINS-61020 Allow custom context for commit status Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.17740.1587834120575%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Parichay Barpanda updated JENKINS-61020 Jenkins / JENKINS-61020 Allow custom context for commit status Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.17738.1587834120545%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Parichay Barpanda started work on JENKINS-61020 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.6434.1585995010252%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Kyle Manna commented on JENKINS-61020 Re: Allow custom context for commit status Interested in this as well. Provided an example of how I use it and how it worked for Bitbucket on the GitHub PR. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.5620.1581360600169%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Michael Musenbrock commented on JENKINS-61020 Re: Allow custom context for commit status A proposal is added as a PR: https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/75 I would be really happy about any feedback and maybe some hints for a proper name of the feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.4637.1581116100282%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Michael Musenbrock created an issue Jenkins / JENKINS-61020 Allow custom context for commit status Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2020-02-07 22:41 Labels: pipeline multi-branch gitlab Priority: Major Reporter: Michael Musenbrock Currently it is only possible to have a single job using the gitlab-branch-source-plugin for a repository due to the fact, that the context of the status updates is always 'jenkinsci/(branch|mr-head|mr-merge|tag)'. I see the reason in an ideal world, to have one job per project, but in real-life I stumbled to often over exactly that issue (previously on github projects). We have currently two use-cases for multiple jobs per repo. First: Large project which has troubles with flaky UI-Tests. So UI-Tests are done in a separate Job to see clearly, that at least the build, code analysis, and the deployment works fine, regardless of the flakiness of the tests. So it would be great to have a 'jenkinsci/ui/branch' and a 'jenkinsci/build-and-deploy/branch' context. Second: A project which consists of different modules in one repo, where every module has it's own multibranch-pipeline. Here a 'jenkinsci/server/branch' and a 'jenkinsci/client/branch' would be of use.
