Hi Everyone,
I'm new to CI/CD and I created a pipeline in bitbucket to push the built Maven application to an AWS S3 bucket.
The issue I need assistance resolving is constantly having to manually update the "ZIP_FILE" file path to the jar file that gets generated with a unique version number.
ZIP_FILE: '/opt/atlassian/pipelines/agent/build/target/application-0.1.0-SNAPSHOT.jar'
File "bitbucket-pipeline.yml"
image: maven:3.6.1
pipelines:
branches:
master:
- step:
name: "PRODUCTION pipeline"
caches:
- maven
deployment: production
script:
- echo "PRODUCTION SCRIPT RUNNING."
develop:
- step:
name: "Staging pipeline"
caches:
- maven
deployment: staging
script:
- echo "STAGING SCRIPT RUNNING."
- mvn -B verify
- mvn install
- mvn clean package spring-boot:repackage
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.6
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION
APPLICATION_NAME: 'application'
ENVIRONMENT_NAME: 'application-staging'
ZIP_FILE: '/opt/atlassian/pipelines/agent/build/target/application-0.1.0-SNAPSHOT.jar'
Any suggestions and questions are welcomed,
Thank you!
@Luis Ramirez Briceño wildcard is not supported in aws elasticbeanstalk, but you can find your file via bash line:
FILE=$(ls /opt/atlassian/pipelines/agent/build/target/*.jar | tail -n 1)
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.