Re: [ovirt-users] Re: [ovirt-devel] Re: Mailing-Lists upgrade
by Marc Dequènes (Duck)
Quack,
On 05/13/2018 08:27 PM, Alex K wrote:
> I am also experiencing random issues with this mailing list, even before
> the upgrade. Some replies I never receive them ( I know this because a
> friend of mine relays the emails I dont get...). I tried to unsubscribe
> and subscribe but I still face this issue.
Well, as it happened before the migration I guess it's more of mail
antispam & co problem. Could you open a JIRA ticket with as much
information as you can on the subject please?
I'm going to focus on migration problems first, but I'll a look at it
afterwards.
\_o<
6 years, 7 months
[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2020?page=com.atlassian.jir... ]
Daniel Belenky reassigned OVIRT-2020:
-------------------------------------
Assignee: Daniel Belenky (was: infra)
> Implement a normalizer for runtime_requirements
> -----------------------------------------------
>
> Key: OVIRT-2020
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Standard CI (Pipelines), STDCI DSL
> Reporter: Daniel Belenky
> Assignee: Daniel Belenky
>
> Currently, we are not parsing the data under runtime_requirements at all.
> It means that the 1st place user will encounter an error is when the job runs -
> it's bad since debugging it is much harder than our DSL.
> Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in
> standard-stage.groovy that verifies the value of some inputs under runtime_requirements.
> It should be removed as soon as a proper normalizer is implemented.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100083)
6 years, 7 months
[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA)
Daniel Belenky created OVIRT-2020:
-------------------------------------
Summary: Implement a normalizer for runtime_requirements
Key: OVIRT-2020
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Standard CI (Pipelines), STDCI DSL
Reporter: Daniel Belenky
Assignee: infra
Currently, we are not parsing the data under runtime_requirements at all.
It means that the 1st place user will encounter an error is when the job runs -
it's bad since debugging it is much harder than our DSL.
Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in
standard-stage.groovy that verifies the value of some inputs under runtime_requirements.
It should be removed as soon as a proper normalizer is implemented.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100083)
6 years, 7 months
[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2020?page=com.atlassian.jir... ]
Daniel Belenky updated OVIRT-2020:
----------------------------------
Epic Link: OVIRT-400
> Implement a normalizer for runtime_requirements
> -----------------------------------------------
>
> Key: OVIRT-2020
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Standard CI (Pipelines), STDCI DSL
> Reporter: Daniel Belenky
> Assignee: infra
>
> Currently, we are not parsing the data under runtime_requirements at all.
> It means that the 1st place user will encounter an error is when the job runs -
> it's bad since debugging it is much harder than our DSL.
> Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in
> standard-stage.groovy that verifies the value of some inputs under runtime_requirements.
> It should be removed as soon as a proper normalizer is implemented.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100083)
6 years, 7 months