Currently I have an issue with notification emails after building. It was absolutely working fine a few days ago, but now it does not trigger the email after successful a build. We found the difference in the email template for the build process. The email trigger is not working after code is checked-in but works fine after a manual build from TFS environment.
Could you please help us to figure out the issue?
Related
I have created an app and I have uploaded it to testflight the first versions all in order but they asked me for more changes and I have uploaded them and the internal tester of my app do not see the changes made, ie if you send them the message that there is a new version to download and they see the version number and they can download it but when testing it you do not see the changes it looks just as it was before. Any idea what it could be? I have searched for info and I can not find almost nothing. Thanks
I've run into this issue before as well. The only way I was able to solve it was to delete the bin/obj folders, close solution, clean, rebuild.
Then the next time the changes were shown.
I'm using Xamarin Forms and Visual Studio
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'm using test flight to share builds with internal testers. But I noticed a weird behavior last week.
I deployed a build almost a month ago, and now the app is live with that build. However, Testflight sent an automated email to testers again saying the build is available for testing. (I know that in current version, we may test the app even if it's live).
The question is:
Is it some bug at test-flight's end that it's sending email notification of
an old build again?
Should I manually expire this build to avoid any
such issue in future? Please note, my app is live with this build
and I don't want it to be affected.
FYI - Same thing just happened to me, but almost 48 hours after I released the app. I don't even have any Testflight users other than me.
I had to double-check to make sure it was really in the App Store. Must be a bug...
Did anyone managed to get Travis CI to deploy the app on iTunesConnect? I have read tons of articles and tried them without success.
My closest bet was this article:
Continuously Delivering iOS Beta Builds Automated with Travis CI
They didn't provide info that you need to install Mako in order to work, so pay attention if you go this way.
The main problem however is the fact that I do not have Crittercism or HockeyApp accounts, however the python script want them from me and no matter if I do not provide them or provide fake it fails later as it actually tries to do something with them.
Other thing that I come across is:
Automated iOS beta distribution using Travis CI and Testflight
which is essentially written on top of Deploy an iOS app to testflight using Travis CI. The problem here is that they deploy to TestFlight app instead of iTunesConnect.
Any help would be appreciated.
I would consider looking into the ruby gem fastlane. We have been using it for quite some time and it has definitely saved us hours of problems related to deploying to iTunesConnect. I haven't used TravisCI before but from this blog post I know they support fastlane. The community is great and #KrauseFX is awesome at answering any questions you might have. He even uses TravisCI to build the fastlane tools!
I am new to TeamCity but have set up version 8.0.5. I am running it on a Windows 2008 R2 server and TeamCity is running as a service. I have configured the authentication to connect to the domain (which all works correctly)
I have created a project which connects to TFS to get the source code and compile it when the source code has changed.
The builds all work fine however, every time the build completes my windows account gets locked out (even if I did not trigger the build). This becomes increasingly annoying as other people are working on this project.
The TeamCity service does not use my account (it uses a service account) and the service account is used to get the code from TFS. When I view the project configurations, my account is not shown anywhere.
I have checked all of the configuration files and non of them are using my account credentials.
I have looked at the log files and I can't see anything there to indicate that my account is locked. However the TeamCity server is the server that is locking my account and it is happening when a build is completed.
As I'm still fairly new to TFS please can someone help me to establish why TeamCity could be locking out my account?
Thanks.
I resolved this by doing two things:
1) The TFS login account was previously using my login credentials, I removed these (to force it to use the service account).
This didn't actually resolve the issue.
2) Rebooting the TeamCity server seemed to resolve the problem (with the step above).