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

Merge upstream -> mainline-criteo #822

Closed
wants to merge 26 commits into from

Conversation

zeralight
Copy link

No description provided.

Olivier Tharan and others added 26 commits July 11, 2017 15:16
- Settle on the 'id' attribute as the attr_name for everything, since it is
  mandatory.
- The xml method can now be shared (protected) with the parent class as it
  would be the same in every subclass.
- Reduce the scope of the private key lookup. Due to the way Jenkins stores
  its credentials, it is quite hard to replicate this logic in integration
  tests without copying it entirely. As an exercise for later, stop reading
  credentials.xml and actually query Jenkins, but this is moving towards
  functional testing.
Make integration tests for credentials creation pass
When ignore_deps_versions is set to true, all
plugin dependencies installed by the jenkins_plugin
resource will be installed with their latest versions.
Because of an runit issue, Jenkins is stopped
after the end of the recipe, preventing the
tests to be run.
Restore smoke testing in Travis CI
- New secret file credentials resource.
- Allow empty passwords.
- Apply ulimit when launching agents or master.
- Apply style fixes.
- New secret file credentials resource.
- Allow empty passwords.
- Apply ulimit when launching agents or master.
- Apply style fixes.
- Remove extra double-quotes around -"remoting".
- New secret file credentials resource.
- Allow empty passwords.
- Apply ulimit when launching agents or master.
- Apply style fixes.
- Remove extra double-quotes around -"remoting".
Apply changes from criteo-forks to catchup with upstream
- This checksum property will be forwarded to chef remote file resource when
  retreiving the *.hpi/*.jpi plugin files.
It is not a good practice to apply remote_file resource without
checksum, add this option here to allow end users add valid one.
Add "checksum" option for slave-jar remote_file resource
Without this attribute, an exception "NoMethodError" will be
raised when we call "new_resource.checksum" to declare remote_file
resource.
Add "checksum" attribute for JenkinsSlave resource
Specifically, to support our docker use case internally.
Allow specification of supplementary groups to start the JNLP slave with
@zeralight zeralight closed this Jul 30, 2024
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.

7 participants