Skip to content
Snippets Groups Projects
  1. Sep 25, 2017
  2. Sep 15, 2017
  3. Sep 06, 2017
  4. Aug 31, 2017
    • Markus Thömmes's avatar
      Simplify Spi implementations. (#2663) · f9450364
      Markus Thömmes authored
      Using `object`s instead of a hollow class as the "factory" for an Spi makes them being singleton by default, which reduces boilerplate to implement an Spi.
      
      The `Dependencies` object is not used anywhere and there might be better alternatives which we can decide on once the need of them comes up. For now, the Spi's interfaces are relatively tightly coupled to their current default implementations anyway.
      
      Also updated documentation.
      f9450364
  5. Aug 16, 2017
  6. Aug 04, 2017
    • tysonnorris's avatar
      SPI approach for pluggable implementations. (#2414) · 1e02bc67
      tysonnorris authored
      Adds the ability to add pluggable implementations for defined Service Provider Interfaces (SPI). The implementation to load is chosen via configuration.
      
      First set of plug-points are:
      - ArtifactStoreProvider
      - MessagingProvider
      1e02bc67
  7. Jul 14, 2017
  8. Jun 28, 2017
  9. Jun 26, 2017
    • Paul Castro's avatar
      Add Swift 3.1.1 as a kind (#2120) · 9d37b3f9
      Paul Castro authored
      * Experimental branch for 2079, uses ibm swift ubuntu image for 3.1
      
      * Fixes issue #2079, add Swift 3.1.1 runtime kind, update Swift dependencies for Watson SDK, KituraNet, SwiftyJson
      
      * add apache license
      
      * Fix swift311 location and catch docker brake
      
      The location of the swift binary for 311 is now in /usr/bin/swift
      Need to catch docker errors when building by usig && instead of ;
      
      * new zip for new swift311 runtime
      9d37b3f9
  10. Jun 20, 2017
  11. Apr 19, 2017
  12. Apr 08, 2017
  13. Apr 03, 2017
    • rodric rabbah's avatar
      Enable tests for unicode for python, swift. (#2070) · 3a319df1
      rodric rabbah authored
      Re-enable build swift/python containers (for tests to run).
      Add unicode unit test for swift action container.
      Allow for reinit with swift for use with invoke.py.
      Fix unicode regression for swift actions.
      Refactor unicode tests to add coverage - now also for base action container.
      Set string encoding to utf-8 for swift action proxy.
      Rewrite result extraction to avoid splitting and printing logs one line at a time.
      Skip decoding when process output is a string; already utf-8.
      
      Consolidate base64 encoding in CLI; remove Jar field in exec.
      3a319df1
  14. Mar 28, 2017
    • cclauss's avatar
      Add python:3 action support. · 415f5628
      cclauss authored
      Update tests to work in both Python 2 and Python 3.
      Rename pythonaction to python3action for container image name for clarity.
      Add tests for python:2 and python:3.
      Add image names for all the actions. Rename javaaction to java8action for consistency.
      415f5628
  15. Mar 15, 2017
  16. Mar 11, 2017
  17. Mar 07, 2017
  18. Mar 06, 2017
  19. Mar 05, 2017
    • Justin Berstler's avatar
      Warn users against the dangers of using Windows Explorer's zip action. · e83e3bfd
      Justin Berstler authored
      Using the Windows Explorer method of creating zip actions results in an incorrect zip structure. OW requires that package.json be found at the root of the zip, while the Explorer action insists on putting everything inside a top-level folder inside the zip.
      
      Return an explicit error when package.json is not found at the root of a zipped action.
      e83e3bfd
  20. Mar 03, 2017
  21. Mar 02, 2017
  22. Mar 01, 2017
  23. Feb 27, 2017
  24. Feb 24, 2017
    • Justin Berstler's avatar
      GC container after a failed unpause · 1c040469
      Justin Berstler authored
      1c040469
    • Justin Berstler's avatar
      Do not retry /run on action containers · 48367750
      Justin Berstler authored
      It should be assumed that /run only happens after /init which should itself ensure that the container is running and ready. With that in mind, it does not make sense to attempt to retry posting to the /run endpoint on connection failures. Such a failure is an indication that something catastrophic has happened to the container, and no attempt at recovery should be made.
      
      This is accomplished by adding a "retry" flag to the appropriate HTTP utilities to control whether or not a retry should be attempted.
      48367750
  25. Feb 22, 2017
  26. Feb 21, 2017
  27. Feb 20, 2017
  28. Feb 17, 2017
Loading