Announcement Announcement Module
No announcement yet.
Remote repository coming in late Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Remote repository coming in late

    dm Server 2.0.1.RELEASE:

    Not every time, but more than not, my remote repository becomes available after dm Server attempts to install my plan files. This causes the plan to fail because all the required bundles are on the remote repository. Log looks something like this:

    dm Kernel ssh shell available on port 2401.
    Kernel started.
    Installed bundle '' version '2.0.1.RELEASE'.
    User region ready.
    Installing plan 'app' version '1.0.0'.

    <bunch of exceptions bundles not being found in ext-usr-remote>

    The repository 'remote' is available.

  • #2
    This might only happen if on the remote server side (hosting the repository), the hosted repository is a watched repository and had been recently updated.


    • #3
      Hmmm. There would be a race like you are seeing if you are copying artifacts into a remote watched repository RW and attempting to deploy a plan that references any of those artifacts on a dm Server instance with RW in its repository chain. But copying unrelated artifacts into RW shouldn't have a disruptive effect on a server with RW in its chain.


      • #4
        Thank you. That is quite likely what's going on. The remote repository is getting updated with the latest continuous integration builds all the time, so it's likely that bundles I would be using would be being updated.

        The goal is to have the latest builds of bundles on a remote repository so that a developer, that is only working on a single bundle, doesn't need to check out the entire application, just the single bundle and the plan file.

        Is it possible to have bundles in the stage repository take precedence over bundles in the other repositories? If I had a bundle of version 1.0.0 checked out, and the latest build in my remote repository was 1.0.0.CI00012, the CI build always gets used.


        • #5
          To make your version override the version in the remote repository, you need to add your version to another repository in the chain. Presumably it would be most convenient to copy your version into the watched repository directory, e.g. repository/usr. Also, give your version a higher version than that in the remote repository, e.g. 1.0.0.Dnnnnn.


          • #6
            Brilliant! Thank you very much.