I am using Google Play. I have a release that is rolled out to two specific countries already. Can I add a third country to this release without building my app again with a new version and/or starting a roll-out again?
Yes, go to your track (Production, open testing , …etc), select countries / regions then click on "add countries / regions"
Related
I have an app on Google Play but I am trying to upload a new version. I am not familar with Google Play but no matter where I go I can't seem to see how to add a new version of the app. The best I have got to is here but the Create New Release button is greyed out. Any pointers?
Click on the "Releases" link next to the "Release dashboard".
It will show you a list with the most recent release.
You can click on the 'edit' link in the release row and it will show you the upload package window or you can discard that draft release.
From there you can update your production release with the new one.
That also happens if you have a draft release for some reasons, you will have to delete it first. Obviously no clue about it from the UI, you need to guess it.
Click on the "Releases" tab, it will show you the draft release and you can delete it from there
This could be as a result of issues associated with the policy status of one of your apps in production. Go to all apps and make sure none of the apps in production have any policy issues that might need attention.
if create new release is still grayed out, do as specified in this answer by ronline.
https://stackoverflow.com/a/63511972/12931715
Click on the "Releases" link next to the "Release dashboard". It will show you a list with the most recent release.
You click on the 'edit' link in the release row and it will show you the upload package widow.
From there you can update your production release with the new one.
Whether check you have Draft releases in the "Release" tab next to the "Release dashboard" on the "Production" page.
Production -> Releases
If there is a release you can "Edit" that version or "Discard" and upload a new version.
We're using TFS 2017 for our CI/CD and I'm trying to configure the users for the Approvals on the production Environment definition of a Release definition.
What I'm try to achieve is assigning two groups of users as approvers, one member of each being required to sign off the release. The screens suggest this should be possible but it's proving difficult to configure.
I've created a Project Manager group and an Infrastructure Team group, both at a TFS collection level and at the project level within TFS and assigned the appropriate members.
Having created the Release definition and created a production Environment, I select the Assign Approvers... which displays a new window. I select the
Pre-deployment approver | Specific Users option, click the More Options link and select the All users in any order option.
However, when I try to select the groups, it doesn't show me any of the groups I've created and I can't select them.
I know that I should be able to manage this via AD but I don't want to have to keep getting AD groups made for me if I can manage this myself within TFS.
Has anyone managed to achieve this in TFS 2017 and could you tell me how please?
I can create the Groups in both Collection and Project level and can select them to Release Approval. Everything works correctly.
Please note that the Groups will not display automatically, you need to enter the Group name in the Search user and groups text box to filter it out. Just have try for that.
I've been relying on email alerts, but I don't like doing that. Is there an alert or notification or some other clue within Visual Studio itself to let me know I need to get latest?
If you're using TFVC, the source control explorer will show you on a file by file basis whether you have the latest version.
If you're using Team Rooms, the team room can be configured to display notifications whenever a user commits a change.
In general, it shouldn't matter too much -- just do a "get latest" a few times a day and resolve any conflicts that pop up.
I need to migrate my Xcode Bot to another repository and I wish to keep build history. In the edit bot interface (both browser and Xcode) repository field is not editable. How can I migrate?
OS X Server version 3.1.2
This is an old question but i suspect people will find this and look for an answer as it is the top result in google. This is how you do it:
change the repo you point to in git
open your Xcode project, select the bot and hit edit bot
in the repositories tab, uncheck the one that you want to update
hit done
go back to edit bot
you should now see the new repo instead of the old one
Is there a way to Link a WorkItem to a Label. Under "All Links" when I create a new WorkItem in Visual Studio I can select many diffrent Link Types, like Changeset, VersionedItem, etc, but theres no type for Label.
The reason why I want to do it is, that I label my releases (like Version 1.0, Version 1.1) and I want to associate a Bug to a specific version of my software.
Isn´t it support to link a WorkItem to a Label or how should I associate a Bug to a version of my software?
Update:
I´m following the Single Team Branching Model (one Dev and one Main branch) documented in the Visual Studio TFS Branching Guide 2010.
You cannot link to a label. However you can achieve your goal in other ways.
First of all, I suggest to use branching instead of labelling to keep track of multiple released versions. In my opninion using branches is a better mechanism then labelling. See also the branching guidance on codeplex
To link your bug to a version of your software, use the Iteration Path in the work item. This field is exactly for that purpose.
Using iteration path field is one option and it gives you the ability to track a work item between versions.
But if you want higher resolution, there is another way:
Team Build marks source code with a label before every build. The bug item type in CMMI project template contains fields called "Found In" and "Fixed In". In these fields you can select from build labels.
Use of these fields allow you to mark any work item with two specific builds. One for when it was found and one for when it was fixed.
Additionally Team Build updates "Fixed In" field of every work item with the label of the build, after the build completes successfully and all tests are ran without a problem.
If you don't have these fields on your work item type, you can always add them using the work item template editor that comes with TFS Power Tools.