[ http://jira.codehaus.org/browse/CONTINUUM-813?page=all ]
Emmanuel Venisse closed CONTINUUM-813.
--------------------------------------
Assignee: Emmanuel Venisse
Resolution: Won't Fix
In a CI environment, files in scm are the reference and used by the process. In
Continuum, the uploaded pom is only for the initialization of the process so it
need to contains at least scm part and continuum checkout the project with this
information but use the one in scm for the build and next updates like other CI
tools.
> When uploading an uncommitted pom : this is the pom currently on scm which is
> used
> -----------------------------------------------------------------------------------
>
> Key: CONTINUUM-813
> URL: http://jira.codehaus.org/browse/CONTINUUM-813
> Project: Continuum
> Issue Type: Bug
> Components: Web interface, SCM
> Affects Versions: 1.0.3
> Reporter: Simon Lebettre
> Assigned To: Emmanuel Venisse
> Priority: Trivial
>
> - I created a test project, without any scm data in the pom. I commited the
> pom as is.
> - then I modified the POM locally to include scm information (I just used a
> local cvs , no viewcvs installed )
> - I deleted my project and re-uploaded the local pom with the correct scm tag
> ==> continuum replaces the correct uploaded pom by the incorrect pom from
> cvs, and tells there is no scm metadata in the pom !
> -------------------------------------------------------------------------------------------------------------------------------------------------
> I suggest just adding a mention on the upload page :
> "warning : the __committed__ pom will be used for the build, not the
> __uploaded__ pom"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
