[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Ben Cooksley commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login I wonder if this is due to the non-standard port for Jenkins itself - that configuration uses 8080, whereas my setup uses 8100/8200 (for each of the two impacted instances respectively), and Olli above uses 8180. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203169.1574080196000.5310.1574359200729%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Ben Cooksley commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Could you provide the ProxyPass / ProxyPassReverse statements from your test image? If they mirror the fix I mentioned above already, then this would explain why it works for you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203169.1574080196000.5277.1574356861021%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title
Ben Cooksley commented on JENKINS-60199
Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Sorry, but setting ProxyPreserveHost to On doesn't appear to be a recommendation currently as it isn't mentioned in the default HTTP configuration in your own documentation for this type of setup. It appears under HTTPS, but there is no justification given for why it is there when it isn't for HTTP. See https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache In terms of a minimal reproduction usecase, the following should do the trick:
ServerAdmin webmas...@example.org
ServerName jenkins.example.org
DocumentRoot /srv/www/jenkins.example.org/
ErrorLog ${APACHE_LOG_DIR}/jenkins.example.org-error.log
CustomLog ${APACHE_LOG_DIR}/jenkins.example.org.log combined
AllowEncodedSlashes NoDecode
ProxyRequests Off
ProxyPass / http://127.0.0.1:8200/ nocanon retry=0
ProxyPassReverse / http://127.0.0.1:8200/
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port "443"# Enable SSL
You will need to change ProxyPassReverse to the very incorrect following line to make it work (as ProxyPass / ProxyPassReverse should be mirrors of each other):
ProxyPassReverse / https://127.0.0.1/
This indicates that Jenkins isn't respecting protocols and ports correctly - and setting ProxyPreserveHost just masks the issue (as most people don't run Jenkins without a web server in front of it, so users won't be connecting to it over a non-standard port)
Add Comment
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Ben Cooksley commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Other endpoints, including those used to access build logs are also impacted. Anywhere where a redirect is used seems to be affected. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203169.1574080196000.4605.1574274840264%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Ben Cooksley commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login I've found that for our instances (at build.kde.org and binary-factory.kde.org) that we've needed to use the following Apache snippets to make it work properly: ```AllowEncodedSlashes NoDecode ProxyRequests Off ProxyPass / http://127.0.0.1:8200/ nocanon retry=0 ProxyPassReverse / https://127.0.0.1/``` Given that ProxyPass and ProxyPassReverse should normally mirror each other, it would appear that whatever code is responsible for creating redirects in Jenkins/Jetty is: a) Forcing HTTPS to On b) Disregarding the port that Jenkins itself is listening on c) Disregarding the Canonical URL preference set in Manage Jenkins > Configure in favour of the host it received the request under Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203169.1574080196000.4586.1574272020549%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable Unfortunately we don't have a test environment for this (due to the size of our Jenkins instance and the resources involved in operating even a small number of the jobs on it) and it would need to run jobs in order to try to reproduce this. I'll report back if this issue reoccurs, but for now this can be closed. Thanks for investigating. 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.200981.1564306537000.1740.1566987660958%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable In this case our sequence could broadly be summarised as: 1) Jobs created, using the Pipeline templates as noted above, with an initial branch of Applications/19.04 2) Jobs are then run, at which point Jenkins becomes aware that the jobs are tracking Applications/19.04 3) Jobs are subsequently updated by re-running the DSL Job, which updates the Pipeline templates to refer to Applications/19.08 4) Jobs are run again manually, which should have updated Jenkins to make it aware that Applications/19.08 should now be tracked 5) Subsequent polling results in Applications/19.04 still being polled... Our Pipeline templates (aside from the additional declarations i've posted above) have remained broadly the same for some time now and haven't changed much in quite some time. 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.200981.1564306537000.6780.1566382380177%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable I'm afraid i've not attempted to reproduce this bug, and experimenting with returning our production systems to a potentially broken state isn't really an option. The only thing I could recommend in this case would be using https://invent.kde.org/sysadmin/ci-tooling/blob/master/pipeline-templates/SUSEQt5.12.template as a starting point. The only Stage that matters in that job from the perspective of this bug is the Checkout Sources stage, so you can probably delete the rest without too much impact (although it may be worth forcing the build to always be UNSTABLE) It is worth noting that we were also experiencing issues with job runs not being considered Successful by Jenkins unless they were also Stable, which impacted views as noted above. As only some jobs were experiencing the issue of not having the correct branches polled, it is possible that these two issues are somehow related - especially given they both disappeared when the plugin is installed. Is it possible that the plugin is causing side effects within Jenkins - so it isn't the symlinks themselves that matter - but rather something else that it causes within Jenkins when performing the symlink update - which resolves our problem here? The additional Groovy declarations you'll need to include to use the above template are as follows: ```def repositoryUrl = "git://anongit.kde.org/konsole" def browserUrl = "https://cgit.kde.org/konsole.git" def branchToBuild = "master" def productName = "Applications" def projectName = "konsole" def branchGroup = "kf5-qt5" def currentPlatform = "SUSEQt5.12" def ciEnvironment = "production" def buildFailureEmails = "konsole-de...@kde.org" def unstableBuildEmails = ""``` 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
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable Mark Waite I'm not sure how it managed to make an impact either, however the behaviour we were seeing prior to the restoration of the maintenance of the symlinks by the plugin was the behaviour noted above - namely, that changes to the branch name weren't being picked up. Interestingly, it picked up that the last successful build was 'Applications/19.08', yet for reasons unknown continued to poll an older branch - 'Applications/19.04'. You can find copies of the Pipeline templates, along with the Job DSL scripts we use to provision all the jobs on our Jenkins instance at https://invent.kde.org/sysadmin/ci-tooling/tree/master/ (running of helpers/gather-jobs.py is required prior to trying to evaluate the dsl/*.groovy scripts) To provide a bit of background, we reuse the same jobs when the stable branches for our software changes, and just update the job to refer to the new branches as needed. This functionality has to date worked perfectly reliably, until the release of Jenkins 2.185/2.186 (we jumped straight from 2.184 to 2.186 due to the Trilead SSH issues in 2.185). The solution for us was to install the Symlink plugin, after which normal functionality was restored with 2.186+ 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.200981.1564306537000.4547.1566116100127%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley updated an issue Jenkins / JENKINS-58692 Change in treatment of Success - Stable vs. Unstable Change By: Ben Cooksley Component/s: git-plugin 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.200981.1564306537000.9598.1565170860567%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley updated an issue Jenkins / JENKINS-58692 Change in treatment of Success - Stable vs. Unstable Change By: Ben Cooksley Priority: Major Critical 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.200981.1564306537000.9597.1565170860276%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable Over the past week we've started receiving additional complaints that a number of projects were not getting builds triggered. Examination of the Polling logs would show something like the following: Started on Aug 7, 2019 8:33:46 AM Using strategy: Default [poll] Last Built Revision: Revision 597ffa6a5e89b7e05180ccb3517973b3867d72fa (refs/remotes/origin/Applications/19.08) No credentials specified > git --version # timeout=10 > git ls-remote -h git://anongit.kde.org/konsole # timeout=10 Found 54 remote heads on git://anongit.kde.org/konsole [poll] Latest remote head revision on refs/heads/Applications/19.04 is: 550cd447bc4bb79cc8920a147e84f7afb35406d6 - already built by 2 no polling baseline in /home/jenkins/workspace/Applications/konsole/stable-kf5-qt5 SUSEQt5.12 on Docker Swarm-353db413f644 no polling baseline in /home/jenkins/workspace/Applications/konsole/stable-kf5-qt5 SUSEQt5.12 on Docker Swarm-353db413f644 no polling baseline in /home/jenkins/workspace/Applications/konsole/stable-kf5-qt5 SUSEQt5.12 on Docker Swarm-353db413f644 no polling baseline in /home/jenkins/workspace/Applications/konsole/stable-kf5-qt5 SUSEQt5.12 on Docker Swarm-353db413f644 no polling baseline in /home/jenkins/workspace/Applications/konsole/stable-kf5-qt5 SUSEQt5.12 on Docker Swarm-353db413f644 Done. Took 0.1 sec No changes Examining the Jenkins Core changelog indicated that maintenance of symlinks within Jenkins Core for jobs/projects had been removed and transferred to a plugin. Following installation of that plugin and running jobs again, we've found that correct functionality (both in terms of the branches being polled by Jenkins and the views being updated). As such this now appears to be a regression, and given it prevents Git polling from working properly in certain cases (when it's managed as part of a Declarative Pipeline) it actually breaks core functionality of Jenkins. Add Comment
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Ben Cooksley created an issue Jenkins / JENKINS-58692 Change in treatment of Success - Stable vs. Unstable Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-28 09:35 Priority: Major Reporter: Ben Cooksley We've recently noticed on our Jenkins instance (at build.kde.org) that builds which are unstable are no longer considered "Successful" by Jenkins. This means that all of our views are now broken, because we've used "Successful" as meaning it successfully built (even if tests failed). Our expectations appear to align with the Jenkins terminology guide ( https://wiki.jenkins.io/display/JENKINS/Terminology ) This behaviour appeared sometime after Jenkins 2.184, and can be viewed at https://build.kde.org/job/Applications/view/Everything%20-%20stable-kf5-qt5/job/kopete/job/stable-kf5-qt5%20SUSEQt5.12/ (Note that only Build #1 is considered Successful, even though all builds of that job had the result of being Unstable. The correct behaviour in this instance should be for the latest Successful activity for that job to be Build #4 - as it did complete successfully, even if it is unstable) Add Comment
[JIRA] (JENKINS-51267) Detection of path names does not work
Title: Message Title Ben Cooksley commented on JENKINS-51267 Re: Detection of path names does not work Thanks for that detail. I suspected that may have been the case. I've deployed that change on our side now and have started a build so let's see how that goes. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51267) Detection of path names does not work
Title: Message Title Ben Cooksley commented on JENKINS-51267 Re: Detection of path names does not work Okay. From my understanding, the following regex should already be achieving this (it's double escaped due to being a regex in a Pipeline): 'C:(Program Files \\(x86\\)|Craft)**' Or have I missed something here? (Qt lives under C:\Craft\ so it should be excluded by the above from my understanding) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Ben Cooksley commented on JENKINS-51267 Re: Warnings polluted with unrelated Qt MSBuild warnings Hi Ulli, I'm the administrator of the KDE CI System. We are already setting a file exclusion pattern, as can be seen at https://cgit.kde.org/sysadmin/ci-tooling.git/tree/pipeline-templates/WindowsMSVCQt5.10.template#n126 The actual issue here is a parsing bug on the part of the Jenkins warnings plugin (from what I can see at least), as can be seen at https://build.kde.org/job/Extragear%20kmymoney%20kf5-qt5%20WindowsMSVCQt5.10/78/warnings45Result/ For example: ,QString>': move assignment operator was implicitly defined as deletedC:/Craft/CI/windows-msvc2017_64-cl-debug/include/qt5/QtWidgets Or one of the later issues: ]C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/include/xatomic.h(1204): warning C4365: 'argument': conversion from 'std::_Uint2_t' to 'short', signed/unsigned mismatchC:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/include/xlocnum(1369): warning C4774: 'sprintf_s' : format string expected in argument 3 is not a string literalC:/Craft/CI/windows-msvc2017_64-cl-debug/include/qt5/QtCore It looks like this a bad split across multiple lines? Additionally it looks like the warnings plugin is reformatting some of the paths, for instance: C:/CI/WORKSP~1/EXTRAG~1.10/INSTAL~1/include/KF5/KACTIV~1/kactivities Is this something which is done before the exclusion rule is applied, or after (for presentation purposes)? Additionally, looking at the various "Folders" which Jenkins has picked up it seems that it has missed the last slash in some cases... Any comments on the above would be appreciated. Add Comment
[JIRA] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /
Title: Message Title Ben Cooksley updated an issue Jenkins / JENKINS-27332 git-plugin no longer detects changes of branch with / Change By: Ben Cooksley Priority: Major Blocker 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] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /
Title: Message Title Ben Cooksley commented on JENKINS-27332 Re: git-plugin no longer detects changes of branch with / Can we please have an update on this? It is causing severe issues for the KDE project, as it breaks our commit hook which our current iteration of Jenkins relies upon. Simply forcing builds to occur when pushes are done is incredibly inefficient, and not particularly possible as it wastes precious system resources. Please correct this as soon as possible. See https://build.kde.org/ 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] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /
Title: Message Title Ben Cooksley commented on JENKINS-27332 Re: git-plugin no longer detects changes of branch with / I can confirm the pre-release builds resolve the issue for me as far as I can tell at this stage. JIRA had automatically folded that comment out of my view for some reason Is there a timeline for when this will be fully released? 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] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Ben Cooksley commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError For those looking for an interim solution, downgrading "Static Code Analysis Plug-ins" to 1.62 appears to allow normal functionality to be restored. Could the maintainers of plugins which know they'll be a dependent chain please co-ordinate releases in the future? 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] [analysis-core] (JENKINS-21268) No build.xml is created when warnings plugin is used in combination with deactivated maven plugin
Ben Cooksley commented on JENKINS-21268 No build.xml is created when warnings plugin is used in combination with deactivated maven plugin I can confirm this issue has also bitten KDE and our Jenkins instance at build.kde.org. The above commits do not correct this issue under Jenkins 1.578 with Warnings 4.41, Maven 2.6. I disabled the Maven plugin to deal with other issues that plugin was causing, didn't expect it to cost us 2 weeks worth of build data. As this bug causes data loss, I find a severity of "minor" unusual - please reassign it a more appropriate severity such as "critical". 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] [ircbot] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
Ben Cooksley created JENKINS-24507 Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled Issue Type: Bug Affects Versions: current Assignee: kutzi Components: ircbot Created: 29/Aug/14 11:59 AM Description: Currently a number of our builds are being forced to fail by the IRC Notification component due to the following stacktrace: ERROR: Publisher hudson.plugins.ircbot.IrcPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.im.build_notify.PrintFailingTestsBuildToChatNotifier.getFailedTestsReport(PrintFailingTestsBuildToChatNotifier.java:68) at hudson.plugins.im.build_notify.PrintFailingTestsBuildToChatNotifier.buildCompletionMessage(PrintFailingTestsBuildToChatNotifier.java:37) at hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:577) at hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304) at hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1765) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Switching the Channel Notification Message to anything which does not mention "failed tests" will resolve the issue. It should be noted that this is only a problem if "failed tests" is selected as part of the Channel Notification Message and the build has tests which then fail. Environment: Jenkins 1.577 Project: Jenkins Priority: Blocker Reporter: Ben Cooksley 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] [ircbot] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
Ben Cooksley commented on JENKINS-24507 Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled Yes, the traces look identical. 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] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Ben Cooksley commented on JENKINS-22319 Referencing a purely local git branch breaks checkout Thanks for implementing the change - it is much appreciated. 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] [git] (JENKINS-22319) Updating Git plugin causes existing builds to immediately fail
Ben Cooksley commented on JENKINS-22319 Updating Git plugin causes existing builds to immediately fail Our build process is a little unusual. It is made up of two components: 1) The setup script, which determines the branch to actually build (this information is published in a JSON file) and then creates a branch locally called "jenkins" pointed at this branch. This script runs in the Pre-SCM phase. This can be seen in the above output - "Branch jenkins set up to track remote branch master from origin". 2) The primary build phase. The Git plugin is invoked between component #1 and #2. Does this help? 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] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Ben Cooksley commented on JENKINS-22319 Referencing a purely local git branch breaks checkout The workspace is created before the Pre-SCM plugin executes, so the build never fails. If no pre-existing clone exists our script will make one as needed (it also knows the repository URL). An extreme pity this is seen as a special case considering it worked perfectly fine in the past. I see two possible solutions: 1) Have an absolute last resort possibleQualifiedBranches entry of singleBranch - ie. totally unmodified from the specification passed to it in the build configuration. 2) Consider the case of "refs/*" to always be properly qualified. Which one do you prefer? 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] [git] (JENKINS-22319) Updating Git plugin causes existing builds to immediately fail
Ben Cooksley commented on JENKINS-22319 Updating Git plugin causes existing builds to immediately fail We use a branch which will only exist locally on the build slave for various reasons. This prefixing is likely the cause of this issue - will attach a job definition shortly. 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] [git] (JENKINS-22319) Updating Git plugin causes existing builds to immediately fail
Ben Cooksley updated JENKINS-22319 Updating Git plugin causes existing builds to immediately fail Job configuration as requested. Change By: Ben Cooksley (25/Mar/14 7:42 AM) Attachment: config.xml 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] [git] (JENKINS-22319) Updating Git plugin causes existing builds to immediately fail
Ben Cooksley created JENKINS-22319 Updating Git plugin causes existing builds to immediately fail Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 24/Mar/14 6:45 AM Description: After upgrading from Git plugin 2.0.1 to 2.0.4 all existing builds on our installation fail. Downgrading is the only way to restore system function. The configured branch for each job is correct and does exist locally on the build nodes. An example of a failed build is as follows: Started by remote host 127.0.0.1 with note: Triggered by commit Building remotely on LinuxSlave - 1 (PACKAGER LINBUILDER) in workspace /srv/jenkins/workspace/skrooge_master Running Prebuild steps skrooge_master $ /bin/sh -xe /tmp/hudson1825262203643394596.sh + /home/jenkins/scripts/setup-env.sh Preparing to perform KDE Continuous Integration build == Setting Up Sources From git://anongit.kde.org/skrooge b59ae7b..a449a3e master - origin/master Branch jenkins set up to track remote branch master from origin. == Cleaning Source Tree HEAD is now at b59ae7b feature: Better date filtering in operation page Removing build/ Removing install/ Removing tests/input/kde/ Removing tests/output/ Removing tests/scripts/init.sh Removing tests/sikuli/shared.sikuli/shared$py.class Success build forhudson.tasks.Shell@3420a61b Fetching changes from the remote Git repository Fetching upstream changes from git://anongit.kde.org/skrooge.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. WARNINGS Skipping publisher since build result is FAILURE Skipping Cobertura coverage report as build was not UNSTABLE or better ... Recording test results IRC notifier plugin: Sending notification to: #kde-builds Finished: FAILURE Project: Jenkins Priority: Blocker Reporter: Ben Cooksley 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.
