[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive from time to time
Frank K edited a comment on JENKINS-21677 Jenkins becomes unresponsive from time to time Starting up fresh also shows that the GUI has trouble responding. It shows the "Please wait while Jenkins is getting ready to work" message to one browser even though the plugins in the background seem to function (in this case I see IRC joins and parts). It appears to be the dashboard, going straight to /login does show the login page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive from time to time
Frank K commented on JENKINS-21677 Jenkins becomes unresponsive from time to time Starting up fresh also shows that the GUI has trouble responding. It shows the "Please wait while Jenkins is getting ready to work" message to one browser even though the plugins in the background seem to function (in this case I see IRC joins and parts). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-20162) TestNG Results Trend doesn't show a failures
Nalin Makar commented on JENKINS-20162 TestNG Results Trend doesn't show a failures Sure, you can now use this feature. I would suggest that you change your maven command to mvn test -Dmaven.test.failure.ignore=true this will ensure that the build is not marked as failed when tests fail. So, the builds will show up as unstable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-20162) TestNG Results Trend doesn't show a failures
Ivan Kazakov edited a comment on JENKINS-20162 TestNG Results Trend doesn't show a failures Thank you. Why does the build fail on test failures? I have some jobs for testing only: mvn test. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-20162) TestNG Results Trend doesn't show a failures
Ivan Kazakov commented on JENKINS-20162 TestNG Results Trend doesn't show a failures Thank you. Why does the build fail on test failures? I have some jobs for testing only mvn test. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Hi This is William Bennett
Hi this is William Bennett and i would like to share a amazing opportunity and show you how i am making thousands of dollars on the internet from home. I get paid every week and every month in commissions, and can make over a 100,000 dollars in bonuses I am in the worlds best comp plan i want every buddy to be apart of it. It is free to sign up and lock in a spot on our team. click here to sign up free >>> http://tinyurl.com/m3zfvg3 <<< This opportunity only cost a total of $86.00 Add me on face book so we can talk about it. click here to add me >>> https://www.facebook.com/william.bennett.5095110 <<< -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19974) git2: http+userpwd credentials fail on subsequent builds
Mark Waite edited a comment on JENKINS-19974 git2: http+userpwd credentials fail on subsequent builds Using git-plugin 2.0.1 and git-client-plugin 1.6.2 I was able to access my bitbucket repository using the URL syntax https://username:passw...@bitbucket.org/markewaite/git-client-plugin.git . I checked that URL with a multi-configuration job that included Debian Testing, Debian Wheezy x64, Debian Wheezy x86, Windows 6.1 (Windows Home Server 2011), Windows 6.2 (Windows 8.1). I believe this bug is fixed. Could you check to confirm it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19974) git2: http+userpwd credentials fail on subsequent builds
Mark Waite resolved JENKINS-19974 as Fixed git2: http+userpwd credentials fail on subsequent builds Using git-plugin 2.0.1 and git-client-plugin 1.6.2 I was able to access my bitbucket repository using the URL syntax https://username:passw...@bitbucket.org/markewaite/git-client-plugin.git I believe this bug is fixed. Could you check to confirm it? Change By: Mark Waite (10/Feb/14 5:36 AM) Status: Reopened 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/groups/opt_out.
[JIRA] [git] (JENKINS-21163) Git server plugin blocks Jenkins startup
Mark Waite resolved JENKINS-21163 as Fixed Git server plugin blocks Jenkins startup I've submitted a pull request that seems to resolve the Jenkins startup problem https://github.com/jenkinsci/git-server-plugin/pull/2 . However, I was unable to use the git-server-plugin with the git-userContent-plugin, so I can't confirm that it works correctly. I can confirm that it does not seem to be broken the same way it was broken before. Change By: Mark Waite (10/Feb/14 5:17 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21513) trigger builds drafts if cahnge-set moved from non-draft to draft status and back again.
rin_ne commented on JENKINS-21513 trigger builds drafts if cahnge-set moved from non-draft to draft status and back again. 1) Yes, create-patchset event is received when draft is uploaded. 2) Correct behavior if you add draft published event to trigger on event in job config. You expect that jobs are not triggered by draft patchset. correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-alias-setter] (JENKINS-21734) When a job is copied, the aliases as copied over and corrupt the new job
Patrice Matignon created JENKINS-21734 When a job is copied, the aliases as copied over and corrupt the new job Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-alias-setter Created: 10/Feb/14 3:10 AM Description: When a job with aliases is used as a copy for a new job, the build aliases are copied over to the new project. It might not fail immediately, but at the very least the job can't be reloaded from disk and it can't be found. Sample from system logs include: Failed Loading job XX (new job) java.lang.NullPointerException at java.util.Vector.addAll(Vector.java:880) at hudson.model.AbstractProject.createTransientActions(AbstractProject.java:756) at hudson.model.Project.createTransientActions(Project.java:213) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:749) at hudson.model.AbstractProject.onLoad(AbstractProject.java:336) Feb 09, 2014 7:03:14 PM INFO jenkins.InitReactorRunner$1 onAttained Loaded all jobs Environment: Linux SLES 11.2; Jenkins v1.543 Project: Jenkins Labels: job copy-job build-alias Priority: Major Reporter: Patrice Matignon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pending-changes] (JENKINS-21733) cicicuit
baharudin yudhi commented on JENKINS-21733 cicicuit http://www.chlarayunita.blogspot.com http://www.tunablebird.blogspot.com http://www.blackdevil182.blogspot.com/ http://www.tunablebird.blogspot.com/2014/01/tips-memilih-kenari-gacor.html http://www.tunablebird.blogspot.com/2014/01/mengetasi-telur-lovebird-gagal-menetas.html http://www.tunablebird.blogspot.com/2014/01/tips-memilih-lovebird-yang-baik.html http://www.tunablebird.blogspot.com/2014/01/mengenal-penyakit-mata-pada-lovebird.html http://www.tunablebird.blogspot.com/2014/01/cara-sederhana-membedakan-jenis-kelamin.html http://tunablebird.blogspot.com/2014/02/mengenal-jenis-kenari-yorkshire.html http://tunablebird.blogspot.com/2014/02/pembahasan-mengenai-kenari-f1.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pending-changes] (JENKINS-21733) cicicuit
baharudin yudhi created JENKINS-21733 cicicuit Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Calculator.java Components: pending-changes Created: 10/Feb/14 2:16 AM Description: that the blog about information of bird http://tunablebird.blogspot.com Due Date: 10/Feb/14 12:00 AM Environment: goverment Fix Versions: current Project: Jenkins Labels: jenkins Priority: Minor Reporter: baharudin yudhi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start So far, no luck in reproducing this problem. From the code of the plugin, it shouldn't be possible to power on a VM twice during the startup cycle. The only thing that I can guess at (and this doesn't look to be the case from your logs) is that two slaves - both point at the same VM are trying to start the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager edited a comment on JENKINS-21528 Can't turn on a VM If there is no further feedback on this issue by Feb 16th, it will closed. As noted, Jenkins doesn't allow a job running on a slave to terminate the slave connection; doing so is considered immediate job failure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager assigned JENKINS-21528 to Jason Swager Can't turn on a VM Change By: Jason Swager (10/Feb/14 1:40 AM) Assignee: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager commented on JENKINS-21528 Can't turn on a VM If there is no further feedback on this issue, it will closed. As noted, Jenkins doesn't allow a job running on a slave to terminate the slave connection; doing so is considered immediate job failure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-20162) TestNG Results Trend doesn't show a failures
Nalin Makar resolved JENKINS-20162 as Fixed TestNG Results Trend doesn't show a failures Fixed. See http://jenkins-ci.org/commit/testng-plugin-plugin/f984cfafde186d3e1f3a779fccb8a2c61a20007d Option will be available in next release to show failed builds in Trend Graphs Change By: Nalin Makar (09/Feb/14 11:02 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/groups/opt_out.
[JIRA] [testng] (JENKINS-20438) Make it an option to show failed builds in trend graph
Nalin Makar resolved JENKINS-20438 as Fixed Make it an option to show failed builds in trend graph Fixed. option will be available in next release. Change By: Nalin Makar (09/Feb/14 11:01 PM) Status: In Progress 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/groups/opt_out.
[JIRA] [testng] (JENKINS-20438) Make it an option to show failed builds in trend graph
SCM/JIRA link daemon commented on JENKINS-20438 Make it an option to show failed builds in trend graph Code changed in jenkins User: Nalin Makar Path: README src/main/java/hudson/plugins/testng/Publisher.java src/main/java/hudson/plugins/testng/TestNGProjectAction.java src/main/resources/hudson/plugins/testng/Publisher/config.jelly src/main/resources/hudson/plugins/testng/Publisher/help-showFailedBuilds.html src/test/java/hudson/plugins/testng/PublisherTest.java src/test/java/hudson/plugins/testng/TestNGProjectActionTest.java src/test/java/hudson/plugins/testng/TestNGTestResultBuildActionTest.java src/test/java/hudson/plugins/testng/results/ClassResultTest.java src/test/java/hudson/plugins/testng/results/MethodResultTest.java src/test/java/hudson/plugins/testng/results/PackageResultTest.java http://jenkins-ci.org/commit/testng-plugin-plugin/f984cfafde186d3e1f3a779fccb8a2c61a20007d Log: Added: JENKINS-20438 - Make it an option to show failed builds in trend graph Compare: https://github.com/jenkinsci/testng-plugin-plugin/compare/b03c0ad77827...f984cfafde18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21675) Concurrent multijob build runs incorrectly link to the latest dependent build run.
hagzag resolved JENKINS-21675 as Fixed Concurrent multijob build runs incorrectly link to the latest dependent build run. Change By: hagzag (09/Feb/14 9:15 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21709) Job link broken if using jenkins with prefix configured
hagzag resolved JENKINS-21709 as Fixed Job link broken if using jenkins with prefix configured Alex merged https://github.com/nmorey suggestion Change By: hagzag (09/Feb/14 9:10 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/groups/opt_out.
[JIRA] [plugin] (JENKINS-21713) MultiJob Plugin does continue phase before current phase succeeded
hagzag resolved JENKINS-21713 as Fixed MultiJob Plugin does continue phase before current phase succeeded Change By: hagzag (09/Feb/14 9:00 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21646) ClassCastException with Maven Project
hagzag resolved JENKINS-21646 as Fixed ClassCastException with Maven Project Change By: hagzag (09/Feb/14 8:58 PM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez edited a comment on JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Noticed Steve merged it, good, I'll close this ticket This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez commented on JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Noticed you Steve merged it, good, I'll close this ticket This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez resolved JENKINS-21732 as Fixed Add an option to Skip DC Check on Upstream Changes Change By: Henri Gomez (09/Feb/14 6:11 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/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez commented on JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Please take a look at this Pull-Request : https://github.com/jenkinsci/dependency-check-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez updated JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Change By: Henri Gomez (09/Feb/14 6:10 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez created JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 09/Feb/14 6:10 PM Description: With multi-modular Maven projects, we define jobs to be triggered by Snapshot Dependency changes. Adding Disable Check on such change to Dependency Check will avoid to have jobs triggered by any changes in related modules Project: Jenkins Priority: Major Reporter: Henri Gomez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21708) Add an option to Skip DC Check on SCM Changes
Steve Springett resolved JENKINS-21708 as Fixed Add an option to Skip DC Check on SCM Changes Feature added to v1.1.1.1 Change By: Steve Springett (09/Feb/14 4:47 PM) Status: In Progress Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
Vincent Latombe commented on JENKINS-20534 Pegged CPU by writeSymlink calls PR to avoid renaming of symlinks https://github.com/jenkinsci/jenkins/pull/1057 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16734) Whitespace in label expression is not getting ignored
evernat commented on JENKINS-16734 Whitespace in label _expression_ is not getting ignored reproduced using Jenkins 1.549 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16728) "windows->x86" is an invalid expression
evernat commented on JENKINS-16728 "windows->x86" is an invalid _expression_ reproduced using Jenkins 1.549: "windows->x64", without space, is still an example in the context help for the label of any type of job, but "windows->x64" does not work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11329) Jenkins shows only Error after starting as a service on Ubuntu natty after upgrade to 1.434
evernat resolved JENKINS-11329 as Incomplete Jenkins shows only Error after starting as a service on Ubuntu natty after upgrade to 1.434 No response on this issue, so resolving as incomplete. Please reopen if needed. Change By: evernat (09/Feb/14 1:31 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21664) Plugins with optional dependencies and compiled with Java6 cause Exception in loading
ikedam
commented on JENKINS-21664
Plugins with optional dependencies and compiled with Java6 cause Exception in loading
I finally found the root cause.
Upcasting in codes cause class loading:
public void doSomething()
{
if(Jenkins.getInstance().getPlugin("dependee"))
{
Derived d = somemethod();
Base b = (Derive)d; // <- This causes load Derive even not executing doSomething().
}
}
and in Java6,
for(Base b: getDerivedList())
{
someMethodForBase(b);
}
This code is compiled as following:
for(Derived b: getDerivedList()) // <- Base is changed to Derived
{
someMethodForBase(b); // Here causes upcasting.
}
There are some exceptions:
Upcasting to Object does not cause class loading.
Conversion between generic types does not cause class loading. (as generic types are completely ignored in execution time)
Base b = derivedList.get( i ); does not cause class loading.
Base b = derivedIterator.next(); does not cause class loading.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-16240) Problem with NOT_BUILT build result
Mahmoud AllamehAmiri reopened JENKINS-16240 Problem with NOT_BUILT build result Change By: Mahmoud AllamehAmiri (09/Feb/14 8:00 AM) Resolution: Won't Fix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
