- Infra - oVirt List Archives

[JIRA] (OVIRT-1959) Make usrc.py support Git tags
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1959?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1959: -------------------------------- Epic Link: OVIRT-1124 (was: OVIRT-400) > Make usrc.py support Git tags > ----------------------------- > > Key: OVIRT-1959 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1959 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: usrc.py > Reporter: Barak Korren > Assignee: infra > > There are multiple features that could be useful to add to {{usrc.py}} that has to do with Git tags: > # *Snap to tag* - when running {{update}} take the latest tagged commit from the branch instead of the latest commit. This could further be enhanced to decide what to do when there is no tagged commit that is newer then what we already have - we can either decide not to update or update to the latest (untagged) commit. > # *Copy tag* - when running with {{--commit}} and the upstream commit we're updating into is tagged, store some information somewhere so that if the commit is merged, the CI system could tag it automatically and push that tag. It should be possible to customise the tag we add to allow it to be different but derived from the upstream tag. One possible place to store the needed information is to use a header in the commit message like we do for auto-merge. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1960: -------------------------------- Epic Link: (was: OVIRT-400) > Make pusehr.py able to push Git tags > ------------------------------------ > > Key: OVIRT-1960 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > > {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: > # It should be possible to request that and arbitrary tag for HEAD be created and pushed. This should make it possible to implement OVIRT-1717 > # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1960: -------------------------------- Epic Link: (was: OVIRT-400) > Make pusehr.py able to push Git tags > ------------------------------------ > > Key: OVIRT-1960 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > > {{pusher.py}} knows how to push patches into remote SCMs. WE should also add functionality for pushing tags. More specifically: > # It should be possible to request that and arbitrary tag for HEAD be created and pushed. This should make it possible to implement OVIRT-1717 > # It should be possible to create and push a tag with information that is gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1963) Nicer UI for OST manual job
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1963?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1963: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Nicer UI for OST manual job > ---------------------------- > > Key: OVIRT-1963 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > Make the following details shown in the builds list of the OST manual job so that finding a particular build in the builds list is easier: > # The person who triggered the build > # The suit that was run > # The amount of URLs passed into extra-sources, and if possible - the name of the project whose modified packages were included. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1963) Nicer UI for OST manual job
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1963?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1963: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Nicer UI for OST manual job > ---------------------------- > > Key: OVIRT-1963 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > Make the following details shown in the builds list of the OST manual job so that finding a particular build in the builds list is easier: > # The person who triggered the build > # The suit that was run > # The amount of URLs passed into extra-sources, and if possible - the name of the project whose modified packages were included. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1965) Add failure details to CQ messages
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1965?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1965: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Add failure details to CQ messages > ---------------------------------- > > Key: OVIRT-1965 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > > In order to streamline the process for debugging CQ issues, we should have more failure details added to the messages it sends. Those details should include: > # The names of the OST suits that failed > # The OST tests that failed > # If it was a build failure rather then an OST failure > # If it was possible to detect - the particular change(s) that caused failure. > #if its possible to tell - if its an infra issue or a code regression > To implement this we would need at the very least a richer interface for passing information between the CQ tester and the and manager jobs - possibly some kind of a structured data file passed around. We may also need a richer interface to OST itself (to tell which test failed) and perhaps even to the build jobs (to tell why the build failed). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1965) Add failure details to CQ messages
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1965?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1965: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Add failure details to CQ messages > ---------------------------------- > > Key: OVIRT-1965 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > > In order to streamline the process for debugging CQ issues, we should have more failure details added to the messages it sends. Those details should include: > # The names of the OST suits that failed > # The OST tests that failed > # If it was a build failure rather then an OST failure > # If it was possible to detect - the particular change(s) that caused failure. > #if its possible to tell - if its an infra issue or a code regression > To implement this we would need at the very least a richer interface for passing information between the CQ tester and the and manager jobs - possibly some kind of a structured data file passed around. We may also need a richer interface to OST itself (to tell which test failed) and perhaps even to the build jobs (to tell why the build failed). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1973: -------------------------------- Issue Type: Outage (was: By-EMAIL) > vdsm_master_check-patch-fc27 fail due to yum repo issues > -------------------------------------------------------- > > Key: OVIRT-1973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects > Reporter: danken > Assignee: infra > > Once in a while, jobs are failing due to > [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful, > but checksum doesn't match. Calculated: > 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256) > Expected: 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256) > for example > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1973: -------------------------------- Epic Link: (was: OVIRT-400) > vdsm_master_check-patch-fc27 fail due to yum repo issues > -------------------------------------------------------- > > Key: OVIRT-1973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI client projects > Reporter: danken > Assignee: infra > > Once in a while, jobs are failing due to > [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful, > but checksum doesn't match. Calculated: > 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256) > Expected: 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256) > for example > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1973: -------------------------------- Epic Link: (was: OVIRT-400) > vdsm_master_check-patch-fc27 fail due to yum repo issues > -------------------------------------------------------- > > Key: OVIRT-1973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI client projects > Reporter: danken > Assignee: infra > > Once in a while, jobs are failing due to > [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful, > but checksum doesn't match. Calculated: > 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256) > Expected: 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256) > for example > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0