Domain transfer to another project on same subscription - google-cloud-dns

is there a procedure to make a transfer domain from a project to another administred by the same subscription?
We tried to export a public dns zone from a project to another with same NS but the lookup doesn't work.
The projects are in different sub folder.
Many thanks

Related

When creating a public workspace, does using the fully qualified name help to distinguish between computers with the same name?

I have two DevOps projects based on TFS. I need two public workspaces set to local (not server) to support each project. The projects' implimintation are rubber stamps of each other down to the computer names, though their fully qualified names and IP4 addresses are differnet because they are in differnt domains. The first project is finished and now we are constructing the second project.
On the second project I get the error - "TF400285: This operation cannot be performed on a local workspace that does not reside on this computer." I assume the error is because the machine name already exists in DevOps (for example, MYDEV). Can I change the short computer name of the first project's workspace (MYDEV) to a fully qualifed name MYDEV.MYFIRSTDOMAIN.local as to distinquish it from the second machine MYDEV.MYSECONDDOMAIN.local?
On the second project, I tried using aliased names to trick the server into creating the public workspace with a different computer name, but it looks like DevOps uses the computer's original short name and does not allow the action. I can create a workspace in the second project with the fully qualified name registered with the DevOps server, when using the workspace is marked as server (not local) but DevOps considers the workspace remote - I assume it is associating the workspace with the first project because of the machine's short name. I am tempted to change the first project's workspace computer name to a fully qualified name, if it will let me. But I wanted to check here first.

Deploying a MERN app to render.com with one main folder structure - not separate front and back

I have a MERN app that I would like to deploy to render.com. I just have 2 quick questions:
Of all the tutorials that I have watched, they all have separate github repos - 1 for the frontend, 1 for the backend. So on render.com, they can simply choose the frontend or the backend repo when they want to deploy. However, my folder structure is not like this - mine is one main github repo, and inside that repo, there is 1 frontend folder and 1 backend folder. How do I go about solving this?
When I give render.com (or heroku, netlify, etc.) access to my github account, is it safe? Does this mean they will be able to read and change stuff in my github account?
Thanks in advance for your help
My repo has the same structure as yours, one frontend folder and one backend folder.
You need to create a new Web Service for your backend folder. When creating a new web service, just set the Root Directory to backend. When you're done with the other fields and deployed your backend, create a Static Site for your frontend. Set the root directory of your static site to frontend. Set Publish Directory to build.
Probably safe but I'm new to the service as well. I believe they are only using that to be able to pull your repositories so that you can select them on Render. And also, of course, for auto or manual deployment.

CI/CD for multi-tenant application with single repository but multiple clients

I have a database-driven application with a single code base configured for multiple clients using the database setting and config files.
The main code base consists of common/core code/files that are being used by all the clients and some client-specific code/files. Both types of files are in different folders of the same repository.
We have been planning to integrate CI/CD using GitHub and Jenkins. I am new to Jenkins.
In GitHub, we have a single repository that contains all the code/files. I want to use Jenkins to deploy to different client environments but make sure that only files related to a specific client should be deployed to that client environment.
What could be the best way or possible solutions for this?
Edit: Basically I want to deploy specific files that are client related to specific client environments.
Any and all suggestions would be highly appreciated.

Change the Jazz ID for a Bluemix account

Some time ago I started to use the Bluemix platform to develop PHP services that were used by a mobile application. After a while, I realized that it would be very useful to have a repository to which I can connect multiple Eclipse IDEs and work on the same application.
I already had a Jazz ID which was used for the work projects; I am talking about using Bluemix+Jazz for personal projects.
When I first connected the Bluemix ID with the Jazz ID, everything was well. But I realized that it might be a conflict of interest because I am using the same Jazz ID for both work and personal projects.
My question is: Is there a way to use a new Jazz ID in Bluemix?
It seems that the connection between the two IDs cannot be changed from Bluemix, DevOps or Jazz.net.
Costin, thanks for your interest in IBM Bluemix and the IBM Bluemix DevOps Services. Like Lauren has said, you'll probably want two IBM IDs, one for your work email address and one for your personal. They ultimately can be associated with two Bluemix orgs, each associated with a different DevOps user.
You'll need to decide which Bluemix org you want each of your apps to live in; the corresponding user should own the app's Git repository. To move a Git repository, you can use either of these approaches:
Use the repository's "Download the contents of this branch as a zip file" button to download the contents. Then as the other user, create a repository and import the zip file.
Share the repository with the other user, fork as the new user to get a copy.
Once you have the code in the other user's repository, redeploy to that user's Bluemix org.
Once you have everything where you want it, delete the stuff (apps and repositories) that are not where you want them.
One option is to create a new IBM id that is linked to your personal e-mail address. The IBM id could be used to sign in to Bluemix and DevOps Services.

How to deploy only worker/web role in Azure

If you have a web AND a worker role in an Azure solution, all the waiting for the publishing an update package, uploading to the cloud storage, waiting for the package to be deployed could be exhausting, an waste a lot of time.
How to upload/deploy only the worker or web role of an Microsoft Azure Solution, that contains both roles, and save both internet traffic and time?
There is no option to build a package for only one of the both roles, but if you have limited bandwidth or traffic, and want to save from the upload time (which can be quite a big portion if you have a lot of static content: Look here for an example), there is one option.
As maybe you know, the package generated from Visual Studio for deployment (the 'cspkg' file) is nothing more, than an archive file.
Suppose, you want to update the WORKER role only. The steps are:
Create the update package as normal
Open it with the best archive manager (7zfm)
Inside, besides the other files are 2 'cssx' files - one for each
role. Delete the unnecessary cssx file.
Upload to Azure Blob Storage (optional)
Update the instances from the Azure Management Portal using the
'local' or 'storage' source as normal
On the Role dropdown, select only the role you want to update
Press OK :)
Hope this helps.
It is a lot easier to just add two additional cloud projects to your solution. In one project, have it reference only your web role. In the other project, have it reference only your worker role.
You can keep the cloud project that references both roles and use that for local debugging but when it is time to deploy, right click the cloud project that references only role you wish to deploy and click "Publish"
You will end up maintaining configuration files for each cloud project but that sounds a lot easier than manually messing around with editing the package file each time.