After running the migration script, I've gotten confused with the command-tests job that's automatically included in the test-deploy workflow. It think its' intent is to let the users know:
where to add their jobs
that they need to add filters: *filters to every test job.
that the job also needs to be added to the requires parameter in the orb-tools/publish job.
I think it needs to be be more explicitly clear with something like -FIRST-TEST-JOB
Examples:
workflows:
test-deploy:
jobs:
# Make sure to include "filters: *filters" in every test job you want to run as part of your deployment.
--> - command-tests:
filters: *filters
- orb-tools/pack:
filters: *filters
- orb-tools/publish:
orb-name: circleci/aws-s3-orb
vcs-type: << pipeline.project.type >>
pub-type: production
requires:
- orb-tools/pack
-----> - command-tests
Describe Request:
After running the migration script, I've gotten confused with the
command-tests
job that's automatically included in thetest-deploy
workflow. It think its' intent is to let the users know:filters: *filters
to every test job.requires
parameter in theorb-tools/publish
job.I think it needs to be be more explicitly clear with something like
-FIRST-TEST-JOB
Examples: