[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Oliver Gondža commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden What is the point in having footer fixed-positioned, btw? This makes sense for breadcrumbs that contain often used navigation links which is not the case for footer. 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-16599) Master label settings are lost when configuring system settings
Stefan Landström commented on JENKINS-16599 Master label settings are lost when configuring system settings Seems like it might have been resolved in JENKINS-23966? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26317) CommitHookCause should extend SCMTriggerCause
Bradley Baetz created JENKINS-26317 CommitHookCause should extend SCMTriggerCause Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 07/Jan/15 6:27 AM Description: When a commit hook triggers a Jenkins build using the git-plugin's REST API, the cause of this is a CommitHookCause. However, this Cause doesn't extend SCMTriggerCause. This means that plugins which have an option to do things like ignore SCM-triggered changes (eg the sonar plugin) don't treat these triggers correctly. I'm happy to submit a pull request, but I'm not sure if there are any subtle/unwanted side effects from this. I saw a similar request (JENKINS-15823) for the gerrit jenkins plugin. (Note that some plugins will still not detect this - the sonar plugin uses "SCMTrigger.SCMTriggerCause.class.isInstance(cause)" and so is fine with subclasses, but eg the run condition plugin does a string comparison on the class name, so will still not see this properly) Project: Jenkins Priority: Minor Reporter: Bradley Baetz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-26316) Plaintext password shown in logged error string
Isaac A created JENKINS-26316 Plaintext password shown in logged error string Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 07/Jan/15 4:43 AM Description: In the polling log if the poll fails the command is printed out which includes the password in plaintext. Environment: mercurial-plugin 1.51 jenkins 1.580.1 Project: Jenkins Priority: Major Reporter: Isaac A 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] [virtualbox-plugin] (JENKINS-16631) Virtual machine cannot be added to a new node
Isaac A commented on JENKINS-16631 Virtual machine cannot be added to a new node With: Plugin 0.7 VBox 4.3.20 Jenkins ver. 1.580.1 With a Win7x64 host and guest I have the same problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26310) notifyCommit URL responds with "No Git consumers using SCM API"
Mark Waite resolved JENKINS-26310 as Not A Defect notifyCommit URL responds with "No Git consumers using SCM API" Per the commit message, that is an expected message. You can confirm that the notifyCommit had the expected result by reviewing the git polling log immediately after a notifyCommit. It should report the polling time in the polling log and that time should be very near the time of the poll. Change By: Mark Waite (07/Jan/15 3:52 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds
Jackey Cheung edited a comment on JENKINS-26280 Missing "Integrate Branch" from feature branch builds Not sure if I get it right, are you concerning about svn:externals? If it's the repo itself, I've just created a fresh repo, make some directories in it (src, build, etc.), and put them all to trunk. Then I created the feature branch from within the Jenkins plugin. Inside "Feature Branches" of the master job, I see this: "Detected repository layout: single project layout". 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] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds
Jackey Cheung commented on JENKINS-26280 Missing "Integrate Branch" from feature branch builds Not sure if I get it right, are you concerning about svn:externals? If it's the repo itself, I've just created a fresh repo, make some directories in it (src, build, etc.), and put them all to trunk. Then I created the feature branch from within the Jenkins plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin can't handle property references in repository URLs when polling
Ron MacNeil updated JENKINS-26315 Git plugin can't handle property references in repository URLs when polling Change By: Ron MacNeil (07/Jan/15 3:25 AM) Summary: Git plugin can't handle repository URLs containing property references in repository URLs when polling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin can't handle repository URLs containing property references when polling
Ron MacNeil updated JENKINS-26315 Git plugin can't handle repository URLs containing property references when polling Change By: Ron MacNeil (07/Jan/15 3:24 AM) Summary: Git plugin can't handle repository URLs containing property reference(s) references when polling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin can't handle repository URLs containing property reference(s) when polling
Ron MacNeil
updated JENKINS-26315
Git plugin can't handle repository URLs containing property reference(s) when polling
Change By:
Ron MacNeil
(07/Jan/15 3:21 AM)
Summary:
Git plugin
incorrectly adds trailing slash to
can't handle
repository URLs containing property reference(s) when polling
Description:
We use a global property called "RepoRoot" to specify where our Git repositories live, so our repository URL's look similar to:${RepoRoot}/RepoA.git${RepoRoot}/RepoB.git
These resolve correctly
This works fine
when
the job
jobs
actually
runs, but
run:{code}...Fetching changes from the remote Git repository > git.exe config remote.origin.url https://github.com/Foo/RepoA.git # timeout=10Cleaning workspace > git.exe rev-parse --verify HEAD # timeout=10Resetting working tree > git.exe reset --hard # timeout=10 > git.exe clean -fdx # timeout=10Fetching upstream changes from https://github.com/Foo/RepoA.git > git.exe --version # timeout=10using .gitcredentials to set credentials > git.exe config --local credential.helper store --file=\"C:\Users\FOO\AppData\Local\Temp\git6742298409525835661.credentials\" # timeout=10 > git.exe -c core.askpass=true fetch --tags --progress https://github.com/Foo/RepoA.git +refs/heads/*:refs/remotes/origin/*...{code}But
we're seeing errors similar to the following in our polling log:{code}Fetching upstream changes from ${RepoRoot}/RepoA.git > git.exe --version # timeout=10 > git.exe -c core.askpass=true fetch --tags --progress ${RepoRoot}/RepoA.git +refs/heads/*:refs/remotes/origin/*FATAL: hudson.plugins.git.GitException: Failed to fetch from ${RepoRoot}/RepoA.githudson.util.IOException2: hudson.plugins.git.GitException: Failed to fetch from ${RepoRoot}/RepoA.git at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:518) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at org.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:92) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1462) at hudson.model.AbstractProject._poll(AbstractProject.java:1433) at hudson.model.AbstractProject.poll(AbstractProject.java:1344) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.plugins.git.GitException: Failed to fetch from ${RepoRoot}/RepoA.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:695) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:598) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:516) ... 16 moreCaused by: hudson.plugins.git.GitException: Command "git.exe -c core.askpass=true fetch --tags --progress ${RepoRoot}/RepoA.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: repository 'https://github.com/Foo/RepoA.git/' not found at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:693) ... 18 moreDone. Took 2.3 sec{code}If I hard-code the repo root rather than use the global property reference, polling
works
starts working
.
So
From the polling log,
it
seems
appears
as though
there's a difference in
the
handling of repository URLs between
polling
for changes and actually pulling changes during job executi
[JIRA] [git-plugin] (JENKINS-26315) Git plugin incorrectly adds trailing slash to repository URLs containing property reference(s) when polling
Ron MacNeil
updated JENKINS-26315
Git plugin incorrectly adds trailing slash to repository URLs containing property reference(s) when polling
Change By:
Ron MacNeil
(07/Jan/15 3:10 AM)
Description:
We use a global property called "RepoRoot" to specify where our Git repositories live, so our repository URL's look similar to:${RepoRoot}/RepoA.git${RepoRoot}/RepoB.gitThese resolve correctly when the job actually runs, but we're seeing errors similar to the following in our polling log:{code}Fetching upstream changes from ${RepoRoot}/RepoA.git > git.exe --version # timeout=10 > git.exe -c core.askpass=true fetch --tags --progress ${RepoRoot}/RepoA.git +refs/heads/*:refs/remotes/origin/*FATAL: hudson.plugins.git.GitException: Failed to fetch from ${RepoRoot}/RepoA.githudson.util.IOException2: hudson.plugins.git.GitException: Failed to fetch from ${RepoRoot}/RepoA.git at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:518) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at org.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:92) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1462) at hudson.model.AbstractProject._poll(AbstractProject.java:1433) at hudson.model.AbstractProject.poll(AbstractProject.java:1344) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.plugins.git.GitException: Failed to fetch from ${RepoRoot}/RepoA.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:695) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:598) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:516) ... 16 moreCaused by: hudson.plugins.git.GitException: Command "git.exe -c core.askpass=true fetch --tags --progress ${RepoRoot}/RepoA.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: repository 'https://github.com/Foo/RepoA.git/' not found at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:693) ... 18 moreDone. Took 2.3 sec{code}
If I hard-code the repo root rather than use the global property reference, polling works. So it seems as though there's a difference in the handling of repository URLs between polling for changes and actually pulling changes during job execution.
Thanks folks, love your work.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26315) Git plugin incorrectly adds trailing slash to repository URLs containing property reference(s) when polling
Ron MacNeil
updated JENKINS-26315
Git plugin incorrectly adds trailing slash to repository URLs containing property reference(s) when polling
Change By:
Ron MacNeil
(07/Jan/15 3:07 AM)
Summary:
Git plugin incorrectly adds trailing slash to repository
URL when it ends with
URLs containing
property reference
(s) when polling
Description:
We use
a
global
properties
property called "RepoRoot"
to specify
:Where
where
our Git repositories live,
so our repository URL's look similar to:
${RepoRoot}
Whether or not they have a "
/RepoA
.git
" suffix,
${
RepoSuffix
RepoRoot
}
/RepoB.git
So our repository URL
These resolve correctly when the job actually runs, but we
'
s look
re seeing errors
similar to
the following in our polling log
:
{code}Fetching upstream changes from
${RepoRoot}/RepoA
.git > git.exe --version # timeout=10 > git.exe -c core.askpass=true fetch --tags --progress
${
RepoSuffix
RepoRoot
}
/RepoA.git +refs/heads/*:refs/remotes/origin/*
FATAL: hudson.plugins.git.GitException: Failed to fetch from
${RepoRoot}/
RepoB
RepoA.githudson.util.IOException2: hudson.plugins.git.GitException: Failed to fetch from
${
RepoSuffix
RepoRoot
}
/RepoA.git
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:518)
at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380)
When
at hudson.scm.SCM.poll(SCM.java:397) at org.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:92) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1462) at hudson.model.AbstractProject._poll(AbstractProject.java:1433) at hudson.model.AbstractProject.poll(AbstractProject.java:1344) at hudson.triggers.SCMTrigger
$
Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.plugins.git.GitException: Failed to fetch from $
{
RepoSuffix
RepoRoot
}
is set to "
/RepoA
.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:695) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:598) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:516) ... 16 moreCaused by: hudson.plugins.git.GitException: Command
"
, we're seeing errors similar to the following in our polling log, note the incorrectly
git.exe
-
added trailing slash
c core.askpass=true fetch --tags --progress ${RepoRoot}/RepoA.git +refs/heads/*
:
refs/remotes/origin/*" returned status code 128:
stdout:
stderr:
fatal:
Authentication failed for
repository
'https://github.com/Foo/RepoA.git/'
not found
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457)
I'm sure auto-adding the trailing slash was well-intentioned, but it's a case of trying to make the software too clever for its own good
at org
.
At the very least, there needs to be an option to disable this behaviour
jenkinsci
.
plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:693) ... 18 moreDone. Took 2.3 sec{code}
Thanks folks, love your work.
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
--
[JIRA] [git-plugin] (JENKINS-26315) Git plugin incorrectly adds trailing slash to repository URL when it ends with property reference
Ron MacNeil
created JENKINS-26315
Git plugin incorrectly adds trailing slash to repository URL when it ends with property reference
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
07/Jan/15 2:47 AM
Description:
We use global properties to specify:
Where our Git repositories live, ${RepoRoot}
Whether or not they have a ".git" suffix, ${RepoSuffix}
So our repository URL's look similar to:
${RepoRoot}/RepoA${RepoSuffix}
${RepoRoot}/RepoB${RepoSuffix}
When ${RepoSuffix} is set to ".git", we're seeing errors similar to the following in our polling log, note the incorrectly-added trailing slash:
fatal: Authentication failed for 'https://github.com/Foo/RepoA.git/'
I'm sure auto-adding the trailing slash was well-intentioned, but it's a case of trying to make the software too clever for its own good. At the very least, there needs to be an option to disable this behaviour.
Thanks folks, love your work.
Project:
Jenkins
Priority:
Minor
Reporter:
Ron MacNeil
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Patrick Wong
edited a comment on JENKINS-23232
SEVERE: I/O error in channel Chunked connection
I get the same issue with the following steps:
Client machine is CentOS 6.5 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
Jenkins VM is CentOS 7 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
port 8080 forwarded to host machine port 8081
Vagrant basebox is jayunit/centos7 with Oracle Virtualbox provider
jenkins-cli.jar comes from wget localhost:8081/jnlpjars/jenkins-cli.jar and it is then renamed to have the version string, e.g. mv jenkins-cli.jar jenkins-cli-1.580.2.jar
Command is {{java -jar jenkins-cli-1.580.2.jar -s http://localhost:8081/ list-plugins}}
Have tried with both Jenkins 1.580.2 stable and 1.596 latest.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Patrick Wong
edited a comment on JENKINS-23232
SEVERE: I/O error in channel Chunked connection
I get the same issue with the following steps:
Client machine is CentOS 6.5 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
Jenkins VM is CentOS 7 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
port 8080 forwarded to host machine port 8081
Vagrant basebox is jayunit/centos7 with Oracle Virtualbox provider
jenkins-cli.jar comes from wget localhost:8081/jnlpjars/jenkins-cli.jar and it is then renamed to have the version string, e.g. mv jenkins-cli.jar jenkins-cli-1.580.2.jar
Command is {{ "java -jar jenkins-cli-1.580.2.jar -s http://localhost:8081/ list-plugins" }}
Have tried with both Jenkins 1.580.2 stable and 1.596 latest.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Patrick Wong
edited a comment on JENKINS-23232
SEVERE: I/O error in channel Chunked connection
I get the same issue with the following steps:
Client machine is CentOS 6.5 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
Jenkins VM is CentOS 7 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
port 8080 forwarded to host machine port 8081
Vagrant basebox is jayunit/centos7 with Oracle Virtualbox provider
jenkins-cli.jar comes from wget localhost:8081/jnlpjars/jenkins-cli.jar and it is then renamed to have the version string, e.g. mv jenkins-cli.jar jenkins-cli-1.580.2.jar
Command is {{java -jar jenkins-cli-1.580.2.jar -s http://localhost:8081/ list-plugins}}
Have tried with both Jenkins 1.580.2 stable and 1.596 latest.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Patrick Wong
commented on JENKINS-23232
SEVERE: I/O error in channel Chunked connection
I get the same issue with the following steps:
Client machine is CentOS 6.5 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
Jenkins VM is CentOS 7 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
port 8080 forwarded to host machine port 8081
Vagrant basebox is jayunit/centos7 with Oracle Virtualbox provider
jenkins-cli.jar comes from wget localhost:8081/jnlpjars/jenkins-cli.jar and it is then renamed to have the version string, e.g. mv jenkins-cli.jar jenkins-cli-1.580.2.jar
Command is {{java -jar jenkins-cli-1.580.2.jar -s http://localhost:8081/ list-plugins}}
Have tried with both Jenkins 1.580.2 stable and 1.596 latest.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Patrick Wong
edited a comment on JENKINS-23232
SEVERE: I/O error in channel Chunked connection
I get the same issue with the following steps:
Client machine is CentOS 6.5 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
Jenkins VM is CentOS 7 with Java 1.7.0-b71 (from CentOS package java-1.7.0-openjdk-devel)
port 8080 forwarded to host machine port 8081
Vagrant basebox is jayunit/centos7 with Oracle Virtualbox provider
jenkins-cli.jar comes from wget localhost:8081/jnlpjars/jenkins-cli.jar and it is then renamed to have the version string, e.g. mv jenkins-cli.jar jenkins-cli-1.580.2.jar
Command is {{java -jar jenkins-cli-1.580.2.jar -s http://localhost:8081/ list-plugins}}
Have tried with both Jenkins 1.580.2 stable and 1.596 latest.
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-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Igor Koyfman commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden This also happens on other pages with buttons at the bottom, e.g. the system configuration page, the plugin installation page, etc. The zoom in/zoom out workaround works for all. The CSS workaround with the Simple Theme Plugin mentioned above didn't work. 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] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing "Integrate Branch" from feature branch builds I did some investigation and I found that Integration Action does not work if the feature branch job has more that one Subversion modules. If the job that builds your feature branch has more than one module. Then it is the cause of this issue. I just wanted to confirm that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Daniel Beck
updated JENKINS-26312
Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Workaround would probably be to define
#footer-container { position: fixed !important; }
using Simple Theme Plugin (untested). Alternatively, remove (display:none) a bunch of crap from the footer to reduce its height.
Due to presence of workaround, reducing issue priority. Rewrote issue title to reflect findings.
Assigning tentatively to tfennelly, who appears to have introduced this issue.
Change By:
Daniel Beck
(07/Jan/15 1:53 AM)
Summary:
No save button on the job configuration page
Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Environment:
Jenkins 1.596
Priority:
Major
Critical
Labels:
user-experience
Assignee:
Tom FENNELLY
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-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Daniel Beck updated JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Change By: Daniel Beck (07/Jan/15 1:54 AM) Priority: Critical Minor 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-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (07/Jan/15 1:49 AM) Priority: Blocker Major 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-26312) No save button on the job configuration page
Daniel Beck commented on JENKINS-26312 No save button on the job configuration page Confirmed. For me, Save/Apply buttons are only partially hidden by the footer bar, but that's because I don't have SCM Sync Config Plugin installed. Caused by https://github.com/jenkinsci/jenkins/commit/3e9cdcbc8527d6ee2be143aad3365df8fcd02c74 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-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I zoomed out the browser until it got so small the job did fit on one screen, and the buttons did show up then. So I guess that's a workaround. P.S. Even better, if I scroll to the bottom of the page and zoom in and then zoom out, then the buttons show up even if the scroll bars are still there. 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-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I zoomed out the browser until it got so small the job did fit on one screen, and the buttons did show up then. So I guess that's a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Nathan Smith created JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 07/Jan/15 1:43 AM Description: Use a Tag in the Branch Specifier. Polling on the remote repo will occur. It will run git ls-remote -h MY_REMOTE MY_TAG This will result in nothing returned from the remote repository. git ls-remote has a --tags option which will return the SHA of the Tag. Polling is enabled because the Job also checkouts an SVN repository using the Jenkins Multiple SCMs plugin which doesn't refer to a tag. Environment: Jenkins 1.584 Jenkins Git Plugin 2.3.1 Jenkins Multiple SCMs plugin 0.3 Project: Jenkins Priority: Major Reporter: Nathan Smith 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-26312) No save button on the job configuration page
Igor Koyfman commented on JENKINS-26312 No save button on the job configuration page I zoomed out the screen until it got so small the job did fit on one screen, and the buttons did show up then. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I uninstalled the Simple Theme Plugin, and I'm using Chrome. I don't have any jobs that fit on one screen. Also, I checked in IE and there is no Save or Apply button there either. I don't have Firefox. 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-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (07/Jan/15 1:33 AM) Attachment: JenkinsNoButton.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman commented on JENKINS-26312 No save button on the job configuration page I uninstalled the Simple Theme Plugin, and I'm using Chrome. I don't have any jobs that fit on one screen. 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] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds
Jackey Cheung commented on JENKINS-26280 Missing "Integrate Branch" from feature branch builds There is only one branch. History: I've created a dev (not dev1) branch back then, and couldn't see the Integrate button. So I've deleted it, and do it again, created the dev1 branch. 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-core-plugin] (JENKINS-26235) Tab customizations
Steve Springett commented on JENKINS-26235 Tab customizations I looked into what it would take to make the labels configurable and it appears to be more complex than I thought. When the labels are rendered, it's done so when the AnnotationContainer is of type JavaProject, not TabDetail. JavaProject is constructed by BuildResult so it appears the custom label definitions would need to be defined here. Replacing the hard-coded strings in main.jelly is simple enough. The Dependency-Check Jenkins plugin which uses analysis-core, already overrides TabDetail. But by the time it's called, the text to be rendered for the tabs has already been determined. 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-5135) Adopt everywhere
SCM/JIRA link daemon commented on JENKINS-5135 Adopt everywhere Code changed in jenkins User: Mark Waite Path: src/main/resources/hudson/plugins/git/ChangelogToBranchOptions/config.jelly src/main/resources/hudson/plugins/git/GitBranchTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/digest.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/index.jelly src/main/resources/hudson/plugins/git/GitPublisher/config.jelly src/main/resources/hudson/plugins/git/GitRevisionBuildParameters/config.jelly src/main/resources/hudson/plugins/git/GitRevisionTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitSCM/config.jelly src/main/resources/hudson/plugins/git/GitSCM/global.jelly src/main/resources/hudson/plugins/git/GitSCM/project-changes.jelly src/main/resources/hudson/plugins/git/GitTagAction/tagForm.jelly src/main/resources/hudson/plugins/git/UserMergeOptions/config.jelly src/main/resources/hudson/plugins/git/browser/AssemblaWeb/config.jelly src/main/resources/hudson/plugins/git/browser/BitbucketWeb/config.jelly src/main/resources/hudson/plugins/git/browser/CGit/config.jelly src/main/resources/hudson/plugins/git/browser/FisheyeGitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitBlitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitLab/config.jelly src/main/resources/hudson/plugins/git/browser/GitList/config.jelly src/main/resources/hudson/plugins/git/browser/GitWeb/config.jelly src/main/resources/hudson/plugins/git/browser/GithubWeb/config.jelly src/main/resources/hudson/plugins/git/browser/Gitiles/config.jelly src/main/resources/hudson/plugins/git/browser/GitoriousWeb/config.jelly src/main/resources/hudson/plugins/git/browser/KilnGit/config.jelly src/main/resources/hudson/plugins/git/browser/Phabricator/config.jelly src/main/resources/hudson/plugins/git/browser/RedmineWeb/config.jelly src/main/resources/hudson/plugins/git/browser/RhodeCode/config.jelly src/main/resources/hudson/plugins/git/browser/Stash/config.jelly src/main/resources/hudson/plugins/git/browser/ViewGitWeb/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPath/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPaths/config.jelly src/main/resources/hudson/plugins/git/util/BuildData/index.jelly src/main/resources/hudson/plugins/git/util/BuildData/summary.jelly src/main/resources/index.jelly src/main/resources/jenkins/plugins/git/GitSCMSource/config-detail.jelly http://jenkins-ci.org/commit/git-plugin/07defeb47056a90a591d21c18b3fc77691527d0c Log: Escape jelly output by default - see JENKINS-5135 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-5135) Adopt everywhere
SCM/JIRA link daemon commented on JENKINS-5135 Adopt everywhere Code changed in jenkins User: Mark Waite Path: src/main/resources/hudson/plugins/git/ChangelogToBranchOptions/config.jelly src/main/resources/hudson/plugins/git/GitBranchTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/digest.jelly src/main/resources/hudson/plugins/git/GitChangeSetList/index.jelly src/main/resources/hudson/plugins/git/GitPublisher/config.jelly src/main/resources/hudson/plugins/git/GitRevisionBuildParameters/config.jelly src/main/resources/hudson/plugins/git/GitRevisionTokenMacro/help.jelly src/main/resources/hudson/plugins/git/GitSCM/config.jelly src/main/resources/hudson/plugins/git/GitSCM/global.jelly src/main/resources/hudson/plugins/git/GitSCM/project-changes.jelly src/main/resources/hudson/plugins/git/GitTagAction/tagForm.jelly src/main/resources/hudson/plugins/git/UserMergeOptions/config.jelly src/main/resources/hudson/plugins/git/browser/AssemblaWeb/config.jelly src/main/resources/hudson/plugins/git/browser/BitbucketWeb/config.jelly src/main/resources/hudson/plugins/git/browser/CGit/config.jelly src/main/resources/hudson/plugins/git/browser/FisheyeGitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitBlitRepositoryBrowser/config.jelly src/main/resources/hudson/plugins/git/browser/GitLab/config.jelly src/main/resources/hudson/plugins/git/browser/GitList/config.jelly src/main/resources/hudson/plugins/git/browser/GitWeb/config.jelly src/main/resources/hudson/plugins/git/browser/GithubWeb/config.jelly src/main/resources/hudson/plugins/git/browser/Gitiles/config.jelly src/main/resources/hudson/plugins/git/browser/GitoriousWeb/config.jelly src/main/resources/hudson/plugins/git/browser/KilnGit/config.jelly src/main/resources/hudson/plugins/git/browser/Phabricator/config.jelly src/main/resources/hudson/plugins/git/browser/RedmineWeb/config.jelly src/main/resources/hudson/plugins/git/browser/RhodeCode/config.jelly src/main/resources/hudson/plugins/git/browser/Stash/config.jelly src/main/resources/hudson/plugins/git/browser/ViewGitWeb/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPath/config.jelly src/main/resources/hudson/plugins/git/extensions/impl/SparseCheckoutPaths/config.jelly src/main/resources/hudson/plugins/git/util/BuildData/index.jelly src/main/resources/hudson/plugins/git/util/BuildData/summary.jelly src/main/resources/index.jelly src/main/resources/jenkins/plugins/git/GitSCMSource/config-detail.jelly http://jenkins-ci.org/commit/git-plugin/f297338702395e53f2f4db8d9070de15bc770890 Log: Escape jelly output by default - see JENKINS-5135 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] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8
Daniel Spilker commented on JENKINS-25643 Not able to use example build.gradle file with Java 8 Will be fixed in the next release. https://github.com/jenkinsci/gradle-jpi-plugin/pull/37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl commented on JENKINS-18567 Add Watch button to Job summary screen You don't configure the job's notifications, it only subscribes you. If you are anonymous, then it doesn't allow you to watch a job. I don't want to have a separate UI for this vs. the normal configuration. so maybe I can set some variable to remove those items in the watch area. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Kanstantsin Shautsou commented on JENKINS-18567 Add Watch button to Job summary screen My idea was to allow subscribe yourself, not allow somebody to configure job's notifications. If you are anonymous, then doesn't allow to subscribe. (developers, recipient list, culprits...) - should not be available 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] [workflow-plugin] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Jesse Glick assigned JENKINS-26313 to Kohsuke Kawaguchi Workflow script fails if CPS-transformed methods are called from constructors I wonder if this is even fixable. Change By: Jesse Glick (06/Jan/15 10:35 PM) Assignee: Jesse Glick Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Alexander Bertram commented on JENKINS-26313 Workflow script fails if CPS-transformed methods are called from constructors There is a workaround: annotate sqr() with @com.cloudbees.groovy.cps.NonCPS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Alexander Bertram
created JENKINS-26313
Workflow script fails if CPS-transformed methods are called from constructors
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
06/Jan/15 9:53 PM
Description:
When a CPS-transformed method is called from a Groovy class constructor, the CpsCallableInvocation is not caught and aborts the build.
Here is a minimally-reproducible test case:
class B {
static def sqr(x) { x*x }
}
class A {
A(y) {
B.sqr(y)
}
}
def a = new A(42)
The resulting CpsCallableInvocation is not caught and the build aborts:
Running: End of Workflow
com.cloudbees.groovy.cps.impl.CpsCallableInvocation
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71)
at org.codehaus.groovy.runtime.callsite.ConstructorSite.callConstructor(ConstructorSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:54)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:198)
at B.sqr(WorkflowScript)
at B$sqr.call(Unknown Source)
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:116)
at A.(WorkflowScript:11)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:54)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.constructorCall(DefaultInvoker.java:20)
at WorkflowScript.run(WorkflowScript:15)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:90)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:76)
at sun.reflect.GeneratedMethodAccessor498.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:267)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:70)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:176)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:174)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutor
[JIRA] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookie to be saved when configuring trend graphs
Ulli Hafner commented on JENKINS-25917 Spaces in URL (from project name or view) cause invalid cookie to be saved when configuring trend graphs I see. Since you already found the problematic statement: are you interested in providing a fix as pull request? I currently quite busy with other work... 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-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()
kutzi commented on JENKINS-6560 Plugin should use project.getFullDisplayName() instead of project.getName() Should be fixed in version 1.32 of the instant-messaging plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26307) CPS Groovy collection.find() returns Boolean
Alexander Bertram commented on JENKINS-26307 CPS Groovy collection.find() returns Boolean Think I beat you to it by a few hours https://issues.jenkins-ci.org/browse/JENKINS-26300 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] [findbugs-plugin] (JENKINS-25977) Make FindBugsPublisher a SimpleBuildStep
Jesse Glick commented on JENKINS-25977 Make FindBugsPublisher a SimpleBuildStep should the existing publisher use the new parent class? The existing publisher can just implement SimpleBuildStep. Can I use a SimpleBuildStep also in Maven jobs, or is the MavenReporter type still required? I do not know much about MavenReporter, and anyway it seems to be unused in findbugs-plugin. If there is a BuildStep registered as an extension and it happens to implement SimpleBuildStep, it will be usable from a workflow, otherwise not. Is there already an example around that I can look at? https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md#build-steps-and-post-build-actions Is such a change transparent for users that have existing publishers in their configuration Sure, you should not need to change the name of the class. 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-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()
SCM/JIRA link daemon commented on JENKINS-6560 Plugin should use project.getFullDisplayName() instead of project.getName() Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/im/bot/CurrentlyBuildingCommand.java http://jenkins-ci.org/commit/instant-messaging-plugin/4ca5e97cfdd01ab23e7301f66cfa3471f8a17d3e Log: Use FullDisplayName for 'cb' command, too, if available JENKINS-6560 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26307) CPS Groovy collection.find() returns Boolean
Jesse Glick assigned JENKINS-26307 to Kohsuke Kawaguchi CPS Groovy collection.find() returns Boolean Change By: Jesse Glick (06/Jan/15 8:43 PM) Assignee: Jesse Glick Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19031) com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1
SCM/JIRA link daemon commented on JENKINS-19031 com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1 Code changed in jenkins User: Christoph Kutzinski Path: pom.xml http://jenkins-ci.org/commit/instant-messaging-parent-plugin/3c2666d51c523325621b025c4971232143a8b1f0 Log: Update to Jenkins 1.565 because of JENKINS-19031 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] [mstest-plugin] (JENKINS-19360) Missing classname when used with reports generated from VSTest.Console.exe
SCM/JIRA link daemon commented on JENKINS-19360 Missing classname when used with reports generated from VSTest.Console.exe Code changed in jenkins User: Ivo Bellin Salarin Path: pom.xml src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java src/test/resources/hudson/plugins/mstest/mstest_vs_2012.trx src/test/resources/hudson/plugins/mstest/mstest_vs_2012.xml http://jenkins-ci.org/commit/mstest-plugin/0f2aa07d0fa905819d21997b2595eec54c5fdc88 Log: Merge pull request #3 from iansul/master JENKINS-19360 - Fix for mstest problems with trx files genereated by vstest.console.exe Compare: https://github.com/jenkinsci/mstest-plugin/compare/e11a4dc2471a...0f2aa07d0fa9 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-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
SCM/JIRA link daemon commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java test/src/test/java/hudson/model/RunMapTest.java http://jenkins-ci.org/commit/jenkins/14d676bb15dbf8ddc3208bd8a80033e831756d49 Log: [FIXED JENKINS-25788] RunMap.remove was always returning false, even when the Run was in fact removed. (cherry picked from commit ce94579c50621990517c86120236ee9a1d0490da) Conflicts: changelog.html 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-25989) No wrap up(not in multiple lines) of too long list of slaves at label page
SCM/JIRA link daemon commented on JENKINS-25989 No wrap up(not in multiple lines) of too long list of slaves at label page Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Computer/index.jelly core/src/main/resources/hudson/model/Label/index.jelly http://jenkins-ci.org/commit/jenkins/2172503f3ce2acf1dd9fb95891e41441bff5197f Log: [FIXED JENKINS-25989] Allow breaking label and node lists (cherry picked from commit 2820e59202975ce8ad302e4a0b0e17c07e4c40cf) 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-24272) jnlp slaves fail to reconnect when master is restarted
SCM/JIRA link daemon commented on JENKINS-24272 jnlp slaves fail to reconnect when master is restarted Code changed in jenkins User: Richard Mortimer Path: core/src/main/java/jenkins/slaves/restarter/JnlpSlaveRestarterInstaller.java http://jenkins-ci.org/commit/jenkins/ea6baf9a103b841ec99dd1c2a9aac85fe6d8d29f Log: [FIXES JENKINS-24272] jnlp slaves fail to reconnect when master is restarted During master restart only attempt to reconnect the slave after the master has finished restarting. (cherry picked from commit 48e19c58f9e2caa998d0942417d58679f5ce47f0) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-26251) Groovy Postbuild plugin shows error in project configuration
Marlen Ablaev commented on JENKINS-26251 Groovy Postbuild plugin shows error in project configuration Yes. 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] [redmine-plugin] (JENKINS-8760) detail information for commit messages are missed in changes
Roman Pickl commented on JENKINS-8760 detail information for commit messages are missed in changes if I understand Larry's comment at https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin correctly i came up with a fix for this https://github.com/jenkinsci/redmine-plugin/pull/17 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-26312) No save button on the job configuration page
Daniel Beck commented on JENKINS-26312 No save button on the job configuration page Is the Simple Theme Plugin installed? If so, disable it, or remove the custom CSS/JS assignments from global configuration. Disable Greasemonkey or any similar browser-specific custom JS/CSS insertions. Please provide a screen shot showing the full browser window including scroll bar. Does this only occur on long job configuration pages that exceed the window height (i.e. where scrolling is needed)? 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-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (06/Jan/15 8:01 PM) Description: In 1.596 there is no save button on the job configuration page. Cannot modify any jobs. Reverting to 1.594 got the button back. 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] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert
updated JENKINS-26308
LoadRunner Scenario Always Times Out
Change By:
Connor Gilbert
(06/Jan/15 7:59 PM)
Description:
Simple Loadrunner scenario always times out when ran through Jenkins. The test runs fine when started within Loadrunner. Have tried on multiple machines in the same environment and found this issue. Though on my own personal machine it works fine.LoadRunner Settings are set to default:Controller Polling Interval - 30Scenario Execution Timeout - 10Errors To Ignore - noneBelow is the console output
(notice the timeout occurring at 29 seconds. This is consistent along all attempts)
:Building in workspace C:\Program Files (x86)\Jenkins\jobs\Testing\workspace[workspace] $ "C:\Program Files (x86)\Jenkins\jobs\Testing\workspace\HpToolsLauncher.exe" -paramfile props05012015172238713.txt"Started..."1 tests found:C:\Users\*\Downloads\Scenario1.lrs05/01/2015 17:22:39 Running: C:\Users\\Downloads\Scenario1.lrsCleaning up the environment...Preparing scenario C:\Users\\Downloads\Scenario1.lrs for execution.Load Generator localhost connectedStarting scenario...Error: Scenario Execution timeout (29 seconds) passed.Error: Scenario Execution timeout ({0} seconds) passed.Scenario C:\Users\\Downloads\Scenario1.lrs ended.Analyzing results...Error: Timeout for Analysis passed.Analysis Results:SLA report:Full Name : Errors Per SecondMeasurement : ErrorsPerSecondCriteriaMeasurement Value : RunningVusersLoadThresholds value : status : PassedError(s) summary: 0 ignored , 0 errorsTest PASSEDTest result: Passed05/01/2015 17:24:26 Test complete: C:\Users\\Downloads\Scenario1.lrs---Cleaning up the environment...Run status: Job succeeded, total tests: 1, succeeded: 1, failures: 0, errors: 0Passed : C:\Users\*\Downloads\Scenario1.lrsReport archiving mode is set to: DONT_ARCHIVE_TEST_REPORTFinished: SUCCESS
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-26312) No save button on the job configuration page
Igor Koyfman created JENKINS-26312 No save button on the job configuration page Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Jan/15 7:57 PM Description: In 1.596 there is no save button on the job configuration page. Cannot modify any jobs. Project: Jenkins Priority: Blocker Reporter: Igor Koyfman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Oliver Gondža commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG Rejected for 1.580.3. Removing lts-candidate label entirely, as this will be part of next LTS line anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25474) MultiJob Plugin not recognizing job failures for continuation condition
Mathieu Cantin closed JENKINS-25474 as Fixed MultiJob Plugin not recognizing job failures for continuation condition Change By: Mathieu Cantin (06/Jan/15 7:30 PM) Status: Open Closed 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] [multijob-plugin] (JENKINS-25636) multijob does not finish if phase contains same job multiple times
Mathieu Cantin closed JENKINS-25636 as Fixed multijob does not finish if phase contains same job multiple times Change By: Mathieu Cantin (06/Jan/15 7:28 PM) Status: Open Closed 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] [multijob-plugin] (JENKINS-26004) Priority option in multijob projects
Mathieu Cantin commented on JENKINS-26004 Priority option in multijob projects Please provide more informations or exemple. Yes, with multijob (and Trigger/call builds on other projects) there are possibility to create a deadlock. 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-26306) Disabled scrollbars since upgrading to jenkins 1.596
Alex Lombardi edited a comment on JENKINS-26306 Disabled scrollbars since upgrading to jenkins 1.596 This scrollbar issue is also affecting the jenkins Plugin admin page and hides the OK button under the toolbar if your list of avialable plugins to update is too long (can't scroll down). If you click the blue section on the the toolbar you can get it to update, but it is not intuitive that that is possible. 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-26306) Disabled scrollbars since upgrading to jenkins 1.596
Alex Lombardi commented on JENKINS-26306 Disabled scrollbars since upgrading to jenkins 1.596 This scrollbar issue is also affecting the jenkins Plugin admin page and hides the OK button under the toolbar. If you click the blue section on the the toolbar you can get it to update, but it is not intuitive that that is possible. 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] [warnings-plugin] (JENKINS-26311) Warning plugin archives do not exist
Lance Johnston created JENKINS-26311 Warning plugin archives do not exist Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 06/Jan/15 7:21 PM Description: The warnings plugin does not exist in the plugins download site at "https://updates.jenkins-ci.org/download/plugins/". It does exist at "https://updates.jenkins-ci.org/latest/warnings.hpi", but no releases other than latest appear to be available. Project: Jenkins Labels: plugin plugins Priority: Minor Reporter: Lance Johnston 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-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders The font change was not incidental; it was filed as a specific issue Right, I meant that the layout issue may not be a direct result of the font changes only, but rather interaction of font change and layout change, or layout change only. They were both merged into the same release IIRC. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl commented on JENKINS-18567 Add Watch button to Job summary screen Since I'm am reusing the UI for the trigger setup, the selection of recipients is still there, but only the person who is setting up the trigger will be emailed. If there is no authentication, how would the plugin know who to send the email to? The user would be Anonymous without login. The feature requires authentication in order to work. 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-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders Thanks, Dan, for that good info. I'll recommend we hold off on our upgrade until February. 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-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders > A lot more than font was changed, so this may be incidental. The font change was not incidental; it was filed as a specific issue (JENKINS-23840) separate from the other UI changes. The change submitter also specifically increased the font size. It appears, however, that Marlene's and my complaints about the formatting of columns are not related to the font change, but rather to the UI redesign, probably pull request 1310, which changed the way tables are rendered. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Mathieu Cantin commented on JENKINS-18567 Add Watch button to Job summary screen I have try this feature and it was good. But I don't understand why when I add a trigger on "Watch Job", I have the choice of who I would send a mail (developers, recipient list, culprits...). I think that is not usefull and this feature would just add me as receiver list. Doesn't work, if we have no authentification on jenkins (exemple, a test instance). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders There were changes since then to how the build history looks, and adapts to longer text in the description, build name, and/or badges, which were long-standing problems (screen shots e.g. on https://github.com/jenkinsci/jenkins/pull/1470). I don't think these are eligible for LTS backport though (even if -IRC- long build names or badges don't break and overlap the main panel). You'll need for the next major LTS.1 release that should arrive in February. 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-25971) Job list and console output are not properly aligned in the new UI
Daniel Beck commented on JENKINS-25971 Job list and console output are not properly aligned in the new UI Tom's fix is in 1.596. Does this issue still occur in that version? 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] [jira-plugin] (JENKINS-20424) Error updating JIRA issues - org.xml.sax.SAXParseException
Devin Barbieri commented on JENKINS-20424 Error updating JIRA issues - org.xml.sax.SAXParseException Here is another example of the error org.xml.sax.SAXParseException; lineNumber: 146; columnNumber: 37; XML document structures must start and end within the same entity. 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-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders This is 1.580.1 (the long-term stable release at the time we started our testing). Do you think these issues might be resolved in 1.580.2? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders What version of Jenkins is this? Try the current release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross edited a comment on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders The left-side picture is the new user interface; the right side is the old. These are taken from identically-sized windows. As you can see, two visible problems: the navigation bar takes up much more of the screen, leaving less room for the useful information. the build history window is formatted weirdly. Plus, my users (and I) think it looks ugly. I am using narrow windows to illustrate the problem, but the build history window gets screwed up in almost every screen size (including maximized). If I make the window narrow enough, the build history panel expands to fill the entire window, pushing the job details off the bottom of the screen. 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-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross updated JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders The left-side picture is the new user interface; the right side is the old. These are taken from identically-sized windows. As you can see, two visible problems: the navigation bar takes up much more of the screen, leaving less room for the useful information. the build history window is formatted weirdly. Plus, my users and I think it looks ugly. I am using narrow windows to illustrate the problem, but the build history window gets screwed up in almost every screen size. Change By: Don Ross (06/Jan/15 5:36 PM) Attachment: jenkins-ui-comparison.gif 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-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Don Ross commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders I am with Marlene. The new look is clunky and the automatic window/column sizings don't appear to have been updated to match the new widths. I will attach screenshots. However, according to the original ticket, the change was made to the 'default font'. So, if someone can point me to instructions for overriding the default to set my deployment back to the view my users are used to, I will be on my way. 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] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert commented on JENKINS-26308 LoadRunner Scenario Always Times Out Looking through the code, but I'm having difficulty building a version of this app. Was hoping to check the _perScenarioTimeOut in waitForScenario(ref string errorReason) in the PerformanceTestRunner class. It may be a stretch, but I'm trying to check why the timeout is occurring at 29 seconds (which by the way is pretty consistent) rather than the values I set. 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] [change-assembly-version-plugin] (JENKINS-25510) Change assembly version can set only the file name
Leonardo Kobus commented on JENKINS-25510 Change assembly version can set only the file name Hi just one question, is your AssemblyInfo outside the workspace jenkins? I just need to understand the situation, generally we need the file only to compile so is most probally that the assemblyinfo file is inside the solution (under workspace), that was the purpose of the plugin. If he is outside of solution he can be under workspace, so you don't have more this prob, can you do this? IF not a explain would be welcome to do the right modifications. 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] [change-assembly-version-plugin] (JENKINS-25510) Change assembly version can set only the file name
Leonardo Kobus assigned JENKINS-25510 to Leonardo Kobus Change assembly version can set only the file name Change By: Leonardo Kobus (06/Jan/15 4:32 PM) Assignee: Leonardo Kobus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-24291) GitHub plugin to make parameters from webhook data
Simon Weber commented on JENKINS-24291 GitHub plugin to make parameters from webhook data I'm running into a similar issue: I need access to the hook actor, but the plugin throws that information away. Specific parameters sound good - this is what https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin does - but we might also want to dump the entire hook to an environment variable. I could probably send a PR for this at some point. 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] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
Jason Swager resolved JENKINS-25588 as Fixed Integrate vSphere Cloud plugin with Credentials plugin (auth options) Should be resolved in v2.1 Change By: Jason Swager (06/Jan/15 3:56 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] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH SonarQube 5.0 does/will support slashes in branch names: https://jira.codehaus.org/browse/SONAR-3718 I still do not want all my branches to be prefixed with 'origin/'. 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] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
SCM/JIRA link daemon commented on JENKINS-25588 Integrate vSphere Cloud plugin with Credentials plugin (auth options) Code changed in jenkins User: Jason Swager Path: src/main/java/org/jenkinsci/plugins/vSphereCloud.java src/main/java/org/jenkinsci/plugins/vsphere/tools/VSphere.java src/main/resources/org/jenkinsci/plugins/vSphereCloud/config.jelly http://jenkins-ci.org/commit/vsphere-cloud-plugin/db8104dd3e879927c4811a32e2c749fe4984701a Log: Merge pull request #18 from oleg-nenashev/JENKINS-25588 JENKINS-25588 - Fixed the "Test Connection" validation handler Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/0f17d4b0ed4b...db8104dd3e87 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26310) notifyCommit URL responds with "No Git consumers using SCM API"
Oded Arbel created JENKINS-26310 notifyCommit URL responds with "No Git consumers using SCM API" Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 06/Jan/15 3:29 PM Description: According to the documentation, to get the git plugin to start a build without polling, one needs to set up a post-commit hook to send an HTTP request to `/notifyCommit`. In my tests, I always get the response No Git consumers using SCM API plugin for: g...@bitbucket.org:mycompany/myproject.git even though the URL submitted was copy-pasted from the job configuration screen Environment: Jenkins version 1.595 Project: Jenkins Labels: plugin Priority: Minor Reporter: Oded Arbel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26309) Custom Commit message for git publisher
Layton Whiteley created JENKINS-26309 Custom Commit message for git publisher Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 06/Jan/15 3:23 PM Description: Is there a way to append/add a custom commit message when pushing commits from jenkins. Currently, im not seeing a way to do this. If there is a way and im not seeing it, please point it out. If not, this would be a good feature an eg. use case would be to add ci skip tags to the description of the commit to stop recursive builds when doing a git push from jenkins. Environment: all Project: Jenkins Priority: Minor Reporter: Layton Whiteley 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] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Florent Poinsaut commented on JENKINS-12523 Could not initialize class org.libvirt.Connect Hello, Does this issue have another workaround that downgrade Jenkins or use SSH ? If not, I could fork this plugin but I lack of information to upgrade it. Can someone help me to realize this work ? Thanks in advance. Regards, 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] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert
created JENKINS-26308
LoadRunner Scenario Always Times Out
Issue Type:
Bug
Assignee:
Ofir Shaked
Components:
hp-application-automation-tools-plugin
Created:
06/Jan/15 3:20 PM
Description:
Simple Loadrunner scenario always times out when ran through Jenkins. The test runs fine when started within Loadrunner. Have tried on multiple machines in the same environment and found this issue. Though on my own personal machine it works fine.
LoadRunner Settings are set to default:
Controller Polling Interval - 30
Scenario Execution Timeout - 10
Errors To Ignore - none
Below is the console output:
Building in workspace C:\Program Files (x86)\Jenkins\jobs\Testing\workspace
[workspace] $ "C:\Program Files (x86)\Jenkins\jobs\Testing\workspace\HpToolsLauncher.exe" -paramfile props05012015172238713.txt
"Started..."
1 tests found:
C:\Users*\Downloads\Scenario1.lrs
05/01/2015 17:22:39 Running: C:\Users\Downloads\Scenario1.lrs
Cleaning up the environment...
Preparing scenario C:\Users\Downloads\Scenario1.lrs for execution.
Load Generator localhost connected
Starting scenario...
Error: Scenario Execution timeout (29 seconds) passed.
Error: Scenario Execution timeout ({0} seconds) passed.
Scenario C:\Users\Downloads\Scenario1.lrs ended.
Analyzing results...
Error: Timeout for Analysis passed.
Analysis Results:
SLA report:
Full Name : Errors Per Second
Measurement : ErrorsPerSecond
CriteriaMeasurement Value : RunningVusers
LoadThresholds value :
status : Passed
Error(s) summary:
0 ignored , 0 errors
Test PASSED
Test result: Passed
05/01/2015 17:24:26 Test complete: C:\Users\Downloads\Scenario1.lrs
---
Cleaning up the environment...
Run status: Job succeeded, total tests: 1, succeeded: 1, failures: 0, errors: 0
Passed : C:\Users*\Downloads\Scenario1.lrs
Report archiving mode is set to: DONT_ARCHIVE_TEST_REPORT
Finished: SUCCESS
Environment:
Jenkins 1.596
LoadRunner 11.52
HP Application Automation Tools 3.0.6
Windows server 2008
Java 6 update 38
Project:
Jenkins
Labels:
jenkins
plugin
timeout
loadrunner
Priority:
Major
Reporter:
Connor Gilbert
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] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)
Bue Petersen resolved JENKINS-25960 as Fixed MultiScm configurations does not resolve corret git-client (our case 12426) Change By: Bue Petersen (06/Jan/15 2:59 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] [pretested-integration-plugin] (JENKINS-25959) Post-buid steps is executed though master is integration branch (our case 12427)
Bue Petersen resolved JENKINS-25959 as Fixed Post-buid steps is executed though master is integration branch (our case 12427) Change By: Bue Petersen (06/Jan/15 2:56 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] [pretested-integration-plugin] (JENKINS-25886) Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)
Bue Petersen resolved JENKINS-25886 as Fixed Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401) Change By: Bue Petersen (06/Jan/15 2:50 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] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)
Bue Petersen resolved JENKINS-25546 as Fixed Support individual git scm configuration part in the Multi SCMs plugin (our case 12287) Change By: Bue Petersen (06/Jan/15 2:42 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] [build-pipeline-plugin] (JENKINS-23828) Build Pipeline View doesn't show build user id on Downstream Projects
Gilad Judes commented on JENKINS-23828 Build Pipeline View doesn't show build user id on Downstream Projects this happens in other "pipeline" plugins (i.e. Delivery Pipeline Plugin) when setting up a manual step - the user logs in and press the |> (play) button the build status in jenkins shows "Started by anonymous user" while the build xml (e.g. /var/lib/jenkins/jobs/Product-1.0.6-promote-to-QA/builds/22/build.xml) gilad Gilad Judes BTW we are working with Active Directory authentication 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] [promoted-builds-plugin] (JENKINS-14890) "Force Promotion" and "Re-execute promotion" should be configured by project-based matrix separately
Guillaume Paradis assigned JENKINS-14890 to Guillaume Paradis "Force Promotion" and "Re-execute promotion" should be configured by project-based matrix separately Change By: Guillaume Paradis (06/Jan/15 2:40 PM) Assignee: OHTAKE Tomohiro Guillaume Paradis 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] [promoted-builds-plugin] (JENKINS-14890) "Force Promotion" and "Re-execute promotion" should be configured by project-based matrix separately
Guillaume Paradis assigned JENKINS-14890 to OHTAKE Tomohiro "Force Promotion" and "Re-execute promotion" should be configured by project-based matrix separately Sorry, it got assigned to me by error. Change By: Guillaume Paradis (06/Jan/15 2:41 PM) Assignee: Guillaume Paradis OHTAKE Tomohiro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Kevin Burge commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH While I was able to work around this issue (using CMake and Regular Expressions), as an end user, I can see Tim Pizey's point and agree. Another possibility is to add a variable in addition to GIT_REMOTE that has today's GIT_BRANCH value, like GIT_REF, or GIT_UPSTREAM_BRANCH or something like that. So, if anyone is depending on the current logic, they can simply rename the the variable they are referencing. 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] [pretested-integration-plugin] (JENKINS-25873) Extend version number with git SHA (our case 12396)
Bue Petersen resolved JENKINS-25873 as Fixed Extend version number with git SHA (our case 12396) For the latest release you will see that the version is "2.2.0 (060cf)". This is okay for now, though the short SHA isn't strictly necessary for releases but more important for snapshots. Few other plugins, also uses custom version numbers. Change By: Bue Petersen (06/Jan/15 1:08 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] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Luc Sarzyniec stopped work on JENKINS-16290 git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves Change By: Luc Sarzyniec (06/Jan/15 12:45 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
