[JIRA] (JENKINS-12927) Changes doesn't trigger a build - unknown revision

2012-04-17 Thread fri...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161685#comment-161685
 ] 

frew schmidt commented on JENKINS-12927:


I have the opposite problem with two git repos, that is, no changes and it 
still makes a build.  I got around it by just not using the Multiple SCM 
plugin, setting up a single repo, and then using the shell to check out the 
other one and update it.  Sucks though.

 Changes doesn't trigger a build - unknown revision
 

 Key: JENKINS-12927
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12927
 Project: Jenkins
  Issue Type: Bug
  Components: multiple-scms
Affects Versions: current
 Environment: RHEL 6, Mercurial 1.4, Jenkins 1.452
Reporter: Marcus Eriksson
Assignee: Kevin Bell

 With two Mercurial repositories configured, even though the plug-in detects a 
 changeset it still doesn't trigger a new build because it is referring to a 
 (previous?) known revision.
 Here's the polling log from where it detects a change:
 Started on Feb 29, 2012 7:41:20 AM
 [public] $ /usr/bin/hg pull --rev default
 pulling from http://gbglcrd10/hg/jsf/
 searching for changes
 adding changesets
 adding manifests
 adding file changes
 added 1 changesets with 2 changes to 2 files
 (run 'hg update' to get a working copy)
 [public] $ /usr/bin/hg log --style 
 /ssd/Jenkins/jobs/newjsf/workspace/tmp5480491059555742578style --branch 
 default --no-merges --prune 8ee1ae92f8aa040c970d64c992ece871b994dab9
 abort: unknown revision '8ee1ae92f8aa040c970d64c992ece871b994dab9'!
 [private] $ /usr/bin/hg pull --rev default
 pulling from http://gbglcrd10/hg-jsf/licensing/
 no changes found
 [private] $ /usr/bin/hg log --style 
 /ssd/Jenkins/jobs/newjsf/workspace/tmp4214498074041391865style --branch 
 default --no-merges --prune 8ee1ae92f8aa040c970d64c992ece871b994dab9
 Done. Took 0.92 sec
 No changes
 Is this revision coming from the second configured repository? In any case, 
 this always fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13455) when a submodule can't be checked out an exception is thrown

2012-04-14 Thread fri...@gmail.com (JIRA)
frew schmidt created JENKINS-13455:
--

 Summary: when a submodule can't be checked out an exception is 
thrown
 Key: JENKINS-13455
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13455
 Project: Jenkins
  Issue Type: Bug
  Components: git
Affects Versions: current
Reporter: frew schmidt
Assignee: Nicolas De Loof


Sometimes developers accidentally forget to push a submodule and thus make it 
impossible to check out their changes completely.  This causes jenkins to throw 
an exception and on the next build it merely tries again and will inevitably 
fail.  Maybe we should make an option for failed submodules to fail the build 
and move on instead of throwing an exception.  I'll paste in the console output 
when this happened to me here.

The first time:

