- Infra - oVirt List Archives

[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1135: -------------------------------- Epic Link: (was: OVIRT-400) > consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1135 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Thanks, > I've removed the duplicate message, and opening a ticket on this to > consider more meaningful links or layout on the main page. > On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > If you click the "All" tab, you get double welcome message with > > similar content. > > Welcome to oVirt Jenkins continuous integration serverFor more > > information about the oVirt project visit http://www.ovirt.org > > Welcome to oVirt Jenkins continuous integration serverFor more info about > > the oVirt project, visit oVirt.org <http://ovirt.org/> > > See http://jenkins.ovirt.org/view/All/ > > > > I think we can remove the welcome message entirely, it makes sense only > > when > > you visit http://jenkins.ovirt.org/, and only for unlogged users. > > > > Logged users do not need the welcome message, it takes valuable space on > > the screen that > > can be used for useful data. > > > > Nir > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1135: -------------------------------- Epic Link: (was: OVIRT-400) > consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1135 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Thanks, > I've removed the duplicate message, and opening a ticket on this to > consider more meaningful links or layout on the main page. > On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > If you click the "All" tab, you get double welcome message with > > similar content. > > Welcome to oVirt Jenkins continuous integration serverFor more > > information about the oVirt project visit http://www.ovirt.org > > Welcome to oVirt Jenkins continuous integration serverFor more info about > > the oVirt project, visit oVirt.org <http://ovirt.org/> > > See http://jenkins.ovirt.org/view/All/ > > > > I think we can remove the welcome message entirely, it makes sense only > > when > > you visit http://jenkins.ovirt.org/, and only for unlogged users. > > > > Logged users do not need the welcome message, it takes valuable space on > > the screen that > > can be used for useful data. > > > > Nir > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1135: -------------------------------- Component/s: Jenkins Master > consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1135 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Thanks, > I've removed the duplicate message, and opening a ticket on this to > consider more meaningful links or layout on the main page. > On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > If you click the "All" tab, you get double welcome message with > > similar content. > > Welcome to oVirt Jenkins continuous integration serverFor more > > information about the oVirt project visit http://www.ovirt.org > > Welcome to oVirt Jenkins continuous integration serverFor more info about > > the oVirt project, visit oVirt.org <http://ovirt.org/> > > See http://jenkins.ovirt.org/view/All/ > > > > I think we can remove the welcome message entirely, it makes sense only > > when > > you visit http://jenkins.ovirt.org/, and only for unlogged users. > > > > Logged users do not need the welcome message, it takes valuable space on > > the screen that > > can be used for useful data. > > > > Nir > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Component/s: Standard CI (Pipelines) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: (was: OVIRT-400) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: (was: OVIRT-400) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Status: Done (was: To Do) We no longer use deploy-to-experimental anywhere. > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Epic Link: (was: OVIRT-400) > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Epic Link: (was: OVIRT-400) > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1247) Re-factor SDK standard-CI jobs to not be different from other jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1247?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1247: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Closing as wontfix since this ticket talks about the STDCI V1 jobs - we should convert the project to STDCI V2 anyway, so replacing this ticket with OVIRT-2232 > Re-factor SDK standard-CI jobs to not be different from other jobs > ------------------------------------------------------------------ > > Key: OVIRT-1247 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1247 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now the SDK building jobs use specialized YAML. This makes them different from all other Standard-CI jobs. Need to find a way make them like all the rest. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0