[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Igor Kostenko commented on JENKINS-36776 Re: Support Windows Server Containers It is much easier to use docker client for running jobs and deal with corresponding issues (like interrupting job would not stop running container) than to setup Kubernetes cluster just for that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172815.1468881746000.7385.1562774880929%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title Igor Kostenko commented on JENKINS-29425 Re: Multiple SCM + Mercurial + Git I had to get rid of git+mercurial mix, and for fixing below exception I have to always explicitly specify repository browser. In case multiple scm there is only one available choice: auto, so I'm manually modifying job xml. FATAL: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction java.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction at hudson.plugins.mercurial.MercurialSCM.determineChanges(MercurialSCM.java:612) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:561) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1282) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title Igor Kostenko commented on JENKINS-29425 Re: Multiple SCM + Mercurial + Git I've updated multiple-scms to 0.5, and now I'm getting below error a lot: have to restart build many times before it started properly. Deleting project workspace... done FATAL: null java.lang.NullPointerException at hudson.plugins.templateproject.ProxySCM.checkout(ProxySCM.java:53) at hudson.model.AbstractProject.checkout(AbstractProject.java:1282) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title
Igor Kostenko updated an issue
Jenkins / JENKINS-29425
Multiple SCM + Mercurial + Git
Change By:
Igor Kostenko
Jobswhichuses1Mercurial+3Gitrepositories(viaUseSCMfromanotherprojecttemplateplugin'soption)oftenfailingwithbelowerror.IfIrestartjobwithoutanychangesitbuildingok.Soerrorisnothappeningallthetime,butstillhappensoftenenough.Idon'tseesucherrorsinotherjobswhichusingmultipleMercurialreposormultipleGitrepos.WeonlyrecentlycreatedjobswhichneedmixofMercurialandGitrepos,Ihaven’tseensucherrorbefore. Ithappeningondifferentlinuxandwindowsslaves. ForMercurialrepositorycachingandsharingareenabled.Itlookslikeitdependsonslaveload-whenslaveisnotdoinganythingjobisrunningok,whenthereareotherjobsrunningonslave,jobisfailing. {{ Deletingprojectworkspace...doneFATAL:hudson.plugins.mercurial.MercurialTagActioncannotbecasttoorg.jenkinsci.plugins.multiplescms.MultiSCMRevisionStatejava.lang.ClassCastException:hudson.plugins.mercurial.MercurialTagActioncannotbecasttoorg.jenkinsci.plugins.multiplescms.MultiSCMRevisionState atorg.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:106) athudson.scm.SCM.checkout(SCM.java:485) athudson.plugins.templateproject.ProxySCM.checkout(ProxySCM.java:53) athudson.model.AbstractProject.checkout(AbstractProject.java:1282) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) athudson.model.Run.execute(Run.java:1741) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:381)Archivingartifacts }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [mercurial-plugin] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title
Igor Kostenko created an issue
Jenkins / JENKINS-29425
Multiple SCM + Mercurial + Git
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
mercurial-plugin, multiple-scms-plugin, template-project-plugin
Created:
14/Jul/15 4:43 PM
Environment:
Jenkins 1.620 multiple-scms 0.4 mercurial 1.54 template-project 1.4.2
Priority:
Major
Reporter:
Igor Kostenko
Jobs which uses 1 Mercurial + 3 Git repositories (via Use SCM from another project template plugin's option) often failing with below error. If I restart job without any changes it building ok. So error is not happening all the time, but still happens often enough. I don't see such errors in other jobs which using multiple Mercurial repos or multiple Git repos. We only recently created jobs which need mix of Mercurial and Git repos, I haven’t seen such error before.
{{Deleting project workspace... done
FATAL: hudson.plugins.mercurial.MercurialTagAction cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState java.lang.ClassCastException: hudson.plugins.mercurial.MercurialTagAction cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:106) at hudson.scm.SCM.checkout(SCM.java:485) at
[JIRA] [extra-columns-plugin] (JENKINS-23583) Column Test Result has incorrect link
Igor Kostenko commented on JENKINS-23583 Column Test Result has incorrect link Matthieu, could you upload plugin jar with PR 11 somewhere? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns] (JENKINS-23624) Incorrect Test Result link
Igor Kostenko created JENKINS-23624 Incorrect Test Result link Issue Type: Bug Affects Versions: current Assignee: Fred G Components: extra-columns Created: 30/Jun/14 1:15 PM Description: Test Result link is incorrect because view mentioned twice in it. URL looks like http://jenkins//view/VIEW_NAME/view/VIEW_NAME/job/JOB_NAME/lastCompletedBuild/testReport/ I'm using Test result format 2, Jenkins 1.570, Extra Columns Plugin 1.14 Environment: Jenkins 1.570, Extra Columns Plugin 1.14, Test result format 2 Project: Jenkins Priority: Minor Reporter: Igor Kostenko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
Igor Kostenko commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here Yes, I understand that build number still could be used. Idea was to make life easier - when you have many different jobs with different build numbers it is easy to make a mistake when you getting specific artifacts from there, using the same name everywhere is more convenient. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
Igor Kostenko commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here Yes, it is fair and it is consistent with jeninks url behavior, if you specifying number in http://jenkins/job/job/build/ you will get build by number (and will get an error if you used a number for display name and there is no job with such number). I guess it would be better if just number in display name will be prohibited to avoid confusion and inconsistent behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18459) IOException: No Such File
Igor Kostenko commented on JENKINS-18459 IOException: No Such File I'm so happy that I found that bug. I couldn't upgrade to jenkins 1.519-1.523, no linux slaves were running (windows slaves were fine) and I couldn't figure out what the issue was. Now I see that it was because of my .jenkins script in home directory of build user (and we have mounted home directories - so it is the same directory on all hosts). After renaming the script and changing all jobs which using it upgraded jenkins is working ok. Hopefully this cache directory wouldn't be messed up because many hosts are using it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-10558) Jenkins mercurial plugin - add support for bookmarks
Igor Kostenko commented on JENKINS-10558 Jenkins mercurial plugin - add support for bookmarks When you are using repository caching bookmarks are lost because bundle doesn't support them This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) Sorry for long pause, I've changed a job and only now responsible for jenkins again. Igor: could you, on your slave, create a .hg/hgrc file in the /app/agora/hudsonslave/hgcache/D38534FF4534AE3232A1AB292D5BA54825AE752B-AgoraLight that contains the following information: It helped: [QAF_Test2] $ hg pull --rev default /home/jenkins_local/hgcache/82556880B412DFAE704E615CE9ABB4DA5A38C2EF-doc_source [QAF_Test2] $ hg update --clean --rev default 0 files updated, 0 files merged, 0 files removed, 0 files unresolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
Igor Kostenko
updated JENKINS-18237
Multiple hg repos vs matrix job - the same revision used for all repositories.
Change By:
Igor Kostenko
(06/Jun/13 2:23 PM)
Description:
WhenImusingMultipleSCMplugininMatrixjob,configurationsbuildarefailingbecauseofwrongrevisioninhgupdate.Toplevelbuild:{code}[common]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/730F3D6CF2984FE6965438CDBB2F241CA1B4F220-common[common]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[common]$hglog--rev.--template{node}[common]$hglog--rev.--template{rev}[common]$hglog--rev76175d754787279d7888132d364e2847c576134c...[project_engine]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/892EE33C3F9037402D2325A82FC02A50F873F87F-project_engine[project_engine]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[project_engine]$hglog--rev.--template{node}[project_engine]$hglog--rev.--template{rev}[project_engine]$hglog--rev53dbe704b92059332f0af3ebe2d50f56aac7f4d9{code}
If
As
youcanseerevisionsforcommonproject_enginearedifferent.Thesamebuildforeachconfigurationgivesanerrorbecauseofthesamerevisionforbothprojects:{code}[common]$hgupdate--rev76175d754787279d7888132d364e2847c576134c739filesupdated,0filesmerged,0filesremoved,0filesunresolved...[project_engine]$hgupdate--rev76175d754787279d7888132d364e2847c576134cabort:unknownrevision76175d754787279d7888132d364e2847c576134c!{code}ImusinghgsharingandcachingandTemplateprojectforSCM-buttheybothworkfinefornon-matrixprojects.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
Igor Kostenko
updated JENKINS-18237
Multiple hg repos vs matrix job - the same revision used for all repositories.
Change By:
Igor Kostenko
(06/Jun/13 2:22 PM)
Description:
WhenImusingMultipleSCMplugininMatrixjob,configurationsbuildarefailingbecauseofwrongrevisioninhgupdate.Toplevelbuild:
Mastercachelockreleased.
{code}[common]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/730F3D6CF2984FE6965438CDBB2F241CA1B4F220-common[common]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[common]$hglog--rev.--template{node}[common]$hglog--rev.--template{rev}[common]$hglog--rev76175d754787279d7888132d364e2847c576134c...[project_engine]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/892EE33C3F9037402D2325A82FC02A50F873F87F-project_engine[project_engine]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[project_engine]$hglog--rev.--template{node}[project_engine]$hglog--rev.--template{rev}[project_engine]$hglog--rev53dbe704b92059332f0af3ebe2d50f56aac7f4d9{code}Ifyoucanseerevisionsforcommonproject_enginearedifferent.Thesamebuildforeachconfigurationgivesanerrorbecauseofthesamerevisionforbothprojects:{code}[common]$hgupdate--rev76175d754787279d7888132d364e2847c576134c739filesupdated,0filesmerged,0filesremoved,0filesunresolved...[project_engine]$hgupdate--rev76175d754787279d7888132d364e2847c576134cabort:unknownrevision76175d754787279d7888132d364e2847c576134c!{code}ImusinghgsharingandcachingandTemplateprojectforSCM-buttheybothworkfinefornon-matrixprojects.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
Igor Kostenko
created JENKINS-18237
Multiple hg repos vs matrix job - the same revision used for all repositories.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kevin Bell
Components:
multiple-scms
Created:
06/Jun/13 2:22 PM
Description:
When I'm using Multiple SCM plugin in Matrix job, configurations build are failing because of wrong revision in hg update.
Top level build:
Master cache lock released.
[common] $ hg pull --rev default /mnt/imports/data2/users/jenkins/hgcache/730F3D6CF2984FE6965438CDBB2F241CA1B4F220-common
[common] $ hg update --clean --rev default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
[common] $ hg log --rev . --template {node}
[common] $ hg log --rev . --template {rev}
[common] $ hg log --rev 76175d754787279d7888132d364e2847c576134c
...
[project_engine] $ hg pull --rev default /mnt/imports/data2/users/jenkins/hgcache/892EE33C3F9037402D2325A82FC02A50F873F87F-project_engine
[project_engine] $ hg update --clean --rev default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
[project_engine] $ hg log --rev . --template {node}
[project_engine] $ hg log --rev . --template {rev}
[project_engine] $ hg log --rev 53dbe704b92059332f0af3ebe2d50f56aac7f4d9
If you can see revisions for common project_engine are different. The same build for each configuration gives an error because of the same revision for both projects:
[common] $ hg update --rev 76175d754787279d7888132d364e2847c576134c
739 files updated, 0 files merged, 0 files removed, 0 files unresolved
...
[project_engine] $ hg update --rev 76175d754787279d7888132d364e2847c576134c
abort: unknown revision '76175d754787279d7888132d364e2847c576134c'!
I'm using hg sharing and caching and Template project for SCM - but they both work fine for non-matrix projects.
Project:
Jenkins
Priority:
Major
Reporter:
Igor Kostenko
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) If somebody else have the same issue, here the workaround which I'm using on slaves: In Source Code Management / Mercurial / Advanced / Subdirectory I'm specifying directory fake and adding at the beginning of build Unix: if [ -d MyRepo ]; then hg -R MyRepo update else hg --config extensions.share= share fake MyRepo fi Windows: if exist MyRepo\nul (hg -R MyRepo update) else (hg --config extensions.share= share fake MyRepo) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) what do you mean with the 'fake working copy' option It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did to for having changes information on build's page. It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option. Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko edited a comment on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) what do you mean with the 'fake working copy' option It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did to for having changes information on build's page. It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option. Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves - only master (on linux) is fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Igor Kostenko edited a comment on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) what do you mean with the 'fake working copy' option It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did it for having changes information on build's page. It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option. Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ? Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves - only master (on linux) is fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13774) Provide option for cloning all branches with Mercurial SCM
Igor Kostenko commented on JENKINS-13774 Provide option for cloning all branches with Mercurial SCM That's how I do it - I'm using hg plugin to get data into fake directory (to get at least some changes in build description) and after that getting everything from hg manually. It's working but it's ugly hack - it will be much better if hg plugin could get everything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
