- Infra - oVirt List Archives

[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy
by eyal edri (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519575544-10808-170 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1871: -------------------------------- Assignee: Anton Marchukov (was: infra) > Wrong target milestone check on new 4.2 branches for ovirt-host-deploy > ---------------------------------------------------------------------- > > Key: OVIRT-1871 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: sbonazzo > Assignee: Anton Marchukov > > I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: > Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) https://gerrit.ovirt.org/#/c/86992/ > I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. > When fixing this, please also include link to how to do that, I've other projects that will need similar change. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519575544-10808-170 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1871:</h3> <pre>Assignee: Anton Marchukov (was: infra)</pre> <blockquote><h3>Wrong target milestone check on new 4.2 branches for ovirt-host-deploy</h3> <pre> Key: OVIRT-1871 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: sbonazzo Assignee: Anton Marchukov</pre> <p>I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) <a href="https://gerrit.ovirt.org/#/c/86992/">https://gerrit.ovirt.org/#/c/86992/</a> I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. When fixing this, please also include link to how to do that, I've other projects that will need similar change.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519575544-10808-170--

1 0

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by eyal edri (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519573284-30715-140 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1911: -------------------------------- Assignee: Anton Marchukov (was: infra) Anton, how much effort do you think this will need to add it to Gerrit Hooks? [~ykaul] I also think this should be communicated before adding, people sometimes don't like new automatic info added to bugs without a good reason. We'll also need to think what do you do in case there are multiple external trackers attached to the bug, which is the case most of the time, do you start "spamming" the bug with commit messages from each tracker? sometimes it can be as much as 10 different patches. What about if there are trackers from multiple projects, a quite common scenario with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then? We've seen issues with current new comments added to bugs when they can't move to ON_QA, it has the potential of causing more noise than good, so we really need to think if and how we want to implement this before moving forward. cc [~dfodor] > RFE: Add relevant git commit messages as comments in the relevant Bugzillas > --------------------------------------------------------------------------- > > Key: OVIRT-1911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yaniv Kaul > Assignee: Anton Marchukov > > When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? > I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519573284-30715-140 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1911:</h3> <pre>Assignee: Anton Marchukov (was: infra)</pre> <p>Anton, how much effort do you think this will need to add it to Gerrit Hooks?</p> <p>[~ykaul] I also think this should be communicated before adding, people sometimes don't like new automatic info added to bugs without a good reason.</p> <p>We'll also need to think what do you do in case there are multiple external trackers attached to the bug, which is the case most of the time, do you start “spamming” the bug with commit messages from each tracker? sometimes it can be as much as 10 different patches.</p> <p>What about if there are trackers from multiple projects, a quite common scenario with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then?</p> <p>We've seen issues with current new comments added to bugs when they can't move to ON_QA, it has the potential of causing more noise than good, so we really need to think if and how we want to implement this before moving forward.</p> <p>cc [~dfodor]</p> <blockquote><h3>RFE: Add relevant git commit messages as comments in the relevant Bugzillas</h3> <pre> Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: Anton Marchukov</pre> <p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519573284-30715-140--

1 0

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by Yaniv Kaul (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519571950-30813-109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yaniv Kaul created OVIRT-1911: --------------------------------- Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519571950-30813-109 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Yaniv Kaul created OVIRT-1911:</h3> <pre> Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra</pre> <p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519571950-30813-109--

1 0

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by Yaniv Kaul (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519571950-26090-115 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ] Yaniv Kaul updated OVIRT-1911: ------------------------------ Epic Link: OVIRT-411 > RFE: Add relevant git commit messages as comments in the relevant Bugzillas > --------------------------------------------------------------------------- > > Key: OVIRT-1911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yaniv Kaul > Assignee: infra > > When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? > I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519571950-26090-115 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ]</pre> <h3>Yaniv Kaul updated OVIRT-1911:</h3> <pre>Epic Link: OVIRT-411</pre> <blockquote><h3>RFE: Add relevant git commit messages as comments in the relevant Bugzillas</h3> <pre> Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra</pre> <p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519571950-26090-115--

1 0

[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Barak Korren (oVirt JIRA) 25 Feb '18

25 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1910: -------------------------------- Epic Link: OVIRT-400 > Strange Lago CI test failure > ---------------------------- > > Key: OVIRT-1910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Standard CI (Freestyle) > Reporter: Yaniv Kaul > Assignee: infra > > My patch[1] is failing, but I'm not sure why. > See [2] for the job - the issues seems to be with the pusher - see its > log[3]: > 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1 > --pretty=format:%H' > 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: > c26adc01449d97899aac18406298374de0e7dd73 > 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git > rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}' > 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 > 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument > 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}': > unknown revision or path not in the working tree. > Any ideas? > TIA, > Y. > [1] https://github.com/lago-project/lago/pull/695 > [2] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/ > [3] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Barak Korren (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519559357-18891-124 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1910: ----------------------------------- Assignee: Barak Korren (was: infra) Component/s: Standard CI (Freestyle) Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) Priority: Highest (was: Medium) > Strange Lago CI test failure > ---------------------------- > > Key: OVIRT-1910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Freestyle) > Reporter: Yaniv Kaul > Assignee: Barak Korren > Priority: Highest > > My patch[1] is failing, but I'm not sure why. > See [2] for the job - the issues seems to be with the pusher - see its > log[3]: > 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1 > --pretty=format:%H' > 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: > c26adc01449d97899aac18406298374de0e7dd73 > 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git > rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}' > 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 > 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument > 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}': > unknown revision or path not in the working tree. > Any ideas? > TIA, > Y. > [1] https://github.com/lago-project/lago/pull/695 > [2] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/ > [3] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519559357-18891-124 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1910:</h3> <pre> Assignee: Barak Korren (was: infra) Component/s: Standard CI (Freestyle) Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) Priority: Highest (was: Medium)</pre> <blockquote><h3>Strange Lago CI test failure</h3> <pre> Key: OVIRT-1910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Freestyle) Reporter: Yaniv Kaul Assignee: Barak Korren Priority: Highest</pre> <p>My patch[1] is failing, but I'm not sure why. See [2] for the job – the issues seems to be with the pusher – see its log[3]: 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: ‘git log -1 --pretty=format:%H’ 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- 2018-02-23 12:42:16,230:DEBUG:__main__: c26adc01449d97899aac18406298374de0e7dd73 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: ‘git rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}’ 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument ‘jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}’: unknown revision or path not in the working tree. Any ideas? TIA, Y. [1] <a href="https://github.com/lago-project/lago/pull/695">https://github.com/lago-project/lago/pull/695</a> [2] <a href="http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/">http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/</a> [3] <a href="http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/…">http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/…</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519559357-18891-124--

1 0

[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Yaniv Kaul (oVirt JIRA) 25 Feb '18

25 Feb '18

Yaniv Kaul created OVIRT-1910: --------------------------------- Summary: Strange Lago CI test failure Key: OVIRT-1910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yaniv Kaul Assignee: infra My patch[1] is failing, but I'm not sure why. See [2] for the job - the issues seems to be with the pusher - see its log[3]: 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1 --pretty=format:%H' 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- 2018-02-23 12:42:16,230:DEBUG:__main__: c26adc01449d97899aac18406298374de0e7dd73 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}' 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}': unknown revision or path not in the working tree. Any ideas? TIA, Y. [1] https://github.com/lago-project/lago/pull/695 [2] http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/ [3] http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1909) GetBadges is not working anymore
by eyal edri (oVirt JIRA) 25 Feb '18

25 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1909?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1909: ---------------------------------- Yep, the Jenkins plugin stopped working and we didn't get a reply from them on the ticket. Evgheni, I suggest to try and ping them again and if there is no reply, let's remove the Jenkins integration for now. On Thu, Feb 22, 2018 at 11:23 PM, sbonazzo (oVirt JIRA) < -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > GetBadges is not working anymore > -------------------------------- > > Key: OVIRT-1909 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1909 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Not sure what happened 3 months ago but GetBadges is not receiving data > anymore. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1909) GetBadges is not working anymore
by sbonazzo (oVirt JIRA) 25 Feb '18

25 Feb '18

sbonazzo created OVIRT-1909: ------------------------------- Summary: GetBadges is not working anymore Key: OVIRT-1909 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1909 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Not sure what happened 3 months ago but GetBadges is not receiving data anymore. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

2 1

The importance of fixing failed build-artifacts jobs
by Dafna Ron 25 Feb '18

25 Feb '18

Hi All, We have been seeing a large amount of changes that are not deployed into tested lately because of failed build-artifacts jobs so we decided that perhaps we need to explain the importance of fixing a failed build-artifacts job. If a change failed a build-artifacts job, no matter what platform/arch it failed in, the change will not be deployed to tested. Here is an example of a change that will not be added to tested: [image: Inline image 1] As you can see, only one of the build-artifacts jobs failed but since the project specify that it requires all of these arches/platforms, the change will not be added to tested until all of the jobs are fixed. So what can we do? 1. Add the code which builds-artifacts to 'check-patch' so you'll get a -1 if a build failed (assuming you will not merge with -1 from CI). 2. post merge - look for emails on failed artifacts on your change (you will have to fix the job and then re-trigger the change) 3. you can see all current broken failed artifacts jobs in jenkins under 'unstable critical' view [1] and you will know if your project is being deployed. 4. Remove the broken OS from your project ( either from Jenkins or from your automation dir if you're using V2 ) - ask us for help! this should be an easy patch 5.Don't add new OS builds until you're absolutly sure they work ( you can add check-patch to keep testing it, but don't add build-artifacts until its stable ). Please contact myself or anyone else from the CI team for assistance or questions and we would be happy to help. [1] http://jenkins.ovirt.org/ Thank you, Dafna

4 3