June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1689) Improve error messages in STDCI environment variable handling
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1689: -------------------------------- Epic Link: (was: OVIRT-400) > Improve error messages in STDCI environment variable handling > ------------------------------------------------------------- > > Key: OVIRT-1689 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > * All references to things like 'xdg-home' need to be replaced with specifications of actual paths, as users are not expected to know what XDG is. > * Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages. > * When variable/key names are given in error messages, they need to be quoted for clarity. > * Edge cases like for example an existing but empty secrets file and a missing 'secrets_data' key need to be handled better, with clear error messages > * Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use 'mock_runner.sh' for the 'jenkins' repo for example. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1690: -------------------------------- Epic Link: (was: OVIRT-400) > Add CI for groovy/pipeline code in 'jenkins' repo > ------------------------------------------------- > > Key: OVIRT-1690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task, groovy, jenkins > > We don't have any CI for Groovy code currently. > At the very least we need to check that the code compiles, this is a bit harder then it sounds because in order to test compilation for piepline code we need to mock out things like the '{{NonCPS}}' decorator which is not supported by the standard Groovy compiler. > Ideally we can also ass support for a full test suit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1690: -------------------------------- Epic Link: (was: OVIRT-400) > Add CI for groovy/pipeline code in 'jenkins' repo > ------------------------------------------------- > > Key: OVIRT-1690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task, groovy, jenkins > > We don't have any CI for Groovy code currently. > At the very least we need to check that the code compiles, this is a bit harder then it sounds because in order to test compilation for piepline code we need to mock out things like the '{{NonCPS}}' decorator which is not supported by the standard Groovy compiler. > Ideally we can also ass support for a full test suit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1704) Add a job to update/modify secrets file
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1704?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1704: -------------------------------- Epic Link: (was: OVIRT-400) > Add a job to update/modify secrets file > --------------------------------------- > > Key: OVIRT-1704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1704 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: first_time_task > > We need to have a proper way to update/modify the secrets file which is stored in our Jenkins server. > The alternative is having to add a way to download then update locally and upload again. > If we choose to allow downloading the file, we need to make it convenient and safe so that users which are unauthorized won't be able to download it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1704) Add a job to update/modify secrets file
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1704?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1704: -------------------------------- Epic Link: (was: OVIRT-400) > Add a job to update/modify secrets file > --------------------------------------- > > Key: OVIRT-1704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1704 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: first_time_task > > We need to have a proper way to update/modify the secrets file which is stored in our Jenkins server. > The alternative is having to add a way to download then update locally and upload again. > If we choose to allow downloading the file, we need to make it convenient and safe so that users which are unauthorized won't be able to download it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Epic Link: (was: OVIRT-400) > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Epic Link: (was: OVIRT-400) > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Resolution: Fixed Status: Done (was: To Do) We already have multiple test jobs and projects on the staging system > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, Staging infra, Standard CI (Freestyle) > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Epic Link: (was: OVIRT-400) > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, Staging infra, Standard CI (Freestyle) > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Epic Link: (was: OVIRT-400) > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, Staging infra, Standard CI (Freestyle) > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0