Halyna Berezovska Atlassian Team

@Sohel R Matwakureshi please, describe us the requirement fully just to be on the same page. What do you'd like to do in the pipeline and do with *.war file, so you can choose the actions for the pipeline. Cheers, Galyna

@koen_pijnenburg looks like you need chmod -R <permissions_number-or-symbols> <folder> to enable access in all files in the directory 'output'. Cheers, Galyna

@Richard_Campen thank you for the question. Can you share more output from runserver since you run it with verbosity 3, in the case without nohup using? Perhaps, this way we will be able to help Cheers, Galyna

@Frans Irgolitsch you are right, this solution with ftps needs to be investigated and tested. However right now it is also good idea for custom pipe. You can explore how easily you can write a new one Creating a custom pipe . Contact us in the case of questions!

@mabakr I got your point. As for the user prompt, right now you cannot use it for part of a pipeline. I guess, this is because pipeline on each of steps should be independent of others, otherwise it getting more complex and takes dependencies from other stuff. To avoid this, I guess, the most proper solution currently is…

@Adam Woloszyn to answer on your question, I need to know, what exactly has not been shown up. For example, secured variables like KEY_FILE , they are shown in Deployments section variables, but masked. And in the logs they are not shown.

@Adam Woloszyn , could you provide the full log, please? I don't see json parsed here related, only bash This solution I proposed for local testing KEY_FILE: $(cat gcloud-api-key.json'), but you can still refer to confluence docs I mentioned to set environment variable right in the pipeline (Deployments section, Repository…

Hello @JUSTIN G VARGHESE As an option you could try AWS CLoudformation Deploy Pipe . This pipe should process RDS configuration. Consider also Amazon docs https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-rds-database-instance.html

Hello @Garry Dias , thanks for using pipelines. I suspect, definitions cannot work this way, I could not find example without the image mentioning. Definitions documentation . But if I got your point, the feature you want, is described here…

Hello, @Adam_Woloszyn , you can recheck environment variable KEY_FILE. This should base64 encoded string , not filename. So the setting would be KEY_FILE: $(cat gcloud-api-key.json'). This json file should contain proper base64 content and This can be a tricky part, but we have a guide for this…

@Yadvendra Singh , thanks for using our pipe. Looks like layers should be a list of strings, not the list of dictionaries (by the doc it looks like response body format). Following the doc AWS Update Function Configuration API it can be seen that CodeSize is mentioned a level upper in --cli-input-json setting. As a result…

Hello, @Adam Woloszyn , you can recheck environment variable KEY_FILE. This should base64 encoded string , not filename. So the setting would be KEY_FILE: $(cat gcloud-api-key.json'). This json file should contain proper base64 content and This can be a tricky part, but we have a guide for this…

@Sai Devulapalli , the most suitable pipe, I guess, is https://bitbucket.org/atlassian/aws-sam-deploy/src/master/ - wrapping over cloudformation deploy for lambda. I guess, you need this to deploy it for now

@davidstanton we are looking for the possibility to improve the current pipe, not creating the new one. Our own forking could end up in too many similar repos. But as current solution you can fork it on your own and use it for now. However, I will notify you once the solution for pipe improvement will be aproved and…

@davidstanton yes, you are right, if you want to use rsync exactly, right now you need to fork the pipe and replace there by rsync. As for using this as a pipe, we should investigate this question. Thanks for the question!

Hello, @Sai Devulapalli ! Can you say, which pipe are you using? There is a specific pipe for deploying to serverless AWS and more generic pipe platform-independent. If you need specifically AWS, first choice would be good for you to try.

Hi, @Ankit Jangid ! Thanks for the question. Azure deploy pipe is working right now for one VM only. Actually, this is a great idea for custom pipe! See how easily to writing custom pipes at https://bitbucket.org/blog/build-flexible-ci-cd-pipelines-with-custom-pipes

Hi, @mabakr ! Let me ask a question to understand we are on the same page. I see, you want environment variable where you could say which version to deploy to production and apply this to only a part of a pipeline (not a part of pipe)? Environment variables choice can be one of : repository variables and deployments(…

@Nir Haimov this feature will be included in the next pipe releases. Thank you

Yes, you can do like that with curl. But I guess right now it is not supported within our pipe. Since we are not using bash, but python, it can not be used like that. But I'll propose some improvements for this. I notify once it is approved

@Nir Haimov sure, thank you for giving such an idea

@Nir Haimov , I believe, this corrected command should help you docker run --volume .... --env ..... \ --env=FILENAME="/opt/atlassian/pipelines/agent/build/target/select2-1.3.3.jar" ... Unfortunately, we do not support paths by pattern like you likely wanted: /opt/atlassian/pipelines/agent/build/target/select2-*.jar Right…

Hello,@Nir Haimov , we do not support such declaration of FILENAME variable, since it is only a part of curl command and we do specific checks for the file existence. So, FILENAME should be the local relative / absolute path to the file. For example, "target/myProject.jar" locating at…

Thanks for the reporting the case! We will investigate your issue as soon as we can. At the first look it seems to be worked with yml, but perhaps, there is a separate issue

@Jay Seletz I believe, the updated pipe 4.1.5 can solve this issue, welcome to try out.

Hello, @Erik_Tallang , npm-publish pipe is updated to support your needs, welcome to have a look and try out. Thank you for reporting the case! We are looking forward to seeing the feedback