- Infra - oVirt List Archives

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by danken (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] danken commented on OVIRT-1014: ------------------------------- the translation of *.pacakges to yum command may include more than `cat`. each line may look like python-pthreading >= 0.1.3-3 > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #185 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

------=_Part_241_1562252617.1484056640786 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/185/, Build Number: 185, Build Status: FAILURE ------=_Part_241_1562252617.1484056640786--

1 1

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- {quote} could work for me. But I would like to be able to specify the version of package, in order to be able to generate spec file Requires: and BuildRequires: directives. {quote} The thing with this is that the '{{*.packages}}' file need to be translated to a single '{{yum install foo bar baz...}}' line. So there is not much versioning logic I can do. You can use exact versions though. I suppose we could implement more complex logic, but that will be equivalent to running '{{yum-builddep}' from inside the automation script (Which means, the results will not be cached, and the installation will be done every single time the job runs). We might be able to do more complex stuff when we get around to OVIRT-873. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

CI not running on ovirt-engine-dashboard-1.1 branch
by Greg Sheremeta 10 Jan '17

10 Jan '17

Hi, Even after [3] was merged, no CI is running on [1] and [2]. I tried "Re-run hooks: all" but no luck. Any ideas? Something else I need to do? Greg [1] https://gerrit.ovirt.org/#/c/69731/ [2] https://gerrit.ovirt.org/#/c/69735/ [3] https://gerrit.ovirt.org/#/c/69737/ -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com

3 3

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by danken (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] danken commented on OVIRT-1014: ------------------------------- We are using symlinks when possible. #include "./check-patch.packages" could work for me. But I would like to be able to specify the version of package, in order to be able to generate spec file Requires: and BuildRequires: directives. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4653 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

------=_Part_231_202001478.1484050214666 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4653/, Build Number: 4653, Build Status: FAILURE ------=_Part_231_202001478.1484050214666--

1 3

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #180 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

------=_Part_217_710524236.1484043988492 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/180/, Build Number: 180, Build Status: FAILURE ------=_Part_217_710524236.1484043988492--

1 4

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1014 at 1/10/17 3:15 PM: -------------------------------------------------------------- This had been asked for before. If the files are exact replicas symlinks can be used. WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms... WRT having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure. Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file. was (Author: bkorren(a)redhat.com) This had been asked for before. If the files are exact replicas symlinks can be used. WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms... WTR having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure. Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- This had been asked for before. If the files are exact replicas symlinks can be used. WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms... WTR having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure. Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by danken (oVirt JIRA) 10 Jan '17

10 Jan '17

danken created OVIRT-1014: ----------------------------- Summary: avoid repetition in automation/*packages Key: OVIRT-1014 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra Currently we have many automation/*packages* files, mostly repeating each other. Most of the information there is then repeated in vdsm.spec as well. It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0