[JIRA] [instant-messaging] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
kutzi updated JENKINS-24507 Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled Change By: kutzi (30/Aug/14 9:48 AM) Component/s: jabber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
kutzi resolved JENKINS-24507 as Fixed Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled Change By: kutzi (30/Aug/14 9:50 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
kutzi commented on JENKINS-24507 Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled Just released a new version of the instant-messaging plugin with the fix. Thanks for bringing this issue to attention. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24401) Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone
Daniel Kozar edited a comment on JENKINS-24401 Changelists submit time in the Jenkins changelog is displayed in the Perforce servers timezone I think it might. The time zone of displayed timestamps is a configurable option in the Perforce Visual Client. The command line client, however, always displays timestamps in the server's time zone. I guess it depends on the habits of the users themselves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death No we did almost all of the tasks on slave jobs and the only job on master does not even run when this issue happen and does not have progress killing related command. I believe this might problably related to the last two LFS version. We plan to do a downgrade to 1.532.3 next Monday(we stayed on this version for months and didn't see this issue) to check this issue will be gone or not. Currently even if I delete this dll, it will be generated again automatically. And I don't find a hint which job might trigger it yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24516) git polling results exception because ssh is not found
Jesse Cheng created JENKINS-24516 git polling results exception because ssh is not found Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 30/Aug/14 4:32 PM Description: This happens after jenkins server is upgraded. Only some git repositories have this issue. jenkins git polling of other repositories on the same server works fine. Using strategy: Default poll Last Built Revision: Revision ca82a6dff817ec66f44342007202690a93763949 (refs/remotes/origin/master) git ls-remote -h ssh://username@host/repository.git master # timeout=10 FATAL: hudson.plugins.git.GitException: Command "git ls-remote -h ssh://username@host/repository.git master" returned status code 128: stdout: stderr: error: cannot run ssh: No such file or directory fatal: unable to fork hudson.util.IOException2: hudson.plugins.git.GitException: Command "git ls-remote -h ssh://username@host/repository.git master" returned status code 128: stdout: stderr: error: cannot run ssh: No such file or directory fatal: unable to fork at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:462) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:357) at hudson.scm.SCM.poll(SCM.java:374) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:477) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:506) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: hudson.plugins.git.GitException: Command "git ls-remote -h ssh://username@host/repository.git master" returned status code 128: stdout: stderr: error: cannot run ssh: No such file or directory fatal: unable to fork at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1195) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1119) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1110) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2004) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:495) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:460) ... 13 more Done. Took 0.78 sec Environment: Ubuntu 12.04, jenkins 1.565.1, git plugin 2.2.5, git client plugin 1.10.1 Project: Jenkins Priority: Major Reporter: Jesse Cheng This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression
Dominique Brice assigned JENKINS-2 to Dominique Brice Label display wrong when using operators in _expression_ Change By: Dominique Brice (30/Aug/14 5:23 PM) Assignee: DominiqueBrice This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radargun] (JENKINS-24496) Build-in start up scripts doesn't work on some instances
vjuranek commented on JENKINS-24496 Build-in start up scripts doesnt work on some instances @danielback thanks for a pointer! I wasn't aware about change This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression
Dominique Brice
commented on JENKINS-2
Label display wrong when using operators in _expression_
I had a look at Label.getTiedJobs(), Label.getTiedJobCount(), Computer.getTiedJobs(), and it seems fairly simple to get this behavior. Today the condition is based on Object equality between the Label (tag) itself and the Label assigned to a project. By changing this condition to a string matching, we get what's requested above:
private boolean isProjectTiedToLabel(AbstractProject?,? p) {
// original method of comparison. As a result would not see a project
// with constraint "macosjdk7" tied to label "jdk7"
// return (p != null) (this.equals(p.getAssignedLabel()));
String projectLabel = p.getAssignedLabelString();
return projectLabel != null projectLabel.contains(this.name);
}
Before proceeding further, I would like to discuss the functional implication of this change.
With this simple approach, any project related somehow to this label (or node) would be displayed, mixing together projects tied specifically to this label and those tied via elaborate conditions. One would have to go to each project's settings to see the exact reason why it's listed here. So a more complex display could be built to group such projects by categories, basically by distinct labels found (for instance: all "mastermacos" together, all "jdk7macos" together, all "macos" together", on the page related to "macos" label). That could become quite complex, so delegate to a plugin?
Now back to jenkins-core, we could keep it simple and indeed implement what's proposed above. The only functional change would then be that a Label (or Node) page would list all projects that have a restriction containing that tag (or slave), instead of being equal to it. Is that acceptable for the community?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression
Dominique Brice
edited a comment on JENKINS-2
Label display wrong when using operators in _expression_
I had a look at Label.getTiedJobs(), Label.getTiedJobCount(), Computer.getTiedJobs(), and it seems fairly simple to get this behavior. Today the condition is based on Object equality between the Label (tag) itself and the Label assigned to a project. By changing this condition to a string matching, we get what's requested above:
Label.java - new code
private boolean isProjectTiedToLabel(AbstractProject?,? p) {
// original method of comparison. As a result would not see a project
// with constraint "macosjdk7" tied to label "jdk7"
// return (p != null) (this.equals(p.getAssignedLabel()));
String projectLabel = p.getAssignedLabelString();
return projectLabel != null projectLabel.contains(this.name);
}
Before proceeding further, I would like to discuss the functional implication of this change.
With this simple approach, any project related somehow to this label (or node) would be displayed, mixing together projects tied specifically to this label and those tied via elaborate conditions. One would have to go to each project's settings to see the exact reason why it's listed here. So a more complex display could be built to group such projects by categories, basically by distinct labels found (for instance: all "mastermacos" together, all "jdk7macos" together, all "macos" together", on the page related to "macos" label). That could become quite complex, so delegate to a plugin?
Now back to jenkins-core, we could keep it simple and indeed implement what's proposed above. The only functional change would then be that a Label (or Node) page would list all projects that have a restriction containing that tag (or slave), instead of being equal to it. Is that acceptable for the community?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24510) AlwaysRun and NeverRun conditions are not supported by step.condition.SimpleCondition
Daniel Spilker commented on JENKINS-24510 AlwaysRun and NeverRun conditions are not supported by step.condition.SimpleCondition Thanks for the report, the next release will contain a fix. https://github.com/jenkinsci/job-dsl-plugin/pull/276 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamicparameter] (JENKINS-17422) Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter
Bruno P. Kinoshita commented on JENKINS-17422 Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter My previous comment here was a mistake. But by coincidence I just had the exact same issue in a testing instance. This instance is used for development of a plug-in, and has a bunch of plug-ins installed for checking compatibility. One of them being the dynamic parameter plug-in. Debugging the code it looks like Scriptler's scriptset receives a null list of scripts and throws that exception. The list of plug-ins is initialized from the scriptler.xml file. By renaming it to _scriptler.xml, and renaming the scripts folder to _scripts the problems seems fixed. Should I have more time I'll dig into this issue, but for now I'm moving forward to fix other issues in my plug-in HTH, Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
SCM/JIRA link daemon commented on JENKINS-24436 Bad URLs in view Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/CheckstylePluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/b8a7a0ef9a477789a60019be13cc2b866fe376da Log: JENKINS-24436 Added test case that exposes the bug. Seems that in Jenkins core the base URLs now already contain the view part. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24516) git polling results exception because ssh is not found
Mark Waite commented on JENKINS-24516 git polling results exception because ssh is not found That stack trace seems to indicate that those jobs cannot find "ssh" when "git" is trying to call it. We just had a bug report JENKINS-24467 which may be related. Was there a preceding job for the failing job? If so, was the preceding job executed on a different platform? Are you using the EnvInject plugin? If so, could you insert a step in the build which reports the value of the PATH environment variable and post its value here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24516) git polling results exception because ssh is not found
Mark Waite edited a comment on JENKINS-24516 git polling results exception because ssh is not found That stack trace seems to indicate that those jobs cannot find "ssh" when "git" is trying to call it. We just had a bug report JENKINS-24467 which may be related. Was there a preceding job for the failing job? If so, was the preceding job executed on a different platform? Are you using the EnvInject plugin? If so, could you insert a step in the build which reports the value of the PATH environment variable and post its value here? If you revert to git plugin 2.2.4 does it resolve the issue? The fix for JENKINS-22009 (as mentioned in JENKINS-24467) is first included in git plugin 2.2.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
Ulli Hafner commented on JENKINS-19310 Incorrect links in build history when view is defined inside a folder Caused JENKINS-24436. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
Ulli Hafner commented on JENKINS-24436 Bad URLs in view Since core 1.568. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24467) Possible regression of JENKINS-14321
Mark Waite reopened JENKINS-24467 Possible regression of JENKINS-14321 I'm reopening this because Rob's question seems very reasonable, and there is a hint that JENKINS-24516 may be the same issue, manifest in a different manner. Change By: Mark Waite (30/Aug/14 10:38 PM) Resolution: NotADefect Status: Resolved Reopened Assignee: NicolasDeLoof MarkWaite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24467) ssh not found by git because PATH has been unexpectedly changed
Mark Waite updated JENKINS-24467 ssh not found by git because PATH has been unexpectedly changed Change By: Mark Waite (30/Aug/14 10:40 PM) Summary: PossibleregressionofJENKINS-14321 sshnotfoundbygitbecausePATHhasbeenunexpectedlychanged This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
Mark Waite closed JENKINS-24112 as Fixed git-client does not support authentication proxy Change included in git client plugin 1.10.1 Change By: Mark Waite (30/Aug/14 10:47 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
Mark Waite reopened JENKINS-24112 git-client does not support authentication proxy Reopening to correct my comment. Change By: Mark Waite (30/Aug/14 10:48 PM) Resolution: Fixed Status: Closed Reopened Assignee: OHTAKETomohiro MarkWaite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite closed JENKINS-21469 as Wont Fix Change from git clone to init+fetch makes clone from local GIT mirror a lot slower Change By: Mark Waite (30/Aug/14 10:54 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23656) GitSCM checks wrong branch for changes
Mark Waite closed JENKINS-23656 as Duplicate GitSCM checks wrong branch for changes Alexander Link's changes which were included in git client plugin 1.10.1 provide a solution for this bug report. Refer to the "Branches to build" online help for the description of the various options for the refs/ syntax to construct precise branch names. This can also probably be solved by placing a ":" as the first character of the string in "Branches to build", then follow the colon with a regular _expression_ which matches the desired branch. The regular _expression_ syntax has been in the plugin for quite a while, but it is not mentioned in the online help. A future version of the git plugin will mention it in the online help. Change By: Mark Waite (30/Aug/14 10:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22017) Git client: NoClassDefFoundError
Mark Waite closed JENKINS-22017 as Not A Defect Git client: NoClassDefFoundError Change By: Mark Waite (30/Aug/14 10:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite closed JENKINS-20387 as Fixed git submodule update timeout value should be configurable per job Change By: Mark Waite (30/Aug/14 10:54 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-17629) Regression: git 1.6.2 not supported anymore (failing clone due to existing workspace dir)
Mark Waite closed JENKINS-17629 as Wont Fix Regression: git 1.6.2 not supported anymore (failing clone due to existing workspace dir) Change By: Mark Waite (30/Aug/14 10:57 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-20261) Cannot clone GIT repo from an https URL
Mark Waite closed JENKINS-20261 as Not A Defect Cannot clone GIT repo from an https URL Change By: Mark Waite (30/Aug/14 10:56 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-19593) git HTTP request failed in Jenkins
Mark Waite closed JENKINS-19593 as Not A Defect git HTTP request failed in Jenkins Change By: Mark Waite (30/Aug/14 10:56 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
Mark Waite resolved JENKINS-24112 as Fixed git-client does not support authentication proxy Change By: Mark Waite (30/Aug/14 10:58 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
SCM/JIRA link daemon commented on JENKINS-24436 Bad URLs in view Code changed in jenkins User: Ulli Hafner Path: analysis-core http://jenkins-ci.org/commit/analysis-suite-plugin/129182c8dbc042c638475b9829e819249c982fa0 Log: FIXED JENKINS-24436 Don't use AbstractItem.getUrl anymore when creating job links. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
SCM/JIRA link daemon resolved JENKINS-24436 as Fixed Bad URLs in view Change By: SCM/JIRA link daemon (30/Aug/14 11:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
SCM/JIRA link daemon commented on JENKINS-24436 Bad URLs in view Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/views/WarningsCountColumn.java src/main/resources/hudson/plugins/analysis/views/WarningsCountColumn/column.jelly http://jenkins-ci.org/commit/analysis-core-plugin/b5986361cfecb3220811fd63286f81d4dd83176c Log: FIXED JENKINS-24436 Don't use AbstractItem.getUrl anymore when creating job links. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
SCM/JIRA link daemon commented on JENKINS-24436 Bad URLs in view Code changed in jenkins User: Ulli Hafner Path: clean.sh http://jenkins-ci.org/commit/analysis-suite-plugin/e6e4d739a0552b21579f50835a84bb2441ad3963 Log: FIXED JENKINS-24436 Don't use AbstractItem.getUrl anymore when creating job links. Compare: https://github.com/jenkinsci/analysis-suite-plugin/compare/84ef2b4c31a4...e6e4d739a055 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view
SCM/JIRA link daemon commented on JENKINS-24436 Bad URLs in view Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/cobertura/CoverageColumn.java src/main/resources/hudson/plugins/cobertura/CoverageColumn/column.jelly http://jenkins-ci.org/commit/cobertura-plugin/7fd072ed198217974ef275d5662bf882f92147dd Log: JENKINS-24436 Don't use AbstractItem.getUrl when creating job links. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-24517) there is no api access to changes plugin
Alex Gray created JENKINS-24517 there is no api access to changes plugin Issue Type: Bug Affects Versions: current Assignee: wolfs Components: all-changes Created: 30/Aug/14 11:43 PM Description: I want to get a list of all changes for a programatically. I cannot hit: JENKINS/myjob/changes/api/json There is no way to get the information of JENKINS/myjob/changes without having to parse the raw HTML code of that page. Project: Jenkins Priority: Major Reporter: Alex Gray This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23334) Jenkins Frezees After Windows Security Patches Applied
Donald Morton commented on JENKINS-23334 Jenkins Frezees After Windows Security Patches Applied Please provide thread dumps, log output, and Windows system log information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
