Continuum
  1. Continuum
  2. CONTINUUM-598

Ability to specify which scm connection should be used to build the project (connection or developerConnection)

    Details

    • Complexity:
      Novice
    • Number of attachments :
      0

      Description

      i am a committer on a sf.net project. the anonymous cvs access is extremely unstable, but the developer access is rock solid. since i am a developer and i run a continuum server i am in a position to leverage the developer scm connection. it would be great if i can just tell continuum to use the developerConnection scm url rather then the regular connection scm url.

      i tried chaning the url in the project info manually, but after the project is built once the url reverts back to the one in the pom ( as it should i would imagine )

      i think a simple drop down in project info with connection/developerConnection choice would be great

        Activity

        Hide
        Wendy Smoak added a comment -

        In addition to allowing a choice, Continuum should handle a <scm> element with no <connection> (only <developerConnection>).

        Right now, it complains that <connection> is missing. Adding <connection> causes the generated source-control.html web page to have an "Anonymous Access" section that says anyone can check out the project, which in my case is not true.

        Show
        Wendy Smoak added a comment - In addition to allowing a choice, Continuum should handle a <scm> element with no <connection> (only <developerConnection>). Right now, it complains that <connection> is missing. Adding <connection> causes the generated source-control.html web page to have an "Anonymous Access" section that says anyone can check out the project, which in my case is not true.
        Hide
        Wendy Smoak added a comment -

        This also breaks the release process, since it tries to commit to the <connection> url instead of the <developerConnection> url.

        With this in the pom:
        <scm>
        <connection>scm:git:git://github.com/wsmoak/abc-example.git</connection>
        <developerConnection>scm:git:git://github.com:wsmoak/abc-example.git</developerConnection>
        <url>http://github.com/wsmoak/abc-example/tree/master</url>
        </scm>

        I get this on the scm-commit-release phase of release prepare:

        [ERROR] org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files
        Provider message:
        The git-push command failed.
        Command output:
        fatal: protocol error: expected sha/ref, got '
        *********'

        You can't push to git://github.com/user/repo.git
        Use git@github.com:user/repo.git

        *********'

        Show
        Wendy Smoak added a comment - This also breaks the release process, since it tries to commit to the <connection> url instead of the <developerConnection> url. With this in the pom: <scm> <connection>scm:git:git://github.com/wsmoak/abc-example.git</connection> <developerConnection>scm:git:git://github.com:wsmoak/abc-example.git</developerConnection> <url> http://github.com/wsmoak/abc-example/tree/master </url> </scm> I get this on the scm-commit-release phase of release prepare: [ERROR] org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files Provider message: The git-push command failed. Command output: fatal: protocol error: expected sha/ref, got ' *********' You can't push to git://github.com/user/repo.git Use git@github.com:user/repo.git *********'

          People

          • Assignee:
            Unassigned
            Reporter:
            Igor Vaynberg
          • Votes:
            5 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated: