Share your feedback...
Run only flaky tests
Every so often I create a branch to try to address flaky tests. I think a neat feature would be able to create a flaky-test-smash branch that ONLY runs the tests that have been identified as flaky some number of times. I don't want to eat up credits running tests I know are working, but sometimes a flaky test has a 9X% success rate so I don't know if my "fix" is actually working or not. I'd rather run my most flaked tests 250 times each then rerun my test suite of 3,000 tests over and over eating credits to try to guess if it fixed it or not. Just a thought you guys are great!
Graph for jobs created by circleci/continuation
When using orb/path-filtering and orb/continue, visualizing all related jobs is important. Maybe we can consider each job is a group and have some graph like airflow TaskGroup
Add a login link to the 404 page
i would guess 90% of the time someone sees your 404 page is because they're trying to access one of their projects but their login has expired. it shouldn't take so many clicks to get back to work.
Make trigger pipeline modal keyboard friendly
Hey team, The trigger pipeline modal cannot be controlled with my keyboard, which is really frustrating since I have to do it so often. Please let me me use arrow keys, Enter, and Tab to navigate between each field. In my attached screenshot, I should be able to tab to open the parameter type, press Enter to select the type, then tab to the Name & Value fields accordingly. Thank you!
auto-email receipts for accounting
Clients would like to provide receipts to accounting or finance team mates. Without giving them a login to VCS. It would save engineering time to not manually download them and send them via the UI.
I think there should be a global timeout that spans across all jobs. Pipelines can get pretty complex and there's a plethora of reasons why a job might hang and be stuck processing. And as a customer, we end up paying the costs.
steps: - run: #... run tests and store XML files to a subdirectory, for example, test-results #... - store_test_results: path: test-results