June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1953) Add PPC mirrors
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1953?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1953: -------------------------------- Epic Link: (was: OVIRT-400) > Add PPC mirrors > --------------- > > Key: OVIRT-1953 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1953 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI Mirrors > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1958) Allow custom checkout dir
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1958?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1958: ------------------------------------- [~dbelenky(a)redhat.com] I think we fixed this already no? there is no patch attached... > Allow custom checkout dir > ------------------------- > > Key: OVIRT-1958 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1958 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: infra > > Currently, we assume that the checkout dir has the same name as the project. This should be configurable by environment variable passed from JJB. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1958) Allow custom checkout dir
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1958?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1958: -------------------------------- Epic Link: (was: OVIRT-400) > Allow custom checkout dir > ------------------------- > > Key: OVIRT-1958 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1958 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: infra > > Currently, we assume that the checkout dir has the same name as the project. This should be configurable by environment variable passed from JJB. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1958) Allow custom checkout dir
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1958?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1958: -------------------------------- Epic Link: (was: OVIRT-400) > Allow custom checkout dir > ------------------------- > > Key: OVIRT-1958 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1958 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: infra > > Currently, we assume that the checkout dir has the same name as the project. This should be configurable by environment variable passed from JJB. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[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-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