Core system

Shows the unresolved issues sorted by number of votes

unresolved issues | resolved issues

Votes	T	Key	Summary	Fix Version/s	P	Status
19		CONTINUUM-509	Ability to process scheduled builds the same as forced builds.
11		CONTINUUM-798	Modules automatic discovery
9		CONTINUUM-686	Provide each build definition for a given project with its own checked-out workspace.
7		CONTINUUM-1716	POM URL should accept maven "scm" known protocols
5		CONTINUUM-598	Ability to specify which scm connection should be used to build the project (connection or developerConnection)
4		CONTINUUM-549	A build must always be executed when previous was in failure even if there are no changes in scm
3		CONTINUUM-1193	Can't use continuum for M2 projects with externals
3		CONTINUUM-1854	Error executing action 'update-project-from-working-directory'
3		CONTINUUM-998	Build order doesn't take plugin dependencies into account
3		CONTINUUM-1156	Continuum will not successfully delete build directories containing symbolic links	1.4.2
3		CONTINUUM-1421	Add an admin task to stop properly Continuum
2		CONTINUUM-564	Change focus of build from projects to Build Definitions
2		CONTINUUM-836	Improve HTTP access to POMs for adding a multi-module project
2		CONTINUUM-1770	Build results show current build definition arguments, not those used for the build
1		CONTINUUM-250	Continuum should not update SCM url for Maven1 projects.
1		CONTINUUM-348	allow push build by scm path
1		CONTINUUM-687	Option to trigger the SCM system to tag successful builds with a build number or timestamp.
1		CONTINUUM-714	SCM Connection for PVCS / Serena Version Manager
1		CONTINUUM-1657	Split configuration of pom location, when adding new M2 projects, into two parts; optionally specify a workspace into which a (modular-)project should be checked-out.
1		CONTINUUM-2293	continuum sh script fails to determine the right wrapper
1		CONTINUUM-34	Keep trying till build works, notify via email what is required