[JIRA] (JENKINS-40600) Jobs failing with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class
Title: Message Title Lorelei McCollum commented on JENKINS-40600 Re: Jobs failing with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class This is fixed now!! Thank you.. we have upgraded to latest version and no longer havin the issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40600) Jobs failing with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class
Title: Message Title Lorelei McCollum commented on JENKINS-40600 Re: Jobs failing with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class Dug deeper – we narrowed it down to one particular slave.. every time a job runs against it it hits this.. we are going to try restarting the slave Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40600) Jobs failing with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class
Title: Message Title Lorelei McCollum created an issue Jenkins / JENKINS-40600 Jobs failing with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/21 2:38 PM Priority: Major Reporter: Lorelei McCollum We have not upgraded jenkins in a while, we plan to shortly. We are on version 2.7.4 Recently we are now starting to see jobs fail with java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class It appears to happen in a shell script build step of our jobs, and we have not changed anything in a long time here, so I wanted to report this. Not sure where this is coming from or if I categorized it right, however this stops our pipeline cause jobs just fail and dont finish with this error causing the whole thing to halt and turn red [OfflineA-1-Verse] $ /bin/sh /tmp/hudson8465329998443229968.sh FATAL: command execution failed Userset=SequoiaSCNIris082 Target=w764-us2425.swg.usma.ibm.com java.io.InvalidClassException: cannot bind non-proxy descriptor to a proxy class at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:600) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1630) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1521) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1781) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373) at hudson.remoting.UserRequest.deserialize(UserRequest.java:217) at hudson.remoting.UserResponse.retrieve(UserRequest.java:250) at hudson.remoting.Channel.call(Channel.java:781) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.per
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Lorelei McCollum commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Yeah we really need this update too, do we know when this plugin will be available and released? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33168) Junit plugin took 7 hours to complete recording test failures
Title: Message Title Lorelei McCollum created an issue Jenkins / JENKINS-33168 Junit plugin took 7 hours to complete recording test failures Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 26/Feb/16 12:22 AM Environment: Ubuntu server Jenkins version 1.635 Priority: Blocker Reporter: Lorelei McCollum We heavily use the Junit plugin in our jobs to record our test results as part of our CD/CI pipeline Recently we hit over 10154 tests now, which is contained in about 50 junit.xml files we copy to the jenkins workspace of the job to have them recorded We use the jenkins junit post build step to record with these params Test report XMLs = */.xml Health report amplification factor =1.0 Additional test report features = Allow claiming of failed tests & Test stability History We have had some regressions in our pipeline causing lots of tests to fail, today we had 235 failures, and the jenkins junit plugin blocked our job for 7 hours to complete the recording of the test results... this was crazy long, and "Aborting/canceling" the jenkins job did nothing, so we just had to wait it out. this completely blocks our pipeline I didn't see any other bugs like this in the queue, so sorry if this
[JIRA] [multijob-plugin] (JENKINS-25675) Provide environment variables like Parameterized Trigger Plugin
Title: Message Title Lorelei McCollum commented on JENKINS-25675 Re: Provide environment variables like Parameterized Trigger Plugin Sebastian – I am seeing build vars like this for my triggered jobs in a phase GRTE_SELF_SERVICE___SEQUOIA_BVT_10_BUILD_NUMBER 16439 GRTE_SELF_SERVICE___SEQUOIA_BVT_10_BUILD_RESULT SUCCESS GRTE_SELF_SERVICE___SEQUOIA_BVT_11_BUILD_NUMBER 16442 GRTE_SELF_SERVICE___SEQUOIA_BVT_11_BUILD_RESULT SUCCESS GRTE_SELF_SERVICE___SEQUOIA_BVT_12_BUILD_NUMBER 16425 The name of the jobs I am triggering is "GRTE Self Service Sequoia BVT" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-31640) TRIGGERED_BUILD_RUN_COUNT doesn't properly update when you trigger many jobs with the same name
Title: Message Title Lorelei McCollum updated an issue Jenkins / JENKINS-31640 TRIGGERED_BUILD_RUN_COUNT doesn't properly update when you trigger many jobs with the same name this one I am short 2 Change By: Lorelei McCollum Attachment: envvars.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-31640) TRIGGERED_BUILD_RUN_COUNT doesn't properly update when you trigger many jobs with the same name
Title: Message Title Lorelei McCollum commented on JENKINS-31640 Re: TRIGGERED_BUILD_RUN_COUNT doesn't properly update when you trigger many jobs with the same name added another run where I was short 2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-31640) TRIGGERED_BUILD_RUN_COUNT doesn't properly update when you trigger many jobs with the same name
Title: Message Title Lorelei McCollum created an issue Jenkins / JENKINS-31640 TRIGGERED_BUILD_RUN_COUNT doesn't properly update when you trigger many jobs with the same name Issue Type: Bug Assignee: huybrechts Attachments: envvars.txt Components: parameterized-trigger-plugin Created: 19/Nov/15 12:33 AM Environment: Ubuntu with latest updates for plugins and jenkins Priority: Minor Reporter: Lorelei McCollum We just upgraded and I was excited to see the new TRIGGERED_BUILD_RUN_COUNT env vars however I am seeing a bug with them I have a MultiPlugin Job that has 1 phase and calls something like 45 jobs in that phase These jobs are ALL the same exact jenkins job, but I pass different parameters to them Everything goes well, but at the very end, when I look at the ENV vars, I am always short one or two in the TRIGGERED_BUILD_RUN_COUNT and the TRIGGERED_JOB_NAMES so those above will match, but they are short. You can see the oth
[JIRA] [multijob-plugin] (JENKINS-25675) Provide environment variables like Parameterized Trigger Plugin
Title: Message Title Lorelei McCollum commented on JENKINS-25675 Re: Provide environment variables like Parameterized Trigger Plugin It looks like in latest releases they updated this so we get more ENV vars for the mutlijob phases and the builds it kicked off, but there is an issue if you have 1 phase that kicks off 45+ of the same job (using different params to pass to them).. what happens is you end up with build vars for most of those runs, but it always loses a few Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-19680) Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed)
Title: Message Title Lorelei McCollum commented on JENKINS-19680 Re: Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed) I believe we are hitting this too, we have 1 multiphase that calls 45 of the same job but passes different params. The ENV output at the end, is missing ENV vars for the Build Number and Build Result of some of the 45 runs. It usually has most of them and is short 1 or 2.. which is a pain, cause there is no way to know the result or get the result of the jobs the phase triggered Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Lorelei McCollum commented on JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page added a picture of exact access.Let me know if you need more 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-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Lorelei McCollum updated JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page Change By: Lorelei McCollum (05/Mar/15 7:37 PM) Attachment: bug.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] [core] (JENKINS-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Lorelei McCollum commented on JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page read permission only 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-27226) Clicking More button on build history makes web page unresponsive and never loads
Lorelei McCollum commented on JENKINS-27226 Clicking More button on build history makes web page unresponsive and never loads I did not see anything with my search, sorry if I created a duplicate! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27226) Clicking More button on build history makes web page unresponsive and never loads
Lorelei McCollum created JENKINS-27226 Clicking More button on build history makes web page unresponsive and never loads Issue Type: Bug Assignee: Unassigned Attachments: bug.png Components: core Created: 03/Mar/15 2:58 PM Description: We just upgraded to 1.599. We are using Chrome 40. We have a lot of downstream jobs that are very parametrized and called A LOT throughout the day, so the build history is very large. We keep about 7 days of builds.. so that is QUITE large and from the picture you can see we set the build names as well for the params. What we notice is that now clicking the More button never actually loads. the web page just times out and hangs and becomes un responsive. No error thrown it just never comes back If there are logs I could collect let me know, but as of now since the upgrade we cannot access the build history anymore for most of our jobs If we open another Jenkins window, Jenkins is still responsive and works, its just that one page that is loading the build history stops working Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Lorelei McCollum created JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Mar/15 2:45 PM Description: Since we upgraded to 1.599 on the login of Jenkins it scrolls you all the way to the bottom of the page. We have 30 jenkins slaves, so it scrolls you to the bottom of the last slave, so the login UI is not visible. Then you have to scroll all the way back to the top before you can log in to jenkins I can provide more details if necessary, but I think it has to do with the amount of jenkins slaves we have Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Lorelei McCollum commented on JENKINS-27126 New Scroll bar in Jenkins Build history is showing when shouldn't be Chrome 40 no description is set no custom JS or CSS running, none of those themes 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Lorelei McCollum created JENKINS-27126 New Scroll bar in Jenkins Build history is showing when shouldn't be Issue Type: Bug Assignee: Unassigned Attachments: jenkins.png Components: core Created: 25/Feb/15 2:33 PM Description: We just updated to the latest jenkins version. We like the updates to the build history to control really long text. However it seems we are always seeing "scroll bars" now which are HUGE, but the text is not scrollable and does show up entirely. So not sure why the scroll bar is there This may be an enhancement and not a bug.. but he fact the txt isn't scrollable is why I created a bug. See the screen shot When the txt is longer it is actually wrapping.. so not sure why we have the scroll bar then? I also may have tagged the wrong component and I am sorry if I did so. Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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-26946) Would be nice to have a trigger based on an environment var or parameter
Lorelei McCollum commented on JENKINS-26946 Would be nice to have a trigger based on an environment var or parameter What version of the plugin is that in, the newest one? I don't see anything on the wiki about this, or maybe im missing something, but thanks this is great! We will try upgrading to the newest plugin soo we are on 38.2 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-26946) Would be nice to have a trigger based on an environment var or parameter
Lorelei McCollum created JENKINS-26946 Would be nice to have a trigger based on an environment var or parameter Issue Type: New Feature Assignee: Alex Earl Components: email-ext-plugin Created: 12/Feb/15 10:05 PM Description: Finding I want to send an email based on a build param. There is now way to either wrap the email sending in the post build in an if statement or add a trigger that is based on a environment variable or parameter This functionality would be extremely helpful Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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] [copyartifact-plugin] (JENKINS-26741) Copy Artifact plugin should allow for not failling build as an option
Lorelei McCollum commented on JENKINS-26741 Copy Artifact plugin should allow for not failling build as an option Actually I think we can close this, the help didn't work on the optional check box for me, but after reading more on it, I think optional will solve my need! 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] [copyartifact-plugin] (JENKINS-26741) Copy Artifact plugin should allow for not failling build as an option
Lorelei McCollum created JENKINS-26741 Copy Artifact plugin should allow for not failling build as an option Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 02/Feb/15 3:45 PM Description: We run a lot of jobs in a multi job so that they run in parallel and then when that phase is done we copy artifacts from each of them back to that build The issue I am hitting is the Config space limit for a job. This is because I have to wrap the copy artifact in a conditional statement so that if the env var is set and not FAILED then copy the artifacts I would rather just say if copy artifacts fail ignore and keep going on and don't fail the build Currently if the copy artifacts step fails the build stops and fails and then nothing else happens Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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] [multijob-plugin] (JENKINS-26738) Multi Job Plugin failed to inject variables into build
Lorelei McCollum created JENKINS-26738 Multi Job Plugin failed to inject variables into build Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 02/Feb/15 2:06 PM Description: Seeing this error for some of our jobs [MultiJob] - [ERROR] - Problems occurs on injecting env vars as a build step: null We have an acceptance parent mutli job that kicks off many jobs in parallel. It then copies artifacts from the triggered jobs If this step fails like the above then we cannot copy the artifacts as there is no ENV Var for the triggered build. Our pipeline then turns read and completely fails If there are more logs that I could provide please let me know Project: Jenkins Priority: Major Reporter: Lorelei McCollum 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-22835) User-defined source libraries
Lorelei McCollum commented on JENKINS-22835 User-defined source libraries This would be extremely helpful for us too, as I want to use the code to run from a script, but need the path to that script to use variables not hardcoded as the workspace changes with each execution and we allow for concurrent jobs of this type to run at the same time so you will not know what workspace it is at runtime 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-9980) Add the "Publish JUnit test result report" option to maven job configuration page
Lorelei McCollum commented on JENKINS-9980 Add the "Publish JUnit test result report" option to maven job configuration page Any update here, sounds like a pretty simple thing to add We could use this too the xunit plugin is allowed here, but that plugin has lots of log errors 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-25124) Junit publisher doesn't work for more than one test report
Lorelei McCollum created JENKINS-25124 Junit publisher doesn't work for more than one test report Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 13/Oct/14 3:22 PM Description: In the post build I would like to graph more than one test report for a given run. The flexible publish plugin allows you to use the Junit plugin more than once in a post build step, this does work well, however the main history test trend graph on the main page does not show unique graphs for each Report. It only shows one of the reports and displays the same graph for the second report To Explain better I want to publish reports for BVT1.xml and BVT0.xml.. I want to have separate test trend graphs for each of these. I use the flexible publish plugin + junit plugin in the post build and set one to find the BVT1.xml and the other to find BVT0.xml. When the job runs, it does correctly find the TestResults, but the main page for the job will show two test trend graphs of the same thing, so seems that is not "unique" Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum
commented on JENKINS-24731
Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
This is the issue in the code
while (preCheckResponse.getBoolean("building") == true || preCheckResponse.getString("result") == null) {
listener.getLogger().println("Remote build is currently running - waiting for it to finish.");
preCheckResponse = sendHTTPCall(preCheckUrlString, "POST", build, listener);
listener.getLogger().println("Waiting for " + this.pollInterval + " seconds until next retry.");
// Sleep for 'pollInterval' seconds.
// Sleep takes miliseconds so need to convert this.pollInterval to milisecopnds (x 1000)
try {
Thread.sleep(this.pollInterval * 1000);
} catch (InterruptedException e) {
this.failBuild(e, listener);
}
}
failBuild never is allowed to get into the abort exception because the boolean variable that would allow that is never modified after instance created
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-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum commented on JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Ahh Thanks for the information, I didn't know if core would allow things like this or not. Not good though. Hopefully the plugin team can get a fix out for this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum commented on JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Yeah I had to restart the jenkins server to kill this. VERY bad 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-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum commented on JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Ok I powered off the node this job was running on and still cannot abort this job, there is something seriously wrong with this plugin I added core to this.. because that should be able to overwrite and kill this job but I cannot. I am probably going to have to reboot the 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] [core] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum updated JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Change By: Lorelei McCollum (16/Sep/14 10:51 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum created JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger Created: 16/Sep/14 10:46 PM Description: Using this to execute a remote job on another jenkins system I had the block check box checked and was trying to use a properties file in the workspace for the parameters The job never triggered the remote job on the other jenkins server. The other jenkins server is indeed up. Predefined params with same configuration was working. When tried to do this with properties file check box.. the job got into a BAD state. I tried to abort, did not work. I tried to toggle node offline and disconnect the node, did not work The job is in an infinite loop this is REALLY bad I cannot kill this job. I think I am going to kill the process on the node. [EnvInject] - Loading node environment variables. Building remotely on rh632-us506 in workspace /var/lib/jenkins/workspace/LLBB3-Work-Queue Run condition [Regular _expression_ match] enabling prebuild for step [Trigger/call builds on other projects] Run condition [Regular _expression_ match] enabling prebuild for step [Trigger a remote parameterized job] [LLBB3-Work-Queue] $ /bin/sh -xe /tmp/hudson3940059047949035559.sh + echo 3133 3133 + echo SequoiaBuild=3133 Regular _expression_ run condition: _expression_=[^SCN$], Label=[Sequoia] Run condition [Regular _expression_ match] preventing perform for step [Trigger/call builds on other projects] Regular _expression_ run condition: _expression_=[^Sequoia$], Label=[Sequoia] Run condition [Regular _expression_ match] enabling perform for step [Trigger a remote parameterized job] Triggering this remote job: BVT1-csdl-glider-1 Not checking if the remote job BVT1-csdl-glider-1 is building. This job is build #[111] on the remote server. Triggering remote job now. Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #1 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #2 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #3 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #4 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #5 out of 5 ERROR: Remote build failed for the following reason, but the build will continue: ERROR: Max number of connection retries have been exeeded. Blocking local job until remote job completes Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #1 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #2 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #3 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #4 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #5 out of 5 ERROR: Remote build failed for the following reason, but the build will continue: ERROR: Max number of connection retries have been exeeded. Waiting for remote build to start. Waiting for 60 seconds until next poll. Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #1 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #2 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #3 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #4 out of 5 Connection to remote server failed, waiting for to retry - 60 seconds until next attempt. Retry attempt #5 out of 5 ERROR: Remot
[JIRA] [parameterized-remote-trigger] (JENKINS-23861) Parameterized remote trigger should allow setting parent build status based on downstream build status
Lorelei McCollum commented on JENKINS-23861 Parameterized remote trigger should allow setting parent build status based on downstream build status This would be nice, because right now if the build it triggers is unstable, it will just fail this build.. when you may not want that This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-23748) Connection errors should contain details about the error
Lorelei McCollum commented on JENKINS-23748 Connection errors should contain details about the error We are also seeing this, it will say this, but then the server is up and connection is working, the second attemp works would be good to get more logging 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] [pathignore] (JENKINS-15724) Add option to skip build if change set is empty
Lorelei McCollum commented on JENKINS-15724 Add option to skip build if change set is empty We could really use this option.. we have builds that poll for SCM.. but we would also like to trigger them and run them manually, and we do not need them to "build" if there is no 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] [gui] (JENKINS-24589) Build History - name and links overlap if build names are long
Lorelei McCollum commented on JENKINS-24589 Build History - name and links overlap if build names are long Yes we see this as well now.. granted the UI is much better.. but hard to get to the results now for some jobs 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] [plot] (JENKINS-24236) Support the setting of a threshold so if graph drops below you can take action
Lorelei McCollum created JENKINS-24236 Support the setting of a threshold so if graph drops below you can take action Issue Type: New Feature Assignee: nidaley Components: plot Created: 12/Aug/14 4:38 PM Description: Would be nice to be able to notify or email or flag if the graph yvalues drop below a given threshold so they you can email and notify. Saves the end user from having to review the graphs each day Project: Jenkins Priority: Major Reporter: Lorelei McCollum 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] [plot] (JENKINS-24235) No way to clear out a plot graph without deleting it in the config page
Lorelei McCollum created JENKINS-24235 No way to clear out a plot graph without deleting it in the config page Issue Type: Bug Assignee: nidaley Components: plot Created: 12/Aug/14 4:27 PM Description: I am not sure how to clear out plots and graphs without going into the config and deleting the plot saving, re building then going back into config and readding the plot I would like a way to just clear or wipe out the data for the plot so it starts over Project: Jenkins Priority: Major Reporter: Lorelei McCollum 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] [plot] (JENKINS-24234) Support environment variables in various pieces of the plot section
Lorelei McCollum created JENKINS-24234 Support environment variables in various pieces of the plot section Issue Type: New Feature Assignee: nidaley Components: plot Created: 12/Aug/14 4:21 PM Description: Would be nice to be able to use environment or build variables in the titles or the plot groups of the y axis etc.. mainly any text field when setting this up in the config of your job would allow for variables Project: Jenkins Priority: Major Reporter: Lorelei McCollum 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] [plot] (JENKINS-24233) Support changing the colors of graph lines or bars
Lorelei McCollum created JENKINS-24233 Support changing the colors of graph lines or bars Issue Type: New Feature Assignee: nidaley Components: plot Created: 12/Aug/14 4:20 PM Description: Would be nice to dictate the colors the lines/bars choose.. as it defaults to red for the first one and red always looks like a "fail" type of graph.. when you may not be graphing failures.. would be nice to say use blue or green or yellow Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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] (JENKINS-11280) Downstream project name is not accepting env variable/build parameters
Lorelei McCollum commented on JENKINS-11280 Downstream project name is not accepting env variable/build parameters Yes we would like this as well.. seems it works for the "Build" section but not the "Post Build" section! 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-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum commented on JENKINS-24183 New UI layout is not properly resizing for build history component ahh 1.576.. nevermind then 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-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum updated JENKINS-24183 New UI layout is not properly resizing for build history component Change By: Lorelei McCollum (11/Aug/14 9:29 PM) Status: Reopened Open 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-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum reopened JENKINS-24183 New UI layout is not properly resizing for build history component we upgraded to 1.575 today, which I thought would have the fix in it, but still seeing the build history overlap Not sure if it was in that release or not.. if not then you can close this.. but if it was it didn't fix it for us Change By: Lorelei McCollum (11/Aug/14 9:28 PM) Resolution: Duplicate 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/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24199) Post Build trigger parameterized job does not resolve variables used for job name
Lorelei McCollum created JENKINS-24199 Post Build trigger parameterized job does not resolve variables used for job name Issue Type: Bug Assignee: huybrechts Attachments: triggerjob.png Components: parameterized-trigger Created: 11/Aug/14 1:39 PM Description: When using the trigger parameterized build in a jenkins job, we like to use a variable for the job name and then that variable is part of the current jobs parameters So we build a job with paramters, pass it the name of the job to trigger inside the build section. This works great inside the build section, we can specify $JobName on the projects to build line However if we try to do the same thing in the PostBuild section it does not resolve the variable names. We would like it to also do variable resolution in post build trigger parameterized job You can see in the picture, this is what we would like to do, but it does not resolve the variable $JobName $JobName is a build variable of this current job. If we put this block into the Build section it does work, only post build has the problem Environment: Jenkins Ubuntu server 1.574 Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum commented on JENKINS-24183 New UI layout is not properly resizing for build history component because of how our jobs are we can't click the "more" button anymore..that was why I chose the escalation I did... so we can even get to builds.. we have so many builds we have to use the more button all the time and now it is hidden behind other links.. so its like we can't even debug our jobs I am glad to hear it is fixed though! But what version of Jenkins.. we are on 1.574 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] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading
Lorelei McCollum commented on JENKINS-24182 Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading yep it fixed the issue.. jobs are back.. but wanted to report the issue with latest release 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-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum updated JENKINS-24183 New UI layout is not properly resizing for build history component Change By: Lorelei McCollum (08/Aug/14 7:46 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum commented on JENKINS-24183 New UI layout is not properly resizing for build history component This is also making it really hard to click on the builds, as the text is overlapping with the rest of the 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/d/optout.
[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component
Lorelei McCollum created JENKINS-24183 New UI layout is not properly resizing for build history component Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: buildhistory.png Components: core, gui Created: 08/Aug/14 6:54 PM Description: We just upgraded our jenkins server to Jenkins ver. 1.574 There is now a new Skin and UI look to the server. However there is a regression. We use longer names in our "Build History" of jobs,and now with the longer names, the rest of the page is not resizing properly as it did in the past. so it is very hard to read and see the job page I can provide more details if needed, but it is making it very hard to use the new UI Environment: Jenkins Ubuntu server environment Project: Jenkins Priority: Major Reporter: Lorelei McCollum 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] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading
Lorelei McCollum created JENKINS-24182 Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading Issue Type: Bug Affects Versions: current Assignee: Lucie Votypkova Components: disk-usage Created: 08/Aug/14 6:47 PM Description: We upgraded to version .24 from .23 of the disk usage plugin, and it caused our Maven Project jobs to no longer show up and were not accessible in Jenkins UI. Config.xml files still existed on the server From inspecting the logs we saw this stack Aug 08, 2014 1:51:38 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job ourjobname java.lang.NullPointerException at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:971) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:740) at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:485) at hudson.model.AbstractProject.save(AbstractProject.java:304) at hudson.plugins.disk_usage.DiskUsageProperty.setOwner(DiskUsageProperty.java:150) at hudson.model.Job.onLoad(Job.java:213) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.maven.MavenModule.onLoad(MavenModule.java:283) at hudson.model.Items.load(Items.java:279) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:790) at hudson.model.Items.load(Items.java:279) at jenkins.model.Jenkins$18.run(Jenkins.java:2599) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Environment: Ubuntu server Jenkins environment Project: Jenkins Priority: Blocker Reporter: Lorelei McCollum 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-user-vars] (JENKINS-18535) Retrieve the users e-mail building the job or promoting the job
Lorelei McCollum commented on JENKINS-18535 Retrieve the users e-mail building the job or promoting the job Is this already done? Wondering when the next release of the plugin will be? From looking in GIT seems it is in the source? 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Lorelei McCollum commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Yeah I would like users to be able to build their own stream, and then have a pre submission pipeline run against it, so it would do things like deploy that build, test it, report out on it etc.. but I would want it to be that persons own Stream or workspace... so they can test it out before delivering back to the main trunk - does that make sense? 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Lorelei McCollum commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. I would also like this functionality, it would be nice to be able to have a build with paramaters, where you pass in your credentials and the workspace and it would then build 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] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Lorelei McCollum commented on JENKINS-21086 jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown This is happening for us with delete-node on jenkins 1.564 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-user-vars] (JENKINS-14826) Have the Build User Vars plugin expose the build user's email address
Lorelei McCollum commented on JENKINS-14826 Have the Build User Vars plugin expose the build user's email address From looking at the source looks like they have exposed BUILD_USER_EMAIL But the latest release of the plugin 1.3 doesn't seem to have this support? When will this be included? 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] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Lorelei McCollum created JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 13/Feb/14 1:45 PM Description: A bug was introduced in version 1.11 of this plugin and is still reproduced in 1.12 of the plugin. This prevents us from updating to the latest version of the plugin. When we upgraded to the new version of the plugin, our CPU of the jenkins master was pegged and would not go down. We attempted to add more CPUs but did not help. Turns out from profiling the updateSubBuild function in the plugin is being called millions of times in a few seconds. We are extensively using this plugin for parallel testing of our product, and have many multi job plugin jobs with many parallel steps. Please let us know if we need to collect any other data, or you would like to discuss more of the design and how we use the plugin Environment: Jenkins master server is Ubuntu 12 server build 64 bit Fix Versions: current Project: Jenkins Labels: multi-job concurrent-build multijob Priority: Blocker Reporter: Lorelei McCollum 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.
