June 2018 - Infra - oVirt List Archives

[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

[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

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2168: -------------------------------- Epic Link: (was: OVIRT-400) > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > 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 have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2168: -------------------------------- Epic Link: (was: OVIRT-400) > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > 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 have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2168: -------------------------------- Component/s: Standard CI (Pipelines) STDCI Build Report > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > 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 have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2169) Show important thread information in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2169?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2169: -------------------------------- Epic Link: (was: OVIRT-400) > Show important thread information in STDCI build summary > -------------------------------------------------------- > > Key: OVIRT-2169 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2169 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > When debugging builds on STDCI I want to have quick access to information about thread's execution environment such as: hostname it's being executed on, host's distro and arch, maybe even some basic specs of the host(?) so I won't have to search for this information in Console Output. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0