To show how you can achieve the same pack and push commands as above, here’s an example pipeline step, but this time using the octopus-cli-run Bitbucket Pipe. ![]() out/$BITBUCKET_REPO_SLUG.$VERSION.zip -server $OCTOPUS_SERVER -apiKey $OCTOPUS_APIKEY Pipe example of packing and pushing ![]() pipelines : default : - step : name : Deploy to Octopus image : octopusdeploy/octo:6.17.3-alpine script : - export VERSION=1.0.$BITBUCKET_BUILD_NUMBER - octo pack -id $BITBUCKET_REPO_SLUG -version $VERSION -outFolder. Here’s an example pipeline step that demonstrates using the octo CLI Docker image, which packs the current state of your repository into a zip file and then pushes that package to Octopus Deploy. Docker CLI Example of packing and pushing This is the file we need to modify to run our build, pack and/or push package commands. When you enable BitBucket Pipelines for your repository, BitBucket stores all the information it requires into a bitbucket-pipelines.yml file in the base of your repository. ![]() The Octopus Deploy API Key required for authentication The Octopus Server URL you wish to push the final package to
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |