Are pipelines a development environment?

Question

Hi,

I'm new to BitBucket and I'm trying to get my head around pipelines.

Currently I am outsourcing dev work and I provide each dev with access to my repository, this allows them to submit initial commits.

Where does pipelines come in? Is this a live development environment like a sandbox that they can utilise to complete all of their development work? (thus meaning they wouldn't need access to the platforms or servers that these would be pushed to).

Thanks

unknown · Answer

Thanks very much for your reply. Just to make sure I understand correctly, pipelines cannot be directly integrated with live deployment environments to deploy code - but more so it allows developers to work with a checked out copy of the code and once accepted, the code is merged with the master file as a form of version control?

(i.e. I'm not able to push code directly from bitbucket to AWS for instance)

VICTOR-OSEGHALE · Answer

Hi Ryan,

Thanks for reaching out here.

Pipelines come when you need to automate build, test and deploy your code, based on bitbucket-pipelines.yml file in the repository. B

It's similar in concept to the sandbox where by developers can fully test the code changes with the pipeline build on specific branches, and only successful build can be checked back into and merged with master.

(thus meaning they wouldn't need access to the platforms or servers that these would be pushed to).

Pipeline runs on the remote repository, developers do not necessarily have to access the remote repositories to make pipe line work, but when codes are pushed to remote, the pipeline build is triggered based on the configuration applied.

Am sure users able to push to a remote repository should have some access to the repository except somehow they only have SSH key access to perform git operations.

References

Get started with Bitbucket Pipelines

Configuring the yml file for pipeline