[JIRA] [maven-plugin] (JENKINS-25940) NPE from EmailExtTemplateActionFactory.createFor due to MavenModuleSet.getPublishersList being null
Title: Message Title Alex Earl commented on JENKINS-25940 Re: NPE from EmailExtTemplateActionFactory.createFor due to MavenModuleSet.getPublishersList being null Is this still an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-ssh-plugin] (JENKINS-26215) Add option to recursively copy a tree, as per "scp -r".
Title: Message Title Alex Earl resolved as Duplicate Jenkins / JENKINS-26215 Add option to recursively copy a tree, as per "scp -r". Change By: Alex Earl Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-utilization] (JENKINS-29003) 'No file' option when run jenkins slave agent
Title: Message Title Alex Earl resolved as Duplicate Jenkins / JENKINS-29003 'No file' option when run jenkins slave agent Change By: Alex Earl Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27773) Subversion Plugin 2.5 not able to commit to SVN Repository.
Title: Message Title Swapnil Verma assigned an issue to Unassigned Could you please let me know if there is any roadmap to fix this issue. Also let know if it is reproducible on you side. Jenkins / JENKINS-27773 Subversion Plugin 2.5 not able to commit to SVN Repository. Change By: Swapnil Verma Assignee: Alex Earl Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27773) Subversion Plugin 2.5 not able to commit to SVN Repository.
Title: Message Title Swapnil Verma assigned an issue to Alex Earl Jenkins / JENKINS-27773 Subversion Plugin 2.5 not able to commit to SVN Repository. Change By: Swapnil Verma Assignee: Alex Earl Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-27774) Subversion Plugin 2.5 not able to commit to SVN Repository.
Title: Message Title Swapnil Verma closed an issue as Duplicate Closing this issue as this jira is duplicate of JENKINS-27773 Jenkins / JENKINS-27774 Subversion Plugin 2.5 not able to commit to SVN Repository. Change By: Swapnil Verma Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accelerated-build-now-plugin] (JENKINS-29067) can I Automate a build in Jenkins, if so how
Title: Message Title Alex Earl resolved as Not A Defect Jenkins / JENKINS-29067 can I Automate a build in Jenkins, if so how Change By: Alex Earl Status: In Progress Resolved Assignee: Anthony Dahanne Alex Earl Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [skype-notifier] (JENKINS-14540) hudson.model.Hudson cannot be cast to hudson.model.Slave
Title: Message Title Alex Earl resolved as Not A Defect Not all Nodes are Slaves. hudson.model.Hudson extends hudson.model.Node (up the chain a bit), hudson.model.Slave also extends hudson.model.Node. You can't assume that all Nodes are Slaves. Jenkins / JENKINS-14540 hudson.model.Hudson cannot be cast to hudson.model.Slave Change By: Alex Earl Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-19718) no login possible after udpate due to NoClassDefFoundError
Title: Message Title Alex Earl resolved as Incomplete Need more info Jenkins / JENKINS-19718 no login possible after udpate due to NoClassDefFoundError Change By: Alex Earl Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-19818) Add support of newInstance() invocation
Title: Message Title Alex Earl commented on JENKINS-19818 Re: Add support of newInstance() invocation Is this still an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [redmine-plugin] (JENKINS-23483) java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport()
Title: Message Title Alex Earl commented on JENKINS-23483 Re: java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport() Did you submit a pull request? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-27774) Subversion Plugin 2.5 not able to commit to SVN Repository.
Title: Message Title Alex Earl resolved as Duplicate Jenkins / JENKINS-27774 Subversion Plugin 2.5 not able to commit to SVN Repository. Change By: Alex Earl Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-cifs-plugin] (JENKINS-15272) Matrix project support for Publish Over CIFS/SSH/FTP plugins
Title: Message Title Alex Earl resolved as Incomplete Need more information Jenkins / JENKINS-15272 Matrix project support for Publish Over CIFS/SSH/FTP plugins Change By: Alex Earl Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-6146) Hudson sending mail using SMTP sometimes fails with message "Connection refused"
Title: Message Title Alex Earl resolved as Cannot Reproduce Jenkins / JENKINS-6146 Hudson sending mail using SMTP sometimes fails with message "Connection refused" Change By: Alex Earl Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-880) Per module filtering of java.net commit e-mail
Title: Message Title Alex Earl commented on JENKINS-880 Re: Per module filtering of java.net commit e-mail Is this still an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-836) Mercurial plugin should remember the changeset per build and use that for changelog
Title: Message Title Alex Earl assigned an issue to Jesse Glick Reassigning component Jenkins / JENKINS-836 Mercurial plugin should remember the changeset per build and use that for changelog Change By: Alex Earl Component/s: mercurial-plugin Component/s: other Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-25470) Provided mail-1.4.4.jar seems to be missing the smtp provider
Title: Message Title Alex Earl resolved as Fixed Jenkins / JENKINS-25470 Provided mail-1.4.4.jar seems to be missing the smtp provider Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-28827) send html mails of console log on failure and success
Title: Message Title Alex Earl commented on JENKINS-28827 Re: send html mails of console log on failure and success If you want customizable emails, you need to use email-ext. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7474) Environment variables defined in node configuration disappearing (not set) when system under load
Title: Message Title Alex Earl commented on JENKINS-7474 Re: Environment variables defined in node configuration disappearing (not set) when system under load Related to this somehow? https://issues.jenkins-ci.org/browse/JENKINS-28466 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-29066) Git plugin dev version 2.3.6-0c1a59a8 builds on every poll
Title: Message Title Mark Waite commented on JENKINS-29066 Re: Git plugin dev version 2.3.6-0c1a59a8 builds on every poll Refer to the updated docker repo for more details on how to duplicate the problem for both JGit and command line git. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26061) Incompatible argument to function
Title: Message Title Alex Earl commented on JENKINS-26061 Re: Incompatible argument to function Is there another Apache Commons jar in your classpath? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-1658) Reload shouldn't be automatic but by ENTER
Title: Message Title Alex Earl commented on JENKINS-1658 Re: Reload shouldn't be automatic but by ENTER Is this still a request? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-4785) Hudson Confluence Plugin
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-4785 Hudson Confluence Plugin Change By: Alex Earl Component/s: plugin-proposals Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [versionnumber-plugin] (JENKINS-4936) Version number environment variable should be visible in publishers
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-4936 Version number environment variable should be visible in publishers Change By: Alex Earl Component/s: versionnumber-plugin Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [versionnumber-plugin] (JENKINS-6523) Version number environment variable should be reachable at runtime for ClearCase plugin and for slave hadson
Title: Message Title Alex Earl closed an issue as Duplicate Jenkins / JENKINS-6523 Version number environment variable should be reachable at runtime for ClearCase plugin and for slave hadson Change By: Alex Earl Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [versionnumber-plugin] (JENKINS-6523) Version number environment variable should be reachable at runtime for ClearCase plugin and for slave hadson
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-6523 Version number environment variable should be reachable at runtime for ClearCase plugin and for slave hadson Change By: Alex Earl Component/s: versionnumber-plugin Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-7313) Can't use parameters in git plugin "URL Of Repositoy" configuration
Title: Message Title Alex Earl assigned an issue to Nicolas De Loof Jenkins / JENKINS-7313 Can't use parameters in git plugin "URL Of Repositoy" configuration Change By: Alex Earl Component/s: git-plugin Component/s: plugin-proposals Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-10833) very skow performance using git plugin
Title: Message Title Alex Earl assigned an issue to Nicolas De Loof Jenkins / JENKINS-10833 very skow performance using git plugin Change By: Alex Earl Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-10833) very skow performance using git plugin
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-10833 very skow performance using git plugin Change By: Alex Earl Component/s: git-plugin Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20394) Include ability to run the clirr-maven-plugin as part of the parent pom
Title: Message Title Alex Earl closed an issue as Not A Defect Jenkins / JENKINS-20394 Include ability to run the clirr-maven-plugin as part of the parent pom Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20394) Include ability to run the clirr-maven-plugin as part of the parent pom
Title: Message Title Alex Earl commented on JENKINS-20394 Re: Include ability to run the clirr-maven-plugin as part of the parent pom Found a way to do this in my own pom.xml https://github.com/jenkinsci/email-ext-plugin/blob/master/pom.xml#L180 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28976) windows master, mac slave, polling fails trying to launch windows GIT_SSH program
Title: Message Title Alex Earl commented on JENKINS-28976 Re: windows master, mac slave, polling fails trying to launch windows GIT_SSH program Did you restart the slave after adding the property for the node? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Mark Waite commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Any chance you changed the global settings for security, specifically those related to the handling of HTML embedded in content? Alternately, did you recently upgrade from an older version of the git plugin or the git client plugin? A security fix was applied to git plugin 2.3.4 to prevent malicious code from being inserted into the Jenkins pages through a commit message to the git repository. That might have affected what you are seeing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11326) FileParameter should expose the original file name
Title: Message Title Kelly Johnson commented on JENKINS-11326 Re: FileParameter should expose the original file name How to use, for anyone like me looking for answers: http://stackoverflow.com/questions/13951833/jenkins-parameterized-build-upload-file-and-save-original-file-name Also there is no fix version, but the fix year is '11, so that's probably good enough Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-28298) Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1
Title: Message Title ikedam commented on JENKINS-28298 Re: Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1 I'll introduce a feature like https://wiki.jenkins-ci.org/display/JENKINS/Extensible+Choice+Parameter+plugin#ExtensibleChoiceParameterplugin-Disablingproviders Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-29091) Make local DSL Creation for testing more user-friendly
Title: Message Title A C created an issue Jenkins / JENKINS-29091 Make local DSL Creation for testing more user-friendly Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 25/Jun/15 11:10 PM Priority: Major Reporter: A C Testing DSL scripts before activating them in a production Jenkins environment is good, as documented here https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves It would be great if there was a more user-friendly and less fragile way than the current method, which only works well for trivially small DSL scripts. Attempting to test real production scripts, eg where several Groovy files are involved across directories, immediately surfaces various directory/package problems for resolving external scripts/classes from the root DSL script. (Some of these problems may be issues with Groovy's underlying class loader, which is fairly strict compared to other scripting languages). This makes it difficult to test complex setups before checking them into production. Add Comment
[JIRA] [ansicolor-plugin] (JENKINS-29090) Too many span labels for the same line
Title: Message Title Jose Luis Rivero created an issue Jenkins / JENKINS-29090 Too many span labels for the same line Issue Type: Improvement Assignee: Unassigned Components: ansicolor-plugin Created: 25/Jun/15 10:59 PM Environment: Ansi Color Plugin version 0.4.1 Labels: performance Priority: Minor Reporter: Jose Luis Rivero The Plugin seems to generate a span html tag for several parts of the same line, having all the line the same colour. While this is not a problem on small builds, in large projects the console output can increase considerably (up to 100Mb in ours) and the response time to check the whole log is also affected notably. An example can be checked at: http://build.osrfoundation.org/job/gazebo-default-devel-trusty-amd64-gpu-nvidia/lastSuccessfulBuild/consoleFull For example (all the line is in red):
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-27233) Can't use in combination with rebuild and parameterized build trigger
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-27233 Can't use in combination with rebuild and parameterized build trigger Change By: ikedam Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-28824) Can't launch a manual build when the project is running
Title: Message Title ikedam started work on JENKINS-28824 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-28824) Can't launch a manual build when the project is running
Title: Message Title ikedam commented on JENKINS-28824 Re: Can't launch a manual build when the project is running https://github.com/jenkinsci/matrix-combinations-plugin/pull/9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27748) Jenkins loses history (task page and overview)
Title: Message Title Benjamin Hahne updated an issue Jenkins / JENKINS-27748 Jenkins loses history (task page and overview) Change By: Benjamin Hahne Labels: lazy-loading lts-candidate robustness Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-29034) Modify filename to include date and time
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29034 Re: Modify filename to include date and time The PR has been merged. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-29034) Modify filename to include date and time
Title: Message Title Manuel Jesús Recena Soto closed an issue as Fixed Jenkins / JENKINS-29034 Modify filename to include date and time Change By: Manuel Jesús Recena Soto Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-28454) Workspace Cleanup integration with Workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28454 Workspace Cleanup integration with Workflow Change By: Jesse Glick Summary: Add Workspace Cleanup integration support with Jenkins Workflow DSL Component/s: workflow-plugin Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-26670) Support WorkflowJob for Authorize Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26670 Re: Support WorkflowJob for Authorize Project Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/0f7410cb0e3cd5198c8cdf808309fc694b2c7003 Log: JENKINS-26670 Noting. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27354) Error communicating to server! timeout
Title: Message Title Tommy Tynjä resolved as Won't Fix Marking as resolved since it seems to be caused by job configurations preserving a lot of history. A workaround is to preserve less history. Jenkins / JENKINS-27354 Error communicating to server! timeout Change By: Tommy Tynjä Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28255) DPP don't show if a job is disabled
Title: Message Title Tommy Tynjä commented on JENKINS-28255 Re: DPP don't show if a job is disabled Would it be intuitive to have the job all grayed out in the view? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28708) Add abort button
Title: Message Title Tommy Tynjä commented on JENKINS-28708 Re: Add abort button Good suggestion! This could bloat the view though so it should definitely be a configurable option whether to display them or not. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-29089) Add checkbox to enable "Retain long standard output/error"
Title: Message Title Benjamin Podgursky created an issue Jenkins / JENKINS-29089 Add checkbox to enable "Retain long standard output/error" Issue Type: Improvement Assignee: Unassigned Components: maven-plugin Created: 25/Jun/15 9:25 PM Priority: Major Reporter: Benjamin Podgursky This option is available on freestyle jobs, but not on maven builds. Add Comment This message was sent by Atlassian JIRA
[JIRA] [ssh-plugin] (JENKINS-17440) SSH Plugin throws auth cancel
Title: Message Title Anthony Chan commented on JENKINS-17440 Re: SSH Plugin throws auth cancel I am having the same issue, too. Is anyone looking into it? I hope the following information is helpful for the Jenkins team to analyze the issue Jenkins version: 1.617 SSH plugin version: 2.4 Jenkins server: Jenkins is installed on Red Hat Enterprise Linux Server release 6.6 ssh version is (from output of ssh -V) OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 Remote system (let's say machine A) OS: Red Hat Enterprise Linux Server release 6.5 ssh version: OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 Remote system (let's say machine B) OS: SUSE Linux Enterprise Server 11 ssh version: OpenSSH_6.2p2, OpenSSL 0.9.8j-fips 07 Jan 2009 Observation: The SSH plugin works with machine A, but it return the same error with machine B. Does the ssh version matter? thanks --anthony Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable
Title: Message Title Greg Symons commented on JENKINS-28821 Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable It looks like my problem was a non-writable workspace as well. I fixed that, and now shell tasks no longer hang. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-29045) Mercurial plugin does not work inside container with Docker Workflow plugin
Title: Message Title Greg Symons resolved as Fixed This seems to have been a side-effect of the way I was giving access to docker for Jenkins. After moving from simply sharing a docker Unix socket to running the docker daemon inside the Jenkins container, Mercurial works fine. Jenkins / JENKINS-29045 Mercurial plugin does not work inside container with Docker Workflow plugin Change By: Greg Symons Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Brian Villanueva commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) I'm seeing this as well, running Jenkins 1.617 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2-plugin] (JENKINS-27070) Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
Title: Message Title Chris Luc commented on JENKINS-27070 Re: Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration" Thank you Arnaud. I look forward to the fix asap. This bug is causing performance issue for us – i.e. it will take 10-30 seconds to log in. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Christopher Esser commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Dave, I ran into the same issue. I fixed by making sure there is a '/' on the end of the webhook URL on the Bitbucket side. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-28909) Label Expressions Using Ampersands Rejected
Title: Message Title Dylan Kelly commented on JENKINS-28909 Re: Label Expressions Using Ampersands Rejected Thanks for the fix! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Carlo Alberto Degli Atti commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Dave Thomas no, you don't have to be under https... (but if you are, you absolutely need to have a valid certificate signed by a public authority... otherwise you won't receive any payload... ).. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-27068) P4 plugin logs out or invalidates role user login
Title: Message Title Michael Rose commented on JENKINS-27068 Re: P4 plugin logs out or invalidates role user login Maybe I'm missing something ... The user that is logging in to do the build is not the same user that is currently always logged in. The whole reason why I used the plugin's password setting instead of the ticket was b/c I wanted the user's login to be limited to the triggered build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cpptest-plugin] (JENKINS-29088) Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404.
Title: Message Title James Sweet created an issue Jenkins / JENKINS-29088 Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404. Issue Type: Bug Assignee: Gregory Boissinot Components: cpptest-plugin Created: 25/Jun/15 4:57 PM Environment: Jenkins CppTest Plugin v0.13.2 Priority: Major Reporter: James Sweet There is an issue with the post build action “Publish Cpptest analysis results” of the Cpptest plugin version 0.13.2. Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404. Steps to reproduce. 1. Create a new job or edit an existing one. 2. Add post-build action “Publish Cpptest analysis results”. 3. Click on the “Advanced” button. 4. Check “Compute new warnings (based on the last successful build unless another reference build is chosen below)”. 5. Add a 0 to “All Priorities” box under “Status thresholds (New warnings)”. 6. Click “Save” 7. Now edit the job and go to the “Publish Cpptest analysis results” section. 8. Click the “Advanced” button. 9. You should now see the “Trend graph” section and link “You can define the default values for the trend graph in a separate view.” 10. Click on the link “You can define the default values for the trend graph in a separate view.” 11. Results in HTTP ERROR 404.
[JIRA] [maven-plugin] (JENKINS-29087) NoClassDefFoundError: org.apache.maven.surefire.booter.ForkedBooter
Title: Message Title Amol Chakradeo created an issue Jenkins / JENKINS-29087 NoClassDefFoundError: org.apache.maven.surefire.booter.ForkedBooter Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 25/Jun/15 4:54 PM Priority: Minor Reporter: Amol Chakradeo When trying to run a job for a maven based selenium webdriver test project. I am getting below error: Started by user Amol Chakradeo [EnvInject] - Loading node environment variables. Building in workspace C:\Jenkins\jobs\SeleniumSmokeTest\workspace Parsing POMs [workspace] $ "C:\Program Files\IBM\SDP\jdk/bin/java" -cp C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.6.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven\boot\plexus-classworlds-2.5.2.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven/conf/logging jenkins.maven3.agent.Maven32Main C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven C:\Jenkins\war\WEB-INF\lib\remoting-2.51.jar C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.6.jar C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.6.jar 63859 <===[JENKINS REMOTING CAPACITY]===>channel started ERROR: JENKINS-18403 JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to C:\Program Files\IBM\SDP\jdk [workspace] $ "C:\Program Files (x86)\Java\jre1.8.0_45/bin/java" -cp C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.6.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenIn
[JIRA] [prioritysorter-plugin] (JENKINS-8405) Optionally pause/cancel lower priority jobs in favor of higher priority jobs in the queue
Title: Message Title D R commented on JENKINS-8405 Re: Optionally pause/cancel lower priority jobs in favor of higher priority jobs in the queue +1 for the ability to automatically kill low priority jobs once higher priority jobs come in. The low priority jobs I have are really low priority, and killing them almost certainly won't affect future builds. So, being able to just kill -9 them is a really great solution to my problem. Thanks for your great contributions! FWIW, I'm an active maintainer of the ACL2 Community Books and also believe in the open source model. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Dave Thomas commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Hi Carlo, The Jenkins instance isn't under https at this time, would that be the issue? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Kevin Phillips commented on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent Anything else a blocker for you? One other behavioral change in 1.609.1 is that the BUILD_ID property was changed from a time stamp to a numeric identifier. All of our build configurations and releases processes were dependent upon a builds identifier being a time stamp, and we more-or-less use that BUILD_ID variable everywhere (scripts, code, etc.). I did find a plugin that allows one to create a new time-stamp based environment variable for each build (Zen Time Stamp) but we'll need to reconfigure our infrastructure to use the new variable name throughout. We hit a LOT of problems with the SVN plugin as well but I believe we've finally sorted all those out. I'm also currently investigating some bugs with the way the new Jenkins version handles jobs that are enqueued for builds. There are a couple of cases where jobs may get deadlocked in the queue for various reasons. Still trying to isolate specific use cases though before I file any more bugs. NOTE: We may have to stick with v1.596.3 for the time being. Assuming there are a great number of new changes / improvements / fixes included in the next LTS release, we'll likely have to invest considerable time and expense making sure none of those additional changes break anything else anew. No idea re JENKINS-18671 . I doubt you're seeing the same issue. Make sure your nodes are all in synced time. All of our agents, and the master, are synchronized using the same NTP server and I have confirmed via direct examination of the agents that all the physical clocks on all machines are in fact correct and in sync with each other (to within < 1S variance at least). It's only the Jenkins dashboard that suggests otherwise. If you believe JENKINS-18671 (or the underlying code change from JENKINS-18438 ) just let me know and I'll create a new defect for that. If this problem is in fact a new / different bug, and it is a contributing factor to the inconsistent time stamps being reported, then I would say that would be a significant issue that we'd also want fixed in the next LTS release as well. We can't have build logs getting corrupted even if the problem is intermittent. We use Jenkins as a central service now for all of our production work and we need to be able to rely on its ability to preserve the details of those build operations for auditing purposes. (although, I guess this is a problem we're currently stuck with on 1.596.3 so it hopefully wouldn't get any worse if we were to move to a newer LTS version at least).
[JIRA] [build-pipeline-plugin] (JENKINS-28478) Build Pipeline plugin loses track of upstream build when retrying of a failed build
Title: Message Title Cesar G edited a comment on JENKINS-28478 Re: Build Pipeline plugin loses track of upstream build when retrying of a failed build any updates? I'm having the same issue. I saw also that build-card is not updating the job number even when after a retry the job ends successfully (it changes to green state but after refresh back to red and old build number). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Daniel Beck commented on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent Hopefully the other product-stop bugs that were introduced by the 1.609.1 update can be fixed sooner rather than later so we can get those fixes as well. I know about the queue/build blocker/block while something else is building issues, and expect 1.609.3 to have them resolved. Anything else a blocker for you? No idea re JENKINS-18671 . I doubt you're seeing the same issue. Make sure your nodes are all in synced time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-28478) Build Pipeline plugin loses track of upstream build when retrying of a failed build
Title: Message Title Cesar G commented on JENKINS-28478 Re: Build Pipeline plugin loses track of upstream build when retrying of a failed build any updates? I'm having the same issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin
Title: Message Title Artur Mihura updated an issue Jenkins / JENKINS-29086 User IDs are case sensitive in saml-plugin Change By: Artur Mihura Summary: User ID's IDs are case sensitive in saml-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saml-plugin] (JENKINS-29086) User ID's are case sensitive in saml-plugin
Title: Message Title Artur Mihura created an issue Jenkins / JENKINS-29086 User ID's are case sensitive in saml-plugin Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 25/Jun/15 4:08 PM Labels: plugin Priority: Minor Reporter: Artur Mihura Please make users ID's are case INsensitive in saml plugin. It will be much more convenient than to use only case sensitive id's in the different authorization strategies. Add Comment
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allow to use the docker build {{--file}} option when building an imageWe would like to NOT have the Dockerfile at the root of the project, and have everything docker related in a subfolder "docker".Then we would build the image with {{docker build -t myrepo/myproject:v01 --file docker/Dockerfile .}}'.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using{{ADD../scr/myfile.jar /srv/lib/ myfile.jar }},for example. '..' is not allowed).So it would be nice to still have the option:- "Directory Dockerfile is in" (equivalent of "--file )- "Docker context".Note:In the code, this seems to be in function buildAndTag() in file:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{String context = defined(getDockerfilePath()) ? getDockerfilePath() : "."; lastResult = executeCmd("docker build -t " + i.next() + ((isNoCache()) ? " --no-cache=true " : "") + " " + ((isForcePull()) ? " --pull=true " : "") + " " + context);}}The line{{String context = defined(getDockerfilePath()) }}should be changed so that DockerfilePath is not the same as context. Those should be different things.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribe
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allow to use the docker build {{--file}} option when building an imageWe would like to NOT have the Dockerfile at the root of the project, and have everything docker related in a subfolder "docker".Then we would build the image with {{docker build -t myrepo/myproject:v01 --file docker/Dockerfile .}}'.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using{{ADD../src/myfile.jar /srv/lib/myfile.jar}},for example. '..' is not allowed).So it would be nice to still have the option options, in the GUI :- "Directory Dockerfile is in" (equivalent of "--file )- "Docker context".Note:In the code, this seems to be in function buildAndTag() in file:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{String context = defined(getDockerfilePath()) ? getDockerfilePath() : "."; lastResult = executeCmd("docker build -t " + i.next() + ((isNoCache()) ? " --no-cache=true " : "") + " " + ((isForcePull()) ? " --pull=true " : "") + " " + context);}}The line{{String context = defined(getDockerfilePath()) }}should be changed so that DockerfilePath is not the same as context. Those should be different things.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message beca
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allow to use the docker build {{--file}} option when building an imageWe would like to NOT have the Dockerfile at the root of the project, and have everything docker related in a subfolder "docker".Then we would build the image with {{docker build -t myrepo/myproject:v01 --file docker/Dockerfile .}}'.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using{{ADD../ scr src /myfile.jar /srv/lib/myfile.jar}},for example. '..' is not allowed).So it would be nice to still have the option:- "Directory Dockerfile is in" (equivalent of "--file )- "Docker context".Note:In the code, this seems to be in function buildAndTag() in file:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{String context = defined(getDockerfilePath()) ? getDockerfilePath() : "."; lastResult = executeCmd("docker build -t " + i.next() + ((isNoCache()) ? " --no-cache=true " : "") + " " + ((isForcePull()) ? " --pull=true " : "") + " " + context);}}The line{{String context = defined(getDockerfilePath()) }}should be changed so that DockerfilePath is not the same as context. Those should be different things.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subsc
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allow to use the docker build {{ --file }} option when building an imageWe would like to not have the Dockerfile at the root of the project, and have everything docker related in a subfolder "docker".Then we would build the image with {{docker build -t myrepo/myproject:v01 --file docker/Dockerfile .}}'.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using{{ADD../scr/myfile.jar /srv/lib/}},for example. '..' is not allowed).So it would be nice to still have the option:- "Directory Dockerfile is in" (equivalent of "--file )- "Docker context".Note:In the code, this seems to be in function buildAndTag() in file:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{String context = defined(getDockerfilePath()) ? getDockerfilePath() : "."; lastResult = executeCmd("docker build -t " + i.next() + ((isNoCache()) ? " --no-cache=true " : "") + " " + ((isForcePull()) ? " --pull=true " : "") + " " + context);}}The line{{String context = defined(getDockerfilePath()) }}should be changed so that DockerfilePath is not the same as context. Those should be different things.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to th
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title Quentin Nerden created an issue Jenkins / JENKINS-29085 Allow to use the docker build --file option when building an image Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 25/Jun/15 4:05 PM Environment: Jenkins 1.6.10 CloudBees Docker Build and Publish plugin version 1.0 Ubuntu 14.04 Priority: Minor Reporter: Quentin Nerden Allow to use the docker build --file option when building an image We would like to not have the Dockerfile at the root of the project, and have everything docker related in a subfolder "docker". Then we would build the image with docker build -t myrepo/myproject:v01 --file docker/Dockerfile . '.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using ADD../scr/myfile.jar /srv/lib/ ,for example. '..' is not allowed). So it would be nice to still have the option: "Directory Dockerfile is in" (equivalent of "--file )
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allow to use the docker build {{--file}} option when building an imageWe would like to not NOT have the Dockerfile at the root of the project, and have everything docker related in a subfolder "docker".Then we would build the image with {{docker build -t myrepo/myproject:v01 --file docker/Dockerfile .}}'.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using{{ADD../scr/myfile.jar /srv/lib/}},for example. '..' is not allowed).So it would be nice to still have the option:- "Directory Dockerfile is in" (equivalent of "--file )- "Docker context".Note:In the code, this seems to be in function buildAndTag() in file:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{String context = defined(getDockerfilePath()) ? getDockerfilePath() : "."; lastResult = executeCmd("docker build -t " + i.next() + ((isNoCache()) ? " --no-cache=true " : "") + " " + ((isForcePull()) ? " --pull=true " : "") + " " + context);}}The line{{String context = defined(getDockerfilePath()) }}should be changed so that DockerfilePath is not the same as context. Those should be different things.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to
[JIRA] [p4-plugin] (JENKINS-27068) P4 plugin logs out or invalidates role user login
Title: Message Title Paul Allen commented on JENKINS-27068 Re: P4 plugin logs out or invalidates role user login I agree with you, the original issue might have been better solved using a Ticket Credential. If the home directory (and P4TICKETS file) are shared, then using the TICKET value in the Credential might have been better. An Unlimited ticket work work too. I'm happy to back out the change on 10/Apr/15 and always login if a password is provided. In addition I could add a checkbox (on the Password Credential) for 'p4 login -a', so the ticket is valid on all machines. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-29083) Where is the Messages class?
Title: Message Title Stéphane Bruckert resolved as Fixed Just found out the properties files... https://github.com/jenkinsci/junit-plugin/blob/master/src/main/resources/hudson/tasks/junit/Messages.properties Jenkins / JENKINS-29083 Where is the Messages class? Change By: Stéphane Bruckert Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-29084) Readline support for the Groovy Shell in Jenkins CLI
Title: Message Title Daniel Serodio created an issue Jenkins / JENKINS-29084 Readline support for the Groovy Shell in Jenkins CLI Issue Type: Improvement Assignee: Unassigned Components: cli Created: 25/Jun/15 2:48 PM Environment: Jenkins 1.575 Labels: script groovysh Priority: Minor Reporter: Daniel Serodio Please add support for readline editing in Jenkins CLI's Groovy Shell (groovysh), it would make interactive scripting so much easier…
[JIRA] [core] (JENKINS-29014) REST api link doesn't work from sub pages
Title: Message Title Stanislav Eremin commented on JENKINS-29014 Re: REST api link doesn't work from sub pages That seems not only for that page.. As for now a lot of page without it's own API seems to be broken with that link. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-29083) Where is the Messages class?
Title: Message Title Stéphane Bruckert created an issue Jenkins / JENKINS-29083 Where is the Messages class? Issue Type: Task Assignee: Unassigned Components: junit-plugin Created: 25/Jun/15 2:35 PM Priority: Trivial Reporter: Stéphane Bruckert Hello, I am curious to understand what's exactly this "Messages" class and where it is defined? https://github.com/jenkinsci/junit-plugin/blob/master/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java#L133 There are no imports to a Messages class and no Messages class exists in the project. Thanks! Add Comment
[JIRA] [core] (JENKINS-20731) Dashboard rendering spends too much time in WeatherColumn
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-20731 Dashboard rendering spends too much time in WeatherColumn Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20731) Dashboard rendering spends too much time in WeatherColumn
Title: Message Title Jesse Glick commented on JENKINS-20731 Re: Dashboard rendering spends too much time in WeatherColumn Hmm, seems I filed JENKINS-25075 later, but with better links. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-cifs-plugin] (JENKINS-19075) Publish over CIFS fails with Out of memory error
Title: Message Title Steve Robbins commented on JENKINS-19075 Re: Publish over CIFS fails with Out of memory error This issue bit me this week (Jenkins 1.596.3) and it took a bit of struggle to solve it because I was missing two pieces of information. 1. Even though the failing build was on a slave, the java settings changes (adding -Djcifs...) must be done on the master node. 2. When running as a windows service, the java command line arguments are contained within file jenkins.xml. This is the file to modify. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [doxygen-plugin] (JENKINS-29082) Build does not fail if there is a warning
Title: Message Title H R created an issue Jenkins / JENKINS-29082 Build does not fail if there is a warning Issue Type: Bug Assignee: Gregory Boissinot Components: doxygen-plugin Created: 25/Jun/15 2:23 PM Priority: Minor Reporter: H R I got: If warnings set the build to Unstable = checked But even if there are warnings in the code documentations the build will not fail. Console output: [Project] $ "C:\[...]\doxygen.exe" doc/doxyfile.conf [...]/LogTinyInterface.h:31: warning: explicit link request to 'include' could not be resolved [...]/LogTinyInterface.h:31: warning: explicit link request to 'include' could not be resolved [...]/LogTinyInterface.h:31: warning: explicit link request to 'include' could not be resolved Doxygen documentation generation ended with 0 errors and 0 warnings
[JIRA] [core] (JENKINS-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Kevin Phillips edited a comment on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent NOTE: Based on my brief review of the source code in the link provided above, the 'inconsistent' build labels are defined as build numbers with ascending values that have descending time stamps, or vice versa. As I mentioned in my bug report I have confirmed that none of the builds being reported by our Jenkins instance fall into that category.When I examine the build.xml files on disk on the Jenkins master, the build numbers, time stamps, folder names and symbolic links are all consistent with one another, and all of the values are always in ascending order (ie: build 123 has a time stamp larger than build 122 and smaller than build 124, in every reported case).I suppose this point may be moot if the underlying architecture has been changed in such a way that prevents any of these kinds of problems from happening, but I just thought I should mention it in case a similar bug may still be present in the latest version as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Kevin Phillips commented on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent NOTE: Based on my brief review of the source code in the link provided above, the 'inconsistent' build labels are defined as build numbers with ascending values that have descending time stamps, or vice versa. As I mentioned in my bug report I have confirmed that none of the builds being reported by Jenkins fall into that category. When I examine the build.xml files on disk on the Jenkins master, the build numbers, time stamps, folder names and symbolic links are all consistent with one another, and all of the values are always in ascending order (ie: build 123 has a time stamp larger than build 122 and smaller than build 124, in every reported case). I suppose this point may be moot if the underlying architecture has been changed in such a way that prevents any of these kinds of problems from happening, but I just thought I should mention it in case a similar bug may still be present in the latest version as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-9686) Mercurial polling does not expand parameters/tokens
Title: Message Title Kim Randell reopened an issue Reopened as I'm not sure if my previous comment has much visibility when the issue is closed. Jenkins / JENKINS-9686 Mercurial polling does not expand parameters/tokens Change By: Kim Randell Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Kevin Phillips commented on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent One last question: Assuming you understand the Jenkins internals better than I, can you say whether the weird 'agents out of sync' problem described by JENKINS-18671 may be the cause of this out-of-order build issue? (ie: if the agent says a build started at 12:59:07pm but the clock on the Jenkins master says the current time is 12:59:03, could that lead Jenkins to think the build times are broken when in fact they aren't in actuality?) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Kevin Phillips commented on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent Since 1.597 changed the storage layout of builds on disk, the reported issue should no longer occur there. Good to know. Hopefully the other product-stop bugs that were introduced by the 1.609.1 update can be fixed sooner rather than later so we can get those fixes as well. You need to compare the files on disk, not the loaded build records. Understood. I did actually compare the on-disk log and configuration files as stored on the Jenkins master when examining the data and could see nothing that would suggest that build numbers or time stamps were in any way out of order or duplicated with any other. That's what confused me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Carlo Alberto Degli Atti commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Hey Dave, is your Jenkins under https? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28601) Order of job table reverse
Title: Message Title Daniel Beck resolved as Fixed Fixed towards 1.618 by reverting the earlier change. Jenkins / JENKINS-28601 Order of job table reverse Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29080) Load statistics graphs too large
Title: Message Title Oliver Gondža commented on JENKINS-29080 Re: Load statistics graphs too large It seems that https://github.com/jenkinsci/jenkins/pull/1717 fixes it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title
Dave Thomas commented on JENKINS-28877
Re: Bitbucket Plugin unable to parse Bitbucket webhook response json
I am also getting an error 500 from within bitbucket. When I go to the JENKINS_URL/bitbucket-hook/ it gives me the following error:
javax.servlet.ServletException: net.sf.json.JSONException: A JSONObject text must begin with '{' at character 0 of
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411)
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)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29080) Load statistics graphs too large
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-29080 Load statistics graphs too large Change By: Oliver Gondža Summary: Load statistics graphs too largs large Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29081) Add ability for this plugin to communicate with the docker daemon using a java-based client
Title: Message Title Antoine Leveugle created an issue Jenkins / JENKINS-29081 Add ability for this plugin to communicate with the docker daemon using a java-based client Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 25/Jun/15 12:51 PM Environment: Jenkins 1.609.1 running in a docker container (official image) Labels: plugin build Priority: Major Reporter: Antoine Leveugle I would like to use this plugin in a full containerized environment. My Jenkins is running in a container (so it does not have docker installed on the Jenkins master) and I would like to build my project using this plugin by using the docker remote API. Do you think it would be relevant to be able with this plugin to communicate with the docker daemon using another way that docker cli ? As Ndeloof said for example using a java-based client ? (for example https://github.com/docker-java/docker-java) Thank you!
[JIRA] [core] (JENKINS-29080) Load statistics graphs too largs
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-29080 Load statistics graphs too largs Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 25/Jun/15 12:25 PM Labels: UI Priority: Trivial Reporter: Oliver Gondža The graph tries to fit the page size, though it has the size of the whole window not just the content area. Add Comment
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Rene Affourtit commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Created JENKINS-29079 to discuss possible improvements of the configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29079) Externals With(out) additional credentials is not clear
Title: Message Title Rene Affourtit created an issue Jenkins / JENKINS-29079 Externals With(out) additional credentials is not clear Issue Type: Improvement Assignee: Unassigned Components: subversion-plugin Created: 25/Jun/15 12:08 PM Environment: subversion plugin 2.5 Priority: Minor Reporter: Rene Affourtit The current way of authentification for external references in a project is not clear. See the extended discussion in JENKINS-22542 We specify Credentials to use for check out. With these credentials you have complete (read-only) access to the project and its externals. (project and externals are in the same repository). Why do we need to specify these same credentials again just to get the change log? For security? but the check out is already successful. Dave (our evil developer) can add an external to SecretProjectC to projectA. Dave can no longer do a complete checkout locally as he has no access to projectC. When the build server has access (svn user Jenkins with global read only access) Now the build server can access SecretProjectC (because another external in projectA requires the additional credentials). So you rely on having configured exluded svn user Jenkins from secret projects. In w
[JIRA] [core] (JENKINS-29041) Error Creating symbolic Links using Windows
Title: Message Title Fernando Rosado Altamirano resolved as Not A Defect I have detected the reason. I use conemu as console terminal for my laptop and there is a bug with java and conemu : Java under ConEmu crashes with java.lang.InternalError Using windows console or installing as a service solve the problem. Jenkins / JENKINS-29041 Error Creating symbolic Links using Windows Change By: Fernando Rosado Altamirano Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-7643) "Workspace is offline" on every SCM poll
Title: Message Title Oded Arbel edited a comment on JENKINS-7643 Re: "Workspace is offline" on every SCM poll I'm guessing this is marked as fixed because some SCM plugins implemented "poll only on master" which may have solved the problem. Unfortunately, I'm using the git plugin, whose maintainer chose not to implement it - [ #15136 |https://issues.jenkins-ci.org/browse/JENKINS-15136] , instead using a different functionality that does not work around this bug.I'm still experiencing it with git SCM and EC2 on-demand slaves - ever since I configured the EC2 plugin, occasionally (several times a day) all my jobs start running with the "workspace is offline" notification in the SCM polling log. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-7643) "Workspace is offline" on every SCM poll
Title: Message Title Oded Arbel reopened an issue Jenkins / JENKINS-7643 "Workspace is offline" on every SCM poll Change By: Oded Arbel Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
