Buildr
  1. Buildr
  2. BUILDR-83

Dependency checks as part of the release process

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.1
    • Fix Version/s: 1.3.3
    • Component/s: Core features
    • Labels:
      None

      Description

      Add automated tasks to release process to make sure we have the right set of dependencies:

      • Test with both MRI and JRuby specs, since they use different dependency sets.
      • For each dependency, verify that the Gem is available on the RubyForge server.
      • That goes for platform variance, e.g. RJB has both ruby and win32 platform, both must be checked for existence.
      • From dependency list determine the order in which dependencies will be loaded, and make sure the dependency list is in that order.

        Activity

        Assaf Arkin made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Hide
        Assaf Arkin added a comment -

        Added tests for the other platform (i.e. JRuby when staging on Ruby and vice versa).
        As far as I can tell, no way to tell (given RubyGems API) which platforms we're looking at for a given Gem, so we'll have to trust the manual process to uncover that.

        Show
        Assaf Arkin added a comment - Added tests for the other platform (i.e. JRuby when staging on Ruby and vice versa). As far as I can tell, no way to tell (given RubyGems API) which platforms we're looking at for a given Gem, so we'll have to trust the manual process to uncover that.
        Assaf Arkin made changes -
        Assignee Assaf Arkin [ assafarkin ]
        Assaf Arkin made changes -
        Field Original Value New Value
        Fix Version/s 1.3.3 [ 12313289 ]
        Fix Version/s 1.3.2 [ 12313159 ]
        Hide
        Assaf Arkin added a comment -

        [ ] Test with both MRI and JRuby specs, since they use different dependency sets.
        [x] For each dependency, verify that the Gem is available on the RubyForge server.
        [ ] That goes for platform variance, e.g. RJB has both ruby and win32 platform, both must be checked for existence.
        [x] From dependency list determine the order in which dependencies will be loaded, and make sure the dependency list is in that order.

        Show
        Assaf Arkin added a comment - [ ] Test with both MRI and JRuby specs, since they use different dependency sets. [x] For each dependency, verify that the Gem is available on the RubyForge server. [ ] That goes for platform variance, e.g. RJB has both ruby and win32 platform, both must be checked for existence. [x] From dependency list determine the order in which dependencies will be loaded, and make sure the dependency list is in that order.
        Assaf Arkin created issue -

          People

          • Assignee:
            Assaf Arkin
            Reporter:
            Assaf Arkin
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development