Consider having multiple projects for testing #3310

Activity

1. tmatsuo

   added

   testing

   type: processA process-related concern. May include testing, release, or the like.A process-related concern. May include testing, release, or the like.

   needs-multiple-projectsissues needs multiple projects for fundamental fixissues needs multiple projects for fundamental fix

   on Apr 8, 2020
2. blunderbuss-gcf

   assigned

   crwilcox

   on Apr 8, 2020
3. tmatsuo

   assigned

   tmatsuo

   ,

   leahecole

   and

   kurtisvg

   on Apr 8, 2020
4. tmatsuo commented on Apr 8, 2020

   

   tmatsuo

   on Apr 8, 2020

   Last edited by tmatsuo

   ContributorAuthor

   More actions

   @kurtisvg @crwilcox @leahecole If you know any issues which needs multiple projects for the fundamental fix, please add the label needs-multiple-projects. Once you go through your knowledge and your memory, feel free to unassign yourself.
5. tmatsuo commented on Apr 9, 2020

   

   tmatsuo

   on Apr 9, 2020

   ContributorAuthor

   More actions

   For implementation, I think we should use gimmeproj. Example uses in ruby and go

   To use gimmeproj, I think we'll probably need to

   1. create a new project for meta project
   2. try to run all the tests on the meta project, figure out what configs/operations/resource files are needed besides enabling APIs, and write them down (for example, TEST-REQUIREMENTS.md in each directory).
   3. maybe standardize on the resource files (or even, write a shell script for setup)
   4. then we can finally create pool projects with all the needed stuff
6. tmatsuo commented on May 6, 2020

   

   tmatsuo

   on May 6, 2020

   ContributorAuthor

   More actions

   An easier option.

   Maybe we can have few more cloud projects with suffixes like -py36, -py37, etc.

   We can have a common library in this repo, probably in the lib folder or somewhere. We can add that directory to sys.path in the noxfile.py so that you can just do something like:

   import test_helper
   
   
   project_id = test_helper.get_project_id_from_kokoro_job_name()
   # you'll get `xxx-py36` for the py-36 build and `xxxx-py37` for the py-37 build, etc.

   This way, it is very easy for us to only opt in some of the tests.
7. tmatsuo commented on May 6, 2020

   

   tmatsuo

   on May 6, 2020

   ContributorAuthor

   More actions

   Came up with an easier option.

   Rather than having a library, we can just override the envvar GOOGLE_CLOUD_PROJECT in noxfile.py.
8. tmatsuo commented on May 15, 2020

   

   tmatsuo

   on May 15, 2020

   ContributorAuthor

   More actions

   Created 3 new projects.

   • python-docs-samples-tests-py36
   • python-docs-samples-tests-py37
   • python-docs-samples-tests-py38

   I'll start using those projects with monitoring tests.
9. tmatsuo

   added a commit that references this issue on May 15, 2020

   [monitoring] testing: start using build specific projects

   ...

   86e4e0f
10. gcf-merge-on-green

    added a commit that references this issue on May 16, 2020

    [monitoring] testing: start using build specific projects (#3771)

    ...

    3cc541f
11. tmatsuo

    added a commit that references this issue on May 16, 2020

    [iam] testing: use multiple projects

    ...

    0834e72
12. tmatsuo commented on May 16, 2020

    

    tmatsuo

    on May 16, 2020

    ContributorAuthor

    More actions

    It's live now.
13. tmatsuo

    closed this as completedon May 16, 2020
14. tmatsuo

    added a commit that references this issue on May 18, 2020

    [iam] testing: use multiple projects (#3772)

    ...

    e44bacb
15. arbrown

    added a commit that references this issue on Nov 7, 2022

    move monitoring samples from python-docs-samples (#51)

    ...

    d282153
16. dandhlee

    added a commit that references this issue on Nov 9, 2022

    move monitoring samples from python-docs-samples (#51)

    ...

    f7bca56