Is Google planning to enable pull requests on google cloud repos? We love using these repos in GCP but need to use pull requests in our development process (frankly, we're surprised and curious why they are not enabled). So at this point we are wondering if we need to migrate or if they are planning to add this feature.
Related
I currently have an application in amplify but I want to integrate the repo, but I have it in azure, I don't see the option to integrate directly with azure from amplify.
In your case, the best suggestion would be to use multiple remotes provided by GitHub. no need to worry if you are not using GitHub because the process and the commands are the same.
As you are using 2 different environments you need to use Azure Repos and Code commit with git standard.
Once you have done setting multiple repos, configuring CI/CD pipeline would be a better process to deploy based on your push.
It's worth pointing out that you’ll need to properly setup and configure your CI/CD pipeline. AWS provides a number of services to support this including AWS CodePipeline, AWS CodeBuild, and AWS CodeDeploy.
I developed a SDK.js that ease the use of my API supported by my nodejs server on Azure.
What would be the best way to deploy this SDK.js to the server so that client can make use of it after having it embedded in their code via a tag?
Note: I'd like my SDK.js to be babelled and minified in the process.
As far as where to put the file, there are two options I can recommend: either in a public endpoint or by leveraging Azure Storage.
As for deployment, one solution is to include it in whatever deployment process the API. If you are looking for an outside solution, there are a large number out there, but two that will make the process as simple as possible that I am aware of are Azure Devops and Github Actions. Of those two, Github Actions has a larger free tier if your project is small.
To keep it short and sweet I am attempting to automate my CI/CD process which includes a AzureDevOps build running automatically when code is pushed in a bitbucket server repo. I have not found any documentation on how to set this up. Does anyone have any experience with this process? Keep in mind (even though i've mentioned it) I am using the server version of Bitbucket while using the PAAS version of AzureDevops.
It's fairly straightforward. When you create a pipeline, it will ask you where your repo is.
If it's hosted by Atlassian (you access it by https://bitbucket.org), select the BitBucket Cloud one and provide your login.
If it's self hosted, select "Other Git".
I have a node React project in Bitbucket which is already deployed in Google App Engine. I have made some changes to the my application and I would like to know how to deploy the new changes to the Google App Engine using command shell.
I have tried git pull command it says that there is no repository, even if I can see the project files.
Google Cloud Support here!
With the amount of details given and seeing what you are trying to do, I think that the best solution for you would be using Cloud Source Repositories.
If you end up using Cloud Source Repositories, here you'll find a guide explaining how to mirror a Bitbucket repository. After mirroring the desired repository, as you are using Google App Engine, you should read this documentation in which it is described how to integrate Cloud Source Repositories with Google App Engine.
Please bear in mind that using Cloud Source Repositories might involve additional charges if you exceed the free tier, this is explained in the pricing section for Cloud Source Repositories.
If you don't want to use Cloud Source Repositories, here you'll find how to clone a Bitbucket repository.
I'm using Azure Mobile Services for my mobile app backend. I'd like to make a copy of my current service (scripts, api, schedulers, tables etc.) for Test and Production environments. Is there an automated/scripted process to achieve this?
Unfortunately, at this point the answer is no. You have to create a new Mobile Service, recreate all the tables using the cli or web portal, copy over the database schema, copy over the scripts, and reconfigure any schedulers.
Once you have done that it's easier to maintain the workflow from dev->staging->production if you use a db schema tool like Flyway or Visual Studio. Also connect the git repos for the different services so that you can pull from dev and push to staging and then production.