[google-appengine] Re: AppEngine Dev, QA and production environments, how to manage them and and set it up?

2019-08-27 Thread 'Nicolas (Google Cloud Platform Support)' via Google App Engine


Hi Eduardo,

Thanks for opening this thread, there are multiple training courses 
available[1] to learn more about how to professionally develop, deploy and 
monitor applications on GCP.

This specific learning path[2] concentrates on the concepts of application 
development. I hope you find this interesting. Also you can consider 
passing one of our certifications[3] if you want to become officially GCP 
certified.

[1] https://cloud.google.com/training

[2] https://cloud.google.com/training/application-development
[3] https://cloud.google.com/training/#certification

On Monday, August 26, 2019 at 1:01:23 PM UTC-4, Eduardo Moreira wrote:
>
> Thank you Diogo
>
> That is a great place to get started but it does feel we need proper 
> training for this, do you know where we could get this?
>
> Thank you
>
> On Friday, 23 August 2019 04:47:38 UTC+1, Diogo Almeida wrote:
>>
>> As per the document [1], the different development environments should be 
>> managed by setting up a different project for each environment. That said, 
>> you would manage the different environments with separate repositories and 
>> could use Cloud Source Repository and Cloud Build to deploy the code to App 
>> Engine.
>>
>> I would recommend you explore the documentation of these two products:
>>
>> 1 - Cloud Source Repositories [2][3]: `Google Cloud Source Repositories 
>> provides Git version control to support collaborative development of an 
>> application or service, such as those that run on App Engine and Compute 
>> Engine`. You can automatically deploy an application stored in Cloud Source 
>> Repositories to App Engine when there is a new commit on your repository. 
>>
>> 2 - Cloud Build [4]: `Cloud Build can import source code from a variety 
>> of repositories or cloud storage spaces, execute a build to your 
>> specifications, and produce artifacts such as Docker containers or Java 
>> archives`.
>>
>> I also recommend you take a look at this Youtube video [5] where you will 
>> see a hands-on presentation on how to use both products.
>>
>> [1] 
>> https://cloud.google.com/appengine/docs/standard/go/creating-separate-dev-environments
>> [2] 
>> https://cloud.google.com/source-repositories/docs/quickstart-triggering-builds-with-source-repositories
>> [3] https://cloud.google.com/source-repositories/
>> [4] https://cloud.google.com/cloud-build/
>> [5] https://www.youtube.com/watch?v=yP9a5gDRUqY
>>
>>
>> On Thursday, August 22, 2019 at 8:03:33 PM UTC-4, Eduardo Moreira wrote:
>>>
>>> Hello Everyone
>>>
>>> We have a project that we would like to manage in the most professional 
>>> way, so we would like to have a DEV environment for developers to upload 
>>> the project and test in the AppEnginne environment, then we would like to 
>>> have a QA Environment, where we after the Devs are ok with the work, we 
>>> upload the project for customers and Selenium automated test to their part, 
>>> finally, when we are all happy, then we need to move the project into a 
>>> PRODUCTION environment which is the one where customer actually access the 
>>> final product.
>>>
>>> All we have found about this is the following:
>>>
>>> https://cloud.google.com/appengine/docs/standard/go/creating-separate-dev-environments
>>>
>>> But we have many questions, like what is the best way to setup this 
>>> environment, how to copy code from one environment to the other, for 
>>> example how do we move the code from DEV to QA. 
>>>
>>> Is there a course or a step by step video anyone can share with us? we 
>>> need some help with this.
>>>
>>> Thank you
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/95afcdf9-0966-4a6e-932b-b32140b70db7%40googlegroups.com.


[google-appengine] Re: AppEngine Dev, QA and production environments, how to manage them and and set it up?

2019-08-26 Thread Eduardo Moreira
Thank you Diogo

That is a great place to get started but it does feel we need proper 
training for this, do you know where we could get this?

Thank you

