-
Notifications
You must be signed in to change notification settings - Fork 52
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.
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
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #336 +/- ##
=========================================
Coverage 24.04% 24.04%
Complexity 542 542
=========================================
Files 169 169
Lines 8895 8895
Branches 1230 1230
=========================================
Hits 2139 2139
Misses 6543 6543
Partials 213 213
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
landonreed
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is #321 still a problem? I expect that it probably is.
|
It seems to have worked this time: https://travis-ci.org/github/ibi-group/datatools-server/builds/720900545#L11247. Maybe merge this and if the problem happens again, I'll investigate further? |
binh-dam-ibigroup
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am neutral regarding this and the last CI build went well, so I'm going ahead and pre-approve.
|
I don't think #321 is fixed. It only will fail on merges to master, but here's the travis snippet that causes the issue: The issue is that there are multiple jars that it creates during CI and that it tries to copy all of them to a single filename. |
|
See proposed code that fixes #321. |
.travis.yml
Outdated
| - ls target/*.jar | ||
| # Copy packaged jar over to deploy dir. | ||
| - cp target/dt-*.jar deploy/ | ||
| # get first jar file and copy it into a new file that adds the current branch name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but I think this comment could be expanded a bit:
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 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).
landonreed
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but I think the comment needs to say a bit more (see comment).
|
🎉 This PR is included in version 3.8.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Checklist
devbefore they can be merged tomaster)Description
This PR brings back the uploading of a jar with the name of the latest branch. The e2e tests in datatools-ui depend on downloading the latest jar from a particular branch name.