Halyna Berezovska Atlassian Team

@Max Howarth we merged readme updates. However I have tested different ways and can say that EXTRA_ARGS: '-o yoursetting=yourvalue' and passing it as a list both work EXTRA_ARGS: - '-o yoursetting=yourvalue' Regards, Galyna

@Terence Pires then I know what bug it was. Thank you for raising this! Have a great day!

@pspicer if you mean the title (here ) - yes it is indeed hardcoded. Thank you, we will discuss your initiative within the team and will get back to you with updates. Regards, Galyna

@Terence Pires hello! I am seeing that your EMAIL_PASSWORD var cannot be loaded as yaml. What I can say to debug it more: - please, use the latest email-notify version 0.4.5, we did some changes and we wonder if it fixes it or not - try this typing: PASSWORD: '${EMAIL_PASSWORD}' - if still fails, locally try in Python…

@Adrian Natter please, share the structure of your pipeline - that part when you use this pipe. Looks like some variable you passed is not in right structure

@Andrew McClenaghan welcome to try our newest 1.1.0 aws-s3-deploy pipe version. We introduced preexecution scripts in the pipe. The idea is the following: you pass the filepath like in the example Readme https://bitbucket.org/atlassian/aws-s3-deploy/src/master/ script: - echo 'aws configure max_queue_size 500' >…

@Kush Saraiya exactly, you will firstly need to use example for upload, then one for deploy command usage. It is done to separate this functionality, because it can be too different and with different arguments. Cheers, Galyna

@Jason Harrison @Jonathan Duncan @roman_rakhmatullov we are reporting this to the appropriate team, thank you for the feedback!

@Reethu are you still having the issue? Unfortunately, I should announce that microsoft does not support this pipe anymore. Instead atlassian supports this instead. Please, use readme from here for more examples https://bitbucket.org/atlassian/azure-aks-deploy/src/master/ . If you're still having the issue, could you…

Also share the pipeline paty, how you use this pipe. Example: step: name: Push and Tag script: - pipe: atlassian/bitbucket-pipe-release:4.0.1 variables: DOCKERHUB_USERNAME: <dockerhub username> DOCKERHUB_PASSWORD: $DOCKERHUB_TOKEN_SECRET_VAR IMAGE: 'prod-image-of-something' services: - docker Regards, Galyna

@Mauricio Nicolás Quezada Valdivia let us understand your question clear. I have now 3 variants what you might want: - you have s3 bucket and have zip file there and want to update it? Then you can use aws s3 deploy pipe, but just with a simple zip file, but zip what you need before to the zip archive. - or you have zip…

@Po Lui could you please share your Full log? It is just warning that image is not found locally and it is downloaded after. Regards, Galyna

@Andrew McClenaghan yes, we are working on this pipe right now. We will update you with status in nearest weeks. Cheers, Galyna

@jamerquiroga we are sending 'text' field on our own, so I guess you should specify as MESSAGE variable 'build success'. This is actually strange, your pipeline looks valid. I tried this and succeeded in the case if $build_status var in pipeline has string type. Like $build_status=success or $build_status = 0. But pipeline…

@Mauricio Nicolás Quezada Valdivia yes, sure you can use aws-sam-deploy pipe for that. Check out readme https://bitbucket.org/atlassian/aws-sam-deploy/src/master/ If to go into detail of that readme and for example, you want to upload the code first from from serverless app folder, just use default examples without passing…

@Kostya Kostyushko yeap, you can use also kubectl official version, whatever is suitable for you In the future we may think about suppoorting output sharing from pipe execution, so that you can execute pipes sequentially passing output from previous execution

@Pavan Dronamraju I did not say it is not supported. To say if something is supported or not, we need more clear problem understanding If we talk about aws efs - we just do not have bitbucket PIPE like this. but you still can execute any code in bitbucket pipelines that is recognized by bash, including aws cli options,…

@Abhijeet Sutrave it depends on url you pass. Check typos or reachability of admin-testapp.scm.netpost . Also, please share with us the bitbucket pipeline of failing code, and desirably, the full log , so that we can discover the root cause Regards, Galyna

@Himanshu Thawait to create lambda function, it is not that pipe, for examples check out readme of aws-sam-deploy pipe https://bitbucket.org/atlassian/aws-sam-deploy/src/master/

@Anh Tran I guess, you also could use right now variables like this: S3_BUCKET: 'bucket/path' Regards, Galyna

@Andrew McClenaghan refactoring to Python in our infrastructure is caused by other reasons, but python is much more convenient for different parameters and config things, since we can allow more flexible data structures for variables to pass in the pipe. Like this you'd have the natural ability to make proper config for…

@Eric Fiegehen sure, there is a way, you can execute bash code according to your needs. But if it fails, why you'd like to push? It is not recommended, but you can check $status and exit 0 even if there are vulnerabilties and make the report in after-script or before. Also, if you have questions precisely about anchore,…

@ketan.v check out the page https://www.digitalocean.com/community/meetup_kits/getting-started-with-containers-and-kubernetes-a-digitalocean-workshop-kit and check out kubectl-run pipe readme to have nicer experience with kubectl in pipelines https://bitbucket.org/atlassian/kubectl-run/src/master/README.md Regards, Galyna

@Andrew McClenaghan also , if you want to make a contribution, feel free to do it. We are happy to see new contributors. Just follow contributing guide in the pipe and don't forget to make a changeset in the pr, that will provide pipe's version bump on merge. Also, take into account that we are going to refactor this pipe…

@Andrew McClenaghan I am the right person :) Thanks for raising this. Soon we are going to work on s3 to improve it and can think about additional parameters. I will include your question to the discussion and notify you once we release a new update. Regards, Galyna

@Abdul Rehman it would be nice to share more details about your case: pipeline code, logs of failure. Regards, Galyna

Hello! We will discuss this in the future update soon and will notify once it is released. Be aware that s3:// is necessary in the beginning of S3_BUCKET, but we can allow actually to deploy to specific location like you propose, I suppose this is what you'd like to have? Regards, Galyna

@Rajanikant Beero this is not error, we have the log message like this in every pipe when running. Please, share with us the full log of failure and will help us to understand the problem. If nothing more appears, reload the page and if then you don't see nothing more, run this step again. Regards, Galyna

@Douglas Kolpien try the next version of elasticbeanstalk pipe 0.8.0, we've introduced new S3_KEY variable How this works: S3_KEY: 'prod/my-application' The result of this will be 'prod/my-application.zip' and this s3 key will be taken when registering application version from this s3 bucket path. Regards, Galyna

@Mahesh kumar could you please share the part of script where you execute the pipe? It is hard to understand root cause, because there can be not only one reason of fail. Check if you don't make a typo in application name etc. Regards, Galyna