[JIRA] [run-condition-extras-plugin] (JENKINS-28150) ClassNotFoundException exception happens if a dependent plugin is not installed
Oleg Nenashev created JENKINS-28150 ClassNotFoundException exception happens if a dependent plugin is not installed Issue Type: Bug Assignee: Oleg Nenashev Components: run-condition-extras-plugin Created: 29/Apr/15 10:26 AM Description: New core versions print warnings if a non-optional extension loading fails. All @Extension specs in the plugin should have an optional attribute Project: Jenkins Priority: Minor Reporter: Oleg Nenashev 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Ross Rowe started work on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Change By: Ross Rowe (29/Apr/15 11:14 AM) Status: Open InProgress 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Ross Rowe commented on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Okay, I've just released version 1.128 which should ensure that all open tunnels are closed, when you get a chance could you try this version out? 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] [plugin-proposals] (JENKINS-28137) Static Short URLs for Jobs
Daniel Beck updated JENKINS-28137 Static Short URLs for Jobs Consistent with the ongoing trend to remove functionality from core, this should be added in a plugin instead of core. All required extension points exist AFAICT, so there's nothing preventing creation of such a plugin. Change By: Daniel Beck (29/Apr/15 11:19 AM) 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thank you. I will update and let you know in case I still see it (hopefully 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-28137) Static Short URLs for Jobs
Daniel Beck updated JENKINS-28137 Static Short URLs for Jobs Change By: Daniel Beck (29/Apr/15 11:13 AM) Component/s: plugin-proposals 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-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck updated JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation Change By: Daniel Beck (29/Apr/15 11:14 AM) Component/s: core Component/s: other Component/s: build-blocker-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] [run-condition-extras-plugin] (JENKINS-28150) ClassNotFoundException exception happens if a dependent plugin is not installed
SCM/JIRA link daemon commented on JENKINS-28150 ClassNotFoundException exception happens if a dependent plugin is not installed Code changed in jenkins User: Adrien Lecharpentier Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/run_condition_extras/adapters/build_timeout/ConditionalTimeout.java src/main/java/com/synopsys/arc/jenkinsci/plugins/run_condition_extras/adapters/build_timeout/RunConditionTimeoutStrategy.java src/main/java/com/synopsys/arc/jenkinsci/plugins/run_condition_extras/adapters/mail_ext/RunConditionEmailTrigger.java http://jenkins-ci.org/commit/run-condition-extras-plugin/905dccb190e122dd68342f92e8b45f0a0414fea7 Log: JENKINS-28150 Fix optional dependency loading The extensions here that are using an optional dependency's class must be mark as optional. If not, we can see `ClassNotFoundException` when Jenkins load 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thank you. I will update and let you know in case I still see it (hopefully not). How long does it take for me to see the new version? (still 1.127 is latest on plugin wiki page and in Jenkins config) 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] [run-condition-extras-plugin] (JENKINS-26005) Run condition trigger for Email-ext does not retain Send To information on Save/Apply
SCM/JIRA link daemon commented on JENKINS-26005 Run condition trigger for Email-ext does not retain Send To information on Save/Apply Code changed in jenkins User: Corey Sullivan Path: pom.xml src/main/java/com/synopsys/arc/jenkinsci/plugins/run_condition_extras/adapters/mail_ext/RunConditionEmailTrigger.java http://jenkins-ci.org/commit/run-condition-extras-plugin/19588e6e57c2950ec9559e550345e5d723d1355a Log: Modify the constructor of RunConditionEmailTrigger to call the non-deprecated constructor. The constructor that passes boolean parameters for the "Send To" list has been deprecated as 2.38 (email-ext.) Fix for JENKINS-26005. 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] [run-condition-extras-plugin] (JENKINS-26005) Run condition trigger for Email-ext does not retain Send To information on Save/Apply
SCM/JIRA link daemon commented on JENKINS-26005 Run condition trigger for Email-ext does not retain Send To information on Save/Apply Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkinsci/plugins/run_condition_extras/adapters/mail_ext/RunConditionEmailTrigger.java http://jenkins-ci.org/commit/run-condition-extras-plugin/9ff4683beae73af83f39c02048c6ab629c9251e9 Log: Merge pull request #1 from sullivac/master FIXED JENKINS-26005 - Modify the constructor of RunConditionEmailTrigger to call the non-depre... Compare: https://github.com/jenkinsci/run-condition-extras-plugin/compare/02c2f42e5477...9ff4683beae7 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] [run-condition-extras-plugin] (JENKINS-26005) Run condition trigger for Email-ext does not retain Send To information on Save/Apply
SCM/JIRA link daemon resolved JENKINS-26005 as Fixed Run condition trigger for Email-ext does not retain Send To information on Save/Apply Change By: SCM/JIRA link daemon (29/Apr/15 11:03 AM) 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] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck commented on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation Note that the options are documented as (emphasis mine): When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. So this appears to behave as designed. 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-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck edited a comment on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation Note that the options are documented as (emphasis mine): When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. So this appears to behave as designed (or at least as documented). 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thank you. I will update and let you know in case I still see it (hopefully not). How long does it take for me to see the new version? (still 1.127 is latest on plugin wiki page and in Jenkins config) I think the plugin's build itself is failing. Maybe that's why Jenkins doesn't show the update. 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-plugin] (JENKINS-28143) Docker plugin now fails to mount volumes in version 0.9.0-rc1
Jānis Balodis commented on JENKINS-28143 Docker plugin now fails to mount volumes in version 0.9.0-rc1 The same problem. Jenkins 1.611, Docker 1.6.0 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] [pollscm-plugin] (JENKINS-28099) Poll SCM not working
Daniel Beck commented on JENKINS-28099 Poll SCM not working Please just set up the correct logger. 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] [pollscm-plugin] (JENKINS-28099) Poll SCM not working
Swapnil Kotwal updated JENKINS-28099 Poll SCM not working Change By: Swapnil Kotwal (29/Apr/15 7:44 AM) Attachment: Capture.PNG 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] [xvfb-plugin] (JENKINS-28147) Xvfb not terminated when a Maven module rebuild fails inside a plugin
Sean Flanigan created JENKINS-28147 Xvfb not terminated when a Maven module rebuild fails inside a plugin Issue Type: Bug Assignee: zregvart Components: xvfb-plugin Created: 29/Apr/15 8:12 AM Description: When rebuilding a single module of a multi-module project, I have an environment script which happens to fail (because $WORKSPACE is different from a normal top-level build, but any failure should do). When this environment script fails, the job naturally fails too, but the Xvfb plugin fails to terminate the Xvfb process it started, leading to problems in subsequent builds. I'm having trouble coming up with an easy minimal reproducer, because I think it only happens when a multi-module build is involved. I suspect the failure has to happen in a Jenkins plugin (like Environment Script) too: a normal build failure is not enough. This is the log from the rebuild which failed: Building remotely on jenkins-slave-f20-kvm-7 (amd64-Fedora 20 amd64-Fedora-20 Fedora-20 Fedora kvm amd64) in workspace /home/fedora/jenkins/workspace/zanata-server-github-pull-requests/functional-test Xvfb starting$ Xvfb :1 -screen 0 1024x768x24 -fbdir /home/fedora/jenkins/xvfb-2015-04-28_11-25-15-3566362744314223079.fbdir [functional-test] $ /bin/sh -xe /tmp/org.zanata:functional-test6279959920485140886.sh + etc/scripts/allocate-jboss-ports /tmp/org.zanata:functional-test6279959920485140886.sh: line 1: etc/scripts/allocate-jboss-ports: No such file or directory FATAL: Unable to execute script, return code 1 Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: FAILURE Environment: Xvfb plugin 1.0.15 Jenkins ver. 1.580.3 Rebuilder plugin 1.22 Environment Script Plugin 1.1.2 Project: Jenkins Labels: xvfb rebuild modules Priority: Minor Reporter: Sean Flanigan 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-18536) Remove downstream job from queue before new triggers
Markus updated JENKINS-18536 Remove downstream job from queue before new triggers Change By: Markus (29/Apr/15 7:23 AM) Description: Giventwojobs:*Downstream,whichhasa60squietperiod*Upstream,whichtriggersaparameterizedbuildonDownstreamNow,ifyouquicklytriggerUpstream3times,thentherewillbe3Downstreamjobsinthequeue.Theywillthenallrun.WewouldlikeparameterizedtriggeringincombinationwithdownstreamquietperiodtobehavesortofliketheSVNquietperiodbehaves:IfUpstreamistriggeredmultipletimes,thenonlythelasttriggeredDownstreamwillremaininthequeue. Thiswillhelpwhenyouhavelimitedverificationresourcesduringdevelopmentandwouldliketorunabesteffortapproach.Itwillpreventthequeuefromcontinuouslygrowing. Summary:BeforeUpstreamtriggersDownstream,UpstreamshouldremoveanyinstancesofDownstreamfromthequeue.Thisshouldofcoursebeanoptionandnotthedefaultbehavior. 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-28070) Maven 3.3.1 build fail on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU
updated JENKINS-28070
Maven 3.3.1 build fail on Unix if this Maven version doesnt match with the one in $PATH
I added more precision of the configuration.
Change By:
Laurent TOURREAU
(29/Apr/15 8:31 AM)
Summary:
Maven3.3.1buildfailonUnixif
this
Maven
is
versiondoesntmatchwith
the
defaultinstallation
onein$PATH
Description:
WefacethefollowingbuilderrorwhenusingMaven3.3.1
(
inJenkinswith
the
unique
followingsetup:*
Maven
installation)
3.3.1isinstalledon/apps/tools/distrib/apache-maven-3.3.1*Maven3.1.1isinstalledon/apps/tools/distrib/apache-maven-3.1.1*Wehaveasymboliclink/apps/tools/distrib/maven-/apps/tools/distrib/apache-maven-3.1.1*Wehaveadded/apps/tools/distrib/maven/bin
in
$PATHOSenvironmentvariable*On
Jenkins
wehaveconfiguredaMaveninstallation(name:MAVEN,path:/apps/tools/distrib/apache-maven-3
.
3.1)
{code}Buildingonmasterinworkspace/myapp/mymoduleUpdatingsvn://svn.mycompany.com/mymoduleatrevision2015-04-23T16:00:24.616+0100Atrevision37434nochangeforsvn://svn.mycompany.com/mymodulesincethepreviousbuild[build_mymodule]$mvn-DparentVersion=[31.0.26]versions:update-parentversions:use-releases-XBuildstepInvoketop-levelMaventargetsmarkedbuildasfailure{code}
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-28070) Maven 3.3.1 build fail on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU
updated JENKINS-28070
Maven 3.3.1 build fail on Unix if this Maven version doesnt match with the one in $PATH
Change By:
Laurent TOURREAU
(29/Apr/15 8:51 AM)
Description:
WefacethefollowingbuilderrorwhenusingMaven3.3.1inJenkinswiththefollowingsetup:*Maven3.3.1isinstalledon/apps/tools/distrib/apache-maven-3.3.1*Maven3.1.1isinstalledon/apps/tools/distrib/apache-maven-3.1.1*Wehaveasymboliclink/apps/tools/distrib/maven-/apps/tools/distrib/apache-maven-3.1.1*Wehaveadded/apps/tools/distrib/maven/binin$PATHOSenvironmentvariable*OnJenkinswehaveconfiguredaMaveninstallation(name:MAVEN,path:/apps/tools/distrib/apache-maven-3.3.1)
*ThejobwewanttorunisaMavenprojectwhichhaveapre-stepInvoketop-levelMaventargetshaving(Default)asMavenversionselected.
{code}Buildingonmasterinworkspace/myapp/mymoduleUpdatingsvn://svn.mycompany.com/mymoduleatrevision2015-04-23T16:00:24.616+0100Atrevision37434nochangeforsvn://svn.mycompany.com/mymodulesincethepreviousbuild[build_mymodule]$mvn-DparentVersion=[31.0.26]versions:update-parentversions:use-releases-XBuildstepInvoketop-levelMaventargetsmarkedbuildasfailure{code}
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] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Has anyone tried the latest snapshot release (build 163)? https://jenkins.ci.cloudbees.com/job/plugins/job/p4-plugin/163/org.jenkins-ci.plugins$p4/ This has extra logging which might highlight the error/warning explaining why the file is not synced. The AutoCleanImpl process is quite complicated: ClientHelper.java 1. revert open files (typically a shelf) 2. delete any files that were open for added 3. reconcile -naedlf (to clean up Add/Edit/Deletes) 4. if needed force sync any missing files from step 3 If there are enough users on 14.1 I can simplify most of the steps with a 'p4 clean'. 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] [delivery-pipeline-plugin] (JENKINS-25379) Manual trigger execution causes TriggerException using a 32bits jdk
Aleix Vergés updated JENKINS-25379 Manual trigger execution causes TriggerException using a 32bits jdk Change By: Aleix Vergés (29/Apr/15 7:20 AM) Attachment: 2015-04-29_0918.png 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] [swarm-plugin] (JENKINS-28148) Fail to create a swarm when using a toolLocations with whitespaces.
Paul Popineau created JENKINS-28148 Fail to create a swarm when using a toolLocations with whitespaces. Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins_log_swarm_fail.log Components: swarm-plugin Created: 29/Apr/15 8:57 AM Description: It is impossible to start correctly a swarm when specifying a toolLocations argument with whitespaces (ie. jdk:C:/Program Files/Java/...). The problem seems to come from : swarm-plugin/client/src/main/java/hudson/plugins/swarm/SwarmClient.java, line 308. swarm-plugin/plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java, line 121. which use " " as a separator for tools. As a consequence, the part after the whitespace is considered to be another tool (which is just the rest of the previous one), and throw RuntimeException because it is not recognized. IMO, the solution would either be : change the splitting character (ie. tool1:location@tool2:location). Quick win. use a more complex structure for data sent from client to plugin than just raw text and simple separators. Environment: Jenkins : 1.596.2, swarm-plugin : 1.22, Windows7 Project: Jenkins Labels: slave windows Priority: Minor Reporter: Paul Popineau 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-28149) Excluded Users option doesn't work with multiple branches in Branch Specifier
wa hulu created JENKINS-28149 Excluded Users option doesnt work with multiple branches in Branch Specifier Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 29/Apr/15 9:12 AM Description: I specified two branches separately in "Branch Specifier" option as below: Branch Specifier(blank for 'any'): */master Branch Specifier(blank for 'any'): */develop I also specified two Excluded users under the "Polling ignores commits from certain users' option, show as following: Excluded Users: James Kobe Then when James push his changes to both */master and */develop branches, jenkins still trigger a build, so does Kobe. Based on my understanding, jenkins will not trigger the build since both James and Kobe are both the excluded users. This is definitely a bug, hope someone will fix it soon. Environment: jenkins ver: 1.589 git plugin: 2.3.5 Project: Jenkins Priority: Major Reporter: wa hulu 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] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Damien Coraboeuf commented on JENKINS-27994 The Manifest of the job-dsl JAR is empty, making it unuseable for tests Thanks Daniel. Do I create a PR for the Job DSL plugin to take this version into account, or do you do it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25379) Manual trigger execution causes TriggerException using a 32bits jdk
Aleix Vergés commented on JENKINS-25379 Manual trigger execution causes TriggerException using a 32bits jdk Hi, I could also reproduce this issue with Jenkins version 1.609, and Delivery Plugin 0.8.11. The platform is a FreeBSD 10.1-RELEASE-p9 with OpenJDK Runtime Environment (build 1.7.0_76-b13). As a workaround we are triggering the manual step from the Job itself adding the parameters values also manually. Thanks 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] [delivery-pipeline-plugin] (JENKINS-25379) Manual trigger execution causes TriggerException using a 32bits jdk
Aleix Vergés edited a comment on JENKINS-25379 Manual trigger execution causes TriggerException using a 32bits jdk Hi, I could also reproduce this issue with Jenkins version 1.609, and Delivery Plugin 0.8.11. The platform is a FreeBSD 10.1-RELEASE-p9 with OpenJDK Runtime Environment (build 1.7.0_76-b13). As a workaround we are triggering the manual step from the Job itself using the "Build with Parameters" option and adding the parameters values also manually. Attached is an screenshot of the options we're using to make it possible. Thanks 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] [pollscm-plugin] (JENKINS-28099) Poll SCM not working
Swapnil Kotwal updated JENKINS-28099 Poll SCM not working Change By: Swapnil Kotwal (29/Apr/15 7:44 AM) Attachment: Capture.PNG 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] [pollscm-plugin] (JENKINS-28099) Poll SCM not working
Swapnil Kotwal commented on JENKINS-28099 Poll SCM not working Look like this is happening due to clock difference between slave and 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] [delivery-pipeline-plugin] (JENKINS-28146) Manual trigger step fails with the new version
Nicolae Ghimbovschi created JENKINS-28146 Manual trigger step fails with the new version Issue Type: Bug Assignee: Patrik Boström Attachments: Screen Shot 2015-04-29 at 10.37.29.png Components: delivery-pipeline-plugin Created: 29/Apr/15 7:52 AM Description: Hi, Recently we've upgraded jenkins plugins and noticed an issue with the manual triggered steps from the pipeline. When triggering the manual step from the delivery pipeline, Jenkins returns "Could not trigger build! error: Server Error status: error" If we downgrade the Build Pipeline to version 1.4.3, all works as expected. The error response: ``` https://jenkins/view/APipeline/api/manualStep 500 javax.servlet.ServletException: java.lang.NoSuchMethodError: au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.init(Ljava/lang/String;Ljava/lang/String;Lau/com/centrumsystems/hudson/plugin/buildpipeline/ProjectGridBuilder;Ljava/lang/String;ZLjava/lang/String;Z)V at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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.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 hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] [maven-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU commented on JENKINS-28070 Maven 3.3.1 build fail on Unix if this Maven version doesnt match with the one in $PATH The issue disappears if a set the symbolic link /apps/tools/distrib/maven to /apps/tools/distrib/apache-maven-3.3.1. The build is run. Conclusion : We can't mix Maven version used by "Invoke top-level Maven targets" in Pre-Step section and the Maven used in Build section of the job. 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] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Daniel Spilker commented on JENKINS-27994 The Manifest of the job-dsl JAR is empty, making it unuseable for tests I already did, it's part of https://github.com/jenkinsci/job-dsl-plugin/pull/464 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-timeout-plugin] (JENKINS-28125) No e-mail is sent if build is aborted
Alexander Kriegisch updated JENKINS-28125 No e-mail is sent if build is aborted The config.xml (sensitive data x-ed out) you requested Change By: Alexander Kriegisch (29/Apr/15 6:02 AM) Attachment: config.xml Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-17457) get a non-existing directory problem when making an IPA after building a workspace.
lacostej commented on JENKINS-17457 get a non-existing directory problem when making an IPA after building a workspace. Sorry for the misunderstanding, I marked the other one as resolved because it was resolved as "duplicate of this issue". When they are duplicate, I don't consider their status meaningful. As for the issue itself, the last comment of mine describes the current state of the issue. I haven't concluded on what to do yet. Any feedback on #comment-217588 is appreciated This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-28144) content of NUnit file is not shown correct inside browser
Norbert Krimbacher created JENKINS-28144 content of NUnit file is not shown correct inside browser Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: result.xml, screen1.png, screen2.png Components: nunit-plugin Created: 29/Apr/15 6:51 AM Description: After executing a Jenkins project the NUnit file is read by the NUnit plugin. The visualisation of such a file is wrong inside the browser. The NUnit version of the result file should be 2.5 . see attached NUnit file: result.xml view of build: screen1.jpg Detail view : screen2.jpg Environment: Nunit PlugIn Version 0.16, Jenkins 1.547 Project: Jenkins Labels: plugin exception Priority: Major Reporter: Norbert Krimbacher 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] [email-ext-plugin] (JENKINS-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Jason McDonald
created JENKINS-28145
Editable E-Mail Notification PreSend not loading CLASSPATH
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
29/Apr/15 6:55 AM
Description:
Loading libs described in the field: 'Additional Groovy ClassPath' does not seem to be working. I'm trying to add libs(jars) to the classpath which are stored in the project's ${WORKSPACE}. Execute System Groovy Script classpath var handles this no problem.
Environment:
Jenkins 1.610, Email-EXT 2.39.3
Project:
Jenkins
Labels:
plugin
Priority:
Major
Reporter:
Jason McDonald
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-timeout-plugin] (JENKINS-28125) No e-mail is sent if build is aborted
Alexander Kriegisch commented on JENKINS-28125 No e-mail is sent if build is aborted @ikedam: I am just clarifying if it is okay for our admin to install E-mail-ext. What do you suggest concerning this problem with the Maven plugin? Should I file a request to the maintainer? Or is it rather a core e-mail problem? I am unsure where to address this problem, I just know that I strongly prefer fixes to work-arounds. 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] [clang-scanbuild-plugin] (JENKINS-28130) Latest (1.5) Clang scan-build plugin fails to publish
Francis Labrie edited a comment on JENKINS-28130 Latest (1.5) Clang scan-build plugin fails to publish I get the same error, I had to go back to version 1.4. Xcode version is: $ /usr/bin/xcodebuild -version Xcode 6.2 Build version 6C131e 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] [google-login-plugin] (JENKINS-28152) DNS issue on the server results in
lacostej created JENKINS-28152 DNS issue on the server results in Issue Type: Bug Assignee: recampbell Components: google-login-plugin Created: 29/Apr/15 12:47 PM Description: If the server experiences a DNS issue, the following page is shown: java.net.UnknownHostException: accounts.google.com at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) at sun.net.www.protocol.https.HttpsClient.init(HttpsClient.java:275) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:932) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1091) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250) at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:77) at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:965) at com.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:283) at com.google.api.client.auth.oauth2.TokenRequest.execute(TokenRequest.java:307) at org.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm$2.onSuccess(GoogleOAuth2SecurityRealm.java:171) at org.jenkinsci.plugins.googlelogin.OAuthSession.doFinishLogin(OAuthSession.java:99) at org.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm.doFinishLogin(GoogleOAuth2SecurityRealm.java:218) at sun.reflect.GeneratedMethodAccessor983.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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.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
[JIRA] [google-login-plugin] (JENKINS-28152) DNS issue on the server results in page with stacktrace
lacostej updated JENKINS-28152 DNS issue on the server results in page with stacktrace Change By: lacostej (29/Apr/15 12:48 PM) Summary: DNSissueontheserverresultsin pagewithstacktrace 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-28134) Git clone fails since 1.17.0
Rogério Colferai edited a comment on JENKINS-28134 Git clone fails since 1.17.0 We had same issue. Either at the start of build or at the end of it, like this : Jenkins version: LTS 1.596.1 07:28:17 + git push -f origin jenkins/master-aux:jenkins/master-aux 07:28:21 remote: 07:28:21 remote: remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1, done 07:28:21 To https://ipad...@gerrit.cpqd.com.br/dsso/cdk 07:28:214949602..52d0260 jenkins/master-aux - jenkins/master-aux 07:28:21 FATAL: String index out of range: -1 07:28:21 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 07:28:21 at java.lang.String.substring(String.java:1911) 07:28:21 at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) 07:28:21 at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) 07:28:21 at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) 07:28:21 at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) 07:28:21 at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:894) 07:28:21 at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:862) 07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349) 07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) 07:28:21 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:687) 07:28:21 at hudson.model.Run.execute(Run.java:1784) 07:28:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 07:28:21 at hudson.model.ResourceController.execute(ResourceController.java:89) 07:28:21 at hudson.model.Executor.run(Executor.java:240) 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] [email-ext-plugin] (JENKINS-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Alex Earl commented on JENKINS-28145 Editable E-Mail Notification PreSend not loading CLASSPATH Can you provide an example of what you are doing? 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-28154) IllegalArgumentException thrown when some binary operators are used
Oliver Gondža created JENKINS-28154 IllegalArgumentException thrown when some binary operators are used Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 29/Apr/15 1:08 PM Description: Following exception is thrown when version in ["1.0", "1.1"] used as combination filter. Other operators might cause problems as well since org.codehaus.groovy.syntax.Types seems to define lot more codes than org.kohsuke.groovy.sandbox.impl.Ops. WARNING: Error while serving http://localhost:8080/job/matrix/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since 1.17.0
Rogério Colferai commented on JENKINS-28134 Git clone fails since 1.17.0 We had same issue. Either at the start of build or at the end of it, like this : 07:28:17 + git push -f origin jenkins/master-aux:jenkins/master-aux 07:28:21 remote: 07:28:21 remote: remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1, done 07:28:21 To https://ipad...@gerrit.cpqd.com.br/dsso/cdk 07:28:214949602..52d0260 jenkins/master-aux - jenkins/master-aux 07:28:21 FATAL: String index out of range: -1 07:28:21 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 07:28:21 at java.lang.String.substring(String.java:1911) 07:28:21 at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) 07:28:21 at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) 07:28:21 at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) 07:28:21 at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) 07:28:21 at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:894) 07:28:21 at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:862) 07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349) 07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) 07:28:21 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:687) 07:28:21 at hudson.model.Run.execute(Run.java:1784) 07:28:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 07:28:21 at hudson.model.ResourceController.execute(ResourceController.java:89) 07:28:21 at hudson.model.Executor.run(Executor.java:240) 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] [ws-cleanup-plugin] (JENKINS-28151) if node switched off after execution some garbage generated
Roman G created JENKINS-28151 if node switched off after execution some garbage generated Issue Type: Bug Assignee: vjuranek Components: ws-cleanup-plugin Created: 29/Apr/15 12:24 PM Description: because of specifics of our project we need reboot node just after jenkins build completed After updating I observe that some garbage generated if we enable workspace clean up e.g. I see many dirs like this /local/home/jenkins/fsroot/workspace/my project_ws-cleanup_1430299254267 I suppose that it's connected to asynchronously deletion and deletion is not completed until node reboot Project: Jenkins Priority: Minor Reporter: Roman G 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-28153) Show analysis progress status
Fernando Rosado Altamirano created JENKINS-28153 Show analysis progress status Issue Type: Improvement Assignee: Unassigned Components: build-failure-analyzer-plugin Created: 29/Apr/15 12:50 PM Description: If you create a new failure cause and want rescan old builds,there is no any indication about analysis progress. Perhaps you can provide any global page (not strictly related with current build) showing information about all the analysis running, pending tasks and project analysed. Project: Jenkins Priority: Minor Reporter: Fernando Rosado Altamirano 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-26657) File context menu missing when installing Slave under windows with jnlp
Alex Earl commented on JENKINS-26657 File context menu missing when installing Slave under windows with jnlp I'd still like to determine why this is happening, since other people have been seeing it. I'll play around with it and see what I can find. 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] [google-login-plugin] (JENKINS-28152) DNS issue on the server results in page with stacktrace
lacostej
updated JENKINS-28152
DNS issue on the server results in page with stacktrace
Change By:
lacostej
(29/Apr/15 12:50 PM)
Description:
IftheserverexperiencesaDNSissue,thefollowingpageisshown:{code}java.net.UnknownHostException:accounts.google.com atjava.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) atjava.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) atjava.net.Socket.connect(Socket.java:579) atsun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) atsun.net.NetworkClient.doConnect(NetworkClient.java:175) atsun.net.www.http.HttpClient.openServer(HttpClient.java:432) atsun.net.www.http.HttpClient.openServer(HttpClient.java:527) atsun.net.www.protocol.https.HttpsClient.init(HttpsClient.java:275) atsun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) atsun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:932) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) atsun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1091) atsun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250) atcom.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:77) atcom.google.api.client.http.HttpRequest.execute(HttpRequest.java:965) atcom.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:283) atcom.google.api.client.auth.oauth2.TokenRequest.execute(TokenRequest.java:307) atorg.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm$2.onSuccess(GoogleOAuth2SecurityRealm.java:171) atorg.jenkinsci.plugins.googlelogin.OAuthSession.doFinishLogin(OAuthSession.java:99) atorg.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm.doFinishLogin(GoogleOAuth2SecurityRealm.java:218) atsun.reflect.GeneratedMethodAccessor983.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:875) atorg.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:875) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:648) atorg.kohsuke.stapler.Stapler.service(Stapler.java:237) 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.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)
[JIRA] [google-login-plugin] (JENKINS-28152) DNS issue on the server results in page with stacktrace
lacostej
updated JENKINS-28152
DNS issue on the server results in page with stacktrace
Change By:
lacostej
(29/Apr/15 12:49 PM)
Description:
IftheserverexperiencesaDNSissue,thefollowingpageisshown:{code}java.net.UnknownHostException:accounts.google.com atjava.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) atjava.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) atjava.net.Socket.connect(Socket.java:579) atsun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) atsun.net.NetworkClient.doConnect(NetworkClient.java:175) atsun.net.www.http.HttpClient.openServer(HttpClient.java:432) atsun.net.www.http.HttpClient.openServer(HttpClient.java:527) atsun.net.www.protocol.https.HttpsClient.init(HttpsClient.java:275) atsun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) atsun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:932) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) atsun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1091) atsun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250) atcom.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:77) atcom.google.api.client.http.HttpRequest.execute(HttpRequest.java:965) atcom.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:283) atcom.google.api.client.auth.oauth2.TokenRequest.execute(TokenRequest.java:307) atorg.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm$2.onSuccess(GoogleOAuth2SecurityRealm.java:171) atorg.jenkinsci.plugins.googlelogin.OAuthSession.doFinishLogin(OAuthSession.java:99) atorg.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm.doFinishLogin(GoogleOAuth2SecurityRealm.java:218) atsun.reflect.GeneratedMethodAccessor983.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:875) atorg.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:875) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:648) atorg.kohsuke.stapler.Stapler.service(Stapler.java:237) 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.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)
[JIRA] [google-login-plugin] (JENKINS-28152) Better error messages
recampbell updated JENKINS-28152 Better error messages Change By: recampbell (29/Apr/15 12:58 PM) Summary: DNSissueontheserverresultsinpagewithstacktrace Bettererrormessages 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] [job-dsl-plugin] (JENKINS-22151) Plugin extension point for additional configuration
SCM/JIRA link daemon commented on JENKINS-22151 Plugin extension point for additional configuration Code changed in jenkins User: Daniel Spilker Path: docs/Extending-the-DSL.md docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslExtensionMethod.java job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/AbstractExtensibleContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ExtensibleContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy job-dsl-plugin/build.gradle job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ContextExtensionPoint.java job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/Messages.properties job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ContextExtensionPointSpec.groovy job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/TestContextExtensionPoint.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/TestContextExtensionPoint2.java job-dsl-plugin/src/test/resources/config.xml job-dsl-plugin/src/test/resources/config2.xml job-dsl-plugin/src/test/resources/extension.xml http://jenkins-ci.org/commit/job-dsl-plugin/755011728ba7b971062ab2ee7e2d2f95f29161ba Log: Merge pull request #464 from CoreMedia/extension-point-1 JENKINS-22151 DSL Extension Point Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/db0166e489e6...755011728ba7 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-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Vassilena Treneva created JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Issue Type: Bug Assignee: Unassigned Components: core, slave-utilization Created: 29/Apr/15 1:17 PM Description: Our Windows slaves are JNLP connected using scheduled tasks (like this: https://wiki.jenkins-ci.org/display/JENKINS/Launch+Java+Web+Start+slave+agent+via+Windows+Scheduler). When a job starts working with a slave it suddenly fails because the connection was lost. It says something on slave side killed the connection. Few minutes afterwards the slave is back on-line. I am sure it is not a network issue as I tried pinging the network from system start-up till the problem occurs. I could not find find what kills the connection and disable TCP chimney (advice from google) did not work. The exception is below. I think proper behaviour would be not to fail the job but attempt to reconnect. Any hints of additional configuration that will help me resolve this issue is appreciated. Building remotely on vmbam32.eur.ad.sag (R2 Server 2012 Enterprise Windows) in workspace c:\jenkins\workspace\optimize-install FATAL: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag hudson.remoting.RequestAbortedException: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag at hudson.remoting.Request.abort(Request.java:296) at hudson.remoting.Channel.terminate(Channel.java:815) at hudson.remoting.Channel$2.terminate(Channel.java:492) at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:72) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at ..remote call to vmbam32.eur.ad.sag(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:980) at hudson.FilePath.act(FilePath.java:969) at hudson.FilePath.mkdirs(FilePath.java:1152) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at
[JIRA] [core] (JENKINS-27067) Dropdowns display limited and scrollable
SCM/JIRA link daemon commented on JENKINS-27067 Dropdowns display limited and scrollable Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/lib/form/hetero-list/hetero-list.js http://jenkins-ci.org/commit/jenkins/f6454983acff9687f0655d23157f723ca5e11090 Log: FIXED JENKINS-27067 Larger minimum popup menu height 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-27067) Dropdowns display limited and scrollable
SCM/JIRA link daemon commented on JENKINS-27067 Dropdowns display limited and scrollable Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/resources/lib/form/hetero-list/hetero-list.js http://jenkins-ci.org/commit/jenkins/809c3000d1302f776050b85e7696b036fb65dfe2 Log: Merge pull request #1640 from daniel-beck/JENKINS-27067 FIXED JENKINS-27067 Larger minimum popup menu height Compare: https://github.com/jenkinsci/jenkins/compare/e4458fbe301d...809c3000d130 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-27067) Dropdowns display limited and scrollable
SCM/JIRA link daemon resolved JENKINS-27067 as Fixed Dropdowns display limited and scrollable Change By: SCM/JIRA link daemon (29/Apr/15 5:07 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] [core] (JENKINS-28120) Jenkins core to require Java7
SCM/JIRA link daemon commented on JENKINS-28120 Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/8d3cd91e281861ac9e28f60a39cb7d131e1911f6 Log: Follow up fix to JENKINS-28120. 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-28134) Git clone fails since 1.17.0
Mark Waite commented on JENKINS-28134 Git clone fails since 1.17.0 Looking at the code, I think the change in git client plugin 1.17.0 needs a corresponding change in the git plugin to no longer rely on an git changeset format from the prior plugin. I'll need to check with Nicolas De Loof to see if there are other techniques we can consider to not break the previous version of the git plugin, while still including his fix to date parsing in a changeset. 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-28157) Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org
Daniel Beck commented on JENKINS-28157 Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org Does it mean we can't change the update site URL if we want to use another corporate update site? Again, AFAICT it uses updates.jenkins-ci.org for the tool auto-installer metadata even if you configure a different update site. Nothing in this report indicates you don't get your own update site's data (which plugins are available etc.) 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] [sametime-plugin] (JENKINS-28159) Sametime java.lang.NullPointerException
ravi khetani created JENKINS-28159 Sametime java.lang.NullPointerException Issue Type: Bug Assignee: jamieb Components: sametime-plugin Created: 29/Apr/15 3:47 PM Description: trying to configure sametime for a job, and when I apply the setting for the job, no matter what I put in, the following exception is thrown: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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 com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) 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:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [email-ext-plugin] (JENKINS-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Jason McDonald commented on JENKINS-28145 Editable E-Mail Notification PreSend not loading CLASSPATH org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script1.groovy: 2: unable to resolve class groovyx.net.http.RESTClient @ line 2, column 1. import groovyx.net.http.RESTClient ^ Script1.groovy: 1: unable to resolve class groovyx.net.http.ContentType @ line 1, column 1. import groovyx.net.http.ContentType 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] [websphere-deployer-plugin] (JENKINS-28160) Plugin looking in incorrect Path for Websphere jars
Ricky Shelton updated JENKINS-28160 Plugin looking in incorrect Path for Websphere jars Change By: Ricky Shelton (29/Apr/15 5:05 PM) Description: WhensettingupauthenticationinformationforaLibertyserver,Igetthefollowingerrormessagewhentestingtheconnection: CannotfindtherequiredIBMWebSphereLibertyjarfilesin/var/lib/jenkins/.jenkins/plugins/websphere-deployer/WEB-INF/lib/.PleasecopythemfromIBMWebSphereLiberty(seeplugindocumentation) ThepluginsdirectoryforthisJenkinsinstallisunder:/var/lib/jenkins/pluginsnot/var/lib/jenkins/.jenkins/pluginsHowcanIamendwherethepluginislookingfortherelevantwebspherejars? 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-plugin] (JENKINS-28143) Docker plugin now fails to mount volumes in version 0.9.0-rc1
Kanstantsin Shautsou commented on JENKINS-28143 Docker plugin now fails to mount volumes in version 0.9.0-rc1 This may happen, it is planned that volumes support will be enhanced, main discussions are here https://github.com/jenkinsci/docker-plugin/pull/183 Probably the first issue that need to fixed and released as rc2 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-28134) Git clone fails since 1.17.0
Mark Waite commented on JENKINS-28134 Git clone fails since 1.17.0 Ouch. Sorry about that. What version of the git plugin are you running with the git client plugin? Does the problem resolve itself if you revert from 1.17.0 to 1.16.1 (and restart the Jenkins server)? I assume it will be resolved by that revert, since there was a specific fix included in 1.17.0 for date format parsing in change sets. 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-28120) Jenkins core to require Java7
SCM/JIRA link daemon resolved JENKINS-28120 as Fixed Jenkins core to require Java7 Change By: SCM/JIRA link daemon (29/Apr/15 4:59 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.
[JIRA] [core] (JENKINS-28120) Jenkins core to require Java7
SCM/JIRA link daemon commented on JENKINS-28120 Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/e75bea8928a904c5a2de47f3ee54ae726b12f4af Log: FIXED JENKINS-28120 Merge pull request #1679 Compare: https://github.com/jenkinsci/jenkins/compare/ca3b1db4d6f7...e75bea8928a9 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] [websphere-deployer-plugin] (JENKINS-28160) Plugin looking in incorrect Path for Websphere jars
Ricky Shelton created JENKINS-28160 Plugin looking in incorrect Path for Websphere jars Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 29/Apr/15 5:04 PM Description: When setting up authentication information for a Liberty server, I get the following error message when testing the connection : Cannot find the required IBM WebSphere Liberty jar files in '/var/lib/jenkins/.jenkins/plugins/websphere-deployer/WEB-INF/lib/'. Please copy them from IBM WebSphere Liberty (see plugin documentation) The plugins directory for this Jenkins install is under: /var/lib/jenkins/plugins not /var/lib/jenkins/.jenkins/plugins How can I amend where the plugin is looking for the relevant websphere jars ? Environment: Red Hat Enterprise Linux Server release 6.6, Jenkins 1.611 Websphere Deployer Plugin 1.2 Project: Jenkins Priority: Blocker Reporter: Ricky Shelton 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] [gerrit-trigger-plugin] (JENKINS-28161) Gerrit trigger NPE on report and event
David Caro created JENKINS-28161 Gerrit trigger NPE on report and event Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 29/Apr/15 5:15 PM Description: On a gerrit event, the gerrit trigger fails with NPE: Apr 29, 2015 6:04:43 PM com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler notifyListener SEVERE: Exception thrown during event handling. java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory$GerritTriggeredEventComparator.compare(BuildMemory.java:63) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory$GerritTriggeredEventComparator.compare(BuildMemory.java:60) at java.util.TreeMap.getEntryUsingComparator(TreeMap.java:368) at java.util.TreeMap.getEntry(TreeMap.java:339) at java.util.TreeMap.get(TreeMap.java:272) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory.isBuilding(BuildMemory.java:295) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener.isBuilding(ToGerritRunListener.java:264) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.gerritEvent(GerritTrigger.java:979) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler.notifyListener(GerritHandler.java:328) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler.notifyListeners(GerritHandler.java:290) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.workers.AbstractGerritEventWork.perform(AbstractGerritEventWork.java:45) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.workers.AbstractJsonObjectWork.perform(AbstractJsonObjectWork.java:57) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.workers.StreamEventsStringWork.perform(StreamEventsStringWork.java:66) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.workers.EventThread.run(EventThread.java:65) And on a job finished it also throws NPE on: Apr 29, 2015 5:53:09 PM hudson.model.listeners.RunListener report WARNING: RunListener failed java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory$GerritTriggeredEventComparator.compare(BuildMemory.java:63) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory$GerritTriggeredEventComparator.compare(BuildMemory.java:60) at java.util.TreeMap.getEntryUsingComparator(TreeMap.java:368) at java.util.TreeMap.getEntry(TreeMap.java:339) at java.util.TreeMap.get(TreeMap.java:272) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory.started(BuildMemory.java:168) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener.onStarted(ToGerritRunListener.java:150) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener.onStarted(ToGerritRunListener.java:54) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:213) at hudson.model.Run.execute(Run.java:1737) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Environment: Jenkins 1.607 gerrit trigger 2.11, 2.12 and 2.13 Project: Jenkins Priority: Blocker Reporter: David Caro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your
[JIRA] [core] (JENKINS-27871) Block on upstream projects does not work
Jesse Glick commented on JENKINS-27871 Block on upstream projects does not work Is this now not 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] [email-ext-plugin] (JENKINS-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Alex Earl commented on JENKINS-28145 Editable E-Mail Notification PreSend not loading CLASSPATH Are you adding the classpath at the project level, or in the local config? 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] [email-ext-plugin] (JENKINS-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Alex Earl
commented on JENKINS-28145
Editable E-Mail Notification PreSend not loading CLASSPATH
I think the problem is that the classpath is never resolved for environment variables, so ${WORKSPACE} isn't getting replaced with the path to the workspace. I'll play around with this some more and verify that is what is happening.
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-28134) Git clone fails since git client plugin 1.17.0
Mark Waite commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Thanks, Pavel Batanov, that means we can probably live with this problem for a few days while a new release of the git plugin is prepared. Nicolas De Loof has been using pre-release versions of the git plugin with several other users so now it just needs a careful review of the changes since last release and some detailed testing before it is released generally. Would you be willing to assist with testing a pre-release of the next version of the git plugin? If so, I could give you a link to a version you could upload to your Jenkins server. 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] [nodeofflinenotification] (JENKINS-23197) When entering offline reason for a node, it should be prefixed with a date+time stamp
SCM/JIRA link daemon resolved JENKINS-23197 as Fixed When entering offline reason for a node, it should be prefixed with a date+time stamp Change By: SCM/JIRA link daemon (29/Apr/15 5:39 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.
[JIRA] [build-pipeline-plugin] (JENKINS-26596) On restarting broken build in pipeline, dashboard should update accordingly
Idan Bidani commented on JENKINS-26596 On restarting broken build in pipeline, dashboard should update accordingly Can this issue be considered as higher priority? rerunning a new build is the very basic functionality of the 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-26982) On MacOSX, pkg installation doesn't set newsyslog permissions properly
SCM/JIRA link daemon commented on JENKINS-26982 On MacOSX, pkg installation doesnt set newsyslog permissions properly Code changed in jenkins User: Kohsuke Kawaguchi Path: osx/scripts/postinstall-launchd-jenkins http://jenkins-ci.org/commit/packaging/26b1323a18793e7757423af54171310193b74f29 Log: FIXED JENKINS-26982 MacOSX: re-use jenkins user default group for group own $B!D (Bership permissions Porting https://github.com/lacostej/jenkins/commit/66cb50da3e5ace025f3a44ee727274053a90642b Compare: https://github.com/jenkinsci/packaging/compare/db61586bf48e...26b1323a1879 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-26982) On MacOSX, pkg installation doesn't set newsyslog permissions properly
SCM/JIRA link daemon commented on JENKINS-26982 On MacOSX, pkg installation doesnt set newsyslog permissions properly Code changed in jenkins User: Kohsuke Kawaguchi Path: osx/scripts/postinstall-launchd osx/scripts/postinstall-launchd-jenkins http://jenkins-ci.org/commit/packaging/1f9ef5c79622a51d31c3be2a7b72b84f5ec96e32 Log: JENKINS-26982 MacOSX: configure newsyslog to reset the /var/log/jenkins/ with appropriate permissions Porting the fix from https://github.com/lacostej/jenkins/commit/69d9bff59c2e4e7908a3490f9e154af4490d7298 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-26982) On MacOSX, pkg installation doesn't set newsyslog permissions properly
SCM/JIRA link daemon resolved JENKINS-26982 as Fixed On MacOSX, pkg installation doesnt set newsyslog permissions properly Change By: SCM/JIRA link daemon (29/Apr/15 5:53 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.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Pavel Batanov commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Since it stands revertable and my jenkins is not mission critical - I can spend some time on testing, so feel free to provide me a link and a bit of instructions if more than just run my jobs is needed. 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] [xcode-plugin] (JENKINS-28163) Codesign verification now needs --no-strict parameter
Ben Hochberg created JENKINS-28163 Codesign verification now needs --no-strict parameter Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 29/Apr/15 7:54 PM Description: The codesign verification step of the build process fails with the message "resource envelope is obsolete". Various sources on the web have cited that as of OS 10.9.5 and above a --no-strict parameter must be past during the coding validation step. Environment: OS X 10.10.3 using Xcode 6.3.1 and jenkins plugin 1.4.8 Project: Jenkins Labels: plugin Priority: Blocker Reporter: Ben Hochberg 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] [active-directory-plugin] (JENKINS-28158) if JENKINS_URL is set to an https adress, then login over an alternate http address not working
Daniel Beck commented on JENKINS-28158 if JENKINS_URL is set to an https adress, then login over an alternate http address not working To clarify, it works when you only change the scheme, or only change the host name/domain, but both at the same time breaks? Or why did you change both and not specify what happens when you only change one? 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] [fstrigger-plugin] (JENKINS-21571) FSTrigger doesn't trigger scheduled jobs on restart
Eric Anker commented on JENKINS-21571 FSTrigger doesnt trigger scheduled jobs on restart I'm running into this issue as well. Below are a bunch of guesses by a novice Jenkins Plugin developer. Having a look at: fstrigger-plugin/src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FolderContentTrigger.java and xtrigger-lib/src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java ...it's my *GUESS* that Mr. Boissinot is using the "offlineSlaveOnStartup" member variable to denote that it is the first time that the trigger has been run since the Jenkins Server initialized. It looks like the "MapString, FileInfo md5Map" is just resident in memory and is not saved between sessions. I think it needs to initialize once before the plug-in has a point of reference for future "checkIfModified()" calls. Suggested solutions going forward: EASY: Maybe the message should be more descriptive as to what's going on: "Initilaizing Folder md5Map... Waiting for next schedule to check if there are modifications."); or LESS EASY: Initialize the "md5Map" right when Jenkins starts? (instead of waiting for the next scheduled run) A.K.A. Override: public void start(BuildableItem project, boolean newInstance)??? or HARD?: The "md5Map" variable should be committed to disk... somehow? and reloaded after a Jenkins Server Reboot. 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-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck commented on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation I'm not sure what documentation you're reading (appears to be perhaps the "?" pop-up) Yep, inline help. The checkbox under the "Advanced Projects Option" says "Block build when upstream project is building". I would suggest that if to block also if queued, then the regular text by the text box should say "Block build when upstream project is building or queued". Needs a balance between short enough to be suitable as label, and being long enough to properly explain what it does. You're right that it's probably too short in this case. Second, this is not the way that it worked in 1.530 as I have numerous time when multiple jobs in a stream are queued and one does start running. So when was the implementation changed to also block on queuing? why? Checking the sources, it appears that it always should have behaved like this. Too many changes between the two releases to easily determine what was fixed and when, but it you could narrow it down I'll take another look. There's a chance it's related to a long standing queue concurrency bug that only recently was fixed. Third, perhaps there are useful scenarios to block if simply queued (but none come to mind for my immediate usage). Many features are best left to plugins to allow users to customize and configure Jenkins as much as they want while not overloading the default UI out of the box. Plugins could certainly achieve this with the existing extension points. Fourth, OK, if this check box if not the way, how can I simply block on building and not worry about if multiple jobs are queued? The jenkinsci-users mailing list can best provide answers to your Jenkins usage questions. 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] [nodeofflinenotification] (JENKINS-23197) When entering offline reason for a node, it should be prefixed with a date+time stamp
SCM/JIRA link daemon commented on JENKINS-23197 When entering offline reason for a node, it should be prefixed with a date+time stamp Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/slaves/OfflineCause.java core/src/main/resources/hudson/slaves/OfflineCause/cause.jelly test/src/test/java/hudson/model/NodeTest.java http://jenkins-ci.org/commit/jenkins/0dd2dbc0bf3b29aa64376ecda9959a781aa33b89 Log: FIXED JENKINS-23197 add timestamp to node-offline message Merge pull request #1605. Compare: https://github.com/jenkinsci/jenkins/compare/8d3cd91e2818...0dd2dbc0bf3b 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] [nodeofflinenotification] (JENKINS-23197) When entering offline reason for a node, it should be prefixed with a date+time stamp
SCM/JIRA link daemon commented on JENKINS-23197 When entering offline reason for a node, it should be prefixed with a date+time stamp Code changed in jenkins User: Matt Legrand Path: core/src/main/java/hudson/slaves/OfflineCause.java http://jenkins-ci.org/commit/jenkins/9a69d6191ab3259709ed7fba0411b652a32bbab9 Log: JENKINS-23197: add datestamp to node-offline message 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Jesse Glick commented on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page all the builds are not shown in the graphs Probably unrelated; see JENKINS-25340. 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-26604) Maven GlobalSettingsProvider swallows exceptions
SCM/JIRA link daemon commented on JENKINS-26604 Maven GlobalSettingsProvider swallows exceptions Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/jenkins/mvn/GlobalSettingsProvider.java http://jenkins-ci.org/commit/jenkins/0a6e00cb576cf8beb5c971c682029fb1e761b487 Log: FIXED JENKINS-26604 Ensures GlobalSettingsProvider does not swallow fatal exceptions Merge pull request #1546 Compare: https://github.com/jenkinsci/jenkins/compare/0dd2dbc0bf3b...0a6e00cb576c 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-26604) Maven GlobalSettingsProvider swallows exceptions
SCM/JIRA link daemon commented on JENKINS-26604 Maven GlobalSettingsProvider swallows exceptions Code changed in jenkins User: Alex Bertram Path: core/src/main/java/jenkins/mvn/GlobalSettingsProvider.java http://jenkins-ci.org/commit/jenkins/77bc6ad835fc0fc54e4fed16395deb24332a2b49 Log: JENKINS-26604 Removes try-catch from GlobalSettingsProvider unhelpfully which swallows exceptions If there is a problem providing the Maven global settings file configured by the user, the build should end in error. This is the behavior of SettingsProvider but not of GlobalSettingsProvider, which was swallowing the exception and printing only a warning, without details of the exception. 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-26604) Maven GlobalSettingsProvider swallows exceptions
SCM/JIRA link daemon resolved JENKINS-26604 as Fixed Maven GlobalSettingsProvider swallows exceptions Change By: SCM/JIRA link daemon (29/Apr/15 5:58 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.
[JIRA] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Jesse Glick commented on JENKINS-24608 Test result link displays twice on matrix project page JENKINS-26077 tracks the duplication from xunit. Michael Rose claims this is reproducible even using just junit and matrix-project. 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] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated Test Result Trend charts
Jesse Glick resolved JENKINS-25527 as Duplicate xUnit reports yield duplicated Test Result Trend charts Change By: Jesse Glick (29/Apr/15 6:26 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] [p4-plugin] (JENKINS-27743) Jenkins retriggers job on same changelist every time it polls
Martin Hulth commented on JENKINS-27743 Jenkins retriggers job on same changelist every time it polls After both switching to a new worker machine and upgrading Jenkins to 1.610 (from 1.607) the problem cannot reproduce itself. Not enough to say what the cause was and if it's been fixed (or just hidden). Regardless, my CI setup is up and running 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] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Jesse Glick resolved JENKINS-24608 as Duplicate Test result link displays twice on matrix project page After fixing JENKINS-26077 I cannot reproduce this. (Did not try before.) Change By: Jesse Glick (29/Apr/15 6:55 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] [junit-plugin] (JENKINS-25649) Duplicate Test Reports in Projects
Jesse Glick resolved JENKINS-25649 as Duplicate Duplicate Test Reports in Projects Change By: Jesse Glick (29/Apr/15 6:22 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Jesse Glick started work on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page Change By: Jesse Glick (29/Apr/15 6:21 PM) Status: Open InProgress 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Jesse Glick commented on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page The issue is that while JUnitResultArchiver removed its getProjectActions override in favor of implementing SimpleBuildStep.LastBuildAction, XUnitPublisher continues to implement getProjectAction, so both are used and two TestResultProjectAction instances are included in Job.getAllActions. 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] [ldap-plugin] (JENKINS-28162) Users cannot view the groups they are members of from the user page in jenkins
Dan Dumont created JENKINS-28162 Users cannot view the groups they are members of from the user page in jenkins Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 29/Apr/15 6:03 PM Description: As an admin, I can go to a user page and see the groups they belong to in the LDAP. This page is blank for that user when that user is logged in (they are looking at their page) I see no permission to control this in the security config. How is this controlled? Project: Jenkins Priority: Minor Reporter: Dan Dumont 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] [websphere-deployer-plugin] (JENKINS-28160) Plugin looking in incorrect Path for Websphere jars
Ricky Shelton assigned JENKINS-28160 to Greg Peters Plugin looking in incorrect Path for Websphere jars Change By: Ricky Shelton (29/Apr/15 5:25 PM) Assignee: GregPeters 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-28134) Git clone fails since git client plugin 1.17.0
Pavel Batanov commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Mark, reverting helps. So this can be workarounded 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] [websphere-deployer-plugin] (JENKINS-28160) Plugin looking in incorrect Path for Websphere jars
Greg Peters commented on JENKINS-28160 Plugin looking in incorrect Path for Websphere jars A workaround would be to create a symbolic link that points /var/lib/jenkins/.jenkins -- /var/lib/jenkins 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.
