nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error while deploying maven project to AWS Elastic Beanstalk

AWS Developer

Pipeline code:
DEV-Content-Processor-Beanstalk:
- step:
name: mvn build
image: maven:3.6.1
script:
- cd ContentProcessor
- mvn -B clean install
artifacts:
- target/*.jar

- step:
name: Update Lambda code
script:
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.6
variables:
AWS_ACCESS_KEY_ID: ${AWS_DEV_ACCESS_KEY_ID}
AWS_SECRET_ACCESS_KEY: ${AWS_DEV_SECRET_KEY}
AWS_DEFAULT_REGION: 'us-east-1'
APPLICATION_NAME: 'ContentProcessor-app'
ENVIRONMENT_NAME: 'ContentProcessor-env'
ZIP_FILE: 'target/ContentProcessor-0.0.1-SNAPSHOT.jar'

Error:
Unable to find image 'bitbucketpipelines/aws-elasticbeanstalk-deploy:0.6.6@sha256:dfeaa669b57ad7943a7aeabe741caa608a287818f19b24aec7f57c' locally
docker.io/bitbucketpipelines/aws-elasticbeanstalk-deploy@sha256:dfeaa669b57ad7943a7aeabe741caa608a287818f19b24aec7f57c: Pulling from bitbucketpipelines/aws-elasticbeanstalk-deploy
5d20c808ce19: Pulling fs layer
...
96d448f11450: Pull complete
a36d5e990e62: Pull complete
Digest: sha256:dfeaa669b57ad7943a7aeabe741caa608a287818f19b24aec7f57c
Status: Downloaded newer image for bitbucketpipelines/aws-elasticbeanstalk-deploy@sha256:dfeaa669b57ad7943a7aeabe741caa608a287818f19b24aec7f57c
INFO: The application source bundle doesn't have a known file extension (zip, jar or war). This might cause some issues.
INFO: Uploading to s3 bucket: ContentProcessor-elasticbeanstalk-deployment...
The user-provided path target/ContentProcessor-0.0.1-SNAPSHOT.jar does not exist.

Issue: Deployment failed.

Please let me know, What is the issue here? Is there a way to troubleshoot it in local.?

Accepted answers

Caroline R

Hi, @AWS Developer! Welcome to the community!

By the error message you shared in your description, it looks like the file you are trying to upload doesn’t exist - target/ContentProcessor-0.0.1-SNAPSHOT.jar

Could you please verify that? You can first check if the file exists or not in the Update Lambda code step before calling the Pipe:

- step:
name: Update Lambda code
script:
- ls -lrt target
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.6
variables:
AWS_ACCESS_KEY_ID: ${AWS_DEV_ACCESS_KEY_ID}
AWS_SECRET_ACCESS_KEY: ${AWS_DEV_SECRET_KEY}
AWS_DEFAULT_REGION: 'us-east-1'
APPLICATION_NAME: 'ContentProcessor-app'
ENVIRONMENT_NAME: 'ContentProcessor-env'
ZIP_FILE: 'target/ContentProcessor-0.0.1-SNAPSHOT.jar'

Please feel free to share any additional questions regarding this case.

Kind regards,
Caroline

All comments

Caroline R

Hi, @AWS Developer! Welcome to the community!

By the error message you shared in your description, it looks like the file you are trying to upload doesn’t exist - target/ContentProcessor-0.0.1-SNAPSHOT.jar

Could you please verify that? You can first check if the file exists or not in the Update Lambda code step before calling the Pipe:

- step:
name: Update Lambda code
script:
- ls -lrt target
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.6
variables:
AWS_ACCESS_KEY_ID: ${AWS_DEV_ACCESS_KEY_ID}
AWS_SECRET_ACCESS_KEY: ${AWS_DEV_SECRET_KEY}
AWS_DEFAULT_REGION: 'us-east-1'
APPLICATION_NAME: 'ContentProcessor-app'
ENVIRONMENT_NAME: 'ContentProcessor-env'
ZIP_FILE: 'target/ContentProcessor-0.0.1-SNAPSHOT.jar'

Please feel free to share any additional questions regarding this case.

Kind regards,
Caroline

AWS Developer

Thank you for looking into this issue, Caroline.

Please find the logs for ls -lrt target

+ ls -lrt target
ls: cannot access target: No such file or directory

I verified that, Jar was created during the step1(mvn build), but it was missing, during step2(deployment to Beanstalk). If I run both "mvn build" and deployment commands in the same step, then it works fine.

I need to execute build and deployment in separate steps.

- Can you please advice, what could be the issue with this pipeline?

mvn build log:

mvn -B clean install

...

[INFO] Installing /opt/atlassian/pipelines/agent/build/processor/target/ContentProcessor-0.0.1.jar to /root/.m2/repository/com/myapp/processor/0.0.1/ContentProcessor-0.0.1.jar
[INFO] Installing /opt/atlassian/pipelines/agent/build/processor/pom.xml to /root/.m2/repository/com/myapp/processor/0.0.1/ContentProcessor-0.0.1.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 36.346 s

Build teardown
You already have a 'maven' cache so we won't create it again
Cache "maven": Skipping upload for existing cache
Searching for files matching artifact pattern target/*
Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4
Finished scanning for test reports. Found 0 test report files.
Merged test suites, total number tests is 0, with 0 failures and 0 errors.

deployment log:
Status: Downloaded newer image for bitbucketpipelines/aws-elasticbeanstalk-deploy@sha256:dfe2e669b57ad7943a7aeabe741c43db57c863aa608a287818f19b24aec7f57c
INFO: The application source bundle doesn't have a known file extension (zip, jar or war). This might cause some issues.
INFO: Uploading to s3 bucket: test-bitbucket-ebs...
The user-provided path target/ContentProcessor-0.0.1.jar does not exist.

updated pipeline:

DEV-ContentProcessor-Beanstalk:
- step:
name: mvn build
image: maven:3.6.1
caches:
- maven
script:
- cd processor
- mvn -B clean install
artifacts:
- target/*
- step:
name: Update Beanstalk code
script:
- cd processor
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.6
variables:
AWS_ACCESS_KEY_ID: ${AWS_DEV_ACCESS_KEY_ID}
AWS_SECRET_ACCESS_KEY: ${AWS_DEV_SECRET_KEY}
AWS_DEFAULT_REGION: 'us-east-1'
APPLICATION_NAME: 'ContentProcessor-app'
ENVIRONMENT_NAME: 'ContentProcessor-env'
ZIP_FILE: 'target/ContentProcessor-0.0.1.jar'
S3_BUCKET: ${AWS_DEV_S3_BUCKET_CONTENT}

Caroline R

Hi, @AWS Developer!

Thank you for getting back to me and sharing the additional information.

As per the teardown log, it looks like no file was uploaded as artifacts as there is no matching file. It searches for the files but doesn’t upload anything in the artifacts because it doesn’t find anything:

Searching for files matching artifact pattern target/*
Finished scanning for test reports. Found 0 test report files.

In this case, could you please add ls -lrt in the first step as well and share this here?

script:
- cd ContentProcessor
- mvn -B clean install
- ls -lrt target

Thank you. Looking forward to hearing from you.

Kind regards,
Caroline

AWS Developer

mvn -B clean install 12s

ls -lrt target <1s
+ ls -lrt target
total 53968
drwxrwxrwx 3 root root 4096 Sep 29 07:30 generated-sources
drwxrwxrwx 3 root root 4096 Sep 29 07:30 maven-status
drwxrwxrwx 3 root root 4096 Sep 29 07:30 classes
drwxrwxrwx 3 root root 4096 Sep 29 07:30 generated-test-sources
drwxrwxrwx 3 root root 4096 Sep 29 07:30 test-classes
drwxrwxrwx 2 root root 4096 Sep 29 07:31 maven-archiver
-rw-rw-rw- 1 root root 343070 Sep 29 07:31 ContentProcessor-0.0.1.jar.original
-rw-rw-rw- 1 root root 54892065 Sep 29 07:31 ContentProcessor-0.0.1.jar

Build teardown <1s
You already have a 'maven' cache so we won't create it again
Cache "maven": Skipping upload for existing cache
Searching for files matching artifact pattern target/*
Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4
Finished scanning for test reports. Found 0 test report files.
Merged test suites, total number tests is 0, with 0 failures and 0 errors.

Jar file was present at the end of step1(maven build), but it is missing in step 2(deployment)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-pipelines