| /dports/graphics/ogre3d19/sinbad-ogre-dd30349ea667/Tools/3dsmaxExport/MaxscriptExport/scripts/ogre/macros/ |
| H A D | ogreToolbar.mcr | 25 rollout OgreExportOptions "Options" width:270 height:140 rolledUp:true
124 rollout OgreExportObject "Object" width:270 height:259
352 rollout OgreExportMesh "Mesh" width:270 height:120
418 rollout OgreExportAnimation "Animation" width:270 height:347
612 rollout OgreExportMaterial "Material" width:270 height:33
631 rollout OgreExportAbout "About" rolledUp:true
641 -- add the rollout, which contains the dialog
|
| /dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/spec/migrations/ |
| H A D | 20210722150102_operations_feature_flags_correct_flexible_rollout_values_spec.rb | 18 parameters = { groupId: "default", rollout: "100", stickiness: old }
|
| /dports/textproc/highlight/highlight-4.1/langDefs/ |
| H A D | ms.lang | 18 List={"utility", "rollout", "label", "button", "edittext", "combobox",
|
| /dports/sysutils/helm/helm-3.5.2/vendor/k8s.io/kubectl/docs/book/pages/app_composition_and_deployment/ |
| H A D | accessing_multiple_clusters.md | 6 - Target a cluster for a rollout with the `--context` flag
7 - Target a cluster for a rollout with the `--kubeconfig` flag
|
| /dports/sysutils/istio/istio-1.6.7/vendor/k8s.io/kubectl/docs/book/pages/app_composition_and_deployment/ |
| H A D | accessing_multiple_clusters.md | 6 - Target a cluster for a rollout with the `--context` flag
7 - Target a cluster for a rollout with the `--kubeconfig` flag
|
| /dports/sysutils/kubectl/kubernetes-1.22.2/staging/src/k8s.io/kubectl/docs/book/pages/app_composition_and_deployment/ |
| H A D | accessing_multiple_clusters.md | 6 - Target a cluster for a rollout with the `--context` flag
7 - Target a cluster for a rollout with the `--kubeconfig` flag
|
| /dports/net/google-cloud-sdk/google-cloud-sdk/lib/googlecloudsdk/third_party/apis/osconfig/v1/ |
| H A D | osconfig_v1_messages.py | 152 rollout = _messages.MessageField('PatchRollout', 7) variable in ExecutePatchJobRequest
483 rollout = _messages.MessageField('PatchRollout', 10) variable in PatchDeployment
635 rollout = _messages.MessageField('PatchRollout', 13) variable in PatchJob
|
| /dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/doc/administration/raketasks/ |
| H A D | storage.md | 101 If you have any existing integration, you may want to do a small rollout first,
103 the environment variables `ID_FROM` and `ID_TO`. For example, to limit the rollout
155 the environment variables `ID_FROM` and `ID_TO`. For example, to limit the rollout
|
| /dports/lang/spidermonkey78/firefox-78.9.0/toolkit/components/normandy/docs/ |
| H A D | services.rst | 9 and their metadata for add-on studies and rollout.
|
| /dports/mail/thunderbird/thunderbird-91.8.0/toolkit/components/normandy/docs/ |
| H A D | services.rst | 9 and their metadata for add-on studies and rollout.
|
| /dports/www/firefox/firefox-99.0/toolkit/components/normandy/docs/ |
| H A D | services.rst | 9 and their metadata for add-on studies and rollout.
|
| /dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/lib/atlassian/jira_connect/serializers/ |
| H A D | feature_flag_entity.rb | 58 rollout: {
|
| /dports/sysutils/helm/helm-3.5.2/vendor/k8s.io/kubectl/pkg/cmd/rollout/ |
| H A D | rollout_pause_test.go | 17 package rollout package
|
| /dports/www/firefox-esr/firefox-91.8.0/toolkit/components/normandy/docs/ |
| H A D | services.rst | 9 and their metadata for add-on studies and rollout.
|
| /dports/sysutils/istio/istio-1.6.7/vendor/k8s.io/kubectl/pkg/cmd/rollout/ |
| H A D | rollout_pause_test.go | 17 package rollout package
|
| /dports/sysutils/kubectl/kubernetes-1.22.2/staging/src/k8s.io/kubectl/pkg/cmd/rollout/ |
| H A D | rollout_pause_test.go | 17 package rollout package
|
| /dports/games/openra/OpenRA-release-20200503/mods/ra/audio/ |
| H A D | music.yaml | 29 rollout: Roll Out
|
| /dports/games/gnubg/gnubg-1.06.002/po/ |
| H A D | it.po | 4784 "accuracy of the current rollout result. If the rollout were to be continued "
6078 "or during rollout"
9300 #: rollout.c:1485
9309 #: rollout.c:1685
9313 #: rollout.c:1690
10137 "rollout late plies')."
10222 "rollout jsd limit')."
10390 "rollout')."
10393 "rollout')."
11508 msgid "Cubeful rollout."
[all …]
|
| H A D | en_US.po | 1185 msgid "Full cubeful rollout"
4770 "accuracy of the current rollout result. If the rollout were to be continued "
6023 "or during rollout"
9172 #: rollout.c:1485
9179 #: rollout.c:1685
9183 #: rollout.c:1690
9989 "rollout late plies')."
10216 "rollout')."
11305 msgid "Cubeful rollout."
11306 msgstr "Cubeful rollout."
[all …]
|
| /dports/graphics/openexr/openexr-3.1.4/ASWF/tsc-meetings/ |
| H A D | 2019-07-18.md | 14 * Azure+Sonar rollout
63 * Azure+Sonar rollout
|
| /dports/net/google-cloud-sdk/google-cloud-sdk/lib/googlecloudsdk/command_lib/game/servers/ |
| H A D | flags.yaml | 5 Path to a JSON or YAML file that contains game server config overrides in the rollout. The game
|
| /dports/games/gnubg/gnubg-1.06.002/ |
| H A D | NEWS | 108 *** rollout positions as initial position (i.e., no doubles on first roll).
118 *** much more flexible rollout databases added.
214 after gnubg's first choice move is played; "rollout =1 =3" rolls out the
|
| H A D | TODO | 28 ** Save rollouts and evaluations in moverecords, e.g., a cubeless rollout
61 *** An option to stop a rollout once the stderr error has reached some
67 *** Predefined rollout settings
197 leads to other bad errors (e.g. "set player 0 cubedecision rollout").
215 rollout window -- do we really want a window in this case?)
222 ** make rollout as initial position work correctly. Currently, you have to perform
227 ** the rollout window is a bit to small
|
| /dports/sysutils/nomad/nomad-1.1.0/website/content/docs/job-specification/ |
| H A D | multiregion.mdx | 23 the values of the `region` stanza. Nomad regions coordinate to rollout each
73 a rollout strategy for the regions.
78 ordered; depending on the rollout strategy Nomad may roll out to each region
|
| /dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/doc/development/feature_flags/ |
| H A D | controls.md | 54 As a first step in a feature rollout, you should enable the feature on
101 When enabling a feature flag rollout, the system will automatically block the
248 rollout. Avoid using percentage of _time_ rollouts in this case.
250 A percentage of _time_ rollout can introduce inconsistent behavior when `Feature.enabled?`
319 1. Close the rollout issue for the feature flag after the feature flag is removed from the codebase.
|