{noformat}
Started by an SCM change
Building in workspace /var/lib/jenkins/jobs/Lynx/workspace
Checkout:workspace / /var/lib/jenkins/jobs/Lynx/workspace - 
hudson.remoting.LocalChannel@aa0ff27
Using strategy: Default
Last Built Revision: Revision 15f062624b185b08d695a0949ede1431fe75bdd5 
(origin/feature/LXS-1289-ip.plx-redux)
Fetching changes from 1 remote Git repository
Fetching upstream changes from cs:lynx
Pruning obsolete local branches
Seen branch in repository origin/HEAD
Seen branch in repository origin/LXS/000-dbic-error
Seen branch in repository origin/bug/LXS-000-WebIcons-Pass2Frew
Seen branch in repository origin/bug/LXS-1053-Check-in-Primary
Seen branch in repository origin/bug/LXS-1093-user-password
Seen branch in repository origin/bug/LXS-1094-Account-cleanup
Seen branch in repository origin/bug/LXS-1139-crash
Seen branch in repository origin/bug/LXS-1327-incorrect-sms-errors
Seen branch in repository origin/bug/LXS-1352-snpp-strip-newlines-and-unicode
Seen branch in repository origin/bug/LXS-432-Type-Macro
Seen branch in repository origin/bug/LXS-504-Excel-Openings
Seen branch in repository origin/bug/LXS-774-Shared-RO
Seen branch in repository origin/bug/LXS-948-Log-Shows-Dest-twice
Seen branch in repository origin/bug/LXS-948-log-duplication
Seen branch in repository origin/bug/LXS-971-D-Drive
Seen branch in repository origin/bug/LXS-976-Excel-Button
Seen branch in repository origin/feature/LXS-1060-Active-Dir-SubUsers
Seen branch in repository origin/feature/LXS-1064-Remove-AD-Import
Seen branch in repository origin/feature/LXS-1093-User-Edits
Seen branch in repository origin/feature/LXS-1094-Account-Cleanup
Seen branch in repository origin/feature/LXS-1096-ReadOnly
Seen branch in repository origin/feature/LXS--New-WebIcon
Seen branch in repository origin/feature/LXS--Web-Icon
Seen branch in repository origin/feature/LXS--jason-fix
Seen branch in repository origin/feature/LXS--web-icon-group
Seen branch in repository origin/feature/LXS-1145-remove-theme-and-news
Seen branch in repository origin/feature/LXS-1146-remove-find-Lynxnet
Seen branch in repository origin/feature/LXS-1196-client-database
Seen branch in repository origin/feature/LXS-1198-client-testing
Seen branch in repository origin/feature/LXS-1214-AlarmState
Seen branch in repository origin/feature/LXS-1289-ip.plx-redux
Seen branch in repository origin/feature/LXS-1316-macro-wildcards
Seen branch in repository origin/feature/LXS-1329-database-refactor
Seen branch in repository origin/feature/LXS-1344-ldap-improvements
Seen branch in repository origin/feature/LXS-1349-improved-failover
Seen branch in repository origin/feature/LXS-1353-snpp-logging
Seen branch in repository origin/feature/LXS-1357-apache-2.4.1
Seen branch in repository origin/feature/LXS-865-Excel-Link
Seen branch in repository origin/merge/users
Seen branch in repository origin/merge/webicons
Seen branch in repository origin/preview
Seen branch in repository origin/release
Commencing build of Revision 2cf960767f0bcdcbab95a998aa0d953f3b29db1d 
(origin/LXS/000-dbic-error)
Checking out Revision 2cf960767f0bcdcbab95a998aa0d953f3b29db1d 
(origin/LXS/000-dbic-error)
Trying to fetch ClientUpdates into 
/var/lib/jenkins/jobs/Lynx/workspace/lynx/ClientUpdates
Fetching upstream changes from cs:lynx-client-updates
Trying to fetch Lynxnet into /var/lib/jenkins/jobs/Lynx/workspace/lynx/Lynxnet
Fetching upstream changes from cs:lynx-net
Trying to fetch TrueUpdate into 
/var/lib/jenkins/jobs/Lynx/workspace/lynx/TrueUpdate
Fetching upstream changes from cs:lynx-trueupdate
FATAL: Command git submodule update returned status code 1:
stdout: Cloning into ClientUpdates...
Submodule path 'ClientUpdates': checked out 
'ae2f708d6d69a30e6a54c77b01f0085ab9305000'

stderr: fatal: reference is not a tree: 371a927a4268afc72316e31f9111ad5463305af9
Unable to checkout '371a927a4268afc72316e31f9111ad5463305af9' in submodule path 
'cgi/exe'

hudson.plugins.git.GitException: Command git submodule update returned status 
code 1:
stdout: Cloning into ClientUpdates...
Submodule path