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

Move the FIPS configuration back to the build plugin #41989

Merged
merged 2 commits into from
May 21, 2019

Conversation

alpar-t
Copy link
Contributor

@alpar-t alpar-t commented May 9, 2019

This is necesary for external users of build-tools.
Closes #41721

This is necesary for external users of build-tools.
Closes elastic#41721
@alpar-t alpar-t added :Delivery/Build Build or test infrastructure :Security/Security Security issues without another label v8.0.0 v7.2.0 v7.0.2 v7.1.0 v7.3.0 labels May 9, 2019
@alpar-t alpar-t requested a review from mark-vieira May 9, 2019 05:55
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@@ -116,6 +116,21 @@ class BuildPlugin implements Plugin<Project> {
configureTestTasks(project)
configurePrecommit(project)
configureDependenciesInfo(project)

// Common config when running with a FIPS-140 runtime JVM
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a comment on why this is left in the BuildPlugin so that we won't move it again in the future?

@alpar-t
Copy link
Contributor Author

alpar-t commented May 9, 2019

@elasticmachine run elasticsearch-ci/1

@mark-vieira
Copy link
Contributor

Since this is mainly for external users of build-tools, do we really need to backport this change? Isn't build-tools published only from master?

@rjernst
Copy link
Member

rjernst commented May 9, 2019

Isn't build-tools published only from master?

build-tools is published every time we do a release, from the release branch, never from master. The versioning of build-tools matches elasticsearch's versioning

@mark-vieira
Copy link
Contributor

build-tools is published every time we do a release, from the release branch, never from master. The versioning of build-tools matches elasticsearch's versioning

Thanks for the clarification!

@mark-vieira
Copy link
Contributor

FWIW, this is going to conflict a bit with #41392 so if that gets merged first this'll have to get tweaked a bit.

@jakelandis jakelandis removed the v7.1.0 label May 19, 2019
@alpar-t alpar-t merged commit 1911d2a into elastic:master May 21, 2019
alpar-t added a commit that referenced this pull request May 21, 2019
* Move the FIPS configuration back to the build plugin

This is necesary for external users of build-tools.
Closes #41721
alpar-t added a commit that referenced this pull request May 21, 2019
* Move the FIPS configuration back to the build plugin

This is necesary for external users of build-tools.
Closes #41721
mark-vieira added a commit to mark-vieira/elasticsearch that referenced this pull request May 21, 2019
jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request May 21, 2019
…der-permit-primary-mode-only

* elastic/master:
  Move the FIPS configuration back to the build plugin (elastic#41989)
  Remove stray back tick that's messing up table format (elastic#41705)
  Add missing comma in code section (elastic#41678)
  add 7.1.1 and 6.8.1 versions (elastic#42253)
  Use spearate testkit dir for each run (elastic#42013)
  Add experimental and warnings to vector functions (elastic#42205)
  Fix version in tests since elastic#41906 was merged
  Bump version in BWC check after backport
  Prevent in-place downgrades and invalid upgrades (elastic#41731)
  Mute date_histo interval bwc test
jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request May 21, 2019
* master: (176 commits)
  Avoid unnecessary persistence of retention leases (elastic#42299)
  [ML][TEST] Fix limits in AutodetectMemoryLimitIT (elastic#42279)
  [ML Data Frame] Persist and restore checkpoint and position (elastic#41942)
  mute failing filerealm hash caching tests (elastic#42304)
  Safer Wait for Snapshot Success in ClusterPrivilegeTests (elastic#40943)
  Remove 7.0.2 (elastic#42282)
  Revert "Remove 7.0.2 (elastic#42282)"
  [DOCS] Copied note on slicing support to Slicing section. Closes 26114 (elastic#40426)
  Remove 7.0.2 (elastic#42282)
  Mute all ml_datafeed_crud rolling upgrade tests
  Move the FIPS configuration back to the build plugin (elastic#41989)
  Remove stray back tick that's messing up table format (elastic#41705)
  Add missing comma in code section (elastic#41678)
  add 7.1.1 and 6.8.1 versions (elastic#42253)
  Use spearate testkit dir for each run (elastic#42013)
  Add experimental and warnings to vector functions (elastic#42205)
  Fix version in tests since elastic#41906 was merged
  Bump version in BWC check after backport
  Prevent in-place downgrades and invalid upgrades (elastic#41731)
  Mute date_histo interval bwc test
  ...
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
* Move the FIPS configuration back to the build plugin

This is necesary for external users of build-tools.
Closes elastic#41721
@alpar-t alpar-t deleted the fix-fips branch November 11, 2019 09:41
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure :Security/Security Security issues without another label Team:Delivery Meta label for Delivery team v7.1.0 v7.2.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ci] corrupted keystore on java8 fips build
6 participants