Cole Prato
My feedback
36 results found
-
22 votes
An error occurred while saving the comment An error occurred while saving the comment Cole Prato commentedThis is needed for Production CI Jobs, these need to be a little more control over date and time. Example if I want to release everything on Tues, Thursday at 3pm. How it is now is fine for other sandbox orgs.
Cole Prato supported this idea · -
4 votes
An error occurred while saving the comment Cole Prato commentedI would like to see the Name of the Job in the message as well.
Cole Prato supported this idea · -
2 votesCole Prato supported this idea ·
-
5 votesCole Prato supported this idea ·
-
2 votesCole Prato supported this idea ·
-
3 votesCole Prato supported this idea ·
-
10 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Cole Prato supported this idea ·
-
1 voteCole Prato shared this idea ·
-
1 voteCole Prato shared this idea ·
-
11 votesCole Prato supported this idea ·
-
3 votesCole Prato supported this idea ·
-
5 votesCole Prato supported this idea ·
-
21 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Cole Prato supported this idea ·
-
8 votesCole Prato supported this idea ·
-
5 votesCole Prato supported this idea ·
-
2 votesCole Prato supported this idea ·
-
2 votesCole Prato supported this idea ·
-
4 votesCole Prato supported this idea ·
-
3 votesCole Prato supported this idea ·
-
2 votesCole Prato supported this idea ·
I think this is an important function to stay up with other CI/CD Deployment Tools. You need to still have a little control over timing if needed. Even for resource purpose the job could kick off within the hour schedule i.e if you select 1pm every Tuesday and Thursday it would just kick-off sometime in that hour.