I'm pleasently surprised that bitbucket-pipelines has actually worked this well. So well that we have turned off our Jenkins server.
Nice work, atlassian!
i can go for that
Who would want to see a history of deployments for a branch-specific environment? What information would they be looking for?
We have the following branches (simplified):
Now, I was thinking to use the deployments feature to track the deployment of the test environment of each branch. So our testers can see the status of their test environment.
Do you use Bamboo? Anything you’d like to see improved in the deployment support there?
At the moment, direct access to your Amazon resources requires an access key configured via secure variables in Pipelines. We'd consider adding support for IAM roles/key rotation if a lot of people would find it useful.
- elastic beanstalk
I'm currently using the "custom" section with a plugin I developed to deploy to environments. In the default build it pushes the build to Elastic Beanstalk and then deploys to test. The custom builds merely promote the build for other environments.
this is birru you're shared new future in bit-bucket (bit-bucket deployments) but it not visible in bit-bucket account
i am searched is there any add-on future there no add-on
there is no future in bit
how can i go to use deployments future in bitbucket
That can be done using either the built-in Jenkins API https://wiki.jenkins.io/display/JENKINS/Remote+access+API or "Trigger Builds Remotely" Build Trigger option (which basically uses the same mechanism with your own Job-specific token/key). Nice feature is that BitBucket Pipelines supports "environment variables" to enable securely storing Jenkins API keys or tokens that let you securely tunnel through corporate FW rules and the like: