Skip to content

Upload branch jar again #336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
evansiroky merged 5 commits into from
Sep 2, 2020
Merged

Upload branch jar again #336

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a2e9d6c
Revert "ci(travis): remove clean branch cp"
evansiroky Aug 25, 2020
e11b995
Revert "ci(travis): remove creation of branch-named jar"
evansiroky Aug 25, 2020
47ee28a
ci: resolve to first jar file during jar deployment
evansiroky Aug 31, 2020
5b55041
ci: enclose bash variable with quote
evansiroky Aug 31, 2020
46f3919
ci: elaborate a comment a bit
evansiroky Sep 2, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .travis.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,12 +79,23 @@ after_success:
fi
fi
before_deploy:
# get branch name of current branch for use in jar name: https://graysonkoonce.com/getting-the-current-branch-name-during-a-pull-request-in-travis-ci/
- export BRANCH=$(if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then echo $TRAVIS_BRANCH; else echo $TRAVIS_PULL_REQUEST_BRANCH; fi)
# Replace forward slashes with underscores in branch name.
- export BRANCH_CLEAN=${BRANCH//\//_}
# Create directory that will contain artifacts to deploy to s3.
- mkdir deploy
# Display contents of target directory (for logging purposes only).
- ls target/*.jar
# Copy packaged jar over to deploy dir.
- cp target/dt-*.jar deploy/
# Get the first jar file and copy it into a new file that adds the current branch name. During a
# merge to master, there are multiple jar files produced, but they're each effectively the same
# code (there may be slight differences in the version shown in the `pom.xml`, but that's not
# important for the purposes of creating this "latest branch" jar).
- ALL_JARS=(target/dt-*.jar)
- FIRST_JAR="${ALL_JARS[0]}"
- cp "$FIRST_JAR" "deploy/dt-latest-$BRANCH_CLEAN.jar"
deploy:
provider: s3
skip_cleanup: true
Expand Down