Continuum

Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1-alpha-1
  • Fix Version/s: 1.1-beta-3
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

SCM-288 has introduced an attribute in CheckoutScmResult that contains the relative path of the project directory, relative to the checkout directory. This is needed for SCMs like ClearCase that do NOT perform the checkout into the checkout directory itself, but into a subdirectory. See SCM-288 for details.

This information should be honored by Continuum when adding a new project after checking out the sources. The POM filename of the Build Definition should automatically be set accordingly. In most cases the default "pom.xml" is sufficient, but in cases like ClearCase it would be e.g. "MY_VOB/my/project/dir/pom.xml".

Issue Links

Activity

Hide
Arne Degenring added a comment -

I haven't attached a patch to this issue yet, because I do not know the Continuum sources at all, and (even more important) don't have a running Continuum 1.1-SNAPSHOT testing environment.

I expect the change in Continuum to be very simple for Continuum developers.

Maybe someone else can provide a patch or commit the relevant change? Or at least point me into the right direction (which modules and packages to look at). My time to work on this issue during the next days will be very limited though, so I would highly appreciate if a Continuum developer could implement the change. Thanks in advance.

Show
Arne Degenring added a comment - I haven't attached a patch to this issue yet, because I do not know the Continuum sources at all, and (even more important) don't have a running Continuum 1.1-SNAPSHOT testing environment. I expect the change in Continuum to be very simple for Continuum developers. Maybe someone else can provide a patch or commit the relevant change? Or at least point me into the right direction (which modules and packages to look at). My time to work on this issue during the next days will be very limited though, so I would highly appreciate if a Continuum developer could implement the change. Thanks in advance.
Hide
Emmanuel Venisse added a comment -

The change must be done in DefaultBuildController in continuum-core.
When the scmresult is returned, need to update the builddefinition.buildFile if the buildFile is defined to a default value.

Show
Emmanuel Venisse added a comment - The change must be done in DefaultBuildController in continuum-core. When the scmresult is returned, need to update the builddefinition.buildFile if the buildFile is defined to a default value.
Hide
Emmanuel Venisse added a comment -

Fixed.
For the moment, after the first checkout, I modify the default build definition of the project, if the project have other build definitions, they aren't affected but I don't think a user already set some other build definitions before the first run

Show
Emmanuel Venisse added a comment - Fixed. For the moment, after the first checkout, I modify the default build definition of the project, if the project have other build definitions, they aren't affected but I don't think a user already set some other build definitions before the first run

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: