HomeMesosphereNo notifications. 4 unresolved issues.

Find marathon manifest path
ClosedAll Users

Authored by timcharper on Sep 15 2017, 1:50 AM.

Details

Summary

The previous method for finding the manifest would only work for uber-jars

Test Plan

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.
timcharper created this revision.Sep 15 2017, 1:50 AM
timcharper updated this revision to Diff 4278.Sep 15 2017, 1:52 AM
timcharper added 1 JIRA issue(s): MARATHON-7765.

jira issue

jenkins requested changes to this revision.Sep 15 2017, 1:54 AM
This revision now requires changes to proceed.Sep 15 2017, 1:54 AM
ichernetsky accepted this revision.Sep 15 2017, 1:57 AM
jenkins accepted this revision.Sep 15 2017, 2:09 AM
This revision is now accepted and ready to land.Sep 15 2017, 2:09 AM
✔ Build of 4277 completed jenkins-public-marathon-phabricator-1019.

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"

\\ ٩( ᐛ )و //

jenkins requested changes to this revision.Sep 15 2017, 2:10 AM
This revision now requires changes to proceed.Sep 15 2017, 2:10 AM

Error message:

Stage Compile and Test failed.

(๑′°︿°๑)

jenkins accepted this revision.Sep 18 2017, 5:27 PM
This revision is now accepted and ready to land.Sep 18 2017, 5:27 PM
✔ Build of 4278 completed jenkins-public-marathon-phabricator-1026.

You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:

\\ ٩( ᐛ )و //

meln1k added a subscriber: meln1k.Sep 19 2017, 6:06 PM
meln1k added inline comments.
src/main/scala/mesosphere/marathon/BuildInfo.scala
30

I might be wrong, but shouldn't we close the input stream after use?

unterstein accepted this revision.Sep 19 2017, 6:39 PM

we should double check Nikita's question. If close needed, we should close it, Lgtm otherwise. Go for merge if question resolved 🎉

timcharper added inline comments.Sep 20 2017, 5:17 PM
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.

This revision was automatically updated to reflect the committed changes.