- Infra - oVirt List Archives

[JIRA] (OVIRT-1276) generate a link to OST automation job
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1276: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1276: -------------------------------- Component/s: OST Manual job > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1276: -------------------------------- Epic Link: (was: OVIRT-400) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1276: -------------------------------- Epic Link: (was: OVIRT-400) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2221) Reposync builder will not work with DNF
by Gal Ben Haim (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2221?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2221: -------------------------------- Summary: Reposync builder will not work with DNF (was: Reposync builder will no work with DNF ) > Reposync builder will not work with DNF > ---------------------------------------- > > Key: OVIRT-2221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2221 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > Part of the reposync builder tool is a Yum plugin which auto-generates the reposync-config with "includepkgs" field. > DNF doesn't support Yum plugins, so we will have to rewrite the plugin for DNF, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2207) Collect findbugs results in pipeline jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2207?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2207: -------------------------------- Epic Link: (was: OVIRT-400) > Collect findbugs results in pipeline jobs > ----------------------------------------- > > Key: OVIRT-2207 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2207 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to be able to view "findbugs" results in a convenient way such as the Jenkins "findbugs" plugin provides so that I can analyze the results. > Currently, this feature is supported in STDCI V1 jobs only and we need to have the same support in STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2207) Collect findbugs results in pipeline jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2207?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2207: -------------------------------- Epic Link: (was: OVIRT-400) > Collect findbugs results in pipeline jobs > ----------------------------------------- > > Key: OVIRT-2207 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2207 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to be able to view "findbugs" results in a convenient way such as the Jenkins "findbugs" plugin provides so that I can analyze the results. > Currently, this feature is supported in STDCI V1 jobs only and we need to have the same support in STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1290: -------------------------------- Component/s: (was: oVirt CI) OST scheduled jobs OST Manual job > Re-factor OST jobs YAML to reduce duplication > --------------------------------------------- > > Key: OVIRT-1290 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job, OST scheduled jobs > Reporter: Barak Korren > Assignee: infra > Labels: ost, yaml > > Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. > Historically theses suits were written by different people and different job templates in YAML were also written for each suit. > At some point we have normalized all the suit names in OST to be of the following structure: > {code} > <suit_type>-suit-<ovirt version> > {code} > This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. > Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. > All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1290: -------------------------------- Epic Link: (was: OVIRT-400) > Re-factor OST jobs YAML to reduce duplication > --------------------------------------------- > > Key: OVIRT-1290 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: ost, yaml > > Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. > Historically theses suits were written by different people and different job templates in YAML were also written for each suit. > At some point we have normalized all the suit names in OST to be of the following structure: > {code} > <suit_type>-suit-<ovirt version> > {code} > This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. > Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. > All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1290: -------------------------------- Epic Link: (was: OVIRT-400) > Re-factor OST jobs YAML to reduce duplication > --------------------------------------------- > > Key: OVIRT-1290 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: ost, yaml > > Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. > Historically theses suits were written by different people and different job templates in YAML were also written for each suit. > At some point we have normalized all the suit names in OST to be of the following structure: > {code} > <suit_type>-suit-<ovirt version> > {code} > This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. > Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. > All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0