[JIRA] [hp-application-automation-tools-plugin] (JENKINS-25331) Custom code is not executing when running API tests using HP Application Automation Plug-in
Venkata Praveen B commented on JENKINS-25331 Custom code is not executing when running API tests using HP Application Automation Plug-in Even if the activity (Custom Code) is inside Test Flow, Jenkins plug-in is not executing the custom code written. 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] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz created JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/14 8:56 AM Description: Since the latest update the server log contains the following warnings for various jobs. WARNING: hudson.model.FreeStyleProject@9a4e77f[projectX] did not contain projectX #584 to begin with Environment: Fedora release 20 (Heisenbug) x86_64 OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00 Jenkins ver. 1.591 Project: Jenkins Labels: warnings free-style Priority: Minor Reporter: Steffen Sledz 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] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with see also https://github.com/jenkinsci/jenkins/pull/1440 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-plugin] (JENKINS-25552) Git Polling with keys fails for Windows master and OSX slave
Nicolae Ghimbovschi commented on JENKINS-25552 Git Polling with keys fails for Windows master and OSX slave Putting git.exe in PATH solved the issue when using windows Master - mac Slave. But when using "Require workspace for polling" option, I still get the "ssh: command not found". Which is weird, because the mac has ssh in PATH. Is it trying to use ssh from the windows Master ? 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-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
Nicolae Ghimbovschi resolved JENKINS-25172 as Fixed GIT_SSH not always used for git fetch It is does not reproduce in the latest LTS jenkins Change By: Nicolae Ghimbovschi (26/Nov/14 9:07 AM) Status: Open Resolved Resolution: Fixed 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-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
Nicolae Ghimbovschi commented on JENKINS-25172 GIT_SSH not always used for git fetch With the latest LTS jenkins this does not happen any more. I'll close this bug. 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] [core] (JENKINS-25789) Prepare for Shutdown doesn't allow to restart from http://JENKINS_URL/updateCenter/
Félix Belzunce Arcos created JENKINS-25789 Prepare for Shutdown doesnt allow to restart from http://JENKINS_URL/updateCenter/ Issue Type: Bug Assignee: Félix Belzunce Arcos Components: core Created: 26/Nov/14 9:07 AM Description: 1. Activate the shutdown (Manage Jenkins-Prepare for Shutdown) 2. Update some plugins (Plugin Manager-Updates tab choose some plugins to be updated) 3. Click on Download now and install after restart 4. Cancel the shutdown some minutes later 5. Activate the shutdown again 6. Manage Jenkins-Manage plugins-Updates tab-Download now and install after restart 7. Checkbox Restart Jenkins when installation is complete and no jobs are running is pre-checked. Notice that although the Checkbox Restart Jenkins when installation is complete and no jobs are running is pre-checked, if you click several times in the checkbox very quick the instance restart at the end. Then, you cannot restart from there and needs as a workaround go to for example http://JENKINS_URL/restart Environment: Jenkins ver. 1.580.1 Project: Jenkins Labels: jenkins user-experience Priority: Minor Reporter: Félix Belzunce Arcos 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] [android-emulator-plugin] (JENKINS-23134) Mixed separators fail for Linux paths
Nicolae Ghimbovschi commented on JENKINS-23134 Mixed separators fail for Linux paths Also, adb -s emulator-5834 shell getprop dev.bootcomplete does not work on OSX. 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] [android-emulator-plugin] (JENKINS-23134) Mixed separators fail for Linux paths
Nicolae Ghimbovschi edited a comment on JENKINS-23134 Mixed separators fail for Linux paths Also, adb -s emulator-5834 shell getprop dev.bootcomplete does not work on OSX. It works only with adb connect localhost:5834 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus edited a comment on JENKINS-25676 Disconnect from XMPP after a few minutes This is going a bit out of the realm of the jenkins jabber plugin issue tracker. To summarize how the situation appears to me: Either the server or the clients disconnects the XMPP connection. I know Smack and it would tell you why it did so, and this would appear in the Jenkin's log (of the jabber-plugin). I believe Openfire would also log an message if it terminates the connection for some reason. But openfire being a server, logs also many other things, so it's like looking for the needle in the haystack. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes This is going a bit out of the real of the jenkins jabber plugin issue tracker. To summarize how the situation appears to me: Either the server or the clients disconnects the XMPP connection. I know Smack and it would tell you why it did so, and this would appear in the Jenkin's log (of the jabber-plugin). I believe Openfire would also log an message if it terminates the connection for some reason. But openfire being a server, logs also many other things, so it's like looking for the needle in the haystack. 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] [core] (JENKINS-22028) HTML in job description does not get rendered (all html tags escaped)
Frank van Gemeren commented on JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) Follow-up: I couldn't find Antisamy Plugin anywhere. We fixed it by enabling "OWASP Markup Formatter Plugin". The release notes of 1.553 do not explicitly name this plugin. 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] [android-emulator-plugin] (JENKINS-25790) New adb connect command always fails to connect on OS X
Nicolae Ghimbovschi created JENKINS-25790 New adb connect command always fails to connect on OS X Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 26/Nov/14 9:32 AM Description: With the new version of the Android Emulator Plugin the adb cannot connect to the emulator. This will never succeed to connect to the emulator on OS X: adb -s emulator-5834 shell getprop dev.bootcomplete The old version will work on OS X: adb connect localhost:5834 adb -s localhost:5834 shell getprop dev.bootcomplete Environment: OS X 10.9.5 Jenkins ver. 1.580.1 Android Emulator Plugin v2.12 Android SDK Tools 23.0.5 Android SDK Build-tools 21.1.1 Project: Jenkins Labels: connection failure mac osx android-emulator-plugin adb Priority: Blocker Reporter: Nicolae Ghimbovschi 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] [android-emulator-plugin] (JENKINS-25790) New adb connect command always fails to connect emulator on OS X
Nicolae Ghimbovschi updated JENKINS-25790 New adb connect command always fails to connect emulator on OS X Change By: Nicolae Ghimbovschi (26/Nov/14 9:33 AM) Summary: Newadbconnectcommandalwaysfailstoconnect emulator onOSX 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] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with It seems that this is related to an incomplete Last Changes list. 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] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
valentina armenise commented on JENKINS-25727 Occasional exit status -1 with long latencies tested with the plugin version 1.0. It worked 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] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
rsandell created JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth Issue Type: Bug Assignee: Sam Kottler Components: core, github-oauth-plugin Created: 26/Nov/14 9:58 AM Description: SEVERE: Executor threw an exception java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:542) at org.jenkinsci.plugins.GithubSecurityRealm$2.loadUserByUsername(GithubSecurityRealm.java:494) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:282) Environment: Jenkins 1.580.1 Project: Jenkins Priority: Major Reporter: rsandell 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-plugin] (JENKINS-25792) Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason.
Jacob OhNoYouDont created JENKINS-25792 Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason. Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 26/Nov/14 10:17 AM Description: We've been experiencing problems with out builds for a while now and they've been pretty random. Our builds create a sandbox within the workspace directory and use it to run tests and the sandbox is owned by root(as it's a whole system root). It's not a problem as long as all Jenkins does is fetch new changes from git to that workspace, but if the .git directory gets deleted when Jenkins tries doing a clone and it fails with: Cloning the remote Git repository Cloning repository g...@gitlab.something.net:something/something.git ERROR: Failed to clean the workspace java.nio.file.AccessDeniedException: /srv/jenkins/workspace/some-build-job/ec2-precise32-development/sandbox/jail/sys The .git directory(along with .gitignore) has been disappearing randomly from workspace directories randomly and I've configured auditd service in order to find out which process has been deleting them, because I expected it to be something part of our process(Makefile?) and what I've found is stuff like this: time-Sat Nov 22 08:32:03 2014 type=PATH msg=audit(1416645123.091:196): item=1 name="/srv/jenkins/workspace/xxx/label/ec2-precise32-development/.gitignore" inode=827146 dev=ca:01 mode=0100664 ouid=1000 ogid=1000 rdev=00:00 type=PATH msg=audit(1416645123.091:196): item=0 name="/srv/jenkins/workspace/xxx/label/ec2-precise32-development/" inode=814260 dev=ca:01 mode=040755 ouid=1000 ogid=1000 rdev=00:00 type=CWD msg=audit(1416645123.091:196): cwd="/home/ubuntu" type=SYSCALL msg=audit(1416645123.091:196): arch=4003 syscall=10 success=yes exit=0 a0=9f8be2f0 a1=b774c000 a2=b7709ff4 a3=9f8be2f0 items=2 ppid=1011 pid=4298 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=1 comm="java" exe="/usr/lib/jvm/jdk1.7.0_51/bin/java" key=(null) A java process(Jenkins) executes syscall 10 (unlink/remove) on .gitignore(and I assume .git as well, I don't monitor it because the logs would be overflowing). I have no idea why it does that. This particular deletion has caused a failure in a build four days later. The interesting thing is that on the same slave around the same time (Sat Nov 22 08:32:03 2014) there was another build run, but it was completely different from the one that failed four days later. It used a different workspace directory, so it's hard to say if the two things are related. This has been really messing up with out CI because the builds failing randomly are nightlies. Environment: Jenkins ver. 1.586 System: Ubuntu 12.04.4 LTS 32bit Plugins: Amazon EC2 plugin Ant Plugin Async Http Client Backup plugin Build Monitor View Build Pipeline Plugin build timeout plugin buildgraph-view CloudBees Build Flow plugin Cobertura Plugin conditional-buildstep Config File Provider Plugin Copy Artifact Plugin Credentials Plugin CVS Plug-in Deployed On Column Plugin Dynamic Parameter Plug-in Edgewall Trac Plugin Email-ext plugin embeddable-build-status Environment Injector Plugin Fingerprint Plugin Git Client Plugin Git Parameter Plug-In Git Plugin Git Server Plugin Gitlab Hook Plugin Gitlab Merge Request Builder Green Balls HipChat Plugin Hudson Post build task Javadoc Plugin _javascript_ Widgets Plugin jQuery plugin JUnit Plugin LDAP Plugin Locale plugin Log Parser Plugin Mailer Managed Scripts MapDB API Plugin Matrix Authorization Strategy Plugin Matrix Project Plugin Maven Project Plugin Metadata plugin Monitoring Monitoring external jobs Multijob Plugin Node Iterator API Plugin OWASP Markup Formatter Plugin PAM Authentication plugin Parameterized Trigger plugin Post-Build Script Plug-in promoted builds plugin Rebuilder Reverse Proxy Auth Plugin ruby-runtime Run Condition Plugin S3 publisher plugin SCM API
[JIRA] [ssh-slaves-plugin] (JENKINS-25793) Set ssh KeepAlive
BBVA BBVA updated JENKINS-25793 Set ssh KeepAlive Change By: BBVA BBVA (26/Nov/14 10:29 AM) Description: Short:BeabletoconfiguresshKeepAliveintheadvancedpaneofthesshslave.Long:Wehaveafewconnectionsfrommasterto slave slaves usingssh-slaveplugin.Someoftheseconnectionsgothroughsomenetworkequipmentthatmightconsidertheconnectiondeadifithaventseenactivityinthelastxminutes.Wehavebeenexperiencingsomeconnectivityproblemsandwouldliketorulessh/tcprouteissues. 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] [ssh-slaves-plugin] (JENKINS-25793) Set ssh KeepAlive
BBVA BBVA created JENKINS-25793 Set ssh KeepAlive Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 26/Nov/14 10:27 AM Description: Short: Be able to configure ssh KeepAlive in the advanced pane of the ssh slave. Long: We have a few connections from master to slave using ssh-slave plugin. Some of these connections go through some network equipment that might consider the connection dead if it haven't seen activity in the last x minutes. We have been experiencing some connectivity problems and would like to rule ssh/tcp route issues. Environment: Jenkins ver. 1.580.1 SSH Slaves plugin 1.9 Project: Jenkins Labels: ssh slave keepAlive Priority: Minor Reporter: BBVA BBVA 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] [ssh-slaves-plugin] (JENKINS-25793) Set ssh KeepAlive
BBVA BBVA updated JENKINS-25793 Set ssh KeepAlive Change By: BBVA BBVA (26/Nov/14 10:29 AM) Description: Short:BeabletoconfiguresshKeepAliveintheadvancedpaneofthesshslave.Long:Wehaveafewconnectionsfrommastertoslavesusingssh-slaveplugin.Someoftheseconnectionsgothroughsomenetworkequipmentthatmightconsidertheconnectiondeadifithasntseenactivityinthelastxminutes.Wehavebeenexperiencingsomeconnectivityproblemsandwouldliketorule out ssh/tcprouteissues. 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] [ssh-slaves-plugin] (JENKINS-25793) Set ssh KeepAlive
BBVA BBVA updated JENKINS-25793 Set ssh KeepAlive Change By: BBVA BBVA (26/Nov/14 10:29 AM) Description: Short:BeabletoconfiguresshKeepAliveintheadvancedpaneofthesshslave.Long:Wehaveafewconnectionsfrommastertoslavesusingssh-slaveplugin.Someoftheseconnectionsgothroughsomenetworkequipmentthatmightconsidertheconnectiondeadifit haven hasn tseenactivityinthelastxminutes.Wehavebeenexperiencingsomeconnectivityproblemsandwouldliketorulessh/tcprouteissues. 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] [monitoring-plugin] (JENKINS-24838) Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context
evernat commented on JENKINS-24838 Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context Any news? Note that I have not reproduced the issue (monitoring plugin v1.53.0, Jenkins v1.585). So if you don't give more information as asked in the comment above, this can't be fixed. 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] [parameterized-trigger-plugin] (JENKINS-25794) Possibility to trigger a job with all available parameters
Sven K created JENKINS-25794 Possibility to trigger a job with all available parameters Issue Type: Improvement Assignee: huybrechts Attachments: screen_job.png, screen_settings.png Components: parameterized-trigger-plugin Created: 26/Nov/14 11:24 AM Description: I have a job with choice parameter to specify an ant target (target=test or target=productive or target=release). Based on this target the job checks out the project into a specific directory and calls this target. Now I want to use parametrized-trigger-plugin to trigger the job 3 times with all 3 parameters. This is possible but the I have to add the trigger-instruction 3 times (see screen_settings.png for sample job settings) and I don't see the parameters in the overview-page (see screen_job.png). I think this could be improved. It would be nice if there was the possibility to set multiple values for one predefined parameter key, or (even better) if it was possible to specify that all available values for a paramter should be triggered. The problem right now is that I would have to maintain two jobs: The job that has the parameters for different ant targets and also the Build-All-Job (if the targets/parameters change). Maybe there's already another plugin that does this or I'm doing something wrong? Thanks for help in advance. Project: Jenkins Priority: Major Reporter: Sven K 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] [core] (JENKINS-25795) The Test drive in the Meet Jenkins wiki page needs a link
evernat created JENKINS-25795 The Test drive in the Meet Jenkins wiki page needs a link Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/14 11:44 AM Description: A http link should be added on the "Launch Jenkins" words to http://jenkins-ci.org/jenkins.jnlp in the "Test drive" of the "Meet Jenkins" wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins#MeetJenkins-TestDrive Without that link, that "Test drive" goes nowhere. Note that the link was present some time ago. And http://jenkins-ci.org/jenkins.jnlp works now in JavaWebStart (it was fixed by JENKINS-14924). The "Meet Jenkins" page is locked so a wiki admin is needed. Project: Jenkins Priority: Major Reporter: evernat 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] [core] (JENKINS-25795) The Test drive in the Meet Jenkins wiki page needs a link
evernat assigned JENKINS-25795 to Daniel Beck The Test drive in the Meet Jenkins wiki page needs a link Change By: evernat (26/Nov/14 11:46 AM) Assignee: DanielBeck 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] [core] (JENKINS-25795) The Test drive in the Meet Jenkins wiki page needs a link
evernat updated JENKINS-25795 The Test drive in the Meet Jenkins wiki page needs a link Change By: evernat (26/Nov/14 11:45 AM) Description: Ahttplinkshouldbeadded ontheLaunchJenkinswords tohttp://jenkins-ci.org/jenkins.jnlp ontheLaunchJenkinswords intheTestdriveoftheMeetJenkinswikipage:https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins#MeetJenkins-TestDriveWithoutthatlink,thatTestdrivegoesnowhere.Notethatthelinkwaspresentsometimeago.Andhttp://jenkins-ci.org/jenkins.jnlpworksnowinJavaWebStart(itwasfixedbyJENKINS-14924).TheMeetJenkinspageislockedsoawikiadminisneeded. 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] [core] (JENKINS-22514) Zip generated from all files in zip contains the wrong slashes
Daniel Beck commented on JENKINS-22514 Zip generated from all files in zip contains the wrong slashes steven sun Consider reading the preceding comment(s) before writing one of your own I moved the changelog entry to reflect reality. 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] [core] (JENKINS-22028) HTML in job description does not get rendered (all html tags escaped)
Daniel Beck commented on JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) Frank: That's the one. "OWASP Markup Formatter Plugin" is what it's called on the UI. Its ID is antisamy-markup-formatter, and its file name (in JENKINS_HOME/plugins) is antisamy-markup-formatter.hpi/jpi, so that's the name by which I know it. Sorry about that. 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] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Daniel Beck commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with It seems that this is related to an incomplete Last Changes list. What do you mean? This occurs both for deleting single builds manually, as well as builds removed by log rotation. 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] [core] (JENKINS-25704) Scheduled triggering stops working until restart
Daniel Beck commented on JENKINS-25704 Scheduled triggering stops working until restart Are you changing date/time on the Jenkins master, e.g. during tests? 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] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with In jobs where this warning occurs the displayed Last Changes list does contain items for older builds only. The most recent changes are missing. 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-plugin] (JENKINS-25792) Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason.
Mark Waite commented on JENKINS-25792 Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason. That's an interesting report. I'm not aware of any case where the repository is wiped (which would remove the .git directory and the .gitignore file) without either a job configuration which says the workspace should be wiped, or a user action to wipe the workspace. Does it happen with any other job than the specific job which shows the problem? Do you have a history of the configuration of the problem job? Does that history show any significant change at the time the repository was wiped? Do your users have the permission to use the "Wipe out workspace" link that is usually available with each job? Could one of the users have chosen to wipe out that workspace? 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] [multiple-scms-plugin] (JENKINS-25787) Repository Browser broken with Multiple SCMs plugin
Daniel Beck updated JENKINS-25787 Repository Browser broken with Multiple SCMs plugin From https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin section "Limitations": Repository browser configuration is also not supported in the current version. Looks like the Multiple SCMs authors consider this a bug in their plugin. Change By: Daniel Beck (26/Nov/14 12:05 PM) Labels: git-pluginmultiple-scms scm Assignee: NicolasDeLoof KevinBell Component/s: multiple-scms-plugin Component/s: git-plugin 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] [core] (JENKINS-25789) Prepare for Shutdown doesn't allow to restart from http://JENKINS_URL/updateCenter/
Daniel Beck resolved JENKINS-25789 as Duplicate Prepare for Shutdown doesnt allow to restart from http://JENKINS_URL/updateCenter/ Duplicates JENKINS-17324. Change By: Daniel Beck (26/Nov/14 12:06 PM) Status: Open Resolved Resolution: Duplicate 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] [core] (JENKINS-25789) Prepare for Shutdown doesn't allow to restart from http://JENKINS_URL/updateCenter/
Daniel Beck commented on JENKINS-25789 Prepare for Shutdown doesnt allow to restart from http://JENKINS_URL/updateCenter/ Also, ZD-13739. 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] [maven-metadata-plugin] (JENKINS-23206) ARTIFACT_URL is not correctly resolved for SNAPSHOT artifacts
Mathieu POUSSE commented on JENKINS-23206 ARTIFACT_URL is not correctly resolved for SNAPSHOT artifacts I did it, added some unit tests, tested on my jenkins ci see my pull request #5 HIH 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] [parameterized-trigger-plugin] (JENKINS-25794) Possibility to trigger a job with all available parameters
Daniel Beck commented on JENKINS-25794 Possibility to trigger a job with all available parameters Wouldn't using a Matrix (multi-configuration) project for the downstream job work? 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] [multiple-scms-plugin] (JENKINS-25787) Repository Browser broken with Multiple SCMs plugin
Steffen Sledz commented on JENKINS-25787 Repository Browser broken with Multiple SCMs plugin What a pity. 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] [docker-build-step-plugin] (JENKINS-25796) Cannot pass --link parameter to Start docker container step
Alex Chevelev created JENKINS-25796 Cannot pass --link parameter to Start docker container step Issue Type: New Feature Assignee: vjuranek Components: docker-build-step-plugin Created: 26/Nov/14 12:20 PM Project: Jenkins Priority: Major Reporter: Alex Chevelev 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-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Mark Waite commented on JENKINS-25639 Multiple builds can be triggered for same commit The git-client-plugin fix needed for this is included in git-client-plugin 1.12.0. That fix is necessary, but not sufficient to fix the bug. A change will also be needed in the git-plugin. 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-plugin] (JENKINS-25797) jgit is not pushing branch in git publisher
Kanstantsin Shautsou created JENKINS-25797 jgit is not pushing branch in git publisher Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 26/Nov/14 12:23 PM Description: have no more details, but with the same configuration git publisher pushed branch only when i switched back from jgit to git tool. Project: Jenkins Priority: Minor Reporter: Kanstantsin Shautsou 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] [core] (JENKINS-25704) Scheduled triggering stops working until restart
David Resnick commented on JENKINS-25704 Scheduled triggering stops working until restart No. AFAIK there are no changes taking place in the environment. The latest time it stopped triggering was in the middle of the night. 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] [core] (JENKINS-25704) Scheduled triggering stops working until restart
David Resnick commented on JENKINS-25704 Scheduled triggering stops working until restart No building is done on the master, though a couple do run there (e.g. the Reviewbot2 one in the log above). 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] [build-failure-analyzer-plugin] (JENKINS-25798) Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16
Hallvard Nygård created JENKINS-25798 Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16 Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 26/Nov/14 12:33 PM Description: After upgrading some plugins, I got the following error in main build view and project view: Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph at com.sonyericsson.jenkins.plugins.bfa.model.dbf.BuildFlowDBF.getDownstreamBuilds(BuildFlowDBF.java:59) *Is Build Flow 0.16 incompatible with Build Failure Analyzer 1.10.3?* Upgraded plugins: Build Flow Plugin, 0.12 - 0.16, https://github.com/jenkinsci/build-flow-plugin/compare/build-flow-plugin-0.12...build-flow-plugin-0.16 Build Monitor Plugin, 1.5+build.123 - 1.6+build.132 Gerrit trigger, 2.11.1 - 2.12.0ll #147) Git Client Plugin, 1.10.1 - 1.11.1 Matrix Project Plugin, 1.3 - 1.4 Maven Project Plugin, 2.6 - 2.8 SSH Credentials Plugin, 1.9 - 1.10 Subversion Plugin, 2.4.3 - 2.4.5 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/D:/Jenkins/war/WEB-INF/lib/jenkins-core-1.578.jar!/hudson/model/AbstractProject/main.jelly:59:66: st:include org.apache.commons.jelly.JellyTagException: org/jgrapht/DirectedGraph at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25798) Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16
Hallvard Nygård commented on JENKINS-25798 Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16 Downgraded Build Flow to 0.12 again and Build Failure Analyzer started working again. 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] [build-failure-analyzer-plugin] (JENKINS-25798) Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16
Hallvard Nygård
updated JENKINS-25798
Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16
Change By:
Hallvard Nygård
(26/Nov/14 12:44 PM)
Description:
Afterupgradingsomeplugins,Igotthefollowingerrorinmainbuildviewandprojectview:{noformat} Causedby:java.lang.LinkageError:org/jgrapht/DirectedGraph atcom.sonyericsson.jenkins.plugins.bfa.model.dbf.BuildFlowDBF.getDownstreamBuilds(BuildFlowDBF.java:59){noformat}*
*
IsBuildFlow0.16incompatiblewithBuildFailureAnalyzer1.10.3?*
*
Upgradedplugins:-BuildFlowPlugin,0.12-0.16,https://github.com/jenkinsci/build-flow-plugin/compare/build-flow-plugin-0.12...build-flow-plugin-0.16-BuildMonitorPlugin,1.5+build.123-1.6+build.132-Gerrittrigger,2.11.1-2.12.0ll#147)-GitClientPlugin,1.10.1-1.11.1-MatrixProjectPlugin,1.3-1.4-MavenProjectPlugin,2.6-2.8-SSHCredentialsPlugin,1.9-1.10-SubversionPlugin,2.4.3-2.4.5{noformat} javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/D:/Jenkins/war/WEB-INF/lib/jenkins-core-1.578.jar!/hudson/model/AbstractProject/main.jelly:59:66:st:includeorg.apache.commons.jelly.JellyTagException:org/jgrapht/DirectedGraph atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
[JIRA] [git-plugin] (JENKINS-25792) Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason.
Jacob OhNoYouDont commented on JENKINS-25792 Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason. Does it happen with any other job than the specific job which shows the problem? As far as I can tell it doesn't. The job is split through a user defined axis into 7 separate jobs so it's run on multiple slaves. This is done so actually finishes in one hight. This splits the tasks we test into 7 about equal parts. The configuration does not state the workspace should be wiped. The interesting thing is that this loss of .git and .gitignore happens only to one of the parts one one of the slaves out of the 7, seemingly at random. Last time it was the 2nd part. Before we split it into 6 parts and then the failing one was usually the 6th one. Do you have a history of the configuration of the problem job? Not really, but then again it is our nightly, it's been set up the same way(excluding the number of parts) for a very long time. Do your users have the permission to use the "Wipe out workspace" link that is usually available with each job? Yes, they do, but it's only a few developers and they know about our problems with builds. Could one of the users have chosen to wipe out that workspace? Unlikely. Besides, wouldn't that delete the WHOLE workspace(or to be exact, it would try, but fail on the jail which is owned by root), and not just .git and .gitignore? Also, wouldn't that wipe the workspace only on the Jenkins master? The .git and .gitignore files disappear only from the 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 -- 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] [bitbucket-pullrequest-builder-plugin] (JENKINS-25799) Bitbucket Pull Request Builder plugin does not work behind a proxy
Angel López Cima created JENKINS-25799 Bitbucket Pull Request Builder plugin does not work behind a proxy Issue Type: Bug Assignee: Unassigned Attachments: fix_proxy-1.4.1.patch Components: bitbucket-pullrequest-builder-plugin Created: 26/Nov/14 12:50 PM Description: Bitbucket Pull Request Builder plugin can not connect to bitbucket.org if the Jenkins is behind a proxy. I attached a patch that solves this bug. This solution uses the http client SystemDefaultHttpClient in the org.apache.httpcomponents:httpclient instead of using the HttpClient in commons-http library. This class use the system properties to configure a proxy as described in https://docs.oracle.com/javase/7/docs/api/java/net/doc-files/net-properties.html. Another solution is the get the Jenkins' proxy configuration: jenkins.model.Jenkins.getInstance().proxy Environment: Jenkins 1.590, bitbcuket-pullrequest-builder-plugin 1.4.1 Project: Jenkins Priority: Minor Reporter: Angel López Cima 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] [promoted-builds-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Tobias Bertelsen
commented on JENKINS-15980
Promotion job doesnt execute on the same machine that the build job executed on.
Thanks for the comments. I have read a lot more up on it, and I know better understand why the behavior is like it is.
It's sufficient to read the big yellow warning on https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin –
I don't think it will help to rephrase the warning, since it is in the wrong place. You need that information when you are configurating your promotion, not when you are installing the plugin. The person creating the promotions will most likely never have seen the install page, unless your company has a single person managing all builds on Jenkins and its installation.
Secondly I don't find the advice to use permalink very useful, since it can only refer to the latest build/promotion. The promotion is tied to a specific build, so it does not make much sense to use artifacts from a newer version of the build.
I have not been able to find any documentation/guide/tutorial describing this properly, so I decided to write one here. In short: you should set build number to ${PROMOTED_NUMBER} instead of using a permalink, when you copy artifacts.
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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
miguel Rodrigues edited a comment on JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete I've been experiencing this issue also. Jenkins logs don't give more information. It is intermittent, regardless of no changes. Any ideas? Since this plugin hasn't been upgrade for a while now, does anyone have any suggestions on alternatives? 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] [promoted-builds-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Daniel Beck commented on JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. I don't think it will help to rephrase the warning, since it is in the wrong place. You need that information when you are configurating your promotion, not when you are installing the plugin. My point was that the advice not to rely on the workspace is documented. Sure, it could be placed inside some inline help block, but it exists. As such this can hardly be considered a bug. Note that many plugins rely on their wiki page for documentation, since it can be updated without requiring a plugin release, and update by users, and needs not be tied to a specific option. The wiki page of the plugin providing an option is linked from (almost) every inline help block. 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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Daniel Beck commented on JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete https://github.com/jenkinsci/join-plugin/blob/master/src/main/java/join/JoinAction.java#L120 This may occur when the build that was configured to use the join trigger was running on a node that has been removed between the build finishing and the downstream build finishing. (I don't think it's sufficient to take it offline I'd expect a different error but that may also be enough.) 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] [build-failure-analyzer-plugin] (JENKINS-25798) Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16
Daniel Beck commented on JENKINS-25798 Caused by: java.lang.LinkageError: org/jgrapht/DirectedGraph after upgrading Build Flow to 0.16 Weird. Nothing about JGraph in Build Flow changed recently. What happens when you upgrade again? Maybe it was a transient error? Possibly related to the removal of Buildgraph-View, but since both plugins depend on Jgraph, even in the same version, and neither blacks it out, I'm don't know how this could happen. 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-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky commented on JENKINS-25172 GIT_SSH not always used for git fetch which LTS version corrects this? 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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
miguel Rodrigues commented on JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete @Daniel Beck That is a good assumption, given that my use case is various EC2 instances running the jobs in parallel. some jobs take more time than other, and the node where the parent job is running was probably removed when the job that lasts the most ends. 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-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
Nicolae Ghimbovschi commented on JENKINS-25172 GIT_SSH not always used for git fetch Jenkins ver. 1.580.1 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] [http_request] (JENKINS-25801) HTTP Request plugin does not work behind a proxy
Angel López Cima created JENKINS-25801 HTTP Request plugin does not work behind a proxy Issue Type: Bug Assignee: Janario Oliveira Attachments: fix_proxy-1.8.5.patch Components: http_request Created: 26/Nov/14 2:04 PM Description: HTP Request plugin can not connect if the Jenkins is behind a proxy. I attached a patch that solves this bug. This solution uses the http client SystemDefaultHttpClient instead of using the DefaultHttpClient. This class use the system properties to configure a proxy as described in https://docs.oracle.com/javase/7/docs/api/java/net/doc-files/net-properties.html. Environment: Jenkins 1.590, http_request 1.8.5 Project: Jenkins Priority: Minor Reporter: Angel López Cima 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] [naginator-plugin] (JENKINS-25800) parseLog() in NaginatorListener.java does not close its BufferedReader or FileReader, leaking OS resources
Martin Smith commented on JENKINS-25800 parseLog() in NaginatorListener.java does not close its BufferedReader or FileReader, leaking OS resources Submitted a PR to the project to add a try/finally block. https://github.com/jenkinsci/naginator-plugin/pull/12 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-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky commented on JENKINS-25172 GIT_SSH not always used for git fetch thanks! I just tried Jenkins 1.591 with Git Plugin 2.2.6 and it works. 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] [hipchat-plugin] (JENKINS-25802) Notification for failure to success transition
Jay Perry created JENKINS-25802 Notification for failure to success transition Issue Type: Bug Assignee: Unassigned Components: hipchat-plugin Created: 26/Nov/14 2:21 PM Description: I would have expected the back to normal notification to send a notification when the build goes from failure - success. Is there such an option if this doesn't do this. Seems like something that should have been supported from the start. Thanks! Project: Jenkins Priority: Minor Reporter: Jay Perry 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] [remoting] (JENKINS-25803) Slave ping timeout ; build hangs
Wannes Sels created JENKINS-25803 Slave ping timeout ; build hangs Issue Type: Bug Assignee: Unassigned Components: remoting Created: 26/Nov/14 2:30 PM Description: Slave stops responding for whatever reason. First ping thread notices slave does not respond: Nov 26, 2014 2:00:59 PM INFO hudson.slaves.ChannelPinger$1 onDead Ping failed. Terminating the channel. java.util.concurrent.TimeoutException: Ping started on 1417006619758 hasn't completed at 1417006859758 at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) (would be nice if we could see which channel/slave) A bit later: Nov 26, 2014 2:14:34 PM WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor Failed to monitor SV-ARG-DEV-D23 for Clock Difference hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:541) at hudson.remoting.Request.callAsync(Request.java:208) at hudson.remoting.Channel.callAsync(Channel.java:766) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280) Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:1027) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1417006619758 hasn't completed at 1417006859758 ... 2 more Yet node is not shown as offline, and still shows as executor busy. Threaddump shows executor thread on master: Executor #0 for DWI01164 : executing OKA.R201501/Team D/_publics/Public - 4 #103 / waiting for hudson.remoting.Channel@3b91e986:DWI01164 "Executor #0 for DWI01164 : executing OKA.R201501/Team D/_publics/Public - 4 #103 / waiting for hudson.remoting.Channel@3b91e986:DWI01164" Id=16260 Group=main TIMED_WAITING on hudson.remoting.UserRequest@e4ca0c4 at java.lang.Object.wait(Native Method) waiting on hudson.remoting.UserRequest@e4ca0c4 at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy56.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956) at hudson.Launcher$ProcStarter.join(Launcher.java:367) at hudson.tasks.Maven.perform(Maven.java:328) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) It looks like ChannelPinger calls channel.close() which sets channel.outClosed , yet Request is stuck in a loop checking for channel.isInClosed(), which was not set. Should Request check for channel.isClosingOrClosed()? Environment: LTS 1.565.2 slave 2.48 Project: Jenkins Priority: Major Reporter: Wannes Sels This message is automatically generated by JIRA. If
[JIRA] [parameterized-trigger-plugin] (JENKINS-25794) Possibility to trigger a job with all available parameters
Sven K commented on JENKINS-25794 Possibility to trigger a job with all available parameters You're right, in this basic example it would work . But if I had another project (module) which has also a number of targets (parameters) that I want to trigger all in the downstream jon, then this won't be nice with Matrix project because I would have to set a combination filter. It would be therefore great if the plugin would offer the possibility to call a jobs several times with "all avaliable parameters". 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration I can confirm that the ClearCase plugin is the problem. I've uninstalled this plugin (I don't need it) and saving data is now OK. 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] [core] (JENKINS-25704) Scheduled triggering stops working until restart
David Resnick edited a comment on JENKINS-25704 Scheduled triggering stops working until restart No building is done on the master, though a couple jobs do run there (e.g. the Reviewbot2 one in the log above). 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] [core] (JENKINS-25704) Scheduled triggering stops working until restart
David Resnick edited a comment on JENKINS-25704 Scheduled triggering stops working until restart No. AFAIK there are no changes taking place in the environment. The last time triggers stopped was in the middle of the night. 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] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: podskalsky (26/Nov/14 2:57 PM) Component/s: clearcase-plugin 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] [core] (JENKINS-25755) SPDY is not working on 1.580
Ireneusz Makowski commented on JENKINS-25755 SPDY is not working on 1.580 Yes it's true: 1. I've tried on port 80 (proxy through apache) - not working 2. I've tried directly through 8080 port on Winstone-Jetty - not working 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] [core] (JENKINS-25657) JUnit crashes during recording of test results in 1.580.1
Ireneusz Makowski updated JENKINS-25657 JUnit crashes during recording of test results in 1.580.1 Change By: Ireneusz Makowski (26/Nov/14 3:05 PM) Component/s: core 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] [script-security-plugin] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkuns core APIs
ikedam commented on JENKINS-25804 Whitelisted signature presets for Java standard APIs and Jenkuns core APIs The way to provide presets: Built into script-security Built into script-security and administrators can switch enabled/disabled. For the case administrators want complete restriction. script-security provides "import signatures from a file" and signature files are distributed on Wiki page. For the case administrators don't want presets updated with plugin updates. 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] [script-security-plugin] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkuns core APIs
ikedam created JENKINS-25804 Whitelisted signature presets for Java standard APIs and Jenkuns core APIs Issue Type: New Feature Assignee: Jesse Glick Components: script-security-plugin Created: 26/Nov/14 3:15 PM Description: Administrators often approve signatures for fundamental methods. Ones in Java APIs like String.parseInt Ones in Jenkins core like Result#isBetterThan It's not useful that administrators have to approve all those methods. And plugins would be preferred to provide methods returning primitive types. I want whitelisted signature presets. Project: Jenkins Priority: Major Reporter: ikedam 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-plugin] (JENKINS-25792) Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason.
Mark Waite commented on JENKINS-25792 Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason. I wonder if you're encountering something like the condition that is described in JENKINS-13685. Could you review that bug report and see if it might match your case? 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-plugin] (JENKINS-25792) Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason.
Jacob OhNoYouDont
commented on JENKINS-25792
Jenkins deletes .git and .gitignore in workspaces randomly for no apparent reason.
Well for one we don't use the "Clean after checkout" option for git settings. Also we don't get the two copies of the repo, one made by the master and one made by the slave. Copies of repo on slaves end up only in:
/srv/jenkins/workspace/PROJECT_NAME/K/{1-7}/label/ec2-precise32-development/
Where K is the axis that splits the job into multiple builds when run.
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-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Mark Waite resolved JENKINS-25639 as Fixed Multiple builds can be triggered for same commit The fix is now included in the 2.2.x branch and the master branch and should be available on the next release of each of those branches. Likely version numbers 2.2.10 and 2.3.1. Change By: Mark Waite (26/Nov/14 3:45 PM) Status: InProgress Resolved Resolution: Fixed 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-client-plugin] (JENKINS-25351) NoClassDefFoundError: ... GitClient: pasting a repository URL
Mark Waite closed JENKINS-25351 as Cannot Reproduce NoClassDefFoundError: ... GitClient: pasting a repository URL Change By: Mark Waite (26/Nov/14 4:02 PM) Status: Resolved Closed 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-client-plugin] (JENKINS-25351) NoClassDefFoundError: ... GitClient: pasting a repository URL
Mark Waite resolved JENKINS-25351 as Cannot Reproduce NoClassDefFoundError: ... GitClient: pasting a repository URL Cannot reproduce the bug. Change By: Mark Waite (26/Nov/14 4:02 PM) Status: Open Resolved Resolution: CannotReproduce 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] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Core needs to be more resilient wrt form field names by plugins, so core should be fixed IMO. ClearCase did nothing wrong, just bad interaction. 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] [maven-plugin] (JENKINS-20594) Expose parsed maven project version
Michail Plushnikov commented on JENKINS-20594 Expose parsed maven project version +1 Very useful to build pipelines! 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up
Al Ferguson updated JENKINS-25805 Use pretested integration doesnt show up Change By: Al Ferguson (26/Nov/14 4:38 PM) Description: SectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhilethePretestedIntegrationpost-build isavailableinthe Addpost-buildaction dropdown,sectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhyUsepretestedintegrationdoesntshowup?Conflictwithanotherplugin?Somethingmissing? 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up
Al Ferguson created JENKINS-25805 Use pretested integration doesnt show up Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 26/Nov/14 4:37 PM Description: Section 'Use pretested integration' does not appear in the Job configuration page. While the 'Pretested Integration post-build is available in the Add post-build action dropdown, section 'Use pretested integration' does not appear in the Job configuration page. Why 'Use pretested integration' doesn't show up? Conflict with another plugin? Something missing? Environment: Jenkins 1.545 Jenkins GIT plugin 2.2.9 Pretested integration plugin 2.1.2 JDK 1.7.0_45 os Linux amd64 2.6.32-5 Project: Jenkins Priority: Blocker Reporter: Al Ferguson 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up
Al Ferguson updated JENKINS-25805 Use pretested integration doesnt show up Change By: Al Ferguson (26/Nov/14 4:49 PM) Description: Formaven2/3projects(okforfree-stylesoftwareprojects...). SectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhilethePretestedIntegrationpost-buildisavailableintheAddpost-buildactiondropdown,sectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhyUsepretestedintegrationdoesntshowup?Conflictwithanotherplugin?Somethingmissing? 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up
Al Ferguson updated JENKINS-25805 Use pretested integration doesnt show up Change By: Al Ferguson (26/Nov/14 4:50 PM) Description: Formaven2/3projects only (okforfree-stylesoftwareprojects ... ).SectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhilethePretestedIntegrationpost-buildisavailableintheAddpost-buildactiondropdown,sectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhyUsepretestedintegrationdoesntshowup?Conflictwithanotherplugin?Somethingmissing? 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up
Al Ferguson updated JENKINS-25805 Use pretested integration doesnt show up Change By: Al Ferguson (26/Nov/14 4:50 PM) Description: Formaven2/3projectsonly(okforfree-stylesoftwareprojects).SectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage ofmaven2/3projects .WhilethePretestedIntegrationpost-buildisavailableintheAddpost-buildactiondropdown,sectionUsepretestedintegrationdoesnotappearintheJobconfigurationpage.WhyUsepretestedintegrationdoesntshowup?Conflictwithanotherplugin?Somethingmissing? 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up for maven projects
Al Ferguson updated JENKINS-25805 Use pretested integration doesnt show up for maven projects Change By: Al Ferguson (26/Nov/14 4:59 PM) Summary: Usepretestedintegrationdoesntshowup formavenprojects 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] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Jesse Glick assigned JENKINS-25788 to Jesse Glick WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with Change By: Jesse Glick (26/Nov/14 5:02 PM) Assignee: JesseGlick 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] [script-security-plugin] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkuns core APIs
Jesse Glick commented on JENKINS-25804 Whitelisted signature presets for Java standard APIs and Jenkuns core APIs The plugin already ships with a small static whitelist. It needs to be greatly expanded to cover clearly safe Java platform APIs (such as string manipulation), as well as neutral things in the Jenkins API. (Anything in the Jenkins API which calls checkPermission is generally OK to whitelist given a permissions check—this is a separate whitelist mode.) I think it is best to just have this default whitelist be bundled in the plugin, so we can use routine plugin updates to distribute it. And I see no reason to make it configurable. Either there is a known (or reasonably suspected) risk from some method in the standard whitelist, in which case it should be removed and a plugin update distributed as a regular security fix; or there is not, and it should be included. Administrators should not be expected to do the deep thinking. 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] [artifactdeployer-plugin] (JENKINS-25806) Artifact Deployer plugin 0.32 doing nothing
pedro reis created JENKINS-25806 Artifact Deployer plugin 0.32 doing nothing Issue Type: Bug Assignee: Gregory Boissinot Attachments: try_use_artifact_deployer.png Components: artifactdeployer-plugin Created: 26/Nov/14 5:42 PM Description: Hi, I was trying to use Artifact Deployer plugin but it is not working and not outputting anything to console. As you see at the attachment, I even set up to "Fail build if there are no files to deploy". No error is appearing: No read artifacts error and no write to destination is appearing. No message is appearing. And No file is being delivered at our smb server. It is normal for this plugin to operate without any console writings? (I also assume, by reading https://wiki.jenkins-ci.org/display/JENKINS/ArtifactDeployer+Plugin, that doing Archive Artifacts is not necessary as a previous step.) Environment: Jenkins ver. 1.565.3 plugin version 0.32 Project: Jenkins Labels: plugin Priority: Minor Reporter: pedro reis 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] [mask-passwords-plugin] (JENKINS-25735) Mask Passwords doen't mask Credentials Parameter
Marshall GSEIT commented on JENKINS-25735 Mask Passwords doent mask Credentials Parameter Daniel, thank you so much for your time. If I enable "This build is parameterized", and add an existing "Username with password" credential. The build outputs a GUID. E.g. @echo oracleCredentialParameter=%oracleCredentialParameter% will display oracleCredentialParameter=3F2504E0-4F89-41D3-9A0C-0305E82C3301 The behavior is the same whether I select "Mask passwords" or not. I also tried adding a "String Parameter". In this case the build output the correct information. E.g. @echo oracleUsername=%oracleUsername% will display oracleUsername=ThisIsMyOracleUsername But, like above, the behavior is the same whether I select "Mask passwords" or not. 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] [core] (JENKINS-14713) Cancel permission is granted for users having build permission
Jon Radon commented on JENKINS-14713 Cancel permission is granted for users having build permission I would also like to see this fixed. 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] [role-strategy-plugin] (JENKINS-25036) maximum number of jenkins user reached
george trubisky assigned JENKINS-25036 to george trubisky maximum number of jenkins user reached Change By: george trubisky (26/Nov/14 6:35 PM) Assignee: OlegNenashev georgetrubisky 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] [mask-passwords-plugin] (JENKINS-25735) Mask Passwords doen't mask Credentials Parameter
Daniel Beck commented on JENKINS-25735 Mask Passwords doent mask Credentials Parameter The behavior is the same whether I select "Mask passwords" or not. That parameter type only provides the UUID (which isn't particularly sensitive), and needs plugins to cooperate to get the data out from the credentials store. However, I expect if the password were printed somehow, it'd be masked correctly. 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-plugin] (JENKINS-25552) Git Polling with keys fails for Windows master and OSX slave
Mark Waite commented on JENKINS-25552 Git Polling with keys fails for Windows master and OSX slave It is unlikely to be attempting to use the ssh from the Windows master. That would require changes to the git compiled executable on your mac. The "ssh: command not found" is a message from command line git. Command line git is invoked by the Jenkins git plugin, then command line git decides (within the compiled git program) that it needs to invoke the ssh command. My guess is that the PATH environment variable on the machine hosting the workspace (the mac) is wrong. It does not have ssh in the path. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes I am somewhat happy to say that we've figured this out. See here: https://pidgin.im/pipermail/tracker/2010-March/060960.html Our older openfire server will disconnect after 6 minutes. This doesn't affect pidgin users because of the above patch. Jenkins, however, does not send keepalive packets and is disconnected after 6 minutes of inactivity. As a workaround, I made a job that has Jenkins IM itself every 5 minutes. Is it possible to add a keepalive, similar to Pidgin, to Jabber? 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up for maven projects
Daniel Beck updated JENKINS-25805 Use pretested integration doesnt show up for maven projects The build wrapper is deliberately only available in Freestyle projects: https://github.com/jenkinsci/pretested-integration-plugin/blob/master/src/main/java/org/jenkinsci/plugins/pretestedintegration/PretestedIntegrationBuildWrapper.java#L186 Therefore reducing priority as it's probably just the publisher showing up when it shouldn't, and it's easy enough to prevent that: For those plugins that don't want Publisher to show up in different job type, use BuildStepDescriptor for the base type of your descriptor to control which job type it supports. Change By: Daniel Beck (26/Nov/14 7:14 PM) Priority: Blocker Minor 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] [cmakebuilder-plugin] (JENKINS-25807) Is this plugin still maintained?
Martin Weber created JENKINS-25807 Is this plugin still maintained? Issue Type: Task Assignee: Unassigned Components: cmakebuilder-plugin Created: 26/Nov/14 7:25 PM Description: On https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hidereset=truejqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27cmakebuilder-plugin%27 they have issues dating back to Jan 2012, each of them unassigned. And https://wiki.jenkins-ci.org/display/JENKINS/cmakebuilder+Plugin says: Tracking maintainers: n/a. Project: Jenkins Priority: Minor Reporter: Martin Weber 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] [teamconcert-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
bbonn commented on JENKINS-25762 Build Engine going inactive due to no credentials Thanks Heather! This seeme to be having a good effect. We will continue to monitor. Thanks again, Bernie 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] [teamconcert-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
bbonn edited a comment on JENKINS-25762 Build Engine going inactive due to no credentials Thanks Heather! This seems to be having a good effect. We will continue to monitor. Thanks again, Bernie 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] [build-pipeline-plugin] (JENKINS-20841) Links of the pipeline view are not working for project using the Cloudbees folder plug-in
Kanstantsin Shautsou resolved JENKINS-20841 as Fixed Links of the pipeline view are not working for project using the Cloudbees folder plug-in Released as 1.4.5 should appear on mirrors in the next 24h Change By: Kanstantsin Shautsou (26/Nov/14 7:36 PM) Status: Open Resolved Assignee: JeffStorey Resolution: Fixed 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] [core] (JENKINS-25742) Concurrent job rename and edit view results in deadlock that puts Jenkins in a non responsive state
Tony Yang commented on JENKINS-25742 Concurrent job rename and edit view results in deadlock that puts Jenkins in a non responsive state Hi Daniel, We reproduced this in the latest weekly release Jenkins ver. 1.590 Here is the thread deadlock stack trace we captured through jConsole for the pair of threads that got into deadlock Name: Handling POST /jenkins/view/deadlock1/configSubmit from 10.72.120.119 : qtp1955915048-52 State: BLOCKED on hudson.model.Hudson@7e3b42ad owned by: Handling POST /jenkins/job/aaa_test2/doRename from 10.73.211.174 : qtp1955915048-45 Total blocked: 1 Total waited: 14 Stack trace: jenkins.model.Jenkins.save(Jenkins.java:2756) hudson.model.View.save(View.java:333) hudson.model.View.doConfigSubmit(View.java:959) locked hudson.model.ListView@1a6186c3 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:483) org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) org.kohsuke.stapler.Stapler.service(Stapler.java:238) javax.servlet.http.HttpServlet.service(HttpServlet.java:790) org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1667) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:114) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
[JIRA] [build-pipeline-plugin] (JENKINS-14565) Please add support for Cloudbees folder structure
Kanstantsin Shautsou resolved JENKINS-14565 as Fixed Please add support for Cloudbees folder structure As i see commit was released in 1.4.4. Additional fixes are in 1.4.5. Release 1.4.5 should appear on mirrors in the next 24h. Change By: Kanstantsin Shautsou (26/Nov/14 7:46 PM) Status: Open Resolved Resolution: Fixed 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.
