[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run
post-merge tasks
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2037:
--------------------------------
Epic Link: (was: OVIRT-400)
> Patchsets from non-whitelisted users can't run post-merge tasks
> ---------------------------------------------------------------
>
> Key: OVIRT-2037
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2037
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Standard CI (Freestyle)
> Reporter: Daniel Belenky
> Assignee: infra
>
> In some cases, even if a patch was created by a non-whitelisted user, project maintainer can decide to merge
> the patch. Currently, STDCI (V1) will block the patch from running any post-merge jobs due to whitelist check.
> We need to allow project maintainers to bypass the whitelist check or disable whitelist checking on post-merge jobs.
> Note: If we decide to disable whitelist check on post-merge jobs, we need to make sure we run post-merge jobs only on *merged* patchsets.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2039) Make JJB able to configure all aspects of the
Jenkins master
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2039?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2039:
--------------------------------
Epic Link: (was: OVIRT-400)
> Make JJB able to configure all aspects of the Jenkins master
> ------------------------------------------------------------
>
> Key: OVIRT-2039
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2039
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: JJB
> Reporter: Barak Korren
> Assignee: infra
> Labels: upstream-contribution
>
> There are two aspects of jenkins that JJB knows how to configure at this time:
> # Jobs
> # Views
> There are however, other important aspects of the Jenkins configuration one typically needs to deal with:
> # Plugins
> # Credentials
> # Global configuration setting such as global environment
> # Gerrit and GitHub trigger settings
> # Custom user data
> It is desirable that JJB would be able to encompass all the required configuration for a given Jenkins instance. We should consider enabling it to configure the setting mentioned above and contribute that work to the upstream JJB project or distribute it as a separate plugin.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2039) Make JJB able to configure all aspects of the
Jenkins master
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2039?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2039:
--------------------------------
Epic Link: (was: OVIRT-400)
> Make JJB able to configure all aspects of the Jenkins master
> ------------------------------------------------------------
>
> Key: OVIRT-2039
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2039
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: JJB
> Reporter: Barak Korren
> Assignee: infra
> Labels: upstream-contribution
>
> There are two aspects of jenkins that JJB knows how to configure at this time:
> # Jobs
> # Views
> There are however, other important aspects of the Jenkins configuration one typically needs to deal with:
> # Plugins
> # Credentials
> # Global configuration setting such as global environment
> # Gerrit and GitHub trigger settings
> # Custom user data
> It is desirable that JJB would be able to encompass all the required configuration for a given Jenkins instance. We should consider enabling it to configure the setting mentioned above and contribute that work to the upstream JJB project or distribute it as a separate plugin.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months