- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3152 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_429_1703133921.1477937583722 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3152/, Build Number: 3152, Build Status: SUCCESS ------=_Part_429_1703133921.1477937583722--

1 0

[JIRA] (OVIRT-803) [gerrit hooks] enable updating external tracker info for master branch
by Shlomo Ben David (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-803?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-803: ----------------------------------- Epic Link: OVIRT-403 > [gerrit hooks] enable updating external tracker info for master branch > ---------------------------------------------------------------------- > > Key: OVIRT-803 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-803 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > > - Currently we are not updating external tracker info for patches in 'master' branch. > - We should update both 'stable' and 'master' branch patches info in Bugzilla (external tracker) -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-803) [gerrit hooks] enable updating external tracker info for master branch
by Shlomo Ben David (oVirt JIRA) 31 Oct '16

31 Oct '16

Shlomo Ben David created OVIRT-803: -------------------------------------- Summary: [gerrit hooks] enable updating external tracker info for master branch Key: OVIRT-803 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-803 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra - Currently we are not updating external tracker info for patches in 'master' branch. - We should update both 'stable' and 'master' branch patches info in Bugzilla (external tracker) -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-803) [gerrit hooks] enable updating external tracker info for master branch
by Shlomo Ben David (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-803?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-803: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] enable updating external tracker info for master branch > ---------------------------------------------------------------------- > > Key: OVIRT-803 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-803 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > - Currently we are not updating external tracker info for patches in 'master' branch. > - We should update both 'stable' and 'master' branch patches info in Bugzilla (external tracker) -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #2936 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_427_404988837.1477936435734 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/2936/, Build Number: 2936, Build Status: SUCCESS ------=_Part_427_404988837.1477936435734--

1 0

Updating email configuration
by Shlomo Ben David 31 Oct '16

31 Oct '16

Hi All, Due to some restrictions on our email server we need to update our email configuration to increase the security on it. To apply the new configuration i will reboot the server today 31/10/2016 at 20:00 IST. *Downtime EST: ~5 minutes* Best Regards, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #2509 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_423_856995810.1477932712050 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/2509/, Build Number: 2509, Build Status: FAILURE ------=_Part_423_856995810.1477932712050--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #2935 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_421_255920690.1477932704450 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/2935/, Build Number: 2935, Build Status: SUCCESS ------=_Part_421_255920690.1477932704450--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3151 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_419_26124472.1477932217734 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3151/, Build Number: 3151, Build Status: SUCCESS ------=_Part_419_26124472.1477932217734--

1 0

[JIRA] (OVIRT-751) Persistent maven caches on the mock slaves
by Gil Shinar (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-751?page=com.atlassian.jira.p… ] Gil Shinar reassigned OVIRT-751: -------------------------------- Assignee: Gil Shinar (was: infra) > Persistent maven caches on the mock slaves > ------------------------------------------ > > Key: OVIRT-751 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-751 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: Gil Shinar > > I think we need to design a way to retain maven caches on the mocked jenkins slaves. Currently it is stored inside the mock and thus maven downloads packages from artifactory server each time. > However there is really no reason for that. Maven artifacts are designed to be immutable so once artifact is in the repo there is no trivial way to change it without creating a new version. In fact it should never be needed and the correct solution for that is to always create a new version. > SNAPSHOOT artifacts are in fact timestamped and each one have different file name. It is just not visible since maven automatically takes the latest one. But it is not related to caching as the new snapshoot will be a new artifact still. > So based on that point there is no reason to purge maven cache each time, but there are reasons why not to purge. Not purging them will reduce the build times of all java jobs and also reduce the network traffic we have. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0