[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] [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] [core] (JENKINS-28464) Jenkins hangs. Can't access via HTTP
Title: Message Title Marco Jacob commented on JENKINS-28464 Re: Jenkins hangs. Can't access via HTTP In our environment the devs wrote a tool polling on REST that blocked all HTTP threads because te tool used SAXBuild.build(url). That kept the connection open. Maybe that is the problem here also. Please try netstat -a with grep filter to find if there are too many connection kept established. 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] [http_request] (JENKINS-29092) Jenkins HTTP requests hanging on Solaris 11
Title: Message Title Marco Jacob created an issue Jenkins / JENKINS-29092 Jenkins HTTP requests hanging on Solaris 11 Issue Type: Bug Assignee: Janario Oliveira Attachments: jenkins.log, netstatNoRequest.txt, netstatWithRequest.txt, start-jenkins-test.sh, threadDump1.log, threadDump2.log Components: http_request Created: 26/Jun/15 7:23 AM Environment: SunOS AP4S201 5.11 11.1 sun4v sparc sun4v java version 1.7.0_45 Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) Server VM (build 24.45-b08, mixed mode) jenkins-1.609.1.war Priority: Minor Reporter: Marco Jacob I want to update from jenkins-1.532.1.war to jenkins-1.609.1.war. Tested on a clean directory. There are 2 more instances running on 8080 and 8085. The HTTP reuest hangs endless. Uploaded: startup script
[JIRA] [http_request] (JENKINS-29092) Jenkins HTTP requests hanging on Solaris 11
Title: Message Title Marco Jacob updated an issue Jenkins / JENKINS-29092 Jenkins HTTP requests hanging on Solaris 11 Change By: Marco Jacob Priority: Minor Major 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 SCM/JIRA link daemon commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Code changed in jenkins User: kzusy Path: src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java http://jenkins-ci.org/commit/bitbucket-plugin/cddb97e71e5a73f0a8f7242f05739dc7a56ce248 Log: JENKINS-28877 Updated the event payload json reference 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 SCM/JIRA link daemon commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Code changed in jenkins User: fbelzunc Path: src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java http://jenkins-ci.org/commit/bitbucket-plugin/4eaeec7714bbb7411fd7a0cf650911f3551da27a Log: Merge pull request #15 from kzusy/JENKINS-28877 JENKINS-28877 Compare: https://github.com/jenkinsci/bitbucket-plugin/compare/3f54f85234e1...4eaeec7714bb 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 Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Thanks for you quick response, Mark. We didn't change the security settings – the current value for the markup formatter is Safe HTML. The other available value is Escaped HTML. I just changed the setting to Escaped HTML once and back to Safe HTML again to rule out a weird configuration bug, but I doubt that this is the reason. I guess it's rather the security fix for the git plugin Escape HTML generated into jelly pages with escape=true. The last version without this fix is 2.3.2; I'll see if I can install it to verify this. It would be nice if the escaping could be done at a different level, i.e. before the jira-plugin has processed the message, or if it would use the Safe HTML formatter that would only remove potentially malicious tags like script. 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 Nicolas De Loof commented on JENKINS-29066 Re: Git plugin dev version 2.3.6-0c1a59a8 builds on every poll maybe safer to revert this remote-polling stuff and get 2.3.6 released 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 We hit a LOT of problems with the SVN plugin as well but I believe we've finally sorted all those out. More information would be nice, but be aware of JENKINS-21785 etc. (i.e. 'Additional Credentials' is deliberately needed in many situations for security concerns). I'm also currently investigating some bugs with the way the new Jenkins version handles jobs that are enqueued for builds. I was referring to those in my earlier comment. I expect further fixes in 1.609.3. 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 Kay Strobach commented on JENKINS-28827 Re: send html mails of console log on failure and success Alex Earl i think you misunderstood. I do not want to customize Jenkins mails. What i expect: same output in mail as in console view What i get: colored console view with shell color plugin non colored mails Possible solution: put the html from the console view into the mail as second mime part (text/html) Side Effects: failing builds will always deliver a defined set of data (console view) in the same visual way to the mail recipient. 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
[JIRA] [subversion-plugin] (JENKINS-27190) SVN Plugin Polling and Pinning with @ in SVN URL
Title: Message Title Daniel Beck resolved as Cannot Reproduce Needs to happen on a reasonably recent release of the SVN plugin to be relevant. Please update to plugin version 2.4.5 or 2.5. Jenkins / JENKINS-27190 SVN Plugin Polling and Pinning with @ in SVN URL Change By: Daniel Beck Status: Open Resolved Resolution: CannotReproduce 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-27909) SCM poll not working with SubVersion
Title: Message Title Daniel Beck resolved as Cannot Reproduce Please update your software. Issue needs to happen on current versions of Subversion Plugin (2.4.5 or 2.5) to be relevant. Jenkins / JENKINS-27909 SCM poll not working with SubVersion Change By: Daniel Beck Status: Open Resolved Resolution: CannotReproduce 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-with-parameters-plugin] (JENKINS-29094) NodeLabelParameter shouldn't be incompatible with Build with Parameters
Title: Message Title Anna Freiholtz created an issue Jenkins / JENKINS-29094 NodeLabelParameter shouldn't be incompatible with Build with Parameters Issue Type: Bug Assignee: Unassigned Components: build-with-parameters-plugin Created: 26/Jun/15 8:48 AM Environment: Jenkins 1.617 Build with Parameters 1.3 Node and Label Parameter 0.4 Priority: Major Reporter: Anna Freiholtz Build with Parameters doesn't handle the parameters Node and Label from Node and Label Parameter plugin. Add Comment
[JIRA] [core] (JENKINS-27549) Job loading can be broken by a NPE in a build trigger
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-27549 Job loading can be broken by a NPE in a build trigger Change By: Daniel Beck Labels: 1. 509 609 .2-fixedrobustness 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-26516) Build Successful but Commit Release fails
Title: Message Title Daniel Beck resolved as Cannot Reproduce Subversion Plugin 1.45 is several years old, as is Jenkins 1.51x. Please update your software before reporting bugs. Jenkins / JENKINS-26516 Build Successful but Commit Release fails Change By: Daniel Beck Status: Open Resolved Resolution: CannotReproduce 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 Nicolas De Loof commented on JENKINS-29066 Re: Git plugin dev version 2.3.6-0c1a59a8 builds on every poll I was able to reproduce and diagnose this issue. This issue occurs as the remote repo as some branch which is ancestor for another one. On https://github.com/MarkEWaite/JENKINS-26197 you're using to reproduce this issue : master is ancestor for branch-2015-06-10-21-21-21-pe As the job is built first, all `branch-*` branches get built as expected and master is excluded as hudson.plugins.git.util.GitUtils#filterTipBranches is excluding such non-tip branches. Then during polling (without workspace) master branch is detected as a non-built head, a build is triggered for it, and checkout do exclude it again and do re-build previous commit, resulting in infinite build loop. I can't find a reasonable workaround for this issue. I propose to introduce a new FilterTipBranches advanced behavior to enable hudson.plugins.git.util.GitUtils#filterTipBranches, This one would force use of a workspace for polling, and would be automatically added to any pre-2.3.6 job. wdyt ? 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] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target
Title: Message Title Arend v. Reinersdorff created an issue Jenkins / JENKINS-29093 POM location is deleted when changing Maven top-level target Issue Type: Bug Assignee: mdonohue Components: configurationslicing-plugin Created: 26/Jun/15 8:32 AM Environment: Jenkins 1.6.10 Configuration Slicing Plugin 1.40 Priority: Minor Reporter: Arend v. Reinersdorff I noticed that setting the Maven top-level target for a job deletes the job's POM location setting. I can reproduce this as follows: There's a freestyle project with a Maven Build step. The Goals are clean verify, the POM location is myproject-parent/pom.xml. Change the Maven goal with the Configuration Slicing Plugin to clean package Result: The POM location is empty.
[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
The intended design was that Jenkins would only use one Perforce user account (typically 'jenkins') to run all the Jobs. The 'jenkins' account would have limited permissions in the protection table ('open' on '//...' for builds and if using the publish, 'write' on a limited area).
Does this mean that you have a Perforce Password Credential for all your users? How would you switch the credential for the Jenkins job when starting the build? I must admit I hadn't thought of this use case, is it desirable to spoof the user when running a build on their behalf?
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-11370) The directory name is invalid on Windows slaves
Title: Message Title Sorin Sbarnea commented on JENKINS-11370 Re: The directory name is invalid on Windows slaves Somehow I do always get this bug while trying to start Windows slaves from a Linux jenkins instance via SSH. SSH is configured properly on the machine and jenkins is configured to start a session using the Administrator account, which works fine. The log is available at https://gist.github.com/ssbarnea/370949586b622f751d07 and the important part being: #./deploy/slave-setup.sh ' on tocco [marvin] $ /bin/bash C:\Users\Administrator\hudson5000371039477233927.sh hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133) Caused by: java.io.IOException: Cannot run program /bin/bash (in directory C:\tools\cygwin\home\Administrator\marvin\marvin): CreateProcess error=3, The system cannot find the path specified at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) 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 Richard commented on JENKINS-28976 Re: windows master, mac slave, polling fails trying to launch windows GIT_SSH program I went to the mac slave and killed the jenkins runner and the jenkins runner restarted. 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-setup-plugin] (JENKINS-29105) cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash
Title: Message Title
Sorin Sbarnea updated an issue
Jenkins / JENKINS-29105
cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash
Change By:
Sorin Sbarnea
ThesshpartworksproperlyandJenkinssucceedsoncopyingtheslave.jarfileandexecutesitbutitseemsthatitdoesmakesomewrongassumptionsaboutpaths,givingtheerrorbelow:{code:java}[marvin]$/bin/bashC:\Users\Administrator\hudson5000371039477233927.shhudson.util.IOException2:SlaveJVMhasnotreportedexitcode.Isitstillrunning? athudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) athudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133)Causedby:java.io.IOException:Cannotrunprogram/bin/bash(indirectoryC:\tools\cygwin\home\Administrator\marvin\marvin):CreateProcesserror=3,Thesystemcannotfindthepathspecified atjava.lang.ProcessBuilder.start(UnknownSource) athudson.Proc$LocalProc.init(Proc.java:244){code}Fulllogathttps://gist.github.com/ssbarnea/370949586b622f751d07 Thewindowspathiscorrect,beingcreatedbyJenkins,butitseemsthatheexecutionof/bin/bashistheonethatfails.Ifonedoesmanuallyperformssshtothemachine,usingthesamecredentials,theywouldbeabletorun/bin/bash.IbelievethattheproblemisbecauseJenkinsisassumingthatbeingaWindowsmachineithastoprovideaWindowspathtotheCreateProcesswhichprobablyexpectsaUnixpathinsteadbecausetheentireshellisrunundercygwin.Still,Itriedanycombinationsofconfiguringtheslavepathonthenodeconfigurationbutnoneseemstowork.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you
[JIRA] [core] (JENKINS-28912) CLONE - Job naming naming convention
Title: Message Title Sagayaraj David updated an issue Jenkins / JENKINS-28912 CLONE - Job naming naming convention Change By: Sagayaraj David Summary: CLONE-Jobnaming andNode namingconvention 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-28912) CLONE - Job naming and Node naming convention
Title: Message Title Sagayaraj David reopened an issue It appears that by default java.util.regex.Pattern class does not support conditional regex. But it is possible with JRegex. Please check http://stackoverflow.com/questions/3687921/conditional-regular-_expression_-in-java for clarification Jenkins / JENKINS-28912 CLONE - Job naming and Node naming convention Change By: Sagayaraj David Resolution: NotADefect 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] [docker-build-publish-plugin] (JENKINS-29098) Can not use multiple credentials per job
Title: Message Title Antoine Cotten edited a comment on JENKINS-29098 Re: Can not use multiple credentials per job ShouldIcreateanissuethere? (edit:Ididn'tseeyouassignedanewcomponenttomyissue,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] [job-dsl-plugin] (JENKINS-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title Daniel Spilker resolved as Not A Defect Jenkins / JENKINS-29022 Using configure block for scm results in extraneous NullSCM entry Change By: Daniel Spilker Status: Open Resolved Resolution: NotADefect 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-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29022 Re: Using configure block for scm results in extraneous NullSCM entry Code changed in jenkins User: Daniel Spilker Path: docs/The-Configure-Block.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/NodeEnhancement.groovy http://jenkins-ci.org/commit/job-dsl-plugin/6a572fe9b874b5e700a18c573096e7f8e198db6e Log: Merge pull request #507 from CoreMedia/ JENKINS-29022 JENKINS-29022 explain behaviour of div operator when using attributes, fixed example Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/3caed33fa5cd...6a572fe9b874 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-setup-plugin] (JENKINS-29105) cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash
Title: Message Title Sorin Sbarnea commented on JENKINS-29105 Re: cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash Based on https://wiki.jenkins-ci.org/display/JENKINS/SSH+slaves+and+Cygwin page it seems that I need to add a new plugin, https://wiki.jenkins-ci.org/display/JENKINS/Cygpath+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] [slave-setup-plugin] (JENKINS-29105) cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-29105 Re: cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash Basedonhttps://wiki.jenkins-ci.org/display/JENKINS/SSH+slaves+and+CygwinpageitseemsthatIneedtoaddanewplugin,https://wiki.jenkins-ci.org/display/JENKINS/Cygpath+Plugin Still,evenafterIinstalledthecygpathplugin,Jenkinskeepsgivingmethesamekindoferrors. 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-20569) Polling with excluded regions don't prevent job triggered
Title: Message Title Erik Shreve edited a comment on JENKINS-20569 Re: Polling with excluded regions don't prevent job triggered Excludedregionsarealsonotworkingforme.Ihaveatestrepowiththefollowingstructure/src/main.c/docs/otherdocs/somefile.txtI'veaddedForcepollingusingworkspaceasanAdditionalbehavior.Theexcludedregionsaresetto:/docs/otherdocs/.*/docs/otherdocs/somefile.txtdocs/otherdocs/somefile.txtdocs/otherdocs/.*\.txtIncludedregionsisempty.Whentheprojectpollstherepo,itstillbuildswhentheonlychangedfileis:/docs/otherdocs/somefile.txtChangetofileissimplyechohellosomefile.txtgitcommit-a-mchangedsomefilegitpushoriginmasterI'monJenkins1.597,withgit client plugin 1 2 . 16 3 . 1 5 PollingLogshows:StartedonJun26,201510:02:01AMPollingSCMchangesonmybuildmachineUsingstrategy:Default[poll]LastBuiltRevision:Revisionc4ab323cf0ac778ed3b0e5fd13467be5587d3fe7(refs/remotes/ErikTest/master)FetchingchangesfromtheremoteGitrepositoriesPollingforchangesinDone.Took1.1secChangesfound 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] [tap-plugin] (JENKINS-29103) localhost appears in url for Failed Tests
Title: Message Title Han Geerligs created an issue Jenkins / JENKINS-29103 localhost appears in url for Failed Tests Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: localhost issue TAP.PNG Components: tap-plugin Created: 26/Jun/15 2:05 PM Environment: tap-plugin 1.22 Labels: plugin Priority: Minor Reporter: Han Geerligs in All Failed Tests section the url for the test is using 'localhost' as IP-address and not the actual IP-address. This is causing problems when viewing this result outside of the IP-address where Jenkins is running on (e.g. elsewhere)
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on console icon doesn't work
Title: Message Title Joel Njanga commented on JENKINS-25430 Re: Clicking on console icon doesn't work This does NOT work with Jenkins 1.606 + build Pipeline plugin 1.4.7 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-29100) NPE when using previousNames
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29100 Re: NPE when using previousNames Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/Messages.properties job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/b96999486e829a3e2581e26394a946bee54bbeea Log: Merge pull request #508 from CoreMedia/ JENKINS-29100 JENKINS-29100 provide better error message Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/4535b723900a...b96999486e82 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-29100) NPE when using previousNames
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.35. Jenkins / JENKINS-29100 NPE when using previousNames Change By: Daniel Spilker 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] [job-dsl-plugin] (JENKINS-29100) NPE when using previousNames
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29100 Re: NPE when using previousNames Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/Messages.properties job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/835816f72ae437f0c7e627fd7c412d5a8c425f0b Log: JENKINS-29100 provide better error message when trying to move a job into a non-existing folder 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-25430) Clicking on console icon doesn't work
Title: Message Title Nicolas BOHEAS updated an issue Jenkins / JENKINS-25430 Clicking on console icon doesn't work Change By: Nicolas BOHEAS Attachment: jquery.fancybox-1.3.4.js Attachment: jquery.tooltip.min.js 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-25430) Clicking on console icon doesn't work
Title: Message Title Nicolas BOHEAS commented on JENKINS-25430 Re: Clicking on console icon doesn't work I have linked thos files if needed. 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-11370) The directory name is invalid on Windows slaves
Title: Message Title
Sorin Sbarnea edited a comment on JENKINS-11370
Re: The directory name is invalid on Windows slaves
SomehowIdoalwaysgetthisbugwhiletryingtostartWindowsslavesfromaLinuxjenkinsinstanceviaSSH.SSHisconfiguredproperlyonthemachineandjenkinsisconfiguredtostartasessionusingtheAdministratoraccount,whichworksfine.Thelogisavailableathttps://gist.github.com/ssbarnea/370949586b622f751d07andtheimportantpartbeing:{code:java}#./deploy/slave-setup.sh'ontocco[marvin]$/bin/bashC:\Users\Administrator\hudson5000371039477233927.shhudson.util.IOException2:SlaveJVMhasnotreportedexitcode.Isitstillrunning? athudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) athudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133)Causedby:java.io.IOException:Cannotrunprogram/bin/bash(indirectoryC:\tools\cygwin\home\Administrator\marvin\marvin):CreateProcesserror=3,Thesystemcannotfindthepathspecified atjava.lang.ProcessBuilder.start(UnknownSource) athudson.Proc$LocalProc.init(Proc.java:244){code} Thewindowspathiscorrect,beingcreatedbyJenkins,butitseemsthatheexecutionof/bin/bashistheonethatfails.Ifonedoesmanuallyperformssshtothemachine,usingthesamecredentials,theywouldbeabletorun/bin/bash.IbelievethattheproblemisbecauseJenkinsisassumingthatbeingaWindowsmachineithastoprovideaWindowspathtotheCreateProcesswhichprobablyexpectsaUnixpathinsteadbecausetheentireshellisrunundercygwin.Still,Itriedanycombinationsofconfiguringtheslavepathonthenodeconfigurationbutnoneseemstowork.
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-commons-plugin] (JENKINS-29102) prefer .docker/config.json over .dockercfg for docker 1.7+
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-29102 prefer .docker/config.json over .dockercfg for docker 1.7+ Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-commons-plugin Created: 26/Jun/15 1:54 PM Priority: Minor Reporter: Nicolas De Loof see https://github.com/docker/docker/pull/12009 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [slave-setup-plugin] (JENKINS-29105) cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-29105 cannot start windows slaves via SSH (cygwin) due to Caused by: java.io.IOException: Cannot run program /bin/bash Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup-plugin Created: 26/Jun/15 3:27 PM Environment: jenkins-1.611 and Windows with cygwin installed and configured SSH server. Labels: cygwin Priority: Critical Reporter: Sorin Sbarnea The ssh part works properly and Jenkins succeeds on copying the slave.jar file and executes it but it seems that it does make some wrong assumptions about paths, giving the error below: [marvin] $ /bin/bash C:\Users\Administrator\hudson5000371039477233927.sh hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) at
[JIRA] [pretested-integration-plugin] (JENKINS-29101) Multiple SCM plugin behaviour changed after Jenkins core update (Praqma case 13190)
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-29101 Multiple SCM plugin behaviour changed after Jenkins core update (Praqma case 13190) Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 26/Jun/15 1:48 PM Priority: Trivial Reporter: Bue Petersen [TEST] org.jenkinsci.plugins.pretestedintegration.integration.scm.git.MultipleScmIT.verifyOrderOfBuildDataObjects Test fails after updating the Jenkins core (from 1.532.1 to 1.580.3). The assert that fails is one that checks the branch name of a build action. Disabling that assert causes the rest of the job to run fine and pass. Might not be an actual failure, but it's still an unwanted peculiarity. I added (cleaned up) console outputs of both jobs. The biggest difference that jumps out is the fact that in the newer version, the first fetch only finds two branches, where the previous version found three. 1.532.1 (1.5 KB) 1.580.3 (1.9 KB) This issue isn't a current problem as we haven't changed the Jenkins core dependency but it will be soon.
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on console icon doesn't work
Title: Message Title Joel Njanga commented on JENKINS-25430 Re: Clicking on console icon doesn't work thanks for your prompt response. agreed that this issue is minor in comparison with https://issues.jenkins-ci.org/browse/JENKINS-20873 which definitely does not work with jenkins 1.606 even when dowgradind the plugin to ver 1.4.3 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-29100) NPE when using previousNames
Title: Message Title Daniel Spilker commented on JENKINS-29100 Re: NPE when using previousNames https://github.com/jenkinsci/job-dsl-plugin/pull/508 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-28294) JDK 5 not supported with Maven error with JDK 6
Title: Message Title Daniel Beck commented on JENKINS-28294 Re: JDK 5 not supported with Maven error with JDK 6 FWIW at JUC this week I talked to Kohsuke about this. He said that Maven Projects requiring a JDK for building that is able to run the version of Jenkins that invokes it is a limitation in the basic design of Maven Plugin and cannot be changed. 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] [pretested-integration-plugin] (JENKINS-29104) Swith the squash strategy to use Git Client API instead of command line (Praqma case 13136)
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-29104 Swith the squash strategy to use Git Client API instead of command line (Praqma case 13136) Issue Type: New Feature Assignee: Praqma Support Components: pretested-integration-plugin Created: 26/Jun/15 2:07 PM Priority: Critical Reporter: Bue Petersen Part of the roadmap of working towards using GitClient API instead of command line for git operations. https://trello.com/c/gQOkBsdg/22-full-integration-with-gitclient-plugin-facilitates-the-usage-of-credentials This is the first proof-of-concept on getting the features we need into the API. Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Title: Message Title Joel Njanga commented on JENKINS-25427 Re: Build Pipleline Plugin no longer allows starting build with parameters Broken in plugin version 1.4.7 on Jenkins 1.606 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-25430) Clicking on console icon doesn't work
Title: Message Title Nicolas BOHEAS commented on JENKINS-25430 Re: Clicking on console icon doesn't work Hy, I 've found a solution : go to the plugin directory build-pipeline-plugin. and edit the file jquery.fancybox-1.3.4.js : change the test about IE6 by the value false (line 29 and 946). and now edit the file jquery.tooltip.min.js : change column 53 by false (IE=false). whitout restart Jenkins, but by press CTRL+F5 on the job pipeline, the console will appear! Of course, the pb will not be solve on ie6 but is it a real pb? 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-25430) Clicking on console icon doesn't work
Title: Message Title Nicolas BOHEAS edited a comment on JENKINS-25430 Re: Clicking on console icon doesn't work Ihavelinked thos the2 files corrected ifneeded. 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-20569) Polling with excluded regions don't prevent job triggered
Title: Message Title Erik Shreve commented on JENKINS-20569 Re: Polling with excluded regions don't prevent job triggered Excluded regions are also not working for me. I have a test repo with the following structure /src/main.c /docs/otherdocs/somefile.txt I've added Force polling using workspace as an Additional behavior. The excluded regions are set to: /docs/otherdocs/.* /docs/otherdocs/somefile.txt docs/otherdocs/somefile.txt docs/otherdocs/.*\.txt Included regions is empty. When the project polls the repo, it still builds when the only changed file is: /docs/otherdocs/somefile.txt Change to file is simply echo hello somefile.txt git commit -a -m changed somefile git push origin master I'm on Jenkins 1.597, with git client plugin 1.16.1 Polling Log shows: Started on Jun 26, 2015 10:02:01 AM Polling SCM changes on mybuildmachine Using strategy: Default [poll] Last Built Revision: Revision c4ab323cf0ac778ed3b0e5fd13467be5587d3fe7 (refs/remotes/ErikTest/master) Fetching changes from the remote Git repositories Polling for changes in Done. Took 1.1 sec Changes found 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-29092) Jenkins HTTP requests hanging on Solaris 11
Title: Message Title Janario Oliveira assigned an issue to Unassigned Jenkins / JENKINS-29092 Jenkins HTTP requests hanging on Solaris 11 Change By: Janario Oliveira Component/s: core Component/s: http_request Assignee: JanarioOliveira 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] [ci-game-plugin] (JENKINS-23939) CI Game doesn't count points for Maven Project
Title: Message Title mhagnumdw mhagnumdw edited a comment on JENKINS-23939 Re: CI Game doesn't count points for Maven Project Ihavethesameproblem.Ihavecombinedseveralversionsinmytests.Mycurrentversions: Jenkins1.617 ContinuousIntegrationgame1.21maven3.2.1MavenIntegrationplugin2.10StaticAnalysisUtilities1.7.2TaskScannerPlug-in4.45PMDPlug-in3.41FindBugsPlug-in4.61CheckstylePlug-in3.42 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] [ci-game-plugin] (JENKINS-23939) CI Game doesn't count points for Maven Project
Title: Message Title mhagnumdw mhagnumdw commented on JENKINS-23939 Re: CI Game doesn't count points for Maven Project I have the same problem.I have combined several versions in my tests. My current versions: Continuous Integration game 1.21 maven 3.2.1 Maven Integration plugin 2.10 Static Analysis Utilities 1.7.2 Task Scanner Plug-in 4.45 PMD Plug-in 3.41 FindBugs Plug-in 4.61 Checkstyle Plug-in 3.42 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-20569) Polling with excluded regions don't prevent job triggered
Title: Message Title Erik Shreve commented on JENKINS-20569 Re: Polling with excluded regions don't prevent job triggered For me something is fundamentally broken. Exclusion by commit message also does not work (I haven't tried the other exclusion features). Also, I tried setting the excluded regions to just: .* If I read the PathRestriction class correctly, this should prevent all builds from occurring. However, my build still happens. My branch specifier is set to */master Build triggers section just has Poll SCM checked and it is set to poll once an hour. I'm visiting the git/notifyCommit?url= "" of the jenkins server to start the polling. 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-28989) support registry credentials
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28989 Re: support registry credentials Code changed in jenkins User: Nicolas De Loof Path: src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/Docker.java src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/DockerBuildWrapper.java src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/PullDockerImageSelector.java src/main/resources/com/cloudbees/jenkins/plugins/docker_build_env/DockerBuildWrapper/config.jelly src/main/resources/com/cloudbees/jenkins/plugins/docker_build_env/DockerBuildWrapper/help-dockerRegistryCredentials.html http://jenkins-ci.org/commit/docker-custom-build-environment-plugin/7ab4ebbdf94cc3d10def290121dd86f62ff105d3 Log: JENKINS-28989 let user configure registry credentials 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-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title
Daniel Spilker edited a comment on JENKINS-29022
Re: Using configure block for scm results in extraneous NullSCM entry
Thatistheexpectedbehavior.Whenspecifyingattributes,thedivoperatorwillfindthenodewithmatchingattributesorcreateanewone.Iwillupdatethedocs,topointthatout.Tofixyourexample,youcanremovetheexistingscmelement:{code}defp4ConfigureCoordinator(){{project-project.remove(project/scm)project/scm(class:'org.jenkinsci.plugins.p4.PerforceScm'){}}}freeStyleJob('scratch-dsl'){configurep4ConfigureCoordinator()}{code}Youcanalsochangethevalueoftheclassattribute:{code}defp4ConfigureCoordinator(){{project-(project/scm). attributes[' @ class '] ='org.jenkinsci.plugins.p4.PerforceScm'}}freeStyleJob('scratch-dsl'){configurep4ConfigureCoordinator()}{code}
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-20569) Polling with excluded regions don't prevent job triggered
Title: Message Title Erik Shreve commented on JENKINS-20569 Re: Polling with excluded regions don't prevent job triggered I noticed the following in Jenkins' log file: Jun 26, 2015 4:11:02 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default The Git Client plugin was configured with JGit. I deleted the JGit entry on the configuration page and after reloading the page it had put a Git entry in as default. The exclude regions are now working. 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-29107) Changing order of post build steps doesn't trigger job xml update
Title: Message Title Daniel Spilker commented on JENKINS-29107 Re: Changing order of post build steps doesn't trigger job xml update https://github.com/jenkinsci/job-dsl-plugin/pull/510 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-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title
Daniel Spilker commented on JENKINS-29022
Re: Using configure block for scm results in extraneous NullSCM entry
Hm, I tested the example on the playground and it did work there. But now I fixed the example so that it works in Jenkins. I need to investigate that...
So, this works in Jenkins:
def p4ConfigureCoordinator( ) {
{ project -
(project / scm).@class = 'org.jenkinsci.plugins.p4.PerforceScm'
}
}
freeStyleJob('scratch-dsl') {
configure p4ConfigureCoordinator()
}
but fails in the playground:
groovy.lang.MissingFieldException: No such field: class for class: groovy.util.Node
at script14353522663381436870344$_p4ConfigureCoordinator_closure2.doCall(script14353522663381436870344.groovy:3)
at javaposse.jobdsl.dsl.WithXmlAction$_execute_closure1.doCall(WithXmlAction.groovy:18)
at javaposse.jobdsl.dsl.WithXmlAction$_execute_closure1.doCall(WithXmlAction.groovy)
at javaposse.jobdsl.dsl.WithXmlAction.execute(WithXmlAction.groovy:17)
at javaposse.jobdsl.dsl.WithXmlAction$execute.call(Unknown Source)
at javaposse.jobdsl.dsl.Job$_executeWithXmlActions_closure34.doCall(Job.groovy:541)
at javaposse.jobdsl.dsl.Job.executeWithXmlActions(Job.groovy:540)
at javaposse.jobdsl.dsl.Job$executeWithXmlActions.callCurrent(Unknown Source)
at javaposse.jobdsl.dsl.Job.getNode(Job.groovy:533)
at javaposse.jobdsl.dsl.Item.getXml(Item.groovy:37)
at com.sheehan.jobdsl.DslScriptExecutor$_execute_closure2.doCall(DslScriptExecutor.groovy:33)
at com.sheehan.jobdsl.DslScriptExecutor.execute(DslScriptExecutor.groovy:33)
at com.sheehan.jobdsl.ScriptExecutor$execute.call(Unknown Source)
at Ratpack$_run_closure1_closure3_closure7.doCall(Ratpack.groovy:39)
at ratpack.groovy.internal.ClosureInvoker.invoke(ClosureInvoker.java:65)
at ratpack.groovy.handling.internal.ClosureBackedHandler.handle(ClosureBackedHandler.java:42)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.next(DefaultContext.java:223)
at ratpack.http.internal.MethodHandler.handle(MethodHandler.java:41)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:237)
at ratpack.handling.internal.ChainHandler.handle(ChainHandler.java:37)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:246)
at ratpack.path.internal.PathHandler.handle(PathHandler.java:38)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.next(DefaultContext.java:223)
at ratpack.path.internal.PathHandler.handle(PathHandler.java:40)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.next(DefaultContext.java:223)
at ratpack.path.internal.PathHandler.handle(PathHandler.java:40)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:237)
at ratpack.handling.internal.ChainHandler.handle(ChainHandler.java:37)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:237)
at
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Jared Szechy commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated This issue still exists. For the fetch of the main repo it uses... using GIT_SSH to set credentials Kiln SSH Key The error is: FATAL: Command git submodule update --init --recursive returned status code 1 The fix is probably to simply prefix the git submodule command with the GIT_SSH='.' environment variable. 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-28968) Aborting builds does not kill surefire sub-process
Title: Message Title Ryan Desmond commented on JENKINS-28968 Re: Aborting builds does not kill surefire sub-process I think this is a duplicate, closing and moving the conversation there. 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] [github-plugin] (JENKINS-29108) Github pull_request event not supported?
Title: Message Title Bruno Basto created an issue Jenkins / JENKINS-29108 Github pull_request event not supported? Issue Type: Bug Assignee: Unassigned Components: github-plugin Created: 26/Jun/15 9:42 PM Priority: Minor Reporter: Bruno Basto This is the message I get when my webhook tries to send the pull_request event to my Jenkins instance: A problem occurred while processing the request. Please check a href="" bug tracker/a to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. a href="" users list/a might be also useful in understanding what has happened./ph2Stack trace/h2pre style=margin:2em; clear:bothjavax.servlet.ServletException: java.lang.IllegalArgumentException: Github Webhook event of type pull_request is not supported. Only push events are current supported I just updated the plugin. These are the request headers: Request URL: ###/github-webhook/ Request method: POST Authorization: content-type: application/x-www-form-urlencoded Expect: User-Agent: GitHub-Hookshot/2f00e0f X-GitHub-Delivery: 31deb900-1ba2-11e5-8476-6f14de4238e3 X-GitHub-Event: pull_request Notice I omitted the actual URL to Jenkins instance.
[JIRA] [xcode-plugin] (JENKINS-29106) Cannot have more than one Apple Developer Profile
Title: Message Title Gary MacDonald created an issue Jenkins / JENKINS-29106 Cannot have more than one Apple Developer Profile Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 26/Jun/15 7:29 PM Priority: Critical Reporter: Gary MacDonald In Manage Jenkins - Manage Credentials page, we have added one Apple Developer Profile and successfully able to use it to sign builds. Anew project is now hosted on this jenkins instance that requires a different profile. I went to Manage Jenkins - Manage Credentials page, and added a second Apple Developer Profile (with a different description). Upon uploading the second developer profile, I now see that the first one says There's no certificate in this profile. If I re-upload the first developer profile, I now get the same There's no certificate in this profile error on the second developer profile. When I examine the HTML on the page, I notice that the input type=hidden name=id tag has differing value's for the two trees (to be expected), so I'm not quite sure why we're losing the contents of the previous profile when uploading a new one, unless it's because for some reason only one is supported.
[JIRA] [job-dsl-plugin] (JENKINS-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title A C commented on JENKINS-29022 Re: Using configure block for scm results in extraneous NullSCM entry The first example works. The second example, (project / scm).attributes['class'] = 'org.jenkinsci.plugins.p4.PerforceScm' results in a job dsl crash: java.lang.IllegalArgumentException: argument type mismatch 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.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at groovy.lang.MetaClassImpl.setProperty(MetaClassImpl.java:2416) at groovy.lang.MetaClassImpl.setProperty(MetaClassImpl.java:3347) at groovy.lang.DelegatingMetaClass.setProperty(DelegatingMetaClass.java:170) at org.codehaus.groovy.runtime.InvokerHelper.setProperty(InvokerHelper.java:183) at org.codehaus.groovy.runtime.DefaultGroovyMethods.putAt(DefaultGroovyMethods.java:226) at org.codehaus.groovy.runtime.dgm$634.doMethodInvoke(Unknown Source) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1079) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at groovy.lang.DelegatingMetaClass.invokeMethod(DelegatingMetaClass.java:149) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:44) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) at script1435350245097460611414$_p4ConfigureCoordinator_closure2.doCall(script1435350245097460611414.groovy:3) 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.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:39) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at javaposse.jobdsl.dsl.WithXmlAction$_execute_closure1.doCall(WithXmlAction.groovy:18) 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.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at
[JIRA] [job-dsl-plugin] (JENKINS-29070) Support for Maven plugin feature to enable/disable downstream trigger
Title: Message Title Christian Galsterer commented on JENKINS-29070 Re: Support for Maven plugin feature to enable/disable downstream trigger PR available at https://github.com/jenkinsci/job-dsl-plugin/pull/509 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-29070) Support for Maven plugin feature to enable/disable downstream trigger
Title: Message Title Christian Galsterer resolved as Fixed Jenkins / JENKINS-29070 Support for Maven plugin feature to enable/disable downstream trigger Change By: Christian Galsterer Status: InProgress 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] [job-dsl-plugin] (JENKINS-29100) NPE when using previousNames
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29100 Re: NPE when using previousNames Code changed in jenkins User: Daniel Spilker Path: docs/Home.md http://jenkins-ci.org/commit/job-dsl-plugin/a2a96a892557156dc72d20859dc6c6c61d18635e Log: added release notes for JENKINS-29100 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-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Ryan Desmond commented on JENKINS-26048 Re: Jenkins no longer cleaning up child processes when build stopped - as of 1.587 I had a chance to look at it a little more. I don't understand it fully, but I think the big difference is that the process tree is not referenced in the maven job. As such, we kill the maven instance itself but child processes (such as surefire) aren't stopped. I'm not sure why maven isn't taking care of that itself – does Jenkins kill -9 maven? I think the other question is why Jenkins isn't using the process tree to kill the entire tree in maven jobs. It seems like it would be easy for a maven job to spin of a child (like surefire), which could exec another child. 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-29107) Changing order of post build steps doesn't trigger job xml update
Title: Message Title Daniel Spilker created an issue Jenkins / JENKINS-29107 Changing order of post build steps doesn't trigger job xml update Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 26/Jun/15 7:52 PM Priority: Minor Reporter: Daniel Spilker The Job DSL plugin does not update a job if the new config is similar to the existing config. Two configs are considered to be similar if they contain the same elements and attributes regardless of order. This behavior is undesired when e.g. trying to change the order of build steps. This has been reported on the mailing list. Add Comment
[JIRA] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title
Pablo Serrano created an issue
Jenkins / JENKINS-29096
Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-plugin
Created:
26/Jun/15 10:05 AM
Environment:
Jenkins ver. 1.617, Bitbucket-plugin 1.1.0
Priority:
Blocker
Reporter:
Pablo Serrano
Hi, i try to work a webhook on my repo in bitbucket and bitbucket plugin show me this error, and not working also
avax.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)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
[JIRA] [distfork-plugin] (JENKINS-23567) Excessive warnings on exception while evaluating exeparent.url
Title: Message Title Daniel Beck commented on JENKINS-23567 Re: Excessive warnings on exception while evaluating exeparent.url Caused by: https://github.com/jenkinsci/distfork-plugin/blob/master/src/main/java/hudson/plugins/distfork/DistForkTask.java#L104 I wonder what happens when this returns null instead. Ideally Jenkins would just assume there's no URL for the task. 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 Mikhail Tyuzin commented on JENKINS-29086 Re: User IDs are case sensitive in saml-plugin The same is true for groups in newly added groups support so probably both should be fixed at once. For groups this issue is much more significant. 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-monitor-plugin] (JENKINS-29097) Possibility to add Test results presentation.
Title: Message Title Claes Brussander created an issue Jenkins / JENKINS-29097 Possibility to add Test results presentation. Issue Type: New Feature Assignee: Unassigned Components: build-monitor-plugin Created: 26/Jun/15 10:17 AM Priority: Minor Reporter: Claes Brussander I have been using the radiator plugin to present Test results for our CI test jobs. This plugin is deprecated and not supported anymore and there is a suggestion to use the build monitor plugin instead. I can still use the radiator plugin but this plugin lacks for example the ability to present the display-name instead of the project name. The build monitor plugin doesn't support the possiblity to present Test results. Is it possible to add presentation of Test results (similar to how it is done in the radiator plugin)? This would be a great improvment for this plugin. Best regars, Claes Brussander Add Comment
[JIRA] [core] (JENKINS-29109) 500 error for building without sending parameters
Title: Message Title ikedam created an issue Jenkins / JENKINS-29109 500 error for building without sending parameters Issue Type: Bug Assignee: ikedam Components: core Created: 27/Jun/15 1:37 AM Environment: Jenkins 1.609.1 Priority: Minor Reporter: ikedam Steps to reproduce: Install matrix-combinations-plugin Create a freestyle project Check This build is parameterized and add Matrix Combinations Parameter Set a name like combination Build with Parameters
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title David Katz commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json I am also seeing the same issue described here. However adding a trailing '/' on the webhook in bitbucket did not fix the issue for 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] [git-plugin] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Title: Message Title Mark Waite commented on JENKINS-20569 Re: Polling with excluded regions don't prevent job triggered Erik Shreve I don't understand the conflict between your quote from the log file and your statement about the job using JGit. The message invalid gitTool selection Default is the message I would expect to see when using command line git, yet you indicate that you switched from JGit to command line git. Could you double check that to confirm? If you find that is the case, please open another bug report, since this bug report is focused on the requirement that if an include region is defined, or an exclude region is defined, then the job should implicitly require a workspace for polling. 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-25724) Changes doesn't show unshelved files
Title: Message Title Michael Rose assigned an issue to Paul Allen I am starting to use the workflow plugin and came across the same problem. Jenkins / JENKINS-25724 Changes doesn't show unshelved files Change By: Michael Rose Assignee: PaulAllen 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 Nicolas De Loof commented on JENKINS-29066 Re: Git plugin dev version 2.3.6-0c1a59a8 builds on every poll proposed to revert on https://github.com/jenkinsci/git-plugin/pull/331 introduce a test to prevent such a regression in future will investigate further use of ls-remote in a separate branch 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] [workflow-plugin] (JENKINS-29095) build step is not documented
Title: Message Title Jochen Ulrich created an issue Jenkins / JENKINS-29095 build step is not documented Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 26/Jun/15 9:18 AM Priority: Minor Reporter: Jochen Ulrich It seems that the build step is not documented in the GitHub repository. The introduction text just mentions build other projects (workflow or freestyle) but the build step is neither used nor explained anywhere (tutorial etc.). Coming from the Build Flow plugin, I'd say it's an important step and should be documented. Add Comment
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-27233) Can't use in combination with rebuild and parameterized build trigger
Title: Message Title ikedam commented on JENKINS-27233 Re: Can't use in combination with rebuild and parameterized build trigger https://github.com/jenkinsci/matrix-combinations-plugin/pull/10 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-27233) Can't use in combination with rebuild and parameterized build trigger
Title: Message Title ikedam started work on JENKINS-27233 Change By: ikedam Status: Open InProgress 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-20569) Polling with excluded regions don't prevent job triggered
Title: Message Title Mark Waite edited a comment on JENKINS-20569 Re: Polling with excluded regions don't prevent job triggered [~eshreveti]Idon'tunderstandtheconflictbetweenyourquotefromthelogfileandyourstatementaboutthejobusingJGit.ThemessageinvalidgitToolselectionDefaultisthemessageIwouldexpecttoseewhenusingcommandlinegit,yetyouindicatethatyouswitchedfromJGittocommandlinegit.Couldyoudoublecheckthattoconfirm?Ifyoufindthatisthecase,pleaseopenanotherbugreport,sincethisbugreportisfocusedontherequirementthatifanincluderegionisdefined,oranexcluderegionisdefined,thenthejobshouldimplicitlyrequireaworkspaceforpolling. Idoublecheckedwithmy3jobsthatIusetoexperimentwiththisbugreport.IswitchedallthreeofthemtouseJGit,thencommittedfirsttoonlyprojectA,confirmedprojectAwastheonlyonebuilt.ThenIcommittedtoprojectBandconfirmedprojectBwastheonlyonebuilt.ThesameforprojectC,thenforthecombinationofAandB.Allbehavedasexpected.IhadenabledPollingusesworkspacesothattheyexclusionsandinclusionscouldberesolved. 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 be aware of JENKINS-21785 etc That was the issue that help us resolve the major SVN issues we were experiencing. Thanks for the link though. The difficulty involved updating our 1000+ jobs to include the appropriate credentials definitions, which were not a requirement in previous LTS releases. Most, but not all, of our jobs monitor SVN repositories but it was a bit tricky to ensure that all the affected jobs, and only those affected by this change, got updated. For future reference, any time that you include an invasive change like this in an LTS edition you probably should provide an easier way for users to upgrade their configurations instead of leaving them up to their own vices to hack around the changes. It would greatly reduce the pain of upgrading. I was referring to those in my earlier comment. Sorry - my misunderstanding. 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] [ci-game-plugin] (JENKINS-28974) introduce setting to disable blocking behaviour
Title: Message Title kurromat updated an issue Jenkins / JENKINS-28974 introduce setting to disable blocking behaviour Change By: kurromat Issue Type: Improvement Bug 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 edited a comment on JENKINS-29060 Re: Jenkins incorrectly reports timestamps are inconsistent bq.beawareofJENKINS-21785etcThatwastheissuethathelpusresolvethemajorSVNissueswewereexperiencing.Thanksforthelinkthough.Thedifficultyinvolvedupdatingour1000+jobstoincludetheappropriatecredentialsdefinitions,whichwerenotarequirementinpreviousLTSreleases.Most,butnotall,ofourjobsmonitorSVNrepositoriesbutitwasabittrickytoensurethatalltheaffectedjobs,andonlythoseaffectedbythischange,gotupdated. AndunfortunatelywegleanednobenefitfromtheimprovedsecurityasallofourJenkinsinstancesarerunbehindafirewallandoperatewithinaWindowsdomainsoonlytrustedsystemhaveaccesstoourkeyservices.Thenetresultforuswasalotofsuperfluousworkforlittletonogain. Forfuturereference,anytimethatyouincludeaninvasivechangelikethisinanLTSeditionyouprobablyshouldprovideaneasierwayforuserstoupgradetheirconfigurationsinsteadofleavingthemuptotheirownvicestohackaroundthechanges.Itwouldgreatlyreducethepainofupgrading.bq.Iwasreferringtothoseinmyearliercomment.Sorry-mymisunderstanding. 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 Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Yes, I did recently update. And I can confirm that git-plugin 2.3.2 produces correct HTML output. So the change Escape HTML generated into jelly pages with escape=true is mostly likely the cause for this. 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] [chrome-frame-plugin] (JENKINS-28614) Display bug on Weblogic with Google Chrome
Title: Message Title Nicolas BOHEAS commented on JENKINS-28614 Re: Display bug on Weblogic with Google Chrome Ok so the pb is about mimetype _javascript_ which is not executable in Chrome with Weblogic. To by pass it : add this in the web.xml of jenkins.war : mime-mapping extensionjs/extension mime-typeapplication/_javascript_/mime-type /mime-mapping and remove the checksum of this file by deleting thos 2 files : META-INF/JENKINS.RS and META-INF/JENKINS.RSA 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] [sauce-ondemand-plugin] (JENKINS-29054) Facing problems using sauce-connect-3.1.32.jar
Title: Message Title akash sharma commented on JENKINS-29054 Re: Facing problems using sauce-connect-3.1.32.jar The problem is resolved now. It was related to logs, I changed the path of Sauce Connect log and problem solved! Thanks, Ross! Regards, Akash 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-13086) Clone to directory named for repository
Title: Message Title
Sagayaraj David commented on JENKINS-13086
Re: Clone to directory named for repository
Doug and Mark are correct to add local directory as the name of the GIT repo itself. In fact, it would be nice have it configured in the global GIT configuration whether to checkout GIT into workspace or workspace\$ {GIT_REPO}
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-28912) CLONE - Job and Node naming convention
Title: Message Title Sagayaraj David updated an issue Jenkins / JENKINS-28912 CLONE - Job and Node naming convention Change By: Sagayaraj David Summary: CLONE-Job andNode naming naming convention 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-build-publish-plugin] (JENKINS-29098) Can not use multiple credentials per job
Title: Message Title Antoine Cotten commented on JENKINS-29098 Re: Can not use multiple credentials per job Should I create an issue there? 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-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title Daniel Spilker commented on JENKINS-29022 Re: Using configure block for scm results in extraneous NullSCM entry https://github.com/jenkinsci/job-dsl-plugin/pull/507 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-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title
Daniel Spilker commented on JENKINS-29022
Re: Using configure block for scm results in extraneous NullSCM entry
That is the expected behavior. When specifying attributes, the div operator will find the node with matching attributes or create a new one. I will update the docs, to point that out.
To fix your example, you can remove the existing scm element:
def p4ConfigureCoordinator( ) {
{ project -
project.remove(project / scm)
project / scm( class: 'org.jenkinsci.plugins.p4.PerforceScm' ) {
}
}
}
freeStyleJob('scratch-dsl') {
configure p4ConfigureCoordinator()
}
You can also change the value of the class attribute:
def p4ConfigureCoordinator( ) {
{ project -
(project / scm).attributes['class'] = 'org.jenkinsci.plugins.p4.PerforceScm'
}
}
freeStyleJob('scratch-dsl') {
configure p4ConfigureCoordinator()
}
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 Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin It looks like I was a bit too quick. When I click on Changes, I get a page Changes from Git with a summary table. That one is OK, i.e. the links to Jira issues are good. The page of an individual build that also lists the changes still shows escaped HTML, even with 2.3.2. I tested this with a fresh build, so I can't display information recorded with the previous (newer) git 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] [redmine-plugin] (JENKINS-23483) java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport()
Title: Message Title Alex Muthmann commented on JENKINS-23483 Re: java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport() Yes, you can find the request here: https://github.com/jenkinsci/redmine-plugin/pull/14 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-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28655 Make Docker Traceability tolerant against FingerprintCleanupThread Change By: Oleg Nenashev FingerprintCleanupThreadmaydeletefingerprintsifthereisnoreferencestojobs. *[DECLINED] Foroldcoresitisrequiredtocreateanartificialproject,whichwouldreferencebuildson-demand.Suchprojectwouldalsoallowtomanagefingerprintsfromitsinterface. * 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-build-publish-plugin] (JENKINS-29098) Can not use multiple credentials per job
Title: Message Title Carlos Sanchez commented on JENKINS-29098 Re: Can not use multiple credentials per job This is something that will have to be handled at the docker-commons 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] [git-parameter-plugin] (JENKINS-28597) GIT Parameter Plugin not using stored credentials
Title: Message Title Marcin Zajączkowski commented on JENKINS-28597 Re: GIT Parameter Plugin not using stored credentials I have the same problem. In Jenkins logs there is: Caused by: hudson.plugins.git.GitException: Command git -c core.askpass=true fetch --tags --progress http://my-stash/scm/foo/bar.git +refs/heads/*:refs/remotes/origin/* returned status code 128: stdout: stderr: fatal: Authentication failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:314) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:536) ... 70 more 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-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-28655
Make Docker Traceability tolerant against FingerprintCleanupThread
Change By:
Oleg Nenashev
FingerprintCleanupThreadmaydeletefingerprintsifthereisnoreferencestojobs.*[DECLINED]Foroldcoresitisrequiredtocreateanartificialproject,whichwouldreferencebuildson-demand.Suchprojectwouldalsoallowtomanagefingerprintsfromitsinterface.*Weshouldaddanextensionpoint,whichwouldallowtoprohibittheFingerprintdeletion Olddiscussionsummary:{quote}*Containerfingerprintsarenotprotectedfromfingerprintcleanupbythecoreduetothemissingbuildreferences*I'veneverseentheTraceabilityfingerprintscleanup,butitmayhappenaccordingtotheJenkinscorecode*FingerprintsCleanupThreadshouldrunrandomlywithonedayintervalaccordingtothecode{quote}
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-13086) Clone to directory named for repository
Title: Message Title
Sagayaraj David edited a comment on JENKINS-13086
Re: Clone to directory named for repository
DougandMarkarecorrecttoaddlocaldirectoryasthenameoftheGITrepoitself.Infact,itwouldbenicehaveitconfiguredintheglobalGITconfigurationwhethertocheckoutGITintoworkspaceorworkspace\$ \ {GIT_REPO \ }
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] [chrome-frame-plugin] (JENKINS-28614) Display bug on Weblogic with Google Chrome
Title: Message Title Nicolas BOHEAS assigned an issue to Nicolas BOHEAS Jenkins / JENKINS-28614 Display bug on Weblogic with Google Chrome Change By: Nicolas BOHEAS Assignee: NicolasBOHEAS 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.
