[JIRA] [matrix-project-plugin] (JENKINS-28107) Matrix parent should take an executor slot until the point where children are triggered
Simon Richter commented on JENKINS-28107 Matrix parent should take an executor slot until the point where children are triggered That helps distribute the load a bit, but is still suboptimal (rather than 30 concurrent parent jobs I now have 10). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Mark Waite commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided That's a fair approach as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos edited a comment on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Mark Waite I will really love to do it, but unfortunately my days are way too short to do that. This issue is not impacting just me. I am sure that there are other folks around here with better understanding of this plugin and they can do it in a blink of an eye. Worst case I will say bye bye to this plugin and I will handle that like in the old days "Executed Windows Batch cmd" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Mark Waite commented on JENKINS-28032 Included Regions do not work when monitoring all branches When you say "monitor all branches", the plugin thinks that means "if a previously unbuilt SHA1 is detected on any branch, then compute the differences between the most recent build and that unbuilt SHA1 and pass those differences through the inclusion and exclusion filters". There is an option in the plugin to make comparisons to a specific named branch, rather than to the last build, but I'm not sure if even that would meet your needs. You might try a different experiment, using the multi-branch plugin to automatically create and delete jobs for branches as they are created and deleted. I'm not sure that plugin allows inclusion / exclusion, but it is probably worth an experiment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Mark Waite I will really love to do it, but unfortunately my days are way too short to do that. This issue is not impacting just me. I am sure that there are other folks around here with better understanding of this plugin and they can do it in a blink of an eye. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28124) userContent is corrupt in 1.610
Igor Koyfman created JENKINS-28124 userContent is corrupt in 1.610 Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Apr/15 3:46 AM Description: After updating to 1.610 a part of userContent, which in our case is less than 1 MB or python scripts, is full of bad characters. Everything works again after reverting to 1.607. It's an identical corruption in all jobs on all nodes; I suspect it's whatever gets transferred last. Project: Jenkins Priority: Major Reporter: Igor Koyfman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Mark Waite commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Zeus Minos, I mean that you can fork your own copy of the git client plugin source code and the git plugin source code on GitHub, compile them, locate the places in the source code where the --tag argument is passed to command line git, then you can experiment with modifying the behavior to better match what you want. That will allow you to modify and test your changes. If you find the changes are useful to you and don't break other use cases, you could provide unit tests which confirm the new behavior you've added, and can submit them as a pull request for possible inclusion in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @MArk Waite What do you mean by "Investigating the area of plugin where the --tag argument is passed?". Isn't such behavior hardcoded in the plugin? If not how shall I disabled 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] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided In our case, we just want a flag to disable the "initial" fetch of all tags. With Gerrit plugin, we're fetching a unique refspec afterward, so there's no need for us to do more than "git init". Would it be possible to have the option of disabling the initial fetch/clone? We don't need anything more complex than 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] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Mark Waite commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided The plugin already has significant challenges the plugin maintaining compatibility among its many different use cases. I'd rather not provide even more opportunities for user surprises by allowing general purpose customization of the parameters passed to git. If we allow you to pass a custom parameter to a specific git command, it seems like that will then guarantee that the plugin must use that exact command and honor that exact parameter indefinitely. As an example, previously the plugin used "git clone" to populate the repository. When credentials support was added, that was switched to "git fetch". In the future, it may switch back to "git clone". Allowing you to pass arbitrary parameters to a subset of git commands used by the plugin seems like it will either make compatibility even more difficult, or make future changes even more difficult. Have you considered investigating the area of the plugin where the --tags argument is passed, seeking a way to remove that call to --tags without harming the rest of the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Dominique Brice commented on JENKINS-27588 Labels used in Label Factory are shown as not used Plugin page updated. Stefan Kalmelid, how's the new version working on your prod instance? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos edited a comment on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Robert More: Thank you for your replay . Well Shallow Clone has been active since day 1 in our jobs and still 7 min. Guys can you please allow us to customize the git parameters in the coming versions. In first place I do not need or want to fetch any tags :-/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Robert More: Thank you for your replay . Well Shallow Clone has been active since day 1 in our jobs and still 7 min. Guys can you please allow us to customize the git parameters in the coming versions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided We've been able to reduce cloning time by using a reference repo. We first created a bare clone in a shared space on each build slave, then use this as a reference repo in the build job. Now it clones from the reference, but it's a much faster FS operation rather than network. It's still not ideal, since we don't really need the repo to consume disk (or duplicated into the builds), but it's cut out ~2 minutes of the build job. In the project configuration, navigate to "Source code management" -> "Additional Behaviours" -> "Advanced Clone Behaviors". Check "Shallow Clone" and then the absolute path to the local cloned repo. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore edited a comment on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided We've been able to reduce cloning time by using a reference repo. We first created a bare clone in a shared space on each build slave, then use this as a reference repo in the build job. Now it clones from the reference, but it's a much faster FS operation rather than network. It's still not ideal, since we don't really need the repo to consume disk (or duplicated into the builds), but it's cut out ~2 minutes of the build job. In the project configuration, navigate to "Source code management" -> "Additional Behaviours" -> "Advanced Clone Behaviors". Check "Shallow Clone" and then the absolute path to the local cloned repo. EDIT: If you're not already using "Advanced Clone Behaviours", be sure to add it from the "Add" button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Is there any temp workaround ? Fetching all the tags in our case is just a waist of time. 00:01:28.364 > C:\Program Files\Git\cmd\git.exe -c core.askpass=true fetch --tags --progress g...@gitlab.dev.local:superman/b.git +refs/heads/:refs/remotes/origin/ --depth=1 00:07:05.694 > C:\Program Files\Git\cmd\git.exe config remote.origin.url g...@gitlab.dev.local:superman/b.git # timeout=10 As you can see It takes about 7 min to execute the next cmd. This is just a waist of time :-/ Please share with me any workaround This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [logstash-plugin] (JENKINS-28040) Allow logstash plugin to feed a syslog server
Rusty Gerard commented on JENKINS-28040 Allow logstash plugin to feed a syslog server While I think this functionality belongs in the syslog-logger plugin rather than the logstash plugin, it might be useful to share the BuildData object I created for the logstash plugin across both. Cyrille Le Clerc, what do you think? The logstash plugin sends data across as JSON. Would it be useful to split out BuildData.java in logstash out to share across both plugins so they share a common format? https://github.com/jenkinsci/logstash-plugin/blob/master/src/main/java/jenkins/plugins/logstash/persistence/BuildData.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Brantone updated JENKINS-28043 Reload configs of all jobs in folder Change By: Brantone (28/Apr/15 1:00 AM) Description: If manual changes made to config.xml, hitting Jenkins > Manage > Reload Configuration from Disk does not seem to actually take jobs within the folder. Actually Repro:1 . Create folder2 . Create job within folder3 . that may be a Jenkins core issue Make changes by hand directly to Folder's config.xml4. Make changes by hand directly to Job's config.xml5. Reload config6. Folder has updates , worth checking though but Job does not reflect changes . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Brantone commented on JENKINS-28043 Reload configs of all jobs in folder Yeah, my bad, I was pretty sure I had selected the correct component for Cloudbees Folder Will add repro steps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23460) 'pkg.jenkins-ci.org' unavailable (or running very slow)
Brantone commented on JENKINS-23460 'pkg.jenkins-ci.org' unavailable (or running very slow) Not sure this is an issue with Multi-Job plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-25062) Jenkins Testlink plugin cannot find testing result, shows "Not run"
Bruno P. Kinoshita commented on JENKINS-25062 Jenkins Testlink plugin cannot find testing result, shows "Not run" Not really Kishore. I'm busy relocating and starting with a new job. Should you have a pull request, let me know and we can merge / release it. Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-monitor-plugin] (JENKINS-28102) Getting error with build Monitor plugin
viral shah commented on JENKINS-28102 Getting error with build Monitor plugin HI Daniel, I managed to fix the issue by uninstalling the plugin Claim build . As per your advised i saw the logs and it was showing some exception due to claim build so tried to uninstall it and it worked. But i dont know if you have to fix anything from your side ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski commented on JENKINS-28032 Included Regions do not work when monitoring all branches Thanks for looking into this, Mark. My use case seems simple on the surface. These are the basic requirements: One single repo with all projects in different folders (ProjectA, ProjectB, etc.) Jenkins has a universal jobs called 'ProjectA', 'ProjectB' and so on, that monitor all branches. This way I can have devs validate their changes and validate anything going into a release branch using one job. At the same time, when polling Git, check for changes only under 'ProjectA' folder, so I don't trigger 'ProjectA' job for changes under 'ProjectB' folder. Let me know if you have an idea on how to deal with this setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Mark Waite commented on JENKINS-28032 Included Regions do not work when monitoring all branches I think that hints at a fundamental difference between your use model and the way the plugin is coded in that area. I think you want to compare against some prior point that is not the preceding build, while the plugin wants to compare against the results of the preceding build. Can you explain further how you would envision the plugin should decide the base SHA1 for the comparison? If the job changes freely from one unrelated branch to another, how would it assemble the list of files which changed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27998) Git plugin fails to clone with ssh protected passphrase
Mark Waite updated JENKINS-27998 Git plugin fails to clone with ssh protected passphrase Change By: Mark Waite (28/Apr/15 12:08 AM) Summary: Git plugin fails to connect clone with ssh protected passphrase This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27998) Git plugin fails to connect
Mark Waite edited a comment on JENKINS-27998 Git plugin fails to connect It is possible to fix that. Someone would need to add support for passphrase protected ssh keys to the git plugin authentication, or if it is implemented and not working, they would need to fix the bug. Pull requests with automated tests are welcomed. Regarding your comment about it being a security flaw, I don't see how entering the passphrase into a web form in Jenkins is any more secure than using an ssh key with no passphrase. In both cases, there is enough information stored in Jenkins to use the credential, without any additional prompting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27998) Git plugin fails to connect
Mark Waite commented on JENKINS-27998 Git plugin fails to connect It is possible to fix that. Someone would need to add support for passphrase protected ssh keys to the git plugin authentication, or if it is implemented and not working, they would need to fix the bug. Regarding your comment about it being a security flaw, I don't see how entering the passphrase into a web form in Jenkins is any more secure than using an ssh key with no passphrase. In both cases, there is enough information stored in Jenkins to use the credential, without any additional prompting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski updated JENKINS-28032 Included Regions do not work when monitoring all branches The issue appears to boil down to the way changelist is being gathered via the git log command. That is happening in 'showRevision' method (CliGitAPIImpl.java): git log --full-history --no-abbrev --format=raw -M -m --raw .. When the SHAs come from different branches, the result has more entries than expected, so 'isRevExcluded' method in GiSCM.java will check changes that were already built before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink-plugin] (JENKINS-28122) Plugin doesn't update the test cases status properly on testlink (ver:1.9.13)
kishore vnjam updated JENKINS-28122 Plugin doesn't update the test cases status properly on testlink (ver:1.9.13) Change By: kishore vnjam (27/Apr/15 11:13 PM) Description: Tried following the tutorials, test completed with SUCCESS status.The test case in Testlink is reported as Not Run. It never updates the status on Test Link. Attaching the screens from both Jenkins and TestLink. Please let me know if you need any additional information to further troubleshoot this.Thanks. Attachment: 28122-TestResults-Jenkins.JPG Attachment: 28122-TestLink-JobDefinition.JPG Attachment: 28122-jenkins-workspace.tar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-label-assignment-plugin] (JENKINS-28123) Jobs stay queued forever if label assignment is initially unavailable
Christian Goetze
commented on JENKINS-28123
Jobs stay queued forever if label assignment is initially unavailable
The way a node can become available is also via a script, which modifies the labels on nodes and then runs:
jenkins.model.Jenkins.instance.labels.each { it.reset() }
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [groovy-label-assignment-plugin] (JENKINS-28123) Jobs stay queued forever if label assignment is initially unavailable
Christian Goetze commented on JENKINS-28123 Jobs stay queued forever if label assignment is initially unavailable See also: http://stackoverflow.com/questions/29907462/jobs-using-groovy-label-assignment-plugin-stay-queued-forever-if-no-slave-is-ini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-label-assignment-plugin] (JENKINS-28123) Jobs stay queued forever if label assignment is initially unavailable
Christian Goetze created JENKINS-28123 Jobs stay queued forever if label assignment is initially unavailable Issue Type: Bug Assignee: Unassigned Components: groovy-label-assignment-plugin Created: 27/Apr/15 10:59 PM Description: If a job sets a label and no node is available to run the job, the job just stays queued forever even if an appropriate node later becomes available. Is there some (groovy) way to "tickle" the job in the queue? Project: Jenkins Priority: Minor Reporter: Christian Goetze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink-plugin] (JENKINS-28122) Plugin doesn't update the test cases status properly on testlink (ver:1.9.13)
kishore vnjam created JENKINS-28122 Plugin doesn't update the test cases status properly on testlink (ver:1.9.13) Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink-plugin Created: 27/Apr/15 10:56 PM Description: Tried following the tutorials, test completed with SUCCESS status. The test case in Testlink is reported as Not Run. It never updates the status on Test Link. Please let me know if Environment: Testlink Verion : 1.9.13 Plugin Version : 3.10 Jenkins Version : 1.610 Project: Jenkins Priority: Blocker Reporter: kishore vnjam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27998) Git plugin fails to connect
Jamie Doornbos commented on JENKINS-27998 Git plugin fails to connect The credentials for the original key do have a passphrase attached; the SSH agent plugin is using it correctly. But it looks like the git plugin is not. I tested a key with no passphrase and confirmed that the git plugin does work in that case. Is it possible to fix this? It seems like a security flaw to have to always use keys with no passphrase. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink-plugin] (JENKINS-25062) Jenkins Testlink plugin cannot find testing result, shows "Not run"
kishore vnjam commented on JENKINS-25062 Jenkins Testlink plugin cannot find testing result, shows "Not run" Was there any update on this issue? I am running in to similar issue. Following are my versions: TestLink Version : 1.9.13 Jenkins Version : 1.610 Plugin Version : 3.10 I tried the steps mentioned in the tutorial and is not updating the TestLink results ( it is listing all the tests as Not Run just as mentioned in the original issue). Is this version incompatibility or any work arounds? Appreciate any help/suggestions on 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] [mercurial-plugin] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Geoffrey Edwards
created JENKINS-28121
Mercurial GeneralSCM step does not create intermediary directories.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
mercurial-plugin, workflow-plugin
Created:
27/Apr/15 10:28 PM
Description:
Base slave install with nothing in the home directory.
Standard Freestyle project creates the full path ($JENKINS_HOME\\workspace).
Workflow project fails the scm step with 'abort: The system cannot find the path specified: $JENKINS_HOME\workspace\\'
Manually creating the $JENKINS_HOME\workspace directory fixes the issue unless the scm step specifies a sub-directory, in which case the parent of the sub-directory also has to be manually created.
Workflow script was a simple:
node('slave-name') {
checkout([$class: 'MercurialSCM', ...])
}
Environment:
Jenkins Master (Fedora 22 - Server 64bit)
Jenkins Slave (Win7 - 64bit)
Jenkins Version - v1.611
Mercurial Plugin - v1.52
Workflow Plugin - v1.5
Project:
Jenkins
Labels:
workflow
scm
Priority:
Major
Reporter:
Geoffrey Edwards
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-23609) "Successful" and "Failed" link in matrix-combinations-parameter do not work
ikedam closed JENKINS-23609 as Fixed "Successful" and "Failed" link in matrix-combinations-parameter do not work 1.0.8 with this fix released. It will be available in a day. Change By: ikedam (27/Apr/15 10:14 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28120) Jenkins core to require Java7
SCM/JIRA link daemon commented on JENKINS-28120 Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly pom.xml http://jenkins-ci.org/commit/jenkins/de8bba40cf593bec5fda197e09f644ae53e207a3 Log: JENKINS-28120 As the first step of Java7 migration, ship Java7 class files without requiring Java7 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] [core] (JENKINS-28120) Jenkins core to require Java7
SCM/JIRA link daemon commented on JENKINS-28120 Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly pom.xml http://jenkins-ci.org/commit/jenkins/2826ea3185f5ca1df02ab54d465a14308ecffe05 Log: JENKINS-28120 As the first step of Java7 migration, ship Java7 class files without requiring Java7 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Jesse Glick assigned JENKINS-28110 to Jesse Glick NoStaplerConstructorException for Jenkins 1.610 Change By: Jesse Glick (27/Apr/15 9:48 PM) Assignee: Manuel Carrasco Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28120) Jenkins core to require Java7
Kohsuke Kawaguchi created JENKINS-28120 Jenkins core to require Java7 Issue Type: Task Assignee: Kohsuke Kawaguchi Components: core Created: 27/Apr/15 9:47 PM Description: This ticket tracks the promise made in http://jenkins-ci.org/content/good-bye-java6 that we are bumping up core requirements from Java6 to Java7. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28114) Update to 1.610 causing main Jenkins config page to throw
Jesse Glick assigned JENKINS-28114 to Jesse Glick Update to 1.610 causing main Jenkins config page to throw Change By: Jesse Glick (27/Apr/15 9:47 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28093) Plugin Manager gets exception because of FileNotFound nodejs Installer
Jesse Glick assigned JENKINS-28093 to Jesse Glick Plugin Manager gets exception because of FileNotFound nodejs Installer Change By: Jesse Glick (27/Apr/15 9:46 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28112) JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+
stephenconnolly started work on JENKINS-28112 JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+ Change By: stephenconnolly (27/Apr/15 9:43 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/9c9049eb4da6145261d6b5fda6ed57dd676bf108 Log: Noting merge of JENKINS-28111 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-27953) Fails to load a matrix project for script-security
Jesse Glick resolved JENKINS-27953 as Duplicate Fails to load a matrix project for script-security That is it. Change By: Jesse Glick (27/Apr/15 9:42 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Code changed in jenkins User: Stephen Connolly Path: core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly http://jenkins-ci.org/commit/jenkins/ce94434b164d1ac74132cecdc6f123787decbf48 Log: Merge pull request #1676 from stephenc/jenkins-28111 [FIXED JENKINS-28111] JNLP slave JVM Options are inconsistently applied Compare: https://github.com/jenkinsci/jenkins/compare/5b4ed2dae2dd...ce94434b164d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon resolved JENKINS-28111 as Fixed JNLP slave JVM Options are inconsistently applied Change By: SCM/JIRA link daemon (27/Apr/15 9:40 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Code changed in jenkins User: Stephen Connolly Path: core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly http://jenkins-ci.org/commit/jenkins/84e485fc5e608bccf080bf46c0e31c43c6bef474 Log: [FIXED JENKINS-28111] JNLP slave JVM Options are inconsistently applied This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
Alon Chanukov commented on JENKINS-23577 Add support for using branches in Git Parameter plugin Any update on 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-28111) JNLP slave JVM Options are inconsistently applied
stephenconnolly assigned JENKINS-28111 to stephenconnolly JNLP slave JVM Options are inconsistently applied Change By: stephenconnolly (27/Apr/15 9:27 PM) Assignee: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Serge Zukov commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 to Daniel: yes, 1.611 is also affected. Sorry, I've missed the version number in the title. In my case project uses both copy and performance plugins. I'm confirming that rolling back to 1.609 resolves the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-23609) "Successful" and "Failed" link in matrix-combinations-parameter do not work
SCM/JIRA link daemon commented on JENKINS-23609 "Successful" and "Failed" link in matrix-combinations-parameter do not work Code changed in jenkins User: Stephen Connolly Path: src/test/java/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinitionTest.java http://jenkins-ci.org/commit/matrix-combinations-plugin/f5c1b0bfd32e57548462bd7588113dd0ba4394e8 Log: JENKINS-23609 Re-enable Successful and Failed link tests Also None link test was actually testing Successful link! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-23609) "Successful" and "Failed" link in matrix-combinations-parameter do not work
SCM/JIRA link daemon commented on JENKINS-23609 "Successful" and "Failed" link in matrix-combinations-parameter do not work Code changed in jenkins User: ikedam Path: src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinition/index.groovy src/test/java/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinitionTest.java http://jenkins-ci.org/commit/matrix-combinations-plugin/29dfcb053cb515fa20e5611a2ec638e49f0fc3cd Log: Merge pull request #8 from stephenc/jenkins-23609 [FIXED JENKINS-23609] "Successful" and "Failed" links do not work Compare: https://github.com/jenkinsci/matrix-combinations-plugin/compare/b516d49d0a96...29dfcb053cb5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-23609) "Successful" and "Failed" link in matrix-combinations-parameter do not work
SCM/JIRA link daemon resolved JENKINS-23609 as Fixed "Successful" and "Failed" link in matrix-combinations-parameter do not work Change By: SCM/JIRA link daemon (27/Apr/15 9:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-23609) "Successful" and "Failed" link in matrix-combinations-parameter do not work
SCM/JIRA link daemon commented on JENKINS-23609 "Successful" and "Failed" link in matrix-combinations-parameter do not work Code changed in jenkins User: Stephen Connolly Path: src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinition/index.groovy http://jenkins-ci.org/commit/matrix-combinations-plugin/9716d77a77c6ca011c6bf28bca6a26d43056ce60 Log: [FIXED JENKINS-23609] "Successful" and "Failed" links do not work Seemed to not actually be providing the run result data to the matrix. Unclear how this could ever have worked This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-28116) Password injection no longer supplies password
Daniel Beck resolved JENKINS-28116 as Duplicate Password injection no longer supplies password Change By: Daniel Beck (27/Apr/15 9:06 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28117) NodeJS err=13; permission denied on fedora20
Daniel Beck commented on JENKINS-28117 NodeJS err=13; permission denied on fedora20 Any noexec flags to mount around? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28114) Update to 1.610 causing main Jenkins config page to throw
Daniel Beck commented on JENKINS-28114 Update to 1.610 causing main Jenkins config page to throw Referenced this issue in https://github.com/jenkinsci/jenkins/pull/1563#issuecomment-96742579 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Daniel Beck commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 Referenced this issue from https://github.com/jenkinsci/jenkins/pull/1563#issuecomment-96775752 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
Daniel Beck commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied stephenconnolly Should this be assigned to you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28112) JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+
Daniel Beck updated JENKINS-28112 JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+ Change By: Daniel Beck (27/Apr/15 9:01 PM) Assignee: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
Daniel Beck updated JENKINS-28115 Division by zero in Executor.getProgress Change By: Daniel Beck (27/Apr/15 9:02 PM) Assignee: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-28107) Matrix parent should take an executor slot until the point where children are triggered
Daniel Beck commented on JENKINS-28107 Matrix parent should take an executor slot until the point where children are triggered Possible workaround: Don't restrict the parent build to a 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Daniel Beck commented on JENKINS-23902 Matrix parent takes executor slot and blocks children There have been fixes to the queue behavior until 1.610. That version or higher would be needed for any follow-up issue to 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] [core] (JENKINS-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon commented on JENKINS-28115 Division by zero in Executor.getProgress Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/5b4ed2dae2dd0122e65641e01c141f76ac5fd0b8 Log: Noting merge of JENKINS-28115 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon commented on JENKINS-28115 Division by zero in Executor.getProgress Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/a574cd9574f7ce1386816c0cc10560a341861b3c Log: Merge pull request #1678 from stephenc/jenkins-28115 [FIXED JENKINS-28115] Division by zero in Executor.getProgress() Compare: https://github.com/jenkinsci/jenkins/compare/cd8dbedaf0f8...a574cd9574f7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon resolved JENKINS-28115 as Fixed Division by zero in Executor.getProgress Change By: SCM/JIRA link daemon (27/Apr/15 8:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon commented on JENKINS-28115 Division by zero in Executor.getProgress Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/e685b604d9c48bee2f728c3ecec3303e5c56 Log: [FIXED JENKINS-28115] Division by zero in Executor.getProgress() ``` WARNING: Caught exception evaluating: executor.progress in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException ... at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ArithmeticException: / by zero at hudson.model.Executor.getProgress(Executor.java:649) ... 154 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] [scm-sync-configuration-plugin] (JENKINS-15128) Renaming job doesn't work with Git
Dave Cadwallader commented on JENKINS-15128 Renaming job doesn't work with Git Seems not to be fixed. When renaming a job, we get this in the logs and all future SCM syncs fail. This is using the latest v0.0.8: Apr 27, 2015 1:13:20 PM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Deleting SCM hierarchy [/root/jenkins/scm-sync-configuration/checkoutConfiguration/jobs/Frontend_Test] from SCM ... Apr 27, 2015 1:13:20 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-4152) Incremental builds should include previous builds' modules if previous build failed
Tim Drury commented on JENKINS-4152 Incremental builds should include previous builds' modules if previous build failed I see this behavior happening in Jenkins 1.596.1. A job is configured for incremental build. Module A fails due to a broken unit test. A change to module B is made. The next build builds only module B so the build goes green even though module A's unit test is still broken. Unstable and failed modules should be included in the next incremental build (and subsequent builds until the module is stable). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
SCM/JIRA link daemon resolved JENKINS-26558 as Fixed createSlave Node name collision avoidance creates dead nodes Change By: SCM/JIRA link daemon (27/Apr/15 7:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
SCM/JIRA link daemon commented on JENKINS-26558 createSlave Node name collision avoidance creates dead nodes Code changed in jenkins User: Peter Jönsson Path: client/src/main/java/hudson/plugins/swarm/Client.java client/src/main/java/hudson/plugins/swarm/SwarmClient.java plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/5f622da0e1eb54ec84626dbc9aceaa1aafb4a0ac Log: Merge pull request #26 from stephenc/jenkins-26558 [FIXED JENKINS-26558] Clients should provide a unique ID to be used for ... Compare: https://github.com/jenkinsci/swarm-plugin/compare/bef8ccbe8906...5f622da0e1eb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
SCM/JIRA link daemon commented on JENKINS-26558 createSlave Node name collision avoidance creates dead nodes Code changed in jenkins User: Stephen Connolly Path: client/src/main/java/hudson/plugins/swarm/Client.java client/src/main/java/hudson/plugins/swarm/SwarmClient.java plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/ab37bc84eb9639888f3a66c68a9b1536c5882c88 Log: [FIXED JENKINS-26558] Clients should provide a unique ID to be used for name collision avoidance The current name collision avoidance uses the requests address, which could very likely be the same for all clients as they could be being routed through a HTTP proxy (or two) so that is not a good disambiguator We use a digest of the client's interfaces and MAC addresses and the remoteFSRoot to try and give a consistent ID We ALWAYS append the ID if we have it as otherwise during reconnect the slaves with the same name will shuffle around which defeats a lot of the login that Jenkins has internally based on slaves having a consistent name In the event of legacy clients that do not have the ID we will let them connect with their name as long as there is no online slave with that name. This does mean that where there are multiple legacy swarm clients with the same name, only one can be on-line at any moment in time, but that is an improvement on the current where once a shuffle starts, none can stay on-line This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-28119) Link to log of failed step
Jesse Glick
created JENKINS-28119
Link to log of failed step
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
27/Apr/15 7:25 PM
Description:
When a flow involves many steps, long logs, and/or many branches, it can be hard for a developer receiving a failure email (for example) to quickly see what part of the build actually failed and why. I think it would be useful for the catchError step to do a DFS search on the Throwable and its cause chain through the FlowNode graph starting at the end of the catch step, looking for ErrorAction, and setting/appending an environment variable with the URL of the LogAction. Or provide a new step to do the same. Thus you could write
def runStuff(param) {
...
}
try {
parallel a: {runStuff 'a'}, b: {runStuff 'b'}
} catch (e) {
mail to: '...', subject: 'Failure!', body: "Build failed: ${errorUrl(e)}"
}
and get a link to http://jenkins/job/myflow/123/flowGraph/77/console or the like, according to the actual step in one of the branches that threw the error.
Project:
Jenkins
Priority:
Major
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [accurev-plugin] (JENKINS-28118) Poll Accurev SCM does not poll parent streams
Michael Waldorf created JENKINS-28118 Poll Accurev SCM does not poll parent streams Issue Type: Bug Assignee: Scott Tatum Components: accurev-plugin Created: 27/Apr/15 7:10 PM Description: I have a stream where development is occurring and a filter connected to the stream where I build snapshots which are submitted to the build group for my project. I was using Jenkins 1.564 with accurev-plugin 0.6.22 and would poll on the filter and see promotes to the stream. After upgrading to Jenkins 1.606 (and now 1.610), I don't see polling the parent stream in the Accurev Polling Log (and no longer have builds being triggered by promotes to the parent stream). Environment: Jenkins version 1.610, accurev-plugin version 0.6.22 Project: Jenkins Labels: jenkins accurev pollscm polling Priority: Major Reporter: Michael Waldorf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-28117) NodeJS err=13; permission denied on fedora20
Darren Hartford created JENKINS-28117 NodeJS err=13; permission denied on fedora20 Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 27/Apr/15 6:57 PM Description: NodeJS seems to download to /tmp/ which the user running jenkins may not have permission to. Recommend shifting to user-provided location, or JENKINS_HOME/tools/ location (to avoid multiple downloads). reference forum: http://stackoverflow.com/questions/23733541/jenkins-and-nodejs-plugin-permission-denied-error-13 Environment: fedora 20 / Jenkins 1.596.2 Project: Jenkins Priority: Major Reporter: Darren Hartford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Haiqing Zhang commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 I'm on 1.610 and seeing the copy artifact crash. Since I don't use PerformanceReport so I will upgrade to 1.611 and hopefully everything will work. thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Daniel Beck commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 This issue with performance plugin was introduced in either 1.610 or 1.611 (I suspect the later). To clarify, 1.611 is also affected? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [envinject-plugin] (JENKINS-28116) Password injection no longer supplies password
David Venable created JENKINS-28116 Password injection no longer supplies password Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 27/Apr/15 6:10 PM Description: We have a build using the "Inject passwords to the build as environment variables" Build Environment. Recently the passwords started getting injected as all asterisks - . Upon downgrading to 1.90, the passwords began working again. Environment: Jenkins 1.608 running on Linux Builds occur on a Jenkins slave Found in EnvInject plugin versions 1.91 and 1.91.1 Project: Jenkins Priority: Major Reporter: David Venable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Serge Zukov commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 Yes, it did work on 1.609. Maybe relevant: 1.610 broke copy artifact plugin. 1.611 fixed the copy artifact. This issue with performance plugin was introduced in either 1.610 or 1.611 (I suspect the later). I cannot be more precise because I rolled back from 1.610 to 1.609. Now I'm rolling from 1.611 to 1.609. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-monitor-plugin] (JENKINS-28102) Getting error with build Monitor plugin
Daniel Beck commented on JENKINS-28102 Getting error with build Monitor plugin This may actually be a failure to render the real error message. Anything interesting in the Jenkins logs? https://wiki.jenkins-ci.org/display/JENKINS/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] [extensible-choice-parameter-plugin] (JENKINS-28046) Error: No stapler-class is specified
Daniel Beck commented on JENKINS-28046 Error: No stapler-class is specified ikedam Did you test this with 1.611? It looks like nodejs remains broken, so maybe JENKINS-28011 did not fix related issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28114) Update to 1.610 causing main Jenkins config page to throw
Peter Berkman commented on JENKINS-28114 Update to 1.610 causing main Jenkins config page to throw Thank you Daniel! I just tried 1.611... same exception I think (second set of exceptions)... and, when I go into the Plugin Manager and click "Check-Now" button on Updates tab, I get this one: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/updates/updates/jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html?id=jenkins.plugins.nodejs.tools.NodeJSInstaller&version=1.611 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at hudson.model.DownloadService.loadJSONHTML(DownloadService.java:181) at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:342) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:898) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:183) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
[JIRA] [mailer-plugin] (JENKINS-27262) email is not sent
Daniel Beck updated JENKINS-27262 email is not sent Change By: Daniel Beck (27/Apr/15 3:46 PM) Component/s: mailer-plugin 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] [core] (JENKINS-28111) JNLP slave JVM Options are inconsistently applied
stephenconnolly commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Installed service for windows was reported previously. Nobody from what I could find had reported that the displayed command line launch alternative did not include the JVM options This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-oauth-plugin] (JENKINS-26145) Narrow down github auth scope for user logins
Kanstantsin Shautsou updated JENKINS-26145 Narrow down github auth scope for user logins Change By: Kanstantsin Shautsou (27/Apr/15 3:44 PM) Component/s: github-oauth-plugin Component/s: github-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-28101) Unhandled exception in version 1.94
Daniel Beck resolved JENKINS-28101 as Not A Defect Unhandled exception in version 1.94 Jenkins is out of memory. Make sure it has enough heap space (look into the Xmx argument to java). Consider installing the Monitoring plugin to track memory usage. It's possible this is a bug in the plugin (extreme memory usage), but your report contains no indication of that. Change By: Daniel Beck (27/Apr/15 3:41 PM) Status: Open Resolved Assignee: Gregory Boissinot Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28114) Update to 1.610 causing main Jenkins config page to throw
Kanstantsin Shautsou
updated JENKINS-28114
Update to 1.610 causing main Jenkins config page to throw
Change By:
Kanstantsin Shautsou
(27/Apr/15 3:40 PM)
Description:
after upgrading (expanded war within tomcat static web content) to 1.610, getting the following exception when trying to update/apply/save main Jenkins configuration:
{code}
Stack tracejavax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.plugins.nodejs.tools.NodeJSInstallation from {"name":"nodejs (0.11.14)","home":"","properties":{"stapler-class-bag":"true","hudson-tools-InstallSourceProperty":{"installers":{"id":"0.11.14","npmPackages":"bower@~1.2.0 grunt-cli@~0.1.0","npmPackagesRefreshHours":"100","kind":"hudson.plugins.nodejs.tools.NodeJSInstaller" at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.apache.catalina.core.Applicatio
[JIRA] [core] (JENKINS-28114) Update to 1.610 causing main Jenkins config page to throw
Daniel Beck updated JENKINS-28114 Update to 1.610 causing main Jenkins config page to throw This could be a duplicate of JENKINS-28011, please try 1.611. Change By: Daniel Beck (27/Apr/15 3:38 PM) Labels: configuration exception jenkins plugin regression 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Daniel Beck commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 Is this a regression? Did it work in 1.609? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
Daniel Beck commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied I'm fairly sure this has been reported before (or was that for the installed slave service on Windows?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
stephenconnolly created JENKINS-28115 Division by zero in Executor.getProgress Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 3:23 PM Description: Stack traces like WARNING: Caught exception evaluating: executor.progress in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException ... at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ArithmeticException: / by zero at hudson.model.Executor.getProgress(Executor.java:649) ... 154 more Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-28114) Update to 1.610 causing main Jenkins config page to throw
Peter Berkman
created JENKINS-28114
Update to 1.610 causing main Jenkins config page to throw
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodejs-plugin
Created:
27/Apr/15 3:09 PM
Description:
after upgrading (expanded war within tomcat static web content) to 1.610, getting the following exception when trying to update/apply/save main Jenkins configuration:
Stack trace
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.plugins.nodejs.tools.NodeJSInstallation from {"name":"nodejs (0.11.14)","home":"","properties":{"stapler-class-bag":"true","hudson-tools-InstallSourceProperty":{"installers":{"id":"0.11.14","npmPackages":"bower@~1.2.0 grunt-cli@~0.1.0","npmPackagesRefreshHours":"100","kind":"hudson.plugins.nodejs.tools.NodeJSInstaller"
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina
[JIRA] [copyartifact-plugin] (JENKINS-28109) Local artifact cache on slaves
Daniel Beck commented on JENKINS-28109 Local artifact cache on slaves Jenkins doesn't even delete project workspaces when projects are deleted, so deleting any other caches would be surprising behavior. This would require fairly complex behavior anyway, as nodes could be offline when the project gets deleted (and there would be the expectation that it'd get deleted the next time the slave is online). Pretty big can of worms right there for questionable benefit. FWIW all of this could be implemented in the plugin through extension points that already exist AFAICT, so requires no core improvements. (I just don't think this would be useful.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28113) BuildTrigger should accept any ParameterizedJob downstream
Jesse Glick created JENKINS-28113 BuildTrigger should accept any ParameterizedJob downstream Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 2:10 PM Description: ReverseBuildTrigger supports any ParameterizedJob, behaving as a DependencyDeclarer if both sides are AbstractProject, behaving as a simple Trigger otherwise. BuildTrigger should do the same, behaving as a DependencyDeclarer as now if both sides are AbstractProject, behaving as a simple Notifier otherwise. Would allow Build other projects to select a workflow job. Workarounds: JENKINS-26050, if implemented; use of ReverseBuildTrigger, in the common case that it does not matter which side declares the trigger (but not when Item.CONFIGURE is restricted on one side, job templates are in use, etc.). Project: Jenkins Labels: workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Johannes Schüth edited a comment on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 The exception occurs when jenkins tries to instanciate the PerformanceReportParser from the json. This can't work since the PerformanceReportParser class is abstract. I can only assume that somehow something went wrong when creating the json object. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Johannes Schüth commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 The exception jenkins tries to instanciate the PerformanceReportParser from the json. This can't work since the PerformanceReportParser class is abstract. I can only assume that somehow something went wrong when creating the json object. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28112) JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+
stephenconnolly created JENKINS-28112 JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+ Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 1:47 PM Description: The generated JNLP file has version="1.5+" this should be version="1.6+" at present with a view to moving to version="1.7+" or version="1.8+" once the core JVM required version is increased Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
stephenconnolly created JENKINS-28111 JNLP slave JVM Options are inconsistently applied Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 1:45 PM Description: The JVM Options are injected into the JNLP file as the java-vm-args attribute but the command line launch option does not reflect the requirements for JVM Options. The "Run from slave command line" option should include the specified JVM options for the non-javaws varietals. Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
