We passed from TFS 2015 to TFS 2017.2 last week. Apparently, we don't have the Release option when setting notifications. Do you know why is that? Or how can we enable the Release notifications?
Current Notifications Screenshot
Release notifications are only available with TFS 2018 later and VSTS. It's not able to use it in TFS2017. You could refer below blog:
We are now announcing the feature as generally available on all accounts and be the only available release notification settings
experience. The same experience is also available with TFS 2018.
Managing Release Notifications
As a workaround, you could use some 3rd-party E-mail extensions to notify peoples in the Release definition such as Send Email.
You could also set up your own E-mail extension, just follow this blog as a tutorial: Sending Email Notification from VSTS/TFS Build
Related
I have this situation.
I have an already published react native app (both ios and android) (1.0.1).
So far, all the changes needed were made using OTA, so I had a jenkins pipeline which was trigger each time I was pushing anything to production branch. One of the main steps here is expo publish —release-channel prod-1, so I’m having the release channel called prod-1 here.
Now, I had to add some dependencies, therefore I am not allowed to use the OTA for these ones.
Here comes the questions:
What happens if I accidentally publish the current changes (which includes not accepted OTA changes) to the release channel prod-1?
Should I create a new release channel for these new changes called prod-2, then create the build for it, then submit it to stores for approval, then once approved released it in production?
If so, what will happen with the initial release called prod-1, in case I will need to do any changes on that one, should I simply publish again to prod-1 and an OTA will be performed for all the users using the old all version?
I was thinking about this flow, please confirm me if this is right or if you have any other ideas:
Create a new branch called production-v1 where I will merge what I have now on production, with a pipeline for automatically publishing the changes to prod-1 (OTA - if needed for the users using the old app).
Change the production pipeline so instead of using the release channel prod-1, it will use prod-2
Merge the main into production so it will trigger a new publish to prod-2 channel
Submit the build to the stores and once approved, I should be able to release the new version for the users using the old app.
Please let me know if I’m missing anything here, or if my approach is wrong. Thank you so much!
As a Team Foundation Server administrator I'm not able to turn off the Build Failed notifications. Is there a possibility to do that. The Build Notification is sent to the whole team.
I've tried to turn of this message in my own personal Notification Settings. Also in the Team nofication settings and in the notification settings of the Default Collection (that's where my project belongs).
The Build Failed Notification is greyed out for me. The only ability I have is to Turn Off the notification which I did. Unfortunately the Build Failed message will be sent when a build fails.
Can anyone assist me to turn off the build failed notification to the whole team?
You could directly turn off the team notifications in Project Settings--Notifications--Project team
The sample screenshot from Azure DevOps/TFS server 2019 for your reference：
For collection level Notifications, you could choose to disable the subscription.
Note: This will effect any project in the collection.
Finally, I found the reason which was responsible for sending the build failed mails. It was a subscribtion of which I thought is was disabled. Sorry for this question....
I have read about the Xcode 9, and there is an interesting term “bots”, which will do the CI/CD work for you, but didn't get any proper guide. Could anyone help me find the configuration guide on it?
From Apple’s About Continuous Integration in Xcode guide:
Bots are at the center of the Xcode Server automated workflow. Bots
build and test your projects with the schemes you specify. Because
Xcode Server can access the source code repositories of your projects,
you can create and schedule bots to run periodically, on every source
code commit, or manually. You can also configure bots to send email
notification of the success or failure of their integrations. Xcode
Server also allows your bots to conduct performance testing and
initiate pre- and postintegration triggers.
On how to setup and configure bots, please read Install macOS Server and Configure Xcode Server.
I can see from my iTunes connect control panel how many users are on each version of the app I have in beta. When does TestFlight update those apps? Do they have to open TestFlight and manually choose to update? Does it happen automatically when they launch the app they are testing?
I can't seem to find any answer on Apple's documentation.
They have to manually update it. A push notification and email is sent to let the user know that a new version is ready to be tested, but it's up to user to open test flight and install it.
As of November 11, 2020, TestFlight version 3.0 now supports automatic updates:
Source: https://www.macrumors.com/2020/11/11/testflight-app-automatic-update/
After a while, I found a solution that works every time.
You need to remove the version from testing by selecting Not Available for Testing. Then save, approve and reselect the version you want to test and save again.
This will make all your TestFlight users receive a notification with the update (event if they have a different version installed).
It might be possible to do a force upgrade, see https://stackoverflow.com/a/12319198/330067, however I didn't find any details so far.
When I am trying to request a code review, this is what I am getting on TFS and it doesn't allow me to send the code review.
Context for Code Review is not set correctly (probably, Team Project Collection)
any one have had this?
Disconnect. Then Re-connect to Team Projects
This happened to me after I went offline and got disconnected from TFS server. I clicked on the plug icon in Team Explorer ribbon, and I was able to send the code review
Same Issue. connection .
Afret re connect to TFS server. all went smoothly.
I got this message after a TFS upgrade (from 2012 to 2013 in my case).
In the TFS web portal there was a notification in the Overview tab of the Control Panel for my project. After clicking through the links on the wizard that popped up, I no longer had this issue.