Release 0.32

• BUGFIX (#42)
  Apparently, Jenkins at some point changed the way it installs and loads plugins such that it now expects installed plugin file to use the "jpi" extension. The install-jenkins command now uses this extension.

• BUGFIX
  The json report kind works again.

• ENHANCEMENT (#40, #41)
  Jenkins recently started using a stricter cross-site request forgery (CSRF) protection scheme combining session cookies and a CSRF protection token. This stricter scheme is now supported.

• ENHANCEMENT (#39)
  The new variable dependencies.required-upstream-result controls the required status of upstream jobs in order to trigger builds of downstream jobs. Possible values are:

  • success - All upstream jobs must have successful builds.
  • unstable - All upstream jobs must have unstable (e.g. with test failures) or successful builds.
  • any - The build of the downstream job can start irregardless of the status of the upstream jobs.

  The new variable dependencies.required-result can be used to specify the status of jobs required to trigger downstream jobs. This can be used to relax the threshold established via dependencies.required-upstream-result in cases in which a known-unreliable upstream should still trigger downstream jobs. Note that marking the upstream job avoids the need to adapt the threshold in all downstream jobs.

• ENHANCEMENT (#45)
  Dependency specifications (for example in the extra-requires, extra-provides, platform-requires and platform-provides variables) can now use the following shorthand syntax: NATURE: TARGET instead of the usual

  nature: NATURE
  target: TARGET