Release your Action | Actions console | Google Developers
文章推薦指數: 80 %
Alpha: This channel should be used to quickly test early versions of your Action. Lets you distribute your Action to a small set of users ... Google Assistant ActionsonGoogle Waystobuild Overview LearnallthewaystobuildActions. Extendyourmobileapp ProvidefasterwaysforuserstoaccessyourAndroidappviaAssistant. Buildrichandnaturalconversations Buildcustomvoiceandvisualexperiencesforsmartdevices. Enhanceyourwebpresence PresentyourcontentinrichwaysforGoogleSearchandAssistant. Connectyoursmarthomedevices Letuserscontrollights,doors,coffeemachines,andmanyotherdevices. Getinspired Whybuild HelpusersfindanswersandgetthingsdonewithGoogleAssistant. Reach1billiondevices Helpusersathome,onthego,andinthecar—onover1billiondevices. Buildgames Buildfun,voice-enabledgamesforsmartdisplays. ExploreallActions SeewhatothersarebuildingforGoogleAssistant. Getdiscovered PublishyourActionstotheAssistantdirectory. Docs Mobile AppActions AndroidSlices Assistantsharing ReadIt Content Schema.orgwebmarkup Smarthomedevices Overview Devicetypesandtraits LocalHomeSDK Experimentaldevices AssistantSDK Conversational Overview Fundamentals Build InteractiveCanvas Userengagement Transactions Accountlinking Console Overview Localization Analytics Policies Gotoconsole Community Support Language English BahasaIndonesia Deutsch Español Français Português–Brasil Русский 中文–简体 日本語 한국어 Signin Actionsconsole Google Assistant ActionsonGoogle More Docs More Community Support Learn Overview ConsoleUI Build Actionsprojects ActionsBuilder Simulator Firebaseservices Deploy Directoryinformation Prepareforrelease ReleaseyourAction ActionsforFamilies OverviewBuildinganAction Policiesandterms GeneralPrivacypolicyguidanceTermsofserviceTermsexplanationActionsforFamiliesaddendumActionsLauncheraddendumBrandguidelines Grow Brandverification Localize OverviewAddlanguagesandlocalesLanguagesandlocalesPublishlocalizedActions Analyticsandhealth AnalyticsHealthchecksTroubleshooting Waystobuild Overview Extendyourmobileapp Buildrichandnaturalconversations Enhanceyourwebpresence Connectyoursmarthomedevices Getinspired Whybuild Reach1billiondevices Buildgames ExploreallActions Getdiscovered Mobile AppActions AndroidSlices Assistantsharing ReadIt Content Schema.orgwebmarkup Smarthomedevices Overview Devicetypesandtraits LocalHomeSDK Experimentaldevices AssistantSDK Conversational Overview Fundamentals Build InteractiveCanvas Userengagement Transactions Accountlinking Console Overview Localization Analytics Policies Gotoconsole Home Products GoogleAssistant Docs Actionsconsole ReleaseyourAction TestingyourActionwithusersgivesyoutheopportunitytogetearlyfeedbackandfixanytechnicaloruserexperienceissuesbeforeyoureleaseitwidely. TheActionsconsolesupportsreleaseenvironmentssothatyoucangivealimitedsetofusersaccesstotestanewAction,ornewerversionofyourexistingAction,beforedeployingittothepublic. Lifecycleofarelease ThefollowingdiagramshowspotentialpathsthelifecycleofanActioncantake: Figure1.LifecycleofanActionwithreleaseenvironments. Therearetwotypesofpre-productionreleaseenvironmentsthattheActionsconsolesupports: Alpha:ThischannelshouldbeusedtoquicklytestearlyversionsofyourAction. LetsyoudistributeyourActiontoasmallsetofuserswithoutgoingthroughafullGooglereview. UsersaregivenwarningsthattheActionhasn'tundergoneaGooglereviewforpolicycompliance. Idealforinternaltesting. Beta:ThischannelletsyoudistributeanActiontoalimitedsetofusersafterpassingafullGooglereview. YoushouldusethischanneltogiveusersoutsideyourorganizationaccesstoearlyversionsoftheAction. UserswillbeinformedthattheActionisapreviewversion. SincethebetaversionhaspassedGooglereview,youcanelecttomakeitpublicatanytimewithoutanotherreviewbyGoogle. Note:Youcanonlyhaveone"live"alphaorbetaversionofyourActionreleased. Releaseenvironmentcomparison Thetablebelowsummarizesthedifferencesbetweendeploymentchannels. Simulator Alpha Beta Production Intendedaudience Developeronly Earlytesterswithinyourteam,friends,andfamily Testersoutsideofyourteam AllGoogleAssistantusers RequiresGoogleReview No No Yes Yes Whohasaccess Developeronly Developer-definedlistofusers.Usersmustoptin. Developer-definedlistofusers.Usersmustoptin. PubliclyavailabletoallGoogleAssistantusers Max#ofusers 1 20 200 N/A Whereavailable SimulatorandallAssistantdevices AllAssistantdevices AllAssistantdevices AllAssistantdevices ActionsBuilder Supported Supported Supported Yes ActionsSDK Supported Supported Supported Yes Dialogflow Supported Supported Supported Yes SmartHome Supported(requiresaccountlinking) Notsupported Notsupported Yes Templates Supported Notsupported Notsupported Yes Explicitinvocation Supported Supported Supported Yes Implicitinvocation Supported Supported Supported Yes Accountlinking Supported Supported Supported Yes Note:IfyouareusingDialogflowversioning,youcandeploydifferentversions todifferentreleaseenvironments.Tolearnmore,see Submityourproject. Managetestsforalphaorbetarelease Tosetupyourtestingforalphaorbeta,followthesesteps: ClickeitherManageAlphatestersorManageBetatesters. Typeintheemailaddressesforthetesters,separatedbycommas.Youcanspecifyupto20testersforalphatestingandupto200testersforbetatesting. Note:TestersmusthaveaGoogleaccount(@gmail.com)oraGoogleWorkspace.YoucannotdesignatemultipleusersviaaGooglegroupemailalias. CopytheOpt-inlinktosharewithyourtesters. ClickSave. YoushouldsendaninvitationemailtoyourtesterswithalinktothealphaorbetaversionofyourAction(theopt-inlink).Tolearnmore,seeGetfeedback. Opt-inlink Theopt-inlinkrepresentsyourActiondirectorypageandneverchanges.Thelinkpointstesterstoyourdirectorypageandseetheopt-incardfortheeligibleenvironment.Ifyoulistedthesametestersforalphaandbeta,theyareeligibleforbothandseeanopt-incardforthealphaversionfirst. Implementfulfillmentforanalphaorbetarelease ThereleasechannelinformationisnotincludedintheHTTPrequestfromAssistanttoyourfulfillment.Tohandlereleasechannelsinyourfulfillment,youshouldprovidedifferentfulfillmentURLs(forexample,onefulfillmentURLforthebetaandanotherURLfortheproductionversionofyourAction). Getfeedback OnceyourActionhasbeenreleasedtothealphaorbetareleasechannel,youshouldinviteyourtestersbysharingyouropt-inlink(whichisthesameasyourAssistantdirectorylisting). Makesuretoindicatetoyourtestersthattheymust: HavetheGoogleAssistantappdownloadedontheirmobiledevicesinorder toperformalphaorbetatesting. LogintotheGoogleAssistantappusingthesameaccountwhichyou designatedasanalphaorbetatester. AfteryoudeployyourAction,anynewtestersneedtowaitforatleast3hours beforetheycanaccesstheActionusingtheopt-inlink. Whenusersclickonthislink,theyaredirectedtothecorrespondingAction's directorypage.TheyshouldclickontheI'minbuttonatthebottomofthe Action'sdirectorypagetooptinasatesterforthefirsttime. Afterthetesteroptsinontheirphone,yourActionisimmediatelyavailable onalloftheirdevices.TesterswillseeyourActionintheMyAppssection oftheGoogleAssistantapplabeledwithoneofthesemodes:Alpha,Beta, orNotesting.TheNotestingoptionwillserveuserstheProductionversion ofyourAction,ifavailable.IfthereisnoProductionversion,userswillnot beservedwithanything. Note:UserscannotrateyourActionintheGoogleAssistantappiftheyare usingalphaorbetaversions.Instead,youshouldprovidetesterswithawayto providefeedbackbyemail,viaawebsite,inamessageforum,orthroughanother suitablemechanism. Bestpractices Makesureuserscanjointhetests.Yourtestersneedtohavea Googleaccount(@gmail.com)oraGSuiteaccounttojoinatest. Choosetheappropriatetestingtype.Analphatestinggroupshouldbe smallandtesttheleaststable,experimentalversionsofyourActions(such aswithinyourcompanyorteam).Usebetatestingwithalargergroupto teststableversionsofyourActionsthatarenearrelease. Provideachannelfortesterstosendyoufeedback.Alphaandbetachannels areonlyavailabletoyourowntesters.Makesuretoofferthemtheabilityto providefeedbackbyemail,viaawebsite,inamessageforum,orthrough anothersuitablemechanism. Runconcurrenttestsonthesameaction.Youcanrunalphaandbetatests concurrently. Knownissues TheAssistantdirectoryforthewebisnotsupportedforopt-intoalphaorbeta. Makesureyourtestersfollowthelinkontheirmobiledevices(AndroidoriOS). Yourchangesmaytakeafewhourstogolive.Pleaseholdoffforanappropriate periodoftimebeforesharingtheopt-inlinkwithyourusers. Createanewalphaorbetarelease TodeployyourActiontothealphaorbetareleasechannel,followthesesteps: FromtheActionsconsole,clickDeploy>Release. ClickStartnewrelease. SelectAlphaorBetaandclickSubmit. Ifprompted,indicatethatyouhavecompletedtherequiredstepsintheActionreviewrequirementschecklist. Ifapplicabletoyourproject,selectthelanguagesforyourrelease. ClickSubmit. Afteryousubmitthealphaorbetaversion,itappearsintheManageReleasessection. Note:Afteryoudeploy,yourversionwillbeintheDeployingstateforupto3hoursbeforeitisavailabletoyourusers.Afterdeploymentiscomplete,otherliveversionsinthatreleaseenvironmentareremoved.Note:Ifyouareadeveloperoftheproject,thetestversionisenabledbydefaultonyourdevice.Ifyouwanttoaccessthealphaandbetaversions,disabletheOndevicetestingoptionintheActionsconsolesimulator. Upgradeanexistingreleasefromalphaorbetatoproduction ProductionreleasescanbeafullrollouttoallGoogleAssistantusers,orastagedrollouttospecificregionsorapercentageofusers.StagedrolloutshelptestthestabilityofyourActionproject.It'sbesttoreleasetoasmallsetofusersandmakegradualincreasesuntilyou'vereached100%ofusers.Thisallowsyoutoresolvebugsbeforerollingouttotheentireuserbase. Note:Whetherreleasedasafullorstagedrollout,yourActionisrequiredtopassareviewprocessbeforeit'sdeployedtoproduction.Onlyonereviewisrequired;however,ifyourActionismodified,itmustbereviewedagain.YouneedtosubmitanewversionofyourActiontoeitherBetaorProductiontoinitiateareview. Stagedrollout Stagedrolloutsallowdeveloperstomanagetheirproductionreleasesbylaunchingtoasubsetofusersandslowlyrampinguptoallusers.Youcangraduallyincreasetheregionsorthepercentageofusersinyourrollout. Note:Youcannotselectapercentageofuserswithinaselectedregion.Youcannotchangebetweenstagingtypes(locationorpercentageofusers)whenupgradinganongoingrelease.Youmustcancelthereleaseandstartanewoneifyouwanttochangethestagingtype.Therecanbeonlyoneversionactiveonthestagedrollouttrack. TodeployyourActionasastagedrollout,followthesesteps: UnderManagereleases,selecttheversiontobeupgradedtoproductionrollout. ClickManagedeployments. SelectDeploytoProduction. SelectStagedrollout. ClickSelectrollouttype. SelectSpecifiedlocationsorPercentageofusers.Formoreinformationaboutthisselection,seeRolloutbyspecifiedlocationsorRolloutbypercentageofuserbase. ClickSubmit. Toadvancethestageofyourrollout,seeAdvancetherolloutstageofarelease. Fullrollout SelectingthisoptionreleasesyourActionprojecttoallusersinallofyourtargetedcountries. TodeployyourActionasafullrollout,followthesesteps: UnderManagereleases,selecttheversiontobeupgradedtoproductionrollout. ClickManagedeployments. SelectDeploytoProduction. SelectFullrollout. ClickSubmit. Createanewproductionreleasewithoutalphaorbetatesting ProductionreleasescanbeafullrollouttoallGoogleAssistantusers,orastagedrollouttospecificregionsorapercentageofusers.StagedrolloutshelptestthestabilityofyourActionproject.It'sbesttoreleasetoasmallsetofusersandmakegradualincreasesuntilyou'vereached100%ofusers.Thisallowsyoutoresolvebugsbeforerollingouttotheentireuserbase. Note:Whetherreleasedasafullorstagedrollout,yourActionisrequiredtopassareviewprocessbeforeit'sdeployedtoproduction.Onlyonereviewisrequired;however,ifyoumodifyyourActionandreleaseittoproduction,itmustbereviewedagain.YouneedtosubmitanewversionofyourActiontoeitherbetaorproductiontoinitiateareview. Stagedrollout Stagedrolloutsallowdeveloperstomanagetheirproductionreleasesbylaunchingtoasubsetofusersandslowlyrampinguptoallusers.Youcangraduallyincreasetheregionsorthepercentageofusersinyourrollout. Note:Youcannotselectapercentageofuserswithinaselectedregion.Youcannotchangebetweenstagingtypes(locationorpercentageofusers)whenupgradinganongoingrelease.Youmustcancelthereleaseandstartanewoneifyouwanttochangethestagingtype.Therecanbeonlyoneversionactiveonthestagedrollouttrack. TodeployyourActionasastagedrollout,followthesesteps: FromtheActionsconsole,clickDeploy>Release. ClickStartnewrelease. SelectProduction. Ifprompted,indicatethatyouhavecompletedtherequiredstepsintheActionreviewrequirementschecklist. Ifapplicabletoyourproject,selectthelanguagesforyourrelease. SelectStagedrollout. ClickSelectrollouttype. SelectSpecifiedlocationsorPercentageofusers.Formoreinformationaboutthisselection,seeRolloutbyspecifiedlocationsorRolloutbypercentageofuserbase. ClickSubmit. Rolloutbyspecifiedlocations SelectingthisoptionreleasesyourActionprojecttocountriesorregionsyouchoose. TorolloutyourActionbylocation,followthesesteps: ClickSelectcountriesorregionsandchecktheboxesfortheregionstotargetforyourrelease. ClickSubmit. Note:Onlyregionsthatyouselectedinlocationtargetingareallowed. Rolloutbypercentageofuserbase ThisoptionreleasesyourActiontoapercentageofrandomlyselectedusers. TorolloutyourActiontoapercentageofusers,followthesesteps: ClickPercentageofusers. SelectthepercentageofusersyouwanttoreleaseyourActionto. ClickSubmit. Note:Youcanrevertthistypeofreleasebysettingthepercentageto0%. Fullrollout SelectingthisoptionreleasesyourActionprojecttoallusersinallofyourtargetedcountries. TodeployyourActionasafullrollout,followthesesteps: FromtheActionsconsole,clickDeploy>Release. ClickStartnewrelease. SelectProduction. Ifprompted,indicatethatyouhavecompletedtherequiredstepsintheActionreviewrequirementschecklist. Ifapplicabletoyourproject,selectthelanguagesforyourrelease. SelectFullrollout. ClickSubmit. Aftertheproductionversionissubmitted,itappearsintheManageReleasessection. Note:Afteryoudeploy,yourversionwillbeintheDeployingstateforupto3hoursbeforeitbecomesavailabletoyourusers.Afterdeploymentiscomplete,otherliveversionsinthatreleaseenvironmentwillbeundeployedautomatically. Editorundeployarelease OnceyouhavesubmittedyourActiontoareleasechannel,youcanstillmakechanges.Youcantestthecurrentversion,withdrawtheversionfromreview,viewreleasedetails,managedeployments,undeploy,andupgraderolloutstages.Thisisalsowhereyoucanviewdetailsonpastreleases. Viewandeditarelease Toviewreleasedetails,ormakechangestoyourAction'srelease,followthesesteps: UnderManageReleases,selecttheversionunderReleasename. ChooseEditrollout,Managedeployments,orSeemore. Advancetherolloutstageofarelease ToadvancetherolloutstageforyourAction,followthesesteps: UnderManagereleases,selecttheversiontobeupgraded. ClicktheEditrolloutbutton. Makethechangestoyourrollout.Forexample,youmaywanttoadvancetheuserbasefrom5%to20%. ClickSubmit. Undeployfromproduction Ifyouneedtotakeyourstagedrolloutoffline,clickonEditrolloutunderManagereleases.Youcaneitherclearallregionsorselect0%,dependingonifyourrolloutisbylocationorpercentageofuserbase. ToundeployanActionthatisfullyrolledout(100%ofuserbase),clickontheManagedeploymentsbuttonunderManagereleasesandselectUndeployfromProduction. Previous arrow_back Prepareforrelease Exceptasotherwisenoted,thecontentofthispageislicensedundertheCreativeCommonsAttribution4.0License,andcodesamplesarelicensedundertheApache2.0License.Fordetails,seetheGoogleDevelopersSitePolicies.JavaisaregisteredtrademarkofOracleand/oritsaffiliates. Lastupdated2021-08-13UTC. [{ "type":"thumb-down", "id":"missingTheInformationINeed", "label":"MissingtheinformationIneed" },{ "type":"thumb-down", "id":"tooComplicatedTooManySteps", "label":"Toocomplicated/toomanysteps" },{ "type":"thumb-down", "id":"outOfDate", "label":"Outofdate" },{ "type":"thumb-down", "id":"samplesCodeIssue", "label":"Samples/codeissue" },{ "type":"thumb-down", "id":"otherDown", "label":"Other" }] [{ "type":"thumb-up", "id":"easyToUnderstand", "label":"Easytounderstand" },{ "type":"thumb-up", "id":"solvedMyProblem", "label":"Solvedmyproblem" },{ "type":"thumb-up", "id":"otherUp", "label":"Other" }] MoreInformation GoogleAssistant WhybuildfortheAssistant? HowGoogleAssistantworks Assistantdirectory Support Community Programs WomenTechmakers GoogleDeveloperGroups GoogleDevelopersExperts Accelerators GoogleDeveloperStudentClubs Developerconsoles GoogleAPIConsole GoogleCloudPlatformConsole GooglePlayConsole FirebaseConsole ActionsonGoogleConsole CastSDKDeveloperConsole ChromeWebStoreDashboard Android Chrome Firebase GoogleCloudPlatform Allproducts Terms Privacy SignupfortheGoogleDevelopersnewsletter Subscribe Language English BahasaIndonesia Deutsch Español Français Português–Brasil Русский 中文–简体 日本語 한국어
延伸文章資訊
- 1Google play加入測試人員步驟
封閉式Alpha/Beta 版測試:對少數使用者進行測試,測試版本已發佈的現有應用程式,只有測試群組內的使用者會收到Alpha/Beta 版更新。 測試群組內的使用者第一次下載APP ...
- 2Where do alpha testers download Google Play Android apps?
Google play store provides closed testing track to test your application with a limited set of te...
- 3Release your Action | Actions console | Google Developers
Alpha: This channel should be used to quickly test early versions of your Action. Lets you distri...
- 4Android App Google Play測試方式 - 歐文的BLOG - 痞客邦
因為Google Developer Console 有做改版, 很多都不一樣了, 這邊我再介紹一次(16年的文章已砍掉) 在Google Play中,有提供三種測試方式, 這些方式 ...
- 5發佈至Google Play 商店- Visual Studio App Center - Microsoft ...
確定您有適用于App Center 的API 專案和服務帳戶,以建立Google Store 連線並代表您存取Google Api。 如需這些追蹤的詳細資訊,請參閱Beta 和Alpha 的先決...