Halyna Berezovska Atlassian Team

@danbrellis I am glad you figured this out, thanks!

@Sona Harutyunyan hello! right now email-notify pipe does not support two-factor. Because, For example, google has another procedure of authenticating and sending email. Having heterogeneous authorization backend in many vendors sending email, it is not flexible to support just some authorization approach. For such cases…

@martinma you can put your arguments to the Kubectl args. KUBECTL_ARGS: - "--dry-run=server" Regards, Galyna

@danbrellis As in the pipe we cannot see the traceback, it would be useful to dive in to appropriate AWS cloudformation stack or if you don't have one, look into Environment logs. If you go to the appropriate environment dashboard , you can see the bunch of logs at the bottom of the page. If you find the error you think it…

@zh_focus check up with your smtp port on server. You can also discover the problem running pipe with DEBUG: 'true' variable. You can also share the latest log with us. Regards, Galyna

Can you share also with us requirements in your lib in setup.py? Specifically, pyodbc, what version is it?

@Daniel Mossie what image do you use for this step (or for all steps)? python:3.8? I mean, not in google-app-engine (however I will check it out) It says that there is no sql installed (fully or properly).

Or you can directly use gcloud tool, and simply follow docs https://cloud.google.com/compute/docs/instances/stop-start-instance#gcloud I guess, this is much cleaner way to properly start-stop instance

Regarding your questions: 1) is it possible to launch some shell scripts that are in the repo on a remote server >> yes, it is possible right now, you pipe ssh-run , if it is that what you want https://bitbucket.org/atlassian/ssh-run/src/master/ 2) is it possible to turn build machines on and off in google cloud engine >>…

@[deleted] could you please share this in formatted string just as you write in your pipeline , with identation etc.? I tried to order it, but did not succeed. Thanks Cheers, Galyna

@James St-Pierre this means it failed to deploy your version to cloud. If to look more, you probably can see the following string : "See more details stack ....<stack_link>". Is that your case? It can be that updating environment some deploy could fail depending on your setup permissions etc. Here we'd like to see more…

@Klemenn thanks for explaining the case . I have debugged your case on our new refactored pipe, it works. I'll notify you about official release. I left more details (It is unlikely to provide them here) in the ticket in jira you created https://getsupport.atlassian.com/browse/BBS-150719 Tell here your feedback, please.…

Hello, @Klemenn I am debugging now our scp-deploy pipe which is refactored to new one and trying to understand your case. So can you specify in more detail your case, that works for you? What precisely you want to do? Do you want to ssh through proxy (ONE host)? cannot see why you have two different hosts in proxy command.…

@Sergey Mokhov try to go with finalImageName=pfpes-web // name of your repository docker build -t ${finalImageName} THe point is , we are getting registry address in our pipe ourselves. We think it should make things simpler: 1. By your credentials pipe gets token from aws 2. Using token pipe discovers your registry and…

@Sergey Mokhov check the details I pointed to : - if you name the image pfpes-web, the repository, that contains your images in aws should be named pfpes-web. - how you build your docker image in your scripts/build-docker-image.sh script? These details matters, I have tried that and had the same error and then I fixed this…

@Sergey Mokhov I just jave tried our pipe. I am not sure how you setup your infra in AWS ECR, so just in case ensure that you take into account following details, that I did and it worked for me (firstly it also was failing with the same error you provided): - your IMAGE_NAME should equal to repository name you created in…

@Saurabh Singh no, you cannot do it, this would be too complex pipe and would be hard to understand what actually succeeded and how. I propose you to use you command in a separate step. You can also define those steps as parallel to save time (but be aware that perhaps this will require more pipeline resources like memory…

@Sergey Mokhov I guess you want something like changing,e.g feature/jira-story-333 to feature-jira-story-333. You can define another local variable to substisute, BUT with proper escaping before executing pipe, like script: - deploy_tag="${BITBUCKET_BRANCH/\//-}" - pipe: atlassian/aws-ecr-push-image:1.2.0 variables: ....…

@danbrellis hello! Thanks for using the pipe. If this works locally for you, then we would like to see logs of pipeline's failing indeed , so that we know where is the issue root cause - aws, wrong config or our side. For now I can only say that AWS has similar threads related to this error, but let's see the logs first.…

@Klemenn you may have problems to put ssh config, and if you have , I think we may talk about supporting custom ssh config in the pipe.

@Klemenn hello! If you want to run specifically scp-deploy (scp-deploy should be easier), try EXTRA_ARGS: '-v -o ProxyCommand=\"ssh ubuntu@bastion.example.com nc 172.31.1.2 22\"' or EXTRA_ARGS: '-o ProxyCommand="ssh user@host"' or if it does not work for you, you can actually solve your case in more simple way putting this…

@[deleted] exactly. Contact us if you want to raise more questions. Cheers, Galyna

@[deleted] it should be found inside current working dir in the pipeline. How you're looking for it? Try $(cat build_usage.txt) . I executed this and succeeded. Also, it depends on what should be done after. Now the pipe just outputs this to given file and to stdout, both. Regards, Galyna

@Aditya Ekbote hello! try our latest release 0.8.0. If you want to enable multiple sites or specific site, use option MULTI_SITES_CONFIG:* Deploying multiple sites at once script: - pipe: atlassian/firebase-deploy:0.8.0 variables: FIREBASE_TOKEN: $FIREBASE_TOKEN PROJECT_ID: 'myAwesomeProject' MESSAGE: 'Deploying…

@Jason Harrison oh sorry!

Also , Is there a list with all of these? >> We support apply command separately and any other command also in this pipe. For that you just pass , for example KUBECTL_COMMAND: 'autoscale' and put proper KUBECTL_ARGS ( check out our docs, section Variables -…

@Brad Vrabete yes, docs are saying that `-k` flag is about kustomization feature and as I understand, this is absolutely different from what `-f` does. Here I just want to understand your use case, what you exactly want to do with `apply` command, because as I see from the docs, it can be applied for different purposes.…

@Brad Vrabete hello! Can you tell , if you use our pipe as a way to apply kustomization? Like kubectly apply -k <kustomzation dir> ? If yes, this file can have other format and we may also support this in the future. See more in https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/

@Renato Prosofsky bitbucket pipelines allow to use any image available in dockerhub and execute bash scripts in steps. I see there are some android emulator and android sdk images, you can check them out. Regards, Galyna

@Amit Edelshtein there are two possible reasons: - api endpoint you're using is not allowed to use with proxy - user is not recognized when going through proxy. check user's permissions. Also, what authentication are you using? Check out how reports sub endpoints are used in one of our pipes…