May 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1403) Please upgrade the timestamper plugin to 8.8 or higher
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1403?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1403: -------------------------------- Epic Link: OVIRT-403 > Please upgrade the timestamper plugin to 8.8 or higher > ------------------------------------------------------ > > Key: OVIRT-1403 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1403 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Please upgrade the [timetamper|https://wiki.jenkins-ci.org/display/JENKINS/Timestamper] plugin. > The newer version includes better support for pipelines. -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1403) Please upgrade the timestamper plugin to 8.8 or higher
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

Barak Korren created OVIRT-1403: ----------------------------------- Summary: Please upgrade the timestamper plugin to 8.8 or higher Key: OVIRT-1403 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1403 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Please upgrade the [timetamper|https://wiki.jenkins-ci.org/display/JENKINS/Timestamper] plugin. The newer version includes better support for pipelines. -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1401) Request to become a public mirror
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1401?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1401: ----------------------------------- Assignee: Nadav Goldin (was: infra) > Request to become a public mirror > --------------------------------- > > Key: OVIRT-1401 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1401 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Philippe BEAUMONT > Assignee: Nadav Goldin > > Hi, > I'm Philippe from the company NFrance Conseil. I'm in charge to maintain > our public and private repositories. > As we are looking to use Ovirt, I allready made a mirror: > http://ovirt.repo.nfrance.com/ > We have a bandwich of 1Gbit on this repo. > NFrance Conseil is a french web hosting company with his own Network > Infrastructure (AS15826). We work mainly on OpenSource Software and > contribute when we can :) > I officialy ask to become a public mirror for Ovirt > This is the key to add on you authorized_keys: > ssh-rsa > AAAAB3NzaC1yc2EAAAADAQABAAABAQCxDuAJ0utqeqWqsq2zGJ4Ay87xDnmAZlMLQ7K/LvJXQAX/lh0w6lMUlLScR0FFWBa3guysU9vqfpxPIqnbdJJbEpnWrliEyVezd5CusdYCWI5GuVJHRmXI4yO3UnoYuiQ7Av6GO1jtncNUZtBbDmPG8eWccEPg0x9OO5c3GDaxqqtu7WeTB7BfO8W8KygsvqDffZ7ryBWeftQgykHejju9Mao51de1Q0U5ksYqjahusoEpLuG5dSEIS0LziM38lCukBGvtFopMMItKjuAOwqf4XSwp/f2e6u71geBzWRLMugpZtEnQRUgqwXti/fx9485ipp+EnSN1/hkXiIKHrEGL > repo(a)repo.nfrance.com > If you need more informations, feel free to ask me. > Regards, > Philippe Beaumont > NFrance Conseil -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1402) Make pipeline lader more flexible
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1402?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1402: ----------------------------------- Assignee: Barak Korren (was: infra) > Make pipeline lader more flexible > --------------------------------- > > Key: OVIRT-1402 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1402 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Labels: standard-ci > > The pipeline loader, used to load pipeline scripts from the Jenkins repo is missing a couple of useful features: > # It takes on a node and keeps it. If the pipelines are long, the node is kept for the whole time even if its not used. It would be a useful optimization to let pipeline scripts specify code that runs without the node. > # It is impossible to access functions that are defined in the loader from the pipeline scripts. > The following solution is offered to provide both features: > We will change the loader to look for a "{{loader_main}}" function in the pipeline script. If it exists it will call it passing itself as an argument. This way that function will get access to function in the loader and can store them for use by other functions. > If a "{{main}}" function exists in the pipeline script in addition to the "{{loader_main}}" function, if will be called outside of the "{{node}}" block in the loader. This way we can run code in "{{main}}" that does not need the loader node. > If a "{{loader_main}}" function will not exist in a pipeline, the "{{main}}" function will be called from inside the "{{node}}" block, like it is today. This way we maintain compatibility with existing pipeline scripts. -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1402) Make pipeline lader more flexible
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1402?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1402: -------------------------------- Labels: standard-ci (was: ) > Make pipeline lader more flexible > --------------------------------- > > Key: OVIRT-1402 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1402 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The pipeline loader, used to load pipeline scripts from the Jenkins repo is missing a couple of useful features: > # It takes on a node and keeps it. If the pipelines are long, the node is kept for the whole time even if its not used. It would be a useful optimization to let pipeline scripts specify code that runs without the node. > # It is impossible to access functions that are defined in the loader from the pipeline scripts. > The following solution is offered to provide both features: > We will change the loader to look for a "{{loader_main}}" function in the pipeline script. If it exists it will call it passing itself as an argument. This way that function will get access to function in the loader and can store them for use by other functions. > If a "{{main}}" function exists in the pipeline script in addition to the "{{loader_main}}" function, if will be called outside of the "{{node}}" block in the loader. This way we can run code in "{{main}}" that does not need the loader node. > If a "{{loader_main}}" function will not exist in a pipeline, the "{{main}}" function will be called from inside the "{{node}}" block, like it is today. This way we maintain compatibility with existing pipeline scripts. -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1402) Make pipeline lader more flexible
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1402?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1402: -------------------------------- Epic Link: OVIRT-403 > Make pipeline lader more flexible > --------------------------------- > > Key: OVIRT-1402 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1402 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > The pipeline loader, used to load pipeline scripts from the Jenkins repo is missing a couple of useful features: > # It takes on a node and keeps it. If the pipelines are long, the node is kept for the whole time even if its not used. It would be a useful optimization to let pipeline scripts specify code that runs without the node. > # It is impossible to access functions that are defined in the loader from the pipeline scripts. > The following solution is offered to provide both features: > We will change the loader to look for a "{{loader_main}}" function in the pipeline script. If it exists it will call it passing itself as an argument. This way that function will get access to function in the loader and can store them for use by other functions. > If a "{{main}}" function exists in the pipeline script in addition to the "{{loader_main}}" function, if will be called outside of the "{{node}}" block in the loader. This way we can run code in "{{main}}" that does not need the loader node. > If a "{{loader_main}}" function will not exist in a pipeline, the "{{main}}" function will be called from inside the "{{node}}" block, like it is today. This way we maintain compatibility with existing pipeline scripts. -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1402) Make pipeline lader more flexible
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

Barak Korren created OVIRT-1402: ----------------------------------- Summary: Make pipeline lader more flexible Key: OVIRT-1402 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1402 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra The pipeline loader, used to load pipeline scripts from the Jenkins repo is missing a couple of useful features: # It takes on a node and keeps it. If the pipelines are long, the node is kept for the whole time even if its not used. It would be a useful optimization to let pipeline scripts specify code that runs without the node. # It is impossible to access functions that are defined in the loader from the pipeline scripts. The following solution is offered to provide both features: We will change the loader to look for a "{{loader_main}}" function in the pipeline script. If it exists it will call it passing itself as an argument. This way that function will get access to function in the loader and can store them for use by other functions. If a "{{main}}" function exists in the pipeline script in addition to the "{{loader_main}}" function, if will be called outside of the "{{node}}" block in the loader. This way we can run code in "{{main}}" that does not need the loader node. If a "{{loader_main}}" function will not exist in a pipeline, the "{{main}}" function will be called from inside the "{{node}}" block, like it is today. This way we maintain compatibility with existing pipeline scripts. -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

[JIRA] (OVIRT-1401) Request to become a public mirror
by Philippe BEAUMONT (oVirt JIRA) 23 May '17

23 May '17

Philippe BEAUMONT created OVIRT-1401: ---------------------------------------- Summary: Request to become a public mirror Key: OVIRT-1401 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1401 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Philippe BEAUMONT Assignee: infra Hi, I'm Philippe from the company NFrance Conseil. I'm in charge to maintain our public and private repositories. As we are looking to use Ovirt, I allready made a mirror: http://ovirt.repo.nfrance.com/ We have a bandwich of 1Gbit on this repo. NFrance Conseil is a french web hosting company with his own Network Infrastructure (AS15826). We work mainly on OpenSource Software and contribute when we can :) I officialy ask to become a public mirror for Ovirt This is the key to add on you authorized_keys: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCxDuAJ0utqeqWqsq2zGJ4Ay87xDnmAZlMLQ7K/LvJXQAX/lh0w6lMUlLScR0FFWBa3guysU9vqfpxPIqnbdJJbEpnWrliEyVezd5CusdYCWI5GuVJHRmXI4yO3UnoYuiQ7Av6GO1jtncNUZtBbDmPG8eWccEPg0x9OO5c3GDaxqqtu7WeTB7BfO8W8KygsvqDffZ7ryBWeftQgykHejju9Mao51de1Q0U5ksYqjahusoEpLuG5dSEIS0LziM38lCukBGvtFopMMItKjuAOwqf4XSwp/f2e6u71geBzWRLMugpZtEnQRUgqwXti/fx9485ipp+EnSN1/hkXiIKHrEGL repo(a)repo.nfrance.com If you need more informations, feel free to ask me. Regards, Philippe Beaumont NFrance Conseil -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0

FC24 build failure for ovirt-engine-4.1 branch backport
by Martin Perina 23 May '17

23 May '17

Hi, could you please take a look at FC24 build issue [2] for patch [1]? IMO it's CI issue, 4.1 builds should not use ovirt-master-snapshot-static repo, they should use ovirt-4.1-snapshot-static repo instead. Thanks Martin [1] https://gerrit.ovirt.org/77167 [2] http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/1115

2 2

[JIRA] (OVIRT-1399) Install Jenkins TAP results plugin
by Barak Korren (oVirt JIRA) 23 May '17

23 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1399?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1399: ------------------------------------- I'm just wondering if we should add more code to do something we are already doing. Maybe there are tools to convert TAP to JUNIT? > Install Jenkins TAP results plugin > ---------------------------------- > > Key: OVIRT-1399 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1399 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Nadav Goldin > Assignee: infra > Priority: Low > > Please install the TAP Plugin - https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin > It allows to display TAP test results, which we use in Lago(with bats). > Not urgent, can be done whenever time allows(with some other upgrade etc). -- This message was sent by Atlassian JIRA (v1000.996.2#100044)

1 0