June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1988: -------------------------------- Epic Link: (was: OVIRT-400) > Add default behavior in secret_resolvers.py > ------------------------------------------- > > Key: OVIRT-1988 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > Currently, when users try to run CI locally (currently with mock_runner), > if their project has a secret dependency they have to either write a local > secrets file, or to temporary modify their environment.yaml. > The file format should have support for default behavior in case a secret > was not found. Maybe something similar to: > {code:java} > --- > - name: MY_SECRET > valueFrom: > secretKeyRef: > name: secret_name > key: key_from_secret > default: > from-env: ENV_VAR_NAME > # OR > value: default-value > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1988: -------------------------------- Epic Link: (was: OVIRT-400) > Add default behavior in secret_resolvers.py > ------------------------------------------- > > Key: OVIRT-1988 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > Currently, when users try to run CI locally (currently with mock_runner), > if their project has a secret dependency they have to either write a local > secrets file, or to temporary modify their environment.yaml. > The file format should have support for default behavior in case a secret > was not found. Maybe something similar to: > {code:java} > --- > - name: MY_SECRET > valueFrom: > secretKeyRef: > name: secret_name > key: key_from_secret > default: > from-env: ENV_VAR_NAME > # OR > value: default-value > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1991) jenkins triggers a build on a deleted branch
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1991?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1991: -------------------------------- Epic Link: (was: OVIRT-400) > jenkins triggers a build on a deleted branch > -------------------------------------------- > > Key: OVIRT-1991 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1991 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Roy Golan > Assignee: infra > Priority: Low > > I did some pruning, and removed old, unused branches, from > https://github.com/oVirt/ovirt-openshift-extensions. Now I suddenly see my > jenkins build is failing, because it triggered a build on the deleted > branch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1991) jenkins triggers a build on a deleted branch
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1991?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1991: -------------------------------- Epic Link: (was: OVIRT-400) > jenkins triggers a build on a deleted branch > -------------------------------------------- > > Key: OVIRT-1991 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1991 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Roy Golan > Assignee: infra > Priority: Low > > I did some pruning, and removed old, unused branches, from > https://github.com/oVirt/ovirt-openshift-extensions. Now I suddenly see my > jenkins build is failing, because it triggered a build on the deleted > branch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1996) Remove the 4.1 nightly publisher job
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1996?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1996: -------------------------------- Epic Link: OVIRT-2044 (was: OVIRT-400) > Remove the 4.1 nightly publisher job > ------------------------------------ > > Key: OVIRT-1996 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1996 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Publisher jobs > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > It may be the case that we don't need the 4.1 publisher jobs any more. > Since those jobs are still in the old pre-CQ format where artifacts we collected by the job itself, their existence makes the CI system's maintenance harder... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1996) Remove the 4.1 nightly publisher job
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1996?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1996: -------------------------------- Epic Link: OVIRT-2044 (was: OVIRT-400) > Remove the 4.1 nightly publisher job > ------------------------------------ > > Key: OVIRT-1996 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1996 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Publisher jobs > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > It may be the case that we don't need the 4.1 publisher jobs any more. > Since those jobs are still in the old pre-CQ format where artifacts we collected by the job itself, their existence makes the CI system's maintenance harder... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base for STDCI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2001: -------------------------------- Epic Link: (was: OVIRT-400) > Create FAQ/Knowledge Base for STDCI > ----------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base for STDCI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2001: -------------------------------- Epic Link: (was: OVIRT-400) > Create FAQ/Knowledge Base for STDCI > ----------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2025?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2025: -------------------------------- Epic Link: (was: OVIRT-400) > Document STDCI "V1.5" poll upstream sources jobs > ------------------------------------------------ > > Key: OVIRT-2025 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: > # How to create such job for a given project: implement a JJB temlpate > # How to configure STDCI configuration file so poll-upstream-sources will work. > If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2025?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2025: -------------------------------- Epic Link: (was: OVIRT-400) > Document STDCI "V1.5" poll upstream sources jobs > ------------------------------------------------ > > Key: OVIRT-2025 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: > # How to create such job for a given project: implement a JJB temlpate > # How to configure STDCI configuration file so poll-upstream-sources will work. > If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0