Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Tag: katello-headpi…
Commits on Feb 17, 2012
  1. @jsomara
  2. @jsomara

    another gen_changes run

    jsomara authored
Commits on Feb 16, 2012
  1. @jsomara
  2. @jsomara

    gen_changes run

    jsomara authored
  3. @jsomara

    Merge commit 'katello-0.1.240-1' into headpin

    jsomara authored
    Conflicts:
    	src/spec/models/system_spec.rb
  4. @jsomara
  5. @jsomara

    Revert "Temporarily removing selinux requires"

    jsomara authored
    This reverts commit 8464893.
  6. @jsomara
  7. @jsomara

    gen_changes

    jsomara authored
  8. @jsomara

    Merge commit 'katello-0.1.238-1' into headpin

    jsomara authored
    Conflicts:
    	src/app/controllers/api/systems_controller.rb
  9. @tstrachota
  10. @tstrachota
  11. @tstrachota
  12. @tstrachota
  13. @tstrachota
  14. @tstrachota
  15. @tstrachota

    788073 - fixed time formatting in cli

    tstrachota authored
    It now uses xml.utils.iso8601 for parsing all times.
  16. @tstrachota
  17. @tstrachota
  18. @lzap
  19. @lzap
  20. @iNecas
  21. @iNecas
  22. @iNecas
  23. @iNecas

    789456 - candlepin environment orchestration

    iNecas authored
    Create environment in CP on creation, delete on destoy and assign to a content
    on repo promotion. Requires candlepin >= 0.5.16-1
  24. @iNecas

    789456 - pre-save and post-save queues in orchestration

    iNecas authored
    Rename current one queue processed before saving a record to pre_queue and add
    post_queue processed after saving.
    
    This is required in case we need to use id generated in Katello db in
    orchestration (e.g. make a refference in CP to object in Katello - environments
    orchestration).
    
    When a task on post_queue fails, also completed tasks in pre_queue are
    processed.
Commits on Feb 15, 2012
  1. @mccun934
  2. @mccun934
  3. @bbuckingham
  4. @bbuckingham
Commits on Feb 14, 2012
  1. @parthaa
  2. @parthaa
  3. @parthaa
  4. @parthaa
  5. @swarmingbee
Something went wrong with that request. Please try again.