Skip to content
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

0.6.1 release #1201

Closed
wants to merge 9 commits into from
Closed

0.6.1 release #1201

wants to merge 9 commits into from

Conversation

bamarni
Copy link
Contributor

@bamarni bamarni commented Apr 4, 2018

No description provided.

bamarni and others added 7 commits March 6, 2018 20:35
This function is called when reading a password or service account key
file.

It is common to have a trailing newline in files. In the case of a
private key it doesn't harm but for passwords these trailing
whitespace(s) shouldn't be considered as part of the credentials.

Fixes dcos#1167
According to PyInstaller requirements :

  PyInstaller builds apps that are compatible with the Mac OS X release
  in which you run it, and following releases.

Building from an old enough Mac makes sure we support all versions
onwards. The latest Yosemite version was released 3 years ago, so it
already brings a wide range of supported MacOS versions for the CLI.

The Jenkins node has Python 3.5.5 compiled with OpenSSL 1.0.2n.
Previously, there were problems with the way patterns were matched for
the task ID when calling `task exec`. Specifically, it didn't follow the
semantics indicated in the help string for (1) matching regular
expressions and (2) matching any substring within the ID, not just the
prefix of the ID.

The reason we did not adhere to these semantics is because we were
trying to match the exact semantics of `docker exec`, which only allows
prefix matching, not arbitrary regex or 'contains()' like semantics for
pattern matching the ID.

With this change, we have decided to break from the docker semantics and
use the default pattern matching semantics provided by the dcos-cli
library command for pattern matching task ids.

Unfortunately, there is a bug in this library, and regular expressions
are not supported! However, arbitrary substring pattern mathing is.

This commit, therefore, updates the semantics of `task exec` to adhere
to 'contains()' like smeantics within the task ID for the 'task_id'
parameter passed to it, but does not yet support proper regular
expression pattern matching.

A subsequent commit will be added to fix regex matching in library call
implementing task ID pattern matching.
Don't run `pip install --upgrade pip` on Windows, it started to fail in
our Jenkins node and this is not the right command.

https://jira.mesosphere.com/browse/DCOS_OSS-2332
https://pip.pypa.io/en/stable/installing/#upgrading-pip
pypa/pip#1299
This makes it more precise as it accepts Unix file pattern wildcards
instead of regexes.
@bamarni
Copy link
Contributor Author

bamarni commented Apr 4, 2018

run all integration tests

armandgrillet
armandgrillet previously approved these changes Apr 5, 2018
@bamarni
Copy link
Contributor Author

bamarni commented Apr 5, 2018

I will include #1202 before merging.

This re-arranges our Jenkinsfiles now that we have the Go project.

The relevant status checks have been added to Jenkins :

- all-go-binaries
- linux-go-tests
- linux-integration-tests
- linux-python-binary
- mac-integration-tests
- mac-python-binary
- windows-integration-tests
- windows-python-binary
Depending on the user setup, they might contain an incorrect scheme.
This is because Cosmos relies in the scheme used to query admin router.
If a CLI is configured to use HTTPS but a load balancer sits in front
of admin router and does TLS termination, these URLs will use the HTTP
scheme.

Not only that it is a security concern, it would simply fail on setups
which don't support HTTPS. This is hopefully a temporary fix until we
come-up with a long-term fix in DC/OS.

Fixes dcos#1190
https://jira.mesosphere.com/browse/COPS-3052
https://jira.mesosphere.com/browse/DCOS_OSS-2325
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants