Feature #1669
Support Mercurial SCM
Status: | Resolved | Start date: | 12/03/2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Wienke | % Done: | 100% | |
Category: | Project Analysis | |||
Target version: | 0.3 |
Associated revisions
Support mercurial DVCS in src/analysis/mercurial.lisp
fixes #1669
- src/analysis/mercurial.lisp: new file; contains support for the
mercurial DVCS - jenkins.project.asd (system jenkins.project): added file
src/analysis/mercurial.lisp
Fixes for mercurial scm implementation in src/analysis/mercurial.lisp
refs #1669
- src/analysis/mercurial.lisp (header): updated copyright
(analyze uri eql :mercurial): accept versions instead of branches and
tags
Guess mercurial scm in src/analysis/analysis.lisp
refs #1669
- src/analysis/analysis.lisp (analyze uri eql :auto): guess :mercurial
SCM if URI contains "hg"
Support mercurial SCM in lib/jenkins.api/src/api/classes.lisp
refs #1669
- lib/jenkins.api/src/api/classes.lisp (mercurial-revision-type): new
type; either :branch or :tag
(xml-> string eql mercurial-revision-type): new method; convert the
type from XML
(->xml symbol eql string eql mercurial-revision-type): new method;
convert the type to XML
(define-interface-implementations scm): added mercurial implementation - lib/jenkins.api/src/package.lisp (package jenkins.api): added exported
symbols scm/mercurial, credentials, revision-type, branch,
sub-directory, clean? and modules
Added mercurial aspect in src/project/aspects.lisp
fixes #1669
- src/project/aspects.lisp (define-aspect mercurial): new aspect;
configures mercurial plugin
History
#1 Updated by J. Moringen over 10 years ago
- Target version set to 0.3
#2 Updated by J. Moringen about 10 years ago
- Category set to Project Analysis
#3 Updated by J. Moringen almost 10 years ago
- Target version changed from 0.3 to 0.4
#4 Updated by J. Moringen over 9 years ago
- Target version changed from 0.4 to 0.3
#5 Updated by J. Moringen over 9 years ago
- Status changed from New to Feedback
- Assignee changed from J. Moringen to J. Wienke
- Target version changed from 0.3 to 0.4
- % Done changed from 0 to 30
This can be supported in principle. However, one thing I couldn't figure out so far is how to check whether a remote repository is accessible without actually cloning it.
#6 Updated by J. Moringen over 9 years ago
- Target version changed from 0.4 to 0.3
#7 Updated by J. Moringen over 9 years ago
- Status changed from Feedback to Resolved
- % Done changed from 30 to 100
Applied in changeset 44925c584277f9033cbe398756fa3ab128876093.