[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by eedri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jir... ]
eedri reassigned OVIRT-1477:
----------------------------
Assignee: Barak Korren (was: infra)
> Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
> ---------------------------------------------------------------------------------------
>
> Key: OVIRT-1477
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: Barak Korren
> Labels: repositories
>
> The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs.
> As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions.
--
This message was sent by Atlassian JIRA
(v1000.1089.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1257) Setup mail delivery from Jenkins and slaves
by eedri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1257?page=com.atlassian.jir... ]
eedri reassigned OVIRT-1257:
----------------------------
Assignee: Marc Dequènes (Duck) (was: infra)
> Setup mail delivery from Jenkins and slaves
> -------------------------------------------
>
> Key: OVIRT-1257
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1257
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: Marc Dequènes (Duck)
> Priority: High
>
> I'm setting up some jobs that will require Jenkins and/or the slaves to send email to various places. Jenkins and the slaves seem to currently run Postfix in a default configuration that makes them attempt to deliver email directly to its destination. This causes sent email to get delayed.
> We typically don't notice this because our SPF setting for ovirt.org are quite lax (We allow anyone to say he is from @ovirt.org, but delay messages that are not from "{{lists.phx.ovirt.org}}, "{{mail.phx.ovirt.org}}", or "{{gerrit.ovirt.org}}") abd because our ML server where we typically send to, only imposes a 60second delay.
> We need to have a better setup. I suggest we configure Jenkins and the slaves to use some other server as a smart host (maybe "{{mail.phx.ovirt.org}}"?). To make the configuration as generic as possible I suggest we make the slaves deliver via Jenkins and only make Jenkins deliver to the smart host.
> I think smart host configuration on Postfix is simple enough that we can make our usual job-embedded slave setup scrips set it up insead of having to resort to Puppet or Ansible.
--
This message was sent by Atlassian JIRA
(v1000.1089.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1477:
--------------------------------
Labels: repositories (was: )
> Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
> ---------------------------------------------------------------------------------------
>
> Key: OVIRT-1477
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: infra
> Labels: repositories
>
> The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs.
> As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions.
--
This message was sent by Atlassian JIRA
(v1000.1089.0#100053)
7 years, 4 months