These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
Natti Katz suggested an idea (#4786) · Oct 02, 2019 at 03:31 PM · execution serverjob scheduling
By default update local tests triggers a batch script on ALL execution servers. If an execution server is not configured it will be excluded. This is a major pain point for large organizations with lots of execution servers.
All new additional execution servers will also need additional configuration to at minimum run a dummy batch file just to prevent their server from being excluded.
The default behaviour should ideally be execution servers do not trigger the batch script, and only those that 'opt-in' will exhibit the behavior.
Dan Michlin commented · Oct 03, 2019 at 07:50 PM
Hi @Natti Katz, changing this behavior isn't currently planned in our roadmap.
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Help us make things better. Share your great idea or vote for other people's.
Execution Server Selector Pool for Job Scheduling instead of Specific Concrete Server Selection
Allow Data Type - Session to be passed as Output in Job Scheduler
Add Start Time to initial Interval setting within test suite
Execution log of a running CloudShell automation suite
shells should come with execution server selector attribute as a default
Refresh suite page with test status on new JSS
Job Scheduling (SnQ) should log to a sandbox's Activity Feed as Test's start/stop
Alerting Service for Execution Servers
Limit the amount of times shells/scripts requirements are being updated