How does deployment work between dev, test, staging, production?

Question

Software Deployment

Good evening
How to organize the process (what tools, I google, just tell me what to google)?
The developer coded it, uploaded it to git, the pull request passed, the changes were merged into the master branch. Jenkins saw the changes (how?) Launched the build, tests, if everything is ok, launched Ansible, and he posted it in the Test. What's next? Who collects on the test? how do testers know that they have something new on the test and need to test it? How far does it go on stage? also Ansible?
What is being done on the stage? how does it go to production? Where does the docker wedged in here, because in the end there should be a container?
Thank you!

Answer 1

This is all customizable.
As you wish - so be it.
The Jenkins you mentioned is a versatile tool. There are no clearly predetermined paths.
How do testers know?
For example, you can set up notifications in Slack.
Docker is usually used at all stages - so that there is one environment guaranteed both during development and during testing and during operation. But the Docker container is usually rebuilt at each of these stages (or taken automatically from the cache).
You can read specific recommendations-examples. For example, there are several articles on bitbucket about different schemes.
But this is not a standard, not a uniform rule.