On Friday, 23 August 2019 04:47:38 UTC+1, Diogo Almeida wrote:
>
> As per the document [1], the different development environments should be 
> managed by setting up a different project for each environment. That said, 
> you would manage the different environments with separate repositories and 
> could use Cloud Source Repository and Cloud Build to deploy the code to App 
> Engine.
>
> I would recommend you explore the documentation of these two products:
>
> 1 - Cloud Source Repositories [2][3]: `Google Cloud Source Repositories 
> provides Git version control to support collaborative development of an 
> application or service, such as those that run on App Engine and Compute 
> Engine`. You can automatically deploy an application stored in Cloud Source 
> Repositories to App Engine when there is a new commit on your repository. 
>
> 2 - Cloud Build [4]: `Cloud Build can import source code from a variety of 
> repositories or cloud storage spaces, execute a build to your 
> specifications, and produce artifacts such as Docker containers or Java 
> archives`.
>
> I also recommend you take a look at this Youtube video [5] where you will 
> see a hands-on presentation on how to use both products.
>
> [1] 
> https://cloud.google.com/appengine/docs/standard/go/creating-separate-dev-environments
> [2] 
> https://cloud.google.com/source-repositories/docs/quickstart-triggering-builds-with-source-repositories
> [3] https://cloud.google.com/source-repositories/
> [4] https://cloud.google.com/cloud-build/
> [5] https://www.youtube.com/watch?v=yP9a5gDRUqY
>
>
> On Thursday, August 22, 2019 at 8:03:33 PM UTC-4, Eduardo Moreira wrote:
>>
>> Hello Everyone
>>
>> We have a project that we would like to manage in the most professional 
>> way, so we would like to have a DEV environment for developers to upload 
>> the project and test in the AppEnginne environment, then we would like to 
>> have a QA Environment, where we after the Devs are ok with the work, we 
>> upload the project for customers and Selenium automated test to their part, 
>> finally, when we are all happy, then we need to move the project into a 
>> PRODUCTION environment which is the one where customer actually access the 
>> final product.
>>
>> All we have found about this is the following:
>>
>> https://cloud.google.com/appengine/docs/standard/go/creating-separate-dev-environments
>>
>> But we have many questions, like what is the best way to setup this 
>> environment, how to copy code from one environment to the other, for 
>> example how do we move the code from DEV to QA. 
>>
>> Is there a course or a step by step video anyone can share with us? we 
>> need some help with this.
>>
>> Thank you
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/39027187-44d3-4d21-bc28-82e9e6721f20%40googlegroups.com.


[google-appengine] Re: AppEngine Dev, QA and production environments, how to manage them and and set it up?

2019-08-22 Thread 'Diogo Almeida' via Google App Engine
As per the document [1], the different development environments should be 
managed by setting up a different project for each environment. That said, 
you would manage the different environments with separate repositories and 
could use Cloud Source Repository and Cloud Build to deploy the code to App 
Engine.

I would recommend you explore the documentation of these two products:

1 - Cloud Source Repositories [2][3]: `Google Cloud Source Repositories 
provides Git version control to support collaborative development of an 
application or service, such as those that run on App Engine and Compute 
Engine`. You can automatically deploy an application stored in Cloud Source 
Repositories to App Engine when there is a new commit on your repository. 

2 - Cloud Build [4]: `Cloud Build can import source code from a variety of 
repositories or cloud storage spaces, execute a build to your 
specifications, and produce artifacts such as Docker containers or Java 
archives`.

I also recommend you take a look at this Youtube video [5] where you will 
see a hands-on presentation on how to use both products.

[1] 
https://cloud.google.com/appengine/docs/standard/go/creating-separate-dev-environments
[2] 
https://cloud.google.com/source-repositories/docs/quickstart-triggering-builds-with-source-repositories
[3] https://cloud.google.com/source-repositories/
[4] https://cloud.google.com/cloud-build/
[5] https://www.youtube.com/watch?v=yP9a5gDRUqY


On Thursday, August 22, 2019 at 8:03:33 PM UTC-4, Eduardo Moreira wrote:
>
> Hello Everyone
>
> We have a project that we would like to manage in the most professional 
> way, so we would like to have a DEV environment for developers to upload 
> the project and test in the AppEnginne environment, then we would like to 
> have a QA Environment, where we after the Devs are ok with the work, we 
> upload the project for customers and Selenium automated test to their part, 
> finally, when we are all happy, then we need to move the project into a 
> PRODUCTION environment which is the one where customer actually access the 
> final product.
>
> All we have found about this is the following:
>
> https://cloud.google.com/appengine/docs/standard/go/creating-separate-dev-environments
>
> But we have many questions, like what is the best way to setup this 
> environment, how to copy code from one environment to the other, for 
> example how do we move the code from DEV to QA. 
>
> Is there a course or a step by step video anyone can share with us? we 
> need some help with this.
>
> Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/76f925fc-0a89-4ea7-ba46-f7a44e32b6f7%40googlegroups.com.