[JIRA] (OVIRT-1095) replace experimental release rpm with 'oVirt tested' repo
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-1095:
------------------------------------------------
Summary: replace experimental release rpm with 'oVirt tested' repo
Key: OVIRT-1095
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1095
Project: oVirt - virtualization made easy
Issue Type: Task
Reporter: eyal edri [Administrator]
Assignee: infra
We now have an oVirt 'tested' repo [1] which is updated from latest.tested, but also retains versions backwards, so anyone using it doesn't need to worry RPMs might disappear in the middle of a test.
First, lets replace master, if it goes well, continue to all versions.
--
This message was sent by Atlassian JIRA
(v1000.718.4#100026)
7 years, 9 months
[JIRA] (OVIRT-1046) Re: Gerrit hooks sometimes doesn't update bugs status
by Shlomo Ben David (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1046?page=com.atlassian.jir... ]
Shlomo Ben David closed OVIRT-1046.
-----------------------------------
Resolution: Fixed
> Re: Gerrit hooks sometimes doesn't update bugs status
> -----------------------------------------------------
>
> Key: OVIRT-1046
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1046
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: Shlomo Ben David
>
> On Tue, Jan 17, 2017 at 11:06 PM, Tal Nisan <tnisan(a)redhat.com> wrote:
> > I've encountered that a few times today, here's on example:
> >
> > https://gerrit.ovirt.org/#/c/70701/
> >
> > Patch Set 1: Verified-1
> >
> > - Update Tracker::#1413961::OK, status: POST
> >
> > While the tracker was indeed added, you can see that the bug was not
> > updated to post status
> >
> > After the merge:
> >
> > - Update Tracker::#1413961::OK, status: MERGED
> > - set_MODIFIED: OK
> >
> > And the bug was not updated to modified status
> >
> The bug shouldn't change status on master patch, but should have on 4.1, so
> its a bug, thanks for reporting.
> My suspicion is it has to do with the milestone being not in the format of
> ovirt-x.y.z.
> I'm sure Shlomi can debug it in no time and provide a fix.
> >
> > Thanks in advance.
> >
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.718.4#100026)
7 years, 9 months
[ANN] oVirt 4.1.0 Release is now available
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.1.0 Release, as of February 1st, 2017
This major release update is the first of the 4.1 release series.
4.1.0 brings more than 260 enhancements and 790 bugfixes, including 340
high or urgent
severity fixes, on top of oVirt 4.0 series
See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.
This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)
* oVirt Node 4.1
Notes:
- oVirt Live iso is already available[2]
- oVirt Node NG iso is already available[2]
- Hosted Engine appliance is already available.
- oVirt Windows Guest Tools iso is already available[2]
- Mirrors[3] might need up to one day to synchronize.
Additional Resources:
* Read more about the oVirt 4.1.0 release highlights:
http://www.ovirt.org/release/4.1.0/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.1.0/
[2] http://resources.ovirt.org/pub/ovirt-4.1/iso/
[3] http://www.ovirt.org/Repository_mirrors#Current_mirrors
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 9 months
[JIRA] (OVIRT-922) Add new project to standard ci from github
by Ondra Machacek (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira... ]
Ondra Machacek commented on OVIRT-922:
--------------------------------------
I would need to comunicate also with Ansible community to approve that. But I would like to achieve, that once some patch changes specific files(ovirt) in https://github.com/ansible/ansible I would like to trigger oVirt jenkins which executes OST 'ansible-master-suite'.
> Add new project to standard ci from github
> ------------------------------------------
>
> Key: OVIRT-922
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Jenkins
> Reporter: Ondra Machacek
> Assignee: infra
>
> I would like to request a jenkins machine for Ansible modules tests.
> Those tests needs host with nested virtualization as it will create a few virtual machines for tests.
> Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible.
> Then I would need some possibility to run this job from a hook from github, when new commit is pushed.
> The tests are described here for an idea:
> https://github.com/machacekondra/ovirt-tests
> Would that be possible?
--
This message was sent by Atlassian JIRA
(v1000.718.4#100026)
7 years, 9 months