The previous method for finding the manifest would only work for uber-jars
Details
- Reviewers
jenkins ichernetsky unterstein - Commits
- rMARATHON982704446473: Find marathon manifest path
- JIRA Issues
- JIRA MARATHON-7765 /v2/info returns wrong version
build marathon, check that /v2/info endpoint returns correct marathon version
Diff Detail
- Repository
- rMARATHON marathon
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:
"url": "https://s3.amazonaws.com/downloads.mesosphere.io/marathon/snapshots/marathon-1.5.0-74-g906ceee.tgz", "sha1": "9a29b5c051da36a5638d558a39382232719ddf8d"
\\ ٩( ᐛ )و //
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:
\\ ٩( ᐛ )و //
src/main/scala/mesosphere/marathon/BuildInfo.scala | ||
---|---|---|
30 | I might be wrong, but shouldn't we close the input stream after use? |
we should double check Nikita's question. If close needed, we should close it, Lgtm otherwise. Go for merge if question resolved 🎉
src/main/scala/mesosphere/marathon/BuildInfo.scala | ||
---|---|---|
30 | Great catch! I was in the mode of "fix the bug at hand", and didn't notice this was broken before. I'll submit another patch. |
I might be wrong, but shouldn't we close the input stream after use?