March 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

Pavel Zhukov created OVIRT-1250: ----------------------------------- Summary: Github PR builder plugin generates too many messages Key: OVIRT-1250 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Pavel Zhukov Assignee: infra Seems like GH PR builder plugin posts one message like: Can one of the admins verify this patch? Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1249?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1249: ----------------------------------- Assignee: Pavel Zhukov (was: infra) > spamming in github pull requests by ...not sure what it is. > ----------------------------------------------------------- > > Key: OVIRT-1249 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: Pavel Zhukov > > See https://github.com/oVirt/ovirt-web-ui/pull/98 > There's a series of comments: > @lago-bot lago-bot commented 2 days ago > Can one of the admins verify this patch? > - spamming is not useful > - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1249?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1249: ------------------------------------- [~eedri] Can we create more "neutral" github bot like "Testbot/jenkinsbot" or something similar (without project name in the bot name) and share it between both projects? With adopting of default GH PR Builder messages to make them more clear for users. > spamming in github pull requests by ...not sure what it is. > ----------------------------------------------------------- > > Key: OVIRT-1249 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > See https://github.com/oVirt/ovirt-web-ui/pull/98 > There's a series of comments: > @lago-bot lago-bot commented 2 days ago > Can one of the admins verify this patch? > - spamming is not useful > - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1249?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1249: ------------------------------------- Hi Michal, I completely agree with you. The reason is the sender (author) of the patch is not a member of the oVirt organization (whitelist). Lago-bot is used because of jenkins github pull request builder limitation and the fact we use single Jenkins instance for both ovirt and lago-project organization. See OVIRT-1239 for more details. > spamming in github pull requests by ...not sure what it is. > ----------------------------------------------------------- > > Key: OVIRT-1249 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > See https://github.com/oVirt/ovirt-web-ui/pull/98 > There's a series of comments: > @lago-bot lago-bot commented 2 days ago > Can one of the admins verify this patch? > - spamming is not useful > - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Michal Skrivanek (oVirt JIRA) 10 Mar '17

10 Mar '17

Michal Skrivanek created OVIRT-1249: --------------------------------------- Summary: spamming in github pull requests by ...not sure what it is. Key: OVIRT-1249 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra See https://github.com/oVirt/ovirt-web-ui/pull/98 There's a series of comments: @lago-bot lago-bot commented 2 days ago Can one of the admins verify this patch? - spamming is not useful - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1248 at 3/10/17 4:16 PM: -------------------------------------------------------------- [~jhernand(a)redhat.com] This is so we remember to fix what we saw today. was (Author: bkorren(a)redhat.com) [~jhernand(a)redhat.com] This is so we remember to fix what we say today. > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Summary: Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist (was: Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist) > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1248: ------------------------------------- [~jhernand(a)redhat.com] This is so we remember to fix what we say today. > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Description: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. We need to fix this unless OVIRT-1247 gets fixed sooner. was: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. We need to fix this unless OVIRT-1247 get fixed sooner. > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Description: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. We need to fix this unless OVIRT-1247 get fixed sooner. was: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs, so they got overlooked when some if the whitelist changes were introduced. > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 get fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0