Oleksandr Kyrdan Atlassian Team

Hi @msk134 , Thank you for your question! It's a good case for the Bitbucket Pipelines Deployments.

Hi @robdebert , Thank you for your question! Looks like your LOCAL_PATH should include build directory: LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/build' Have tested this case and the ftp-deploy pipe uploads only files from the directory.

Hi @pascal_schroeer , thank you for your question! In your case, artifacts will help you to share generated pdf-file with the next steps: image: dme26/latex-builder:latest pipelines: default: - step: name: Build the pdf script: - pdflatex --shell-escape Test.tex artifacts: - Test.pdf - step: name: Upload to Bitbucket…

Hi @Jeffrey Schwartz , welcome to fork the aws-sam-deploy pipe and provide the PR with your ideas.

Hi @nikos_triantafyllou , Do you mean add support INVALIDATE_CACHE in the aws-cloudfront-invalidate pipe? It would be nice if you provide us with more details about your case. Thank you! 

Hi @Cerruti Giorgio , We've released a new atlassian/aws-ecs-deploy:1.3.0 version with support for the FORCE_NEW_DEPLOYMENT variable. 

Hi @Ben Calnan , Could you provide us with more details about your case?

Hi @naoko rikiyama , Thank you for your question! It's a good practice to update the pipe's version to the newest one periodically. New versions of the pipe could have updates, improvements, new features, or bug-fix. All changes to the pipe are stored in the pipe's changelog. We follow the versioning rules provided…

Hi @ILI.DIGITAL AG , Thank your for your question! Could you provide us with your pipeline configuration and describe it, please?

Hi @asmaa_mahmoud , could you provide us with more details about your build?

@yosser.mahfoudh if you don't want to run your pipeline automatically you could setup custom instead: custom - Defines pipelines that can only be triggered manually or scheduled from the Bitbucket Cloud interface. pipelines: custom: # Pipelines that are triggered manually sonar: # The name that is displayed in the list in…

@yosser.mahfoudh as usual it should be path to the build directory. In your special case it could be: pipelines: default: - step: script: - <your build logic> artifacts: - .m2/repository/mass/masster/2.2.1.9957 But make sure that your follow build versioning.

Hi @yosser.mahfoudh , to run automatically pipeline setup steps in the default section of the pipeline. - echo 'Hello pipes!'pipelines: default: - step: name: Build and test script:<br> More details provided in the Configure bitbucket-pipelines.yml guide.

Hi @yosser.mahfoudh , Thank you for your question! Just, add to your build step a keyword `artifacts`. Also, we have a good example for Java project. More details you could find following the Use artifacts in steps guide.

Hi @Kim Metso , Thank you for your question! Let's try command: vendor/bin/phpunit --log-junit=test-reports/report.xml more details provided in the Test reporting in Pipelines guide.

Hi @Kunal Gupta , Thank you for your question! According to the Docker docs: A tag name must be valid ASCII and may contain lowercase and uppercase letters, digits, underscores, periods and dashes. A tag name may not start with a period or a dash and may contain a maximum of 128 characters.

Hi @Cerruti Giorgio , thank you for your feedback! We'll investigate this feature and notify you.

Hi @Zuberu Abdulrahman , Thank you for your question! Test reporting will be automatically enabled in your pipeline when it detects xUnit/JUnit compatible test results which include a fail. For more details, please, follow the Test reporting in Pipelines guide.

Hi @Abryan Manalansang , Thank you for your question! Have you upload the Application Revision before deploy? Please follow Details section in the README for aws-code-deploy pipe.

Hi @ginukagpr , you could follow a workflow in our .Net example . For STEP Deploy to Production use aws-elasticbeanstalk-deploy pipe , if it's your case: - step: name: Deploy to Production deployment: Production trigger: manual script: - pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.6 variables: AWS_ACCESS_KEY_ID:…

Hi @v_ivanidi , Thank you for your question! Try to use the next pipeline: image: php:7.3 pipelines: default: - step: name: Test image: phpunit/phpunit script: - docker run -v $(pwd):/app --rm phpunit/phpunit test services: - docker - step: name: Lint script: - find . -name '*.php' -exec php -l {} \;

Hi @Antoine Drabble , Thank you for your question! The bitbucket-pipelines.yml file defines your Pipelines builds configuration and has some structure. The pipeline configuration file can have multiple sections identified by particular keywords. Please, follow the guide How to configure bitbucket-pipelines.yml.

Hi @Pra Learn , we have released fixed version of the bitbucket-upload-file:0.3.1 pipe.

Hi @nazia_akhtar , Thank you for your question! You can add it with the next command before using jq: apt-get install -y jq

Hi @Pra Learn , yep, we'll fix this and notify you! Thank you for your feedback!

Hi @cheralathann , it depends on usage conditions of your hosting. Are they provide such option for you? Have you tried to connect to the hosting manually?

Hi @nicolas.fernandez , you can run pipe locally as a general Docker container: docker run \ -e COLLECTIONPATH=$(cat files/goodCollection.json) \ -v $(pwd):$(pwd) \ -w $(pwd) \ xxxx/xxxxx:1.0.47 More details you can find in the Step 3 - Configure the Dockerfile of the Write a pipe for Bitbucket Pipelines guide.

Hi @Nir Haimov @Vladislav Babin , new bitbucket-upload-file pipe's version that supports multiple files released: script: - pipe: atlassian/bitbucket-upload-file:0.2.0 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD FILENAME: 'target/select2*.jar' Welcome to share your…

Hi @Abryan Manalansang , the best way to provide different deployments is set up Bitbucket Deployments . Cheers, Alex

Hi @Nuria Ortuno Martinez , Thank your for your feedback!