-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for app-level test_info #9055
Conversation
So that we can set beta_app_feedback_email and beta_app_description
# for an application. Note that this structure, although looking similar to build test_info | ||
# is test information about the application | ||
|
||
attr_accessor :test_info |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does a test info object have a test_info attribute?
Looks awesome. What's the easiest way to test it on a production system? As part of pilot, right? |
… set app info first.
@KrauseFx I wrote a RakeFile to test it, but yeah, easiest way is to run from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two tiny little things but otherwise 🚀
pilot/lib/pilot/build_manager.rb
Outdated
rescue => ex | ||
UI.user_error!("Could not set changelog: #{ex}") | ||
end | ||
UI.success "Successfully set the changelog for build" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this might be nicer in the begin
block.
pilot/lib/pilot/build_manager.rb
Outdated
if should_update_app_test_information(options) | ||
app_test_info = Spaceship::TestFlight::AppTestInfo.find(app_id: build.app_id) | ||
app_test_info.test_info.feedback_email = options[:beta_app_feedback_email] if options[:beta_app_feedback_email] | ||
app_test_info.test_info.description = options[:beta_app_description] if options[:beta_app_description] | ||
app_test_info.save_for_app(app_id: build.app_id) | ||
begin | ||
app_test_info.save_for_app(app_id: build.app_id) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we put a UI.success
call here with some nice message?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐑
'demoAccountPassword' => 'Password', | ||
'demoAccountRequired' => false, | ||
'notes' => 'notes!!' | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could the pilot docs please be updated to show an example of adding these settings to your Fastfile
(or however they're meant to be set). Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, scratch that, I found them.
Congratulations! 🎉 This was released as part of fastlane 2.28.8 🚀 |
So that we can set beta_app_feedback_email and beta_app_description
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validAdd support for setting TestFlight app-level test info. Previously we had tried to set the beta feedback email and app description through build-level test-info, but this does not work. As such, when specifying feedback email and app description through
pilot
, we now set the app-level test info.