- Infra - oVirt List Archives

[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1394: -------------------------------- Issue Type: Improvement (was: Task) > Remove STD-CI cleanup function cleanup_var > ------------------------------------------ > > Key: OVIRT-1394 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Gil Shinar > Assignee: infra > > We do not remember why /var/tmp is being cleaned on each STD-CI job. > /var/tmp is good place for caching stuff (maven for example). > I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1394: -------------------------------- Epic Link: (was: OVIRT-400) > Remove STD-CI cleanup function cleanup_var > ------------------------------------------ > > Key: OVIRT-1394 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > We do not remember why /var/tmp is being cleaned on each STD-CI job. > /var/tmp is good place for caching stuff (maven for example). > I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1394: -------------------------------- Epic Link: (was: OVIRT-400) > Remove STD-CI cleanup function cleanup_var > ------------------------------------------ > > Key: OVIRT-1394 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > We do not remember why /var/tmp is being cleaned on each STD-CI job. > /var/tmp is good place for caching stuff (maven for example). > I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1396: -------------------------------- Component/s: (was: oVirt CI) Standard CI (Pipelines) > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1396: -------------------------------- Epic Link: (was: OVIRT-400) > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1396: -------------------------------- Epic Link: (was: OVIRT-400) > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1508: -------------------------------- Status: Done (was: To Do) upstream source collector code had been re-factored into two tools command-line - usrc.py and pusher.py > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1508: -------------------------------- Epic Link: (was: OVIRT-400) > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1508: -------------------------------- Epic Link: (was: OVIRT-400) > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1536) Documentation about the change-queue flow
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1536?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1536: -------------------------------- Component/s: (was: oVirt CI) Documentation Change Queue > Documentation about the change-queue flow > ----------------------------------------- > > Key: OVIRT-1536 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1536 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue, Documentation > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Add some reference documentation about the change-queue flow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0