Releases: criteo-forks/marathon
Releases · criteo-forks/marathon
v1.6.576-criteo1: Fix tests for networkBandwidth naming
Search&Replace went wrong
v1.6.574-criteo4: Fix issues with archive naming
Due to lack of depth in the git tree, sbt was unable to compute the correct archive name
v1.6.549-criteo2: Correct marathon jar package filename pattern
The package does not necessarily have the prefix 'marathon-'.
v1.5.6-criteo3: Merge pull request #4 from criteo-forks/partialUpdate
Make sure networkBandwidth can be specified in all scenarii
v1.5.6-criteo2: Merge pull request #3 from clems4ever/bandwidth-control
Implement network bandwidth control in Marathon for Criteo
v1.5.6-test-bandwidth-control
Add network bandwidth in RAML files
v1.5.6-criteo1: Fix patch_version.sh to remove v from tag when building Marathon
Without this fix, Marathon does not detect the version correctly (its expects to have no v in the version you can find in META-INF/MANIFEST.MF in marathon jar). This triggers a migration of app that is failing...
v1.5.5-criteo1: Fixes v1.5 migration issue with args only apps
Protobuf-to-RAML conversion introduced a regression in the interpretation of CommandInfo's content (args vs cmd), which was already properly handled in AppDefinition.mergeFromProto. This patch fixes the issue reported as MARATHON-8015 JIRA: MESOS-866
1.5.1-criteo5: Correct publication
Change-Id: I627ff296e833c7986a394af44e164753ddc31c3f
1.5.1-criteo3: Remove testing from travis
Tests on travis have not passed in more than a month. Mesosphere seems to use jenkins. I am deactivating it for the time being. Change-Id: I4572162e9b569aa2d4448697ed80163fa41f6097