2:53 a.m.
On Mon, Feb 13, 2017 at 9:59 PM, Greg Sheremeta <gshereme(a)redhat.com> wrote:
On Mon, Feb 13, 2017 at 3:55 PM, Eyal Edri <eedri(a)redhat.com>
wrote:
>
>
> On Mon, Feb 13, 2017 at 10:34 PM, Martin Perina <mperina(a)redhat.com>
> wrote:
>
>> Hi,
>>
>> why is this package not contained also in ovirt-master-snapshot
>> repository [6]? Most of developers are using ovirt-master-snapshot, because
>> this is the official repository for oVirt depelopers as mentioned in [7]
>> and [8]. AFAIK there was not yet any official announcement that every
>> developer should switch from ovirt-master-snapshot to ovirt-tested-master
>> ...
>>
>
> I think we should make it official then for master, we've hit too many
> issues in the past weeks due to this repository, that I don't want to see
> new projects added to it.
>
You've run into issues, because
migration to the "new" system is not well prepared. I'm still a bit angry
that you have forced me to migrate all ovirt-engine-extensions* projects
into standard CI (which took me more than 2 days) by breaking existing
build jobs which worked fine until recent changes. And I had to do fast
that otherwise I won't be able to provide new build for upstream 4.1.0
async and 4.1.1 builds ...
So I don't have an issue to move from ovirt-master-snapshot repos to
ovirt-tested-master repos, but please do that properly:
1. Announce on mailing lists that every developer should switch at least
a week before the change
2. Update all developer related documentation about this change
2. Maintain both repos for a week and only after that turn off
ovirt-master-snapshots repos
Also, AFAIK, these are build time dependencies only right? so they are not
> really needed for be in oVirt repo as deliverables, and just
needed for
> other projects to use for building them.
> If this is the case, then the new Standard CI feature of serving each
> build-artifacts job as yum repo can also be used instead of the snapshot
> repo, e.g.,
>
> http://jenkins.ovirt.org/job/ovirt-engine-yarn_master_build-
> artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/ is
> a yum repo which points to the latest successful build of ovirt-engine-yarn
> master.
>
Exported artifacts is not enough, please provide
ovirt-release-tested-master RPM which will include all necessary
repositories same way as we currenlty have in ovirt-release-master
This is a runtime dependency, actually. (Some of the js stuff is
build-time, but this is our only runtime one.)
And yes, we could also use the new-style build_artifacts repo, but I
thought tested-master was nicer for this use case.
@Martin, Eyal beat me to it -- tested-master is the future repo, for
reasons he mentioned. tested-master is all outputted from OST, so you know
it's good! ;)
Greg
>
>
>>
>> Martin
>>
>> [6] http://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/
>> [7] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob_pl
>> ain;f=README.adoc;hb=HEAD
>> [8] http://www.ovirt.org/develop/developer-guide/engine/engine-d
>> evelopment-environment/
>>
>>
>> On Mon, Feb 13, 2017 at 8:42 PM, Greg Sheremeta <gshereme(a)redhat.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Tomorrow (Tues Feb 14) we'll merge a patch [1] that upgrades the
>>> version of PatternFly used by webadmin and userportal to the latest 3.y
>>> version.
>>>
>>> In addition to updating the library, we've also changed the delivery
>>> mechanism. We're no longer maintaining a PatternFly RPM on copr [2]. The
>>> new method is a new project called ovirt-js-dependencies [3] that contains
>>> any runtime JS dependencies required by the engine -- currently patternfly,
>>> bootstrap, and jquery. This project is using oVirt Standard CI [4], and
>>> thus you should get the RPM from the tested master repo [5].
>>>
>>> TL;DR: What you need to do (from the README)
>>> Set Up the Tested Master Repository
>>>
>>> * Automatically
>>> - Run the following command (replace `@distro@` in the following code
>>> block
>>> with `fc` for Fedora or `el` for RHEL or an equivalent distribution):
>>>
>>> # dnf config-manager --add-repo \
>>> http://plain.resources.ovirt.org/repos/ovirt/tested/master/r
>>> pm/@distro@/
>>>
>>> * Manually
>>> - Create the file `/etc/yum.repos.d/ovirt-tested-master.repo`, and
>>> replace
>>> `@distro@` in the following code block with `fc` for Fedora or `el`
>>> for RHEL
>>> or an equivalent distribution.
>>>
>>> [ovirt-tested-master]
>>> name=ovirt-tested-master
>>> baseurl=http://plain.resources.ovirt.org/repos/ovirt/tested/
>>> master/rpm/@distro@/
>>> enabled=1
>>> gpgcheck=0
>>>
>>> And then
>>>
>>> sudo dnf install ovirt-js-dependencies
>>>
>>>
>>> Let me know if you have any questions.
>>>
>>> Best wishes,
>>> Greg
>>>
>>> [1] https://gerrit.ovirt.org/#/c/61716
>>> [2] https://copr.fedorainfracloud.org/coprs/patternfly/patternfly1/
>>> [3] https://gerrit.ovirt.org/#/admin/projects/ovirt-js-dependencies
>>> [4] http://www.ovirt.org/develop/dev-process/build-and-test-standards/
>>> [5] http://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/
>>> <distro>
>>>
>>>
>>> --
>>> Greg Sheremeta, MBA
>>> Red Hat, Inc.
>>> Sr. Software Engineer
>>> gshereme(a)redhat.com
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018 <+972%209-769-2018>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
--
Greg Sheremeta, MBA
Red Hat, Inc.
Sr. Software Engineer
gshereme(a)redhat.com