- Infra - oVirt List Archives

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2033?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2033: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Provide a "tagging" mecahnism for transactional mirrors. > -------------------------------------------------------- > > Key: OVIRT-2033 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now when using the CI mirrors, one can either: > # Use the latest snapshots from all mirrors as mock_runner and all the jobs do. > # Use a specific snapshot by using the direct URL to it as we do on slaves. > It is desirable to be able to mark or tag specific mirror snapshots for various uses. The primary use for this is to track which mirror snapshots have been tested successfully by the change queue in a similar fashion to the way we track passing packages by storing them in the 'tested' repo. The motivation behind doing this is described in OVIRT-1444 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2033?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2033: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Provide a "tagging" mecahnism for transactional mirrors. > -------------------------------------------------------- > > Key: OVIRT-2033 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now when using the CI mirrors, one can either: > # Use the latest snapshots from all mirrors as mock_runner and all the jobs do. > # Use a specific snapshot by using the direct URL to it as we do on slaves. > It is desirable to be able to mark or tag specific mirror snapshots for various uses. The primary use for this is to track which mirror snapshots have been tested successfully by the change queue in a similar fashion to the way we track passing packages by storing them in the 'tested' repo. The motivation behind doing this is described in OVIRT-1444 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2036: -------------------------------- Epic Link: (was: OVIRT-400) > Pre-merged patchsets can run on post-merged jobs in STDCI V2 > ------------------------------------------------------------ > > Key: OVIRT-2036 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs hence bypassing our whitelist filtering. > We need to fix it by checking if the event matches the actual state of the patch before running any user code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2036: -------------------------------- Epic Link: (was: OVIRT-400) > Pre-merged patchsets can run on post-merged jobs in STDCI V2 > ------------------------------------------------------------ > > Key: OVIRT-2036 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs hence bypassing our whitelist filtering. > We need to fix it by checking if the event matches the actual state of the patch before running any user code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2039) Make JJB able to configure all aspects of the Jenkins master
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2039?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2039) Make JJB able to configure all aspects of the Jenkins master
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2039?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2167?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2167: -------------------------------- Component/s: STDCI Build Report > Near real time log updates for STDCI build summary > -------------------------------------------------- > > Key: OVIRT-2167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI Build Report > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2167?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2167: -------------------------------- Epic Link: (was: OVIRT-400) > Near real time log updates for STDCI build summary > -------------------------------------------------- > > Key: OVIRT-2167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0