[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi commented on JENKINS-28238 Re: Github Plugin Failing to re-register for hooks i am having the same problem. Nov 04, 2015 8:41:42 PM WARNING org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeFailed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins] java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:151) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:147) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:137) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:97) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) this is a brand new jenkins setup w/ the following versions: jenkins: 1.636 git plugin: 2.4.0 git client: 1.19.0 github plugin: 1.14.0 my oauth token has the correct permissions and the verify credentials button indicates everything can connect. Add Comment
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title
Jae Gangemi edited a comment on JENKINS-28238
Re: Github Plugin Failing to re-register for hooks
i am having the same problem.{code}Nov 04, 2015 8:41:42 PM WARNING org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeFailed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins]java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:151) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:147) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:137) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:97) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){code}this is a brand new jenkins setup w/ the following versions:{code}jenkins: 1.636git plugin: 2.4.0git api: 1.69git client: 1.19.0github plugin: 1.14.0{code}my oauth token has the correct permissions and the verify credentials button indicates everything can connect.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero updated an issue Jenkins / JENKINS-31406 Promotion Status shows an excess of whitespace (missed one) Change By: jurgezero Environment: Jenkins 1.625.1, promoted-builds-plugin 2.23.1 Firefox 42.0 or Chrome 46, on OSX 10.10.5 and Windows 7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero edited a comment on JENKINS-31406 Re: Promotion Status shows an excess of whitespace (missed one) Firefox 42.0 or Chrome 46, on OSX 10.10.5 on Firefox 42.0 and Windows 7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31387) CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31387 Re: CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild' Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactSelectorContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactUpstreamBuildSelectorContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/8c8ae14a33ca182405742d9b518a82d34adf2ca6 Log: added closure for upstreamBuild selector [FIXES JENKINS-31387] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31406 Re: Promotion Status shows an excess of whitespace (missed one) jurgezero, Please, for this kind of issue it is very useful if you provide information about your S.O. and web browser. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero commented on JENKINS-31406 Re: Promotion Status shows an excess of whitespace (missed one) OSX 10.10.5 on Firefox 42.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30896) Unoptimized node & log storage
Title: Message Title Anshu Arya edited a comment on JENKINS-30896 Re: Unoptimized node & log storage My use case has a job that may run for days looping some workflow steps. This causes the job directory to grow very largee.g. my job ended with 300,000+ small XML files that amount to 600MB+.This also causes navigating to to jenkinsURL/job/JobName/builds/Job_Number/flowGraphTable to crash most browsers.Anyway to disable collecting the flowGraphTable XMLs for long jobs before this bug is fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30896) Unoptimized node & log storage
Title: Message Title Anshu Arya edited a comment on JENKINS-30896 Re: Unoptimized node & log storage My use case has a job that may run for days looping some workflow steps. This causes the job directory to grow very largee.g. my job ended with has 300,000+ small XML files amount to 600MB+.This also causes navigating to to jenkinsURL/job/JobName/builds/Job_Number/flowGraphTable to crash most browsers.Anyway to disable collecting the flowGraphTable XMLs for long jobs before this bug is fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-31384) Redirect to login page on all 404s without discover permission
Title: Message Title James Roper updated an issue Jenkins / JENKINS-31384 Redirect to login page on all 404s without discover permission Change By: James Roper Jenkins currently supports a discover permission, which when granted to the anonymous user, means if you visit a job and you don't have permission to see it, it will redirect you to the login page. Without this, the page just 404s, as if the job didn't exist. But what if you don't want to grant anonymous discover permission? The user experience when you're not logged in and you visit a job that you know exists, eg by clicking a link in GitHub or an email, is terrible, there's not even a link to click log in on the 404 page, you have to manually edit the URL bar to go to a page that does exist, click log in, log in, then click back in your browser until you get back to the screen that you wanted to view, and then click refresh to re-request that page.Behaving the same way is if the job was not found is a good security practice, however returning 404 in both circumstances is not the only way to implement this security practice, in fact in my opinion it's a terrible way, given the terrible experience it yields. A better implementation would be, if the user is not logged in, redirect to the login page in *both* circumstances. Then, if the user does log in, the user can be redirected back to the page they tried to access, and either a 404 page can be rendered (this would happen both if it didn't exist, or if the user didn't have read permission on the job), or the job can be rendered if they do have permission. This way, an anonymous user is still unable to discover the existence of a project, since the same behaviour occurs in either situation, but users clicking links from emails/github etc who aren't logged in are not frustrated by the current terrible experience. This I think is also a more semantic approach - if you 404 when the user doesn't have permission to view the project, you're lying to the user. If you redirect to login (effectively 401), you're saying "you're not allowed to find out whether this exists or not", which is exactly the intent, you don't have discover permission, so before you get a 404 to be told that it doesn't exist, you have to log in. Add Comment
[JIRA] [workflow-plugin] (JENKINS-30896) Unoptimized node & log storage
Title: Message Title Anshu Arya commented on JENKINS-30896 Re: Unoptimized node & log storage My use case has a job that may run for days looping some workflow steps. This causes the job directory to grow very largee.g. my job ended with has 300,000+ small XML files amount to 600MB+. This also causes navigating to to jenkinsURL/job/JobName/builds/Job_Number/flowGraphTable to crash most browsers. Anyway to disable collecting the flowGraphTable XMLs for long jobs before this bug is fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated The git client plugin 1.20.0-beta1 and git plugin 2.5.0-beta1 have been released to the experimental update center. They include Jacob Keller's git client plugin extensions for submodule authentication support and his addition of a checkbox to the submodule "Additional Behaviours" which will allow all submodules of a particular git repository to attempt to use the same credentials which were used with the parent repository. This will need significant beta testing before it can be merged to the master branch for general release, since it changes some core authentication behaviors in the git client plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Greg Peters commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer Rusty Bentz Did running Jenkins under OpenJDK fix this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin I can confirm the same, with 1.625.1. The FINEST added logger does not display any FINE logs, even when Check Now is clicked. I observed this when installing golang plugin, regardless of method (via UI or via .hpi file). After doing Check Now, only the INFO logs are shown. This should be easily reproducible using Jenkins docker image (that I am actually using). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31387) CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31387 Re: CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild' Code changed in jenkins User: Gabor Vasko-Szedlar Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactSelectorContext.groovy http://jenkins-ci.org/commit/job-dsl-plugin/aab4a2b5a3279d1b3f4f9cf04b59cfa29ffb98eb Log: JENKINS-31387 Add new option 'allowUpstreamDependencies' to CopyArtifact/upstreamBuild (cherry picked from commit 6dae8df2b590ccc13889092c3f33ee8e9fc1b3bd) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31387) CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild'
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31387 CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild' Change By: SCM/JIRA link daemon Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31387) CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31387 Re: CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild' Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactSelectorContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactUpstreamBuildSelectorContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/dc05bc19c785cbf0c48bbcd5e5032c42390ac43a Log: Merge branch ' JENKINS-31387 ' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/32a081e37fa7...dc05bc19c785 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title
Jae Gangemi commented on JENKINS-28238
Re: Github Plugin Failing to re-register for hooks
i am also unable to set the build status at the end of the job
Setting commit status on GitHub for https://github.com/condevops/hello-world-jenkins/commit/9147bf95263836cd6bccfd1e7882ac7498e79ca6
ERROR: Step ‘Set build status on GitHub commit’ aborted due to exception:
java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
at org.kohsuke.github.Requester.handleApiError(Requester.java:501)
at org.kohsuke.github.Requester._to(Requester.java:248)
at org.kohsuke.github.Requester.to(Requester.java:194)
at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:829)
at com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:138)
at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:90)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
at hudson.model.Run.execute(Run.java:1766)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: java.io.FileNotFoundException: https://api.github.com/repos/condevops/hello-world-jenkins/statuses/9147bf95263836cd6bccfd1e7882ac7498e79ca6
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:240)
at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
at org.kohsuke.github.Requester.parse(Requester.java:458)
at org.kohsuke.github.Requester._to(Requester.java:227)
... 13 more
Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [htmlpublisher-plugin] (JENKINS-31366) MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31366 Re: MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget' Code changed in jenkins User: Daniel Spilker Path: src/main/java/htmlpublisher/HtmlPublisherTarget.java http://jenkins-ci.org/commit/htmlpublisher-plugin/b3f3d6dd89928c035bcf568489158ec9d1f690c9 Log: added wrapperName field to maintain compatibility [FIXES JENKINS-31366] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-31366) MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31366 Re: MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget' Code changed in jenkins User: Mike Rooney Path: src/main/java/htmlpublisher/HtmlPublisherTarget.java http://jenkins-ci.org/commit/htmlpublisher-plugin/067ff3788556cb7b2b1e08f4fe8dc4213b9eb756 Log: Merge pull request #21 from daspilker/ JENKINS-31366 JENKINS-31366 added wrapperName field to maintain compatibility Compare: https://github.com/jenkinsci/htmlpublisher-plugin/compare/eeddf4492b6a...067ff3788556 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-31366) MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget'
Title: Message Title mcrooney resolved as Fixed Thanks for your time Daniel, that's really helpful I'm a huge fan of job-dsl, by the way! Jenkins / JENKINS-31366 MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget' Change By: mcrooney Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero created an issue Jenkins / JENKINS-31406 Promotion Status shows an excess of whitespace (missed one) Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 04/Nov/15 8:39 PM Environment: Jenkins 1.625.1, promoted-builds-plugin 2.23.1 Priority: Minor Reporter: jurgezero Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-31406 Promotion Status shows an excess of whitespace (missed one) Change By: jurgezero Attachment: 2015-11-04_15-41-49.jpg Assignee: Oleg Nenashev Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-28238 Github Plugin Failing to re-register for hooks Change By: Jae Gangemi Assignee: Richard Duarte Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi reopened an issue Jenkins / JENKINS-28238 Github Plugin Failing to re-register for hooks Change By: Jae Gangemi Status: Resolved Reopened Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-31411) Build is ok, aber
Title: Message Title Manuel created an issue Jenkins / JENKINS-31411 Build is ok, aber Issue Type: Bug Assignee: mcrooney Components: htmlpublisher-plugin Created: 05/Nov/15 12:33 AM Environment: master: debian, build-runner-slave: windows server 2012r2 Priority: Blocker Reporter: Manuel The job is running fine. The results(html directory with index.html) are saved on master. But when we click on the link: always a 404 error throws. Notice: We use the Cloudbees Folder Plugin: https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin But is this the issue??? Microsoft use the same on her build farm for the dotnetframework. Add Comment
[JIRA] [htmlpublisher-plugin] (JENKINS-31411) Build is ok, but...
Title: Message Title Manuel commented on JENKINS-31411 Re: Build is ok, but... The url to the results look like this: https://jenins.server.com/job/jobfolder/job/jobname/html-title/ Whats going on here? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-31407) Tried to install conditional build step and run condition plugins. After that, the main dashboard view is broken. How can I recover? I've managed to dele
Title: Message Title
Andrew McLaughlin created an issue
Jenkins / JENKINS-31407
Tried to install conditional build step and run condition plugins. After that, the main dashboard view is broken. How can I recover? I've managed to delete the new plugins, but still it's broken.
Issue Type:
Bug
Assignee:
Peter Hayes
Components:
dashboard-view-plugin
Created:
04/Nov/15 11:04 PM
Environment:
Jenkins 626 running on Tomcat 7, Java 7 on CentOS 5.11
Priority:
Critical
Reporter:
Andrew McLaughlin
Here's the complete stack trace:
{{javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/usr/java/apache-tomcat-7.0.62/webapps/jenkins/WEB-INF/lib/jenkins-core-1.626.jar!/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: jar:file:/usr/java/apache-tomcat-7.0.62/webapps/jenkins/WEB-INF/lib/jenkins-core-1.626.jar!/lib/hudson/projectView.jelly:67:24: java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin FWIW, workaround via Script console: import jenkins.model.* Jenkins j = Jenkins.getInstance() j.pluginManager.doCheckUpdatesServer() Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31409) Manage jenkins configure system screen crashes after plugins installed
Title: Message Title
Andrew McLaughlin created an issue
Jenkins / JENKINS-31409
Manage jenkins configure system screen crashes after plugins installed
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
04/Nov/15 11:12 PM
Environment:
Jenkins 1.626 on Tomcat 7, Java 7 on CentOS 5.11
Priority:
Critical
Reporter:
Andrew McLaughlin
Received following exception when trying to access manage jenkins configure system screen. Plugins installed were conditional build step and run condition plugins. After restart, this happens:
{{javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/usr/java/apache-tomcat-7.0.62/webapps/jenkins/WEB-INF/lib/jenkins-core-1.626.jar!/jenkins/model/Jenkins/configure.jelly:59:84: java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at
[JIRA] [windows-slaves-plugin] (JENKINS-31408) Unable to browse localhost:8080 on windows 10 laptop
Title: Message Title Saoirse O Comain created an issue Jenkins / JENKINS-31408 Unable to browse localhost:8080 on windows 10 laptop Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins.PNG Components: windows-slaves-plugin Created: 04/Nov/15 11:10 PM Environment: 64bit i7, 8Gb, Windows 10 Chrome/Firefox. The latest Jenkins and Java (just downloaded both). Priority: Blocker Reporter: Saoirse O Comain I recently downloaded and installed the latest java versions (in jdk) and jenkins. Opening the browser at localhost:8080 does not load Jenkins. I ran the same install on a work laptop running Windows 7 without an issue so am wondering if this is a Windows 10-specific issue?
[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Daniel Beck commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin Oops. The logger is supposed to be called hudson.model.DownloadService$DownloadableListener ($ sign). Note that this logger only logs when Jenkins would update its internal list of Downloadables, which happens during plugin installation – So "Check Now" not logging anything is to be expected. However, I just set up a pristine 1.625.1 instance, set up the logger, and installed the Go Plugin, and… Nov 05, 2015 12:46:37 AM FINER hudson.model.DownloadService$DownloadableListener Skipping update of metadata for hudson.tasks.Maven.MavenInstaller Nov 05, 2015 12:46:37 AM FINER hudson.model.DownloadService$DownloadableListener Skipping update of metadata for hudson.tasks.Ant.AntInstaller Nov 05, 2015 12:46:37 AM FINER hudson.model.DownloadService$DownloadableListener Skipping update of metadata for hudson.tools.JDKInstaller Nov 05, 2015 12:46:37 AM FINE hudson.model.DownloadService$DownloadableListener Updating metadata for org.jenkinsci.plugins.golang.GolangInstaller Going back to the global config, I get the versions for Go in a dropdown… Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-31411) Build is ok, but...
Title: Message Title Manuel updated an issue Jenkins / JENKINS-31411 Build is ok, but... Change By: Manuel Summary: Build is ok, aber but... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Title: Message Title nick carpenter commented on JENKINS-25048 Re: Git plugin ignores included/excluded paths when triggering build on commit nitification So this is a major issue for us as well. We are trying to put build job config in source. Right now with commit notifications, we cannot ignore that repository directory with this bug currently active. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Franck Derunes commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module having this issue using Jenkins ver. 1.617 everyday using linux MINT slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jgiven-plugin] (JENKINS-31337) Add support for new --exclude-empty-scenarios option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31337 Re: Add support for new --exclude-empty-scenarios option Code changed in jenkins User: Stefan Wolf Path: pom.xml src/main/java/org/jenkinsci/plugins/jgiven/JgivenDslContext.java src/main/java/org/jenkinsci/plugins/jgiven/JgivenReportGenerator.java src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/config.groovy src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/config.properties src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/config_de.properties src/test/java/org/jenkinsci/plugins/jgiven/JgivenDslContextExtensionTest.java src/test/java/org/jenkinsci/plugins/jgiven/JgivenReportGeneratorTest.java http://jenkins-ci.org/commit/jgiven-plugin/34443efdc9f8099e45922bf4b0861d46a3eed582 Log: [FIXED JENKINS-31337] Update to JGiven 0.9.4 and support --exclude-empty-scenarios option Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rbenv-plugin] (JENKINS-30930) Ruby plugins break with Jenkins v. 1.633 upgrade
Title: Message Title James Nord closed an issue as Duplicate Duplicate of JENKINS-30898 and then JENKINS-31019 Jenkins / JENKINS-30930 Ruby plugins break with Jenkins v. 1.633 upgrade Change By: James Nord Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-31410) Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed
Title: Message Title Praveen Kasireddy created an issue Jenkins / JENKINS-31410 Flexible Publish plugin is waiting for previous builds to complete even if current build is already completed Issue Type: Bug Assignee: bap Components: flexible-publish-plugin Created: 04/Nov/15 11:24 PM Environment: flexible pgublish - 0.15.2 , run condition - 1.0 Priority: Major Reporter: Praveen Kasireddy When two concurrent builds of same project are running (on two different nodes), if second build completes first, it is waiting for first build to complete before running the flexible publish logic. I see a message like "Flexible publish is waiting for a checkpoint on appbuild #3557_remotes/origin/master" in 3558 build. This is unnecessarily delaying the builds from completion.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title
James Nord edited a comment on JENKINS-31019
Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
{noformat}Nov 04, 2015 12:55:13 PM org.jenkinsci.bytecode.ClassWriter getCommonSuperClassFINER: Searching for common super class of org/jruby/RubyClass and org/jruby/runtime/builtin/IRubyObject←[31mNov 04, 2015 12:55:13 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading plugin ruby-runtime{noformat}[RubyClass | http://jruby.org/apidocs/org/jruby/RubyClass.html] implements [IRubyObject | http://jruby.org/apidocs/org/jruby/runtime/builtin/IRubyObject.html] and the class we are loading is RubyClass - hence the circularity here.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord started work on JENKINS-31019 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord updated an issue Jenkins / JENKINS-31019 Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Change By: James Nord Component/s: rbenv-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk reopened an issue Jenkins / JENKINS-27694 Download update data immediately when installing a new tool installer plugin Change By: Radek Antoniuk Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-30545) Active Choices Plugin: Bug with radio boxes
Title: Message Title lyen liang commented on JENKINS-30545 Re: Active Choices Plugin: Bug with radio boxes I created a pull request which (I think) solves this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-plugin] (JENKINS-31412) Form too large
Title: Message Title Narendra Lanka created an issue Jenkins / JENKINS-31412 Form too large Issue Type: Bug Assignee: Unassigned Components: ssh-plugin Created: 05/Nov/15 4:48 AM Priority: Critical Reporter: Narendra Lanka Hai , When I am add a ssh-server in configuration test configuration is success but when I click on save button it shows stack error. I am using Jenkins 1.6.23 . Stack trace javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 204440>20 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [subversion-plugin] (JENKINS-31127) Subversion Notify Commit needs long time to reply
Title: Message Title
Luis Roberto Perez Rios commented on JENKINS-31127
Re: Subversion Notify Commit needs long time to reply
Sorry for the delay Manuel Jesús Recena Soto: The script is:
REPOS="$1" REV="$2" UUID=`svnlook uuid $REPOS` FILES=`svnlook changed -r $ {REV} ${REPOS}` AUTHOR=`svnlook author -r ${REV}
$ {REPOS}
` echo `date` >> /some1.txt echo "rev: $ {REV}
[$AUTHOR]" >> /some2.txt echo "$ {FILES}" >> /some3.txt TRUNK=`echo ${FILES}
| sed -n -e '/^[UAD][ ]*trunk/p'`
if ! test -z "$ {TRUNK}
" ; then echo " TRUNK files, triggering build ..." >> /some4.txt /usr/bin/wget \ --header "Content-Type:text/plain;charset=UTF-8" \ --post-data "`svnlook changed --revision $REV $REPOS`" \ -
output-document "
" \ http://jenkinsIP/subversion/$ {UUID}
/notifyCommit?rev=$REV fi
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status-plugin] (JENKINS-31050) Slave goes offline during the build
Title: Message Title Kevin Navero commented on JENKINS-31050 Re: Slave goes offline during the build I'm getting the same problem on Jenkins 1.625.1 LTS. The configuration I have set up is that I have a slave node running Windows 7 natively which is running a Windows Server 2003 virtual machine. The slave-agent client is running on the virtual machine. The Windows Server 2003 VM is running java version 1.7.0_80. Let me know if I can supply more information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31386) "checkout scm" does not work in standalone jobs
Title: Message Title Chris Willmore commented on JENKINS-31386 Re: "checkout scm" does not work in standalone jobs Thanks for feedback Jesse. Would be a great feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31127) Subversion Notify Commit needs long time to reply
Title: Message Title
Luis Roberto Perez Rios edited a comment on JENKINS-31127
Re: Subversion Notify Commit needs long time to reply
Sorry for the delay [~recena]:The main script lines are:/usr/bin/wget \ --header "Content-Type:text/plain;charset=UTF-8" \ --post-data "`svnlook changed --revision $rev $repo`" \ --output-document "-" \ http://jenkinsIP/subversion/$ {UUID} uuid /notifyCommit?rev=$rev
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-30545) Active Choices Plugin: Bug with radio boxes
Title: Message Title lyen liang edited a comment on JENKINS-30545 Re: Active Choices Plugin: Bug with radio boxes I created a [pull request|https://github.com/jenkinsci/active-choices-plugin/pull/7] which (I think) solves this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-30992) Generate Build Report button does not include all past builds
Title: Message Title Varun Menon commented on JENKINS-30992 Re: Generate Build Report button does not include all past builds Its seems you still have old version of the plugin. Is it possible for you to update to latest 0.2.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-31413) intermittently Deployer failing with socket closed Exception.
Title: Message Title simba s created an issue Jenkins / JENKINS-31413 intermittently Deployer failing with socket closed Exception. Issue Type: Bug Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 05/Nov/15 4:58 AM Environment: Jenkins 1.624 JDK 1.8.0_31 Linux 8.4 WeebLogic Deployer PLug-in 3.2 Weblogic 12C Priority: Major Reporter: simba s I'm trying deploy into weblogic cluster. I see below error in Weblogic Admin server log. - Below is the exception in Jenkins Logs. weblogic.deploy.api.internal.utils.DeployerHelperException: Software caused connection abort: socket write error at weblogic.deploy.api.internal.utils.JMXDeployerHelper.uploadSource(JMXDeployerHelper.java:677) at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:857) at weblogic.deploy.api.spi.deploy.internal.BasicOperation.uploadFiles(BasicOperation.java:332) at weblogic.deploy.api.spi.deploy.internal.BasicOperation.execute(BasicOperation.java:465) at weblogic.deploy.api.spi.deploy.internal.BasicOperation.run(BasicOperation.java:178)
[JIRA] [subversion-plugin] (JENKINS-31127) Subversion Notify Commit needs long time to reply
Title: Message Title
Luis Roberto Perez Rios edited a comment on JENKINS-31127
Re: Subversion Notify Commit needs long time to reply
Sorry for the delay [~recena]:The main script is lines are : REPOS="$1"REV="$2"UUID=`svnlook uuid $REPOS`FILES=`svnlook changed -r ${REV} ${REPOS}`AUTHOR=`svnlook author -r ${REV} ${REPOS}`echo `date` >> / some1.txtecho "rev: ${REV} [$AUTHOR]" >> /some2.txtecho "${FILES}" >> /some3.txtTRUNK=`echo ${FILES} | sed -n -e '/^[UAD][ ]*trunk/p'`if ! test -z "${TRUNK}" ; then echo " TRUNK files, triggering build ..." >> /some4.txt/ usr/bin/wget \ --header "Content-Type:text/plain;charset=UTF-8" \ --post-data "`svnlook changed --revision $ REV rev $ REPOS repo `" \ --output-document "-" \ http://jenkinsIP/subversion/${UUID}/notifyCommit?rev=$ REV rev fi
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31127) Subversion Notify Commit needs long time to reply
Title: Message Title
Luis Roberto Perez Rios edited a comment on JENKINS-31127
Re: Subversion Notify Commit needs long time to reply
Sorry for the delay [~recena]:The script is:REPOS="$1"REV="$2"UUID=`svnlook uuid $REPOS`FILES=`svnlook changed -r ${REV} ${REPOS}`AUTHOR=`svnlook author -r ${REV} ${REPOS}`echo `date` >> /some1.txtecho "rev: ${REV} [$AUTHOR]" >> /some2.txtecho "${FILES}" >> /some3.txtTRUNK=`echo ${FILES} | sed -n -e '/^[UAD][ ]*trunk/p'`if ! test -z "${TRUNK}" ; then echo " TRUNK files, triggering build ..." >> /some4.txt/usr/bin/wget \ --header "Content-Type:text/plain;charset=UTF-8" \ --post-data "`svnlook changed --revision $REV $REPOS`" \ --output-document "-" \ http://jenkinsIP/subversion/${UUID}/notifyCommit?rev=$REVfi
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31015) Failure when downloading zipped artifacts
Title: Message Title Jakub Gawlas commented on JENKINS-31015 Re: Failure when downloading zipped artifacts Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-31019 Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title Martin Weber commented on JENKINS-31371 Re: No tool download known for OS... (Crawler generates empty update file) @georgeg Use the zip installer as a fall back installer on the global config page. Meanwhile, I contacted the cmake guys and they were kind enough to re-enable directory index listing. The issue will resolve with the next run of the crawler (runs daily on jenkins-ci.org). Your Jenkins instance will update the crawler result within 2-3 days. To force an update, you may delete file $JENKINS_HOME/updates/hudson.plugins.cmake.CmakeInstaller Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-31397) Docker plugin does not provision container
Title: Message Title sébastien glon commented on JENKINS-31397 Re: Docker plugin does not provision container I have not docker slave container started. if i increase de max no. of ccontainers, i have the same message but not starting containner. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31396) Access to submitter ID from return value of input step
Title: Message Title owenmehegan commented on JENKINS-31396 Re: Access to submitter ID from return value of input step I was asking for this in IRC (autojack). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Vlad Aginsky commented on JENKINS-21750 Re: Promoted Builds Plugin Guys, any update on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-31394) Using socket as "Docker URL" causes Exception
Title: Message Title Claus Näveke created an issue Jenkins / JENKINS-31394 Using socket as "Docker URL" causes Exception Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 04/Nov/15 2:07 PM Environment: Jenkins 1.636 docker-build-step-plugin 1.32 Labels: exception Priority: Minor Reporter: Claus Näveke When trying to use the socket connection to docker (Docker URL = "" the build fails with the following exception: javax.ws.rs.ProcessingException: Could not initialize class org.newsclub.net.unix.NativeUnixSocket at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:255) at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:683) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:228) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:424) at
[JIRA] [workflow-plugin] (JENKINS-31396) Access to submitter ID from return value of input step
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-31396 Access to submitter ID from return value of input step Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 04/Nov/15 2:34 PM Priority: Major Reporter: Jesse Glick Currently the input step records the submitter ID in ApproverAction but does not make this information available to the script. There should be an option to include a map entry with key submitter in the return value of the step. (Cannot be enabled by default for compatibility reasons.) Add Comment
[JIRA] [workflow-plugin] (JENKINS-31391) Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Title: Message Title
Jesse Glick commented on JENKINS-31391
Re: Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Preferably should introduce an API in CoreEnvironmentContributor to allow implementation to be shared.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31391) Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-31391
Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Change By:
Jesse Glick
Labels:
api environment-variables executor
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-31398) Archive no longer works
Title: Message Title Tommi Kiviniemi created an issue Jenkins / JENKINS-31398 Archive no longer works Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 04/Nov/15 3:12 PM Environment: Mac OS X El Capitan Priority: Major Reporter: Tommi Kiviniemi The archive option no longer works with newer Xcode versions as it has been obsoleted. It can be called via this command instead: xcodebuild -project "XXX.xcodeproj" -scheme "Unity-iPhone" -configuration Release archive Would be great if the plugin could be updated to support this. Thanks! Tommi
[JIRA] [workflow-plugin] (JENKINS-30530) Fix display of SCMBinder
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30530 Fix display of SCMBinder Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30530) Fix display of SCMBinder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30530 Re: Fix display of SCMBinder Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/configure-entries.jelly multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinder.java multibranch/src/main/resources/org/jenkinsci/plugins/workflow/multibranch/SCMBinder/config.jelly http://jenkins-ci.org/commit/workflow-plugin/970547e05b62d5d85e98f64546e3729226023e52 Log: [FIXED JENKINS-30530] SCMBinder should be displayed in r/o branch project configurations. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Nov 04, 2015 12:55:13 PM org.jenkinsci.bytecode.ClassWriter getCommonSuperClass FINER: Searching for common super class of org/jruby/RubyClass and org/jruby/runtime/builtin/IRubyObject ←[31mNov 04, 2015 12:55:13 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin ruby-runtime RubyClass implements IRubyObject hence the circularity here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jgiven-plugin] (JENKINS-31337) Add support for new --exclude-empty-scenarios option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31337 Re: Add support for new --exclude-empty-scenarios option Code changed in jenkins User: Stefan Wolf Path: pom.xml src/main/java/org/jenkinsci/plugins/jgiven/JgivenReportGenerator.java src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/config.groovy src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/config.properties src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/config_de.properties src/test/java/org/jenkinsci/plugins/jgiven/JgivenReportGeneratorTest.java http://jenkins-ci.org/commit/jgiven-plugin/9ae7a3afc4584deef31043b849bd4a169adeb33b Log: [FIXED JENKINS-31337] Update to JGiven 0.9.4 and support --exclude-empty-scenarios option< /p> Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jgiven-plugin] (JENKINS-31337) Add support for new --exclude-empty-scenarios option
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31337 Add support for new --exclude-empty-scenarios option Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-31397) Docker plugin does not provision container
Title: Message Title sébastien glon updated an issue Jenkins / JENKINS-31397 Docker plugin does not provision container Change By: sébastien glon My jenkins is docker image jenkins:latestI have configured access to my docker remote apiand test pass.I have adding template image: evarga/jenkins-slavebut i have always this line:ov 04, 2015 3:01:42 PM com.nirima.jenkins.plugins.docker.DockerCloud provisionINFO: Will provision 'evarga/jenkins-slave', for label: 'jenkins-slave', in cloud: 'api-docker'Nov 04, 2015 3:01:42 PM com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlaveINFO: Not Provisioning 'evarga/jenkins-slave'; Server 'api-docker' full with '1' container(s) And i always have job to wait contianer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Peter Willekens created an issue Jenkins / JENKINS-31395 On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page Issue Type: Bug Assignee: Unassigned Attachments: Jenkins_initial.PNG, Jenkins_scrolled.PNG Components: core Created: 04/Nov/15 2:18 PM Priority: Minor Reporter: Peter Willekens I just installed Jenkins LTS 1.625.1 on Linux in Tomcat. On the Jenkins homepage, the footer scrolls up with the rest of the screen. Jenkins_initial picture shows what i see on the left bottom side of the screen. When I scroll, the footer scrolls up with the rest of the page, revealing what I see in Jenkins_scrolled picture. Add Comment
[JIRA] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Peter Willekens commented on JENKINS-31395 Re: On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page Forgot to mention this is on Internet Explorer 11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31389) SVN changelog on wrong build
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31389 SVN changelog on wrong build Change By: Jesse Glick Summary: Workflow plugin - SVN changelog on wrong build Component/s: core Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Title: Message Title
Adrian Price updated an issue
Jenkins / JENKINS-31258
Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Change By:
Adrian Price
The Jenkins Maven plug-in ignores JUnit format files in the test results directory ($\{project.build.directory\}/surefire-reports by default). Debugging revealed the cause to be that maven-plugin knows about certain\* test-capable MOJOs and attempts to support unknown MOJOs by making the following unjustifiable assumptions:# that the MOJO will target the 'test' goal or similar# that the MOJO configuration will have a 'reportsDirectory' property\* maven testing plug-ins known to the Jenkins Maven plug-in / project type as of 2014-12-04 13:40:29:* org.apache.maven.plugins:maven-surefire-plugin* net.kennychua:phantomjs-qunit-runner* org.apache.maven.plugins:maven-failsafe-plugin* com.sun.maven:maven-junit-plugin* org.sonatype.flexmojos:flexmojos-maven-plugin* org.sonatype.tycho:maven-osgi-test-plugin* org.eclipse.tycho:tycho-surefire-plugin* com.jayway.maven.plugins.android.generation2:maven-android-plugin* com.jayway.maven.plugins.android.generation2:android-maven-plugin* org.codehaus.mojo:gwt-maven-plugin* com.smartbear.soapui:soapui-maven-plugin* com.smartbear.soapui:soapui-pro-maven-plugin* com.github.redfish4ktc.soapui:maven-soapui-extension-plugin* com.github.searls:jasmine-maven-plugin* org.terracotta.maven.plugins:toolkit-resolver-plugin* org.scalatest:scalatest-maven-plugin* org.nanoko.playframework:play2-maven-pluginExamples of unknown/unsupported Maven testing plug-ins:* com.github.eirslett:frontend-maven-plugin:karma* com.kelveden:maven-karma-plugin:start* com.github.greengerong:maven-ng-protractor:run* others, doubtless...In the general 'unknown Maven plug-in' case neither of these assumptions are likely to be valid e.g., com.github.eirslett:frontend-maven-plugin running Karma tests, the goal is 'karma' (phase = 'test' or 'integration-test', typically) and the test output directory is configured in a separate karma.conf.js file.Overall, this means there is no general solution for reporting standard JUnit-format results that have been placed in the Maven-standard location for such results, other than to use only plug-ins that the Jenkins Maven plugin actually knows about! This is inflexible and an unreasonable limitation for a general-purpose CI tool and a highly extensible build tool. I see two three possible solutions:# The Jenkins Job configuration for Maven projects provides some declarative means to identify additional test reports.-- PROs:--- straightforward to configure--- no Jenkins-specific POM changes required--- only one set of changes required-- CONs:--- requires explicit configuration in every Jenkins Maven job# Develop a Maven plug-in that could be incorporated into a POM's pluginManagement section purely as the means to indicate that a given plug-in execution (specified as the groupdId, artifactId, version, goal and phase of the otherwise unknown-to-Jenkins Maven test plug-in) produces test results in the specified directory).-- PROs:--- should work OOTB in any up-to-date Jenkins installation--- the Maven plug-in could be extended to cover additional capabilities where Jenkins' built-in Maven integration is inadquate-- CONs:--- additional POM
[JIRA] [jgiven-plugin] (JENKINS-30981) Absolute paths required for custom JS/CSS files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30981 Re: Absolute paths required for custom JS/CSS files Code changed in jenkins User: Stefan Wolf Path: src/main/java/org/jenkinsci/plugins/jgiven/JgivenReportGenerator.java src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customCssFile.html src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customCssFile_de.html src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customJsFile.html src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customJsFile_de.html http://jenkins-ci.org/commit/jgiven-plugin/414932c7f7e1f5baa041803a58915bfa36d274fc Log: Merge pull request #3 from jenkinsci/from-workspace [FIXED JENKINS-30981] Custom files are now taken from workspace Compare: https://github.com/jenkinsci/jgiven-plugin/compare/62d623a903b6...414932c7f7e1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Title: Message Title
Adrian Price updated an issue
Jenkins / JENKINS-31258
Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Change By:
Adrian Price
The Jenkins Maven plug-in ignores JUnit format files in the test results directory ($\{project.build.directory\}/surefire-reports by default). Debugging revealed the cause to be that maven-plugin knows about certain\* test-capable MOJOs and attempts to support unknown MOJOs by making the following unjustifiable assumptions:# that the MOJO will target the 'test' goal or similar# that the MOJO configuration will have a 'reportsDirectory' property\* maven testing plug-ins known to the Jenkins Maven plug-in / project type as of 2014-12-04 13:40:29:* org.apache.maven.plugins:maven-surefire-plugin* net.kennychua:phantomjs-qunit-runner* org.apache.maven.plugins:maven-failsafe-plugin* com.sun.maven:maven-junit-plugin* org.sonatype.flexmojos:flexmojos-maven-plugin* org.sonatype.tycho:maven-osgi-test-plugin* org.eclipse.tycho:tycho-surefire-plugin* com.jayway.maven.plugins.android.generation2:maven-android-plugin* com.jayway.maven.plugins.android.generation2:android-maven-plugin* org.codehaus.mojo:gwt-maven-plugin* com.smartbear.soapui:soapui-maven-plugin* com.smartbear.soapui:soapui-pro-maven-plugin* com.github.redfish4ktc.soapui:maven-soapui-extension-plugin* com.github.searls:jasmine-maven-plugin* org.terracotta.maven.plugins:toolkit-resolver-plugin* org.scalatest:scalatest-maven-plugin* org.nanoko.playframework:play2-maven-pluginExamples of unknown/unsupported Maven testing plug-ins:* com.github.eirslett:frontend-maven-plugin:karma* com.kelveden:maven-karma-plugin:start* com.github.greengerong:maven-ng-protractor:run* others, doubtless...In the general 'unknown Maven plug-in' case neither of these assumptions are likely to be valid e.g., com.github.eirslett:frontend-maven-plugin running Karma tests, the goal is 'karma' (phase = 'test' or 'integration-test', typically) and the test output directory is configured in a separate karma.conf.js file.Overall, this means there is no general solution for reporting standard JUnit-format results that have been placed in the Maven-standard location for such results, other than to use only plug-ins that the Jenkins Maven plugin actually knows about! This is inflexible and an unreasonable limitation for a general-purpose CI tool and a highly extensible build tool. I see three possible solutions:# The Jenkins Job configuration for Maven projects provides some declarative means to identify additional test reports.-- PROs:--- straightforward to configure--- no Jenkins-specific POM changes required--- only one set of changes required-- CONs:--- requires explicit configuration in every Jenkins Maven job# Develop a Maven plug-in that could be incorporated into a POM's pluginManagement section purely as the means to indicate that a given plug-in execution (specified as the groupdId, artifactId, version, goal and phase of the otherwise unknown-to-Jenkins Maven test plug-in) produces test results in the specified directory).-- PROs:--- should work OOTB in any up-to-date Jenkins installation--- the Maven plug-in could be extended to cover additional capabilities where Jenkins' built-in Maven integration is inadquate-- CONs:--- additional POM
[JIRA] [workflow-plugin] (JENKINS-30530) Fix display of SCMBinder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30530 Re: Fix display of SCMBinder Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/configure-entries.jelly multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinder.java multibranch/src/main/resources/org/jenkinsci/plugins/workflow/multibranch/SCMBinder/config.jelly http://jenkins-ci.org/commit/workflow-plugin/051aeba3ce9f104b5b7b36165332df36effd65c3 Log: Merge pull request #241 from jglick/SCMBinder-display- JENKINS-30530 JENKINS-30530 Display SCMBinder Compare: https://github.com/jenkinsci/workflow-plugin/compare/8505f0f82596...051aeba3ce9f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-31394) Using socket as "Docker URL" causes Exception
Title: Message Title Claus Näveke updated an issue Jenkins / JENKINS-31394 Using socket as "Docker URL" causes Exception Change By: Claus Näveke Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord edited a comment on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass The issue is likely with the bytrcide bytecode- compatbility - transformer not this plugin.The bct is a black art so for now the solution is toA) roll back jenkinsOrB) run without the bct (which may cause other issues)-Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31391) Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Title: Message Title
Jesse Glick commented on JENKINS-31391
Re: Environment variable EXECUTOR_NUMBER should be usable inside node{} block
NODE_LABELS is also missing.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31391) Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-31391
Re: Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Code changed in jenkins User: Jesse Glick Path: support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/8505f0f82596b249b6e8ea8a2957d67d3a487188 Log: Removing TODO comment filed as JENKINS-31391.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31389) SVN changelog on wrong build
Title: Message Title Jesse Glick resolved as Not A Defect If you have a simple inline script definition, build #3 will show SVN changes #22–25, since that is what the checkout scm: … step will be updating. If you are using a script loaded from SCM (and that SCM is in fact the same Subversion repository as the checkout step is using), then the first update will occur before the defined script even starts. Thus build #2 will show SVN changes #22–23 and build #3 will show changes #24–25. Similarly, if you are using a multibranch workflow, the checkout to get Jenkinsfile occurs before the script starts, so each build will be listed as including some SVN changes. Jenkins / JENKINS-31389 SVN changelog on wrong build Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received
[JIRA] [workflow-plugin] (JENKINS-31386) "checkout scm" does not work in standalone jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31386 "checkout scm" does not work in standalone jobs checkout scm is currently only available for multibranch workflows, not for standalone jobs. However I think it could be made to work in standalone jobs using the Workflow script from SCM definition. It would be weaker since it would only be a shortcut for specifying an equivalent SCM definition in the script body, whereas in multibranch projects the scm variable is actually guaranteed to check out the same revision as Jenkinsfile was using. (Consider a commit pushed to the SCM between the time the Workflow script is checked out, and the time the checkout step runs. In a standalone project, the checkout step will pick up the new commit, whereas in a multibranch project scm will use the original commit. That could matter in case you are making changes coördinated between the Workflow script and other project sources, such as this one.) Change By: Jesse Glick Summary: "checkout scm" failing with Groovy "no such property" exception does not work in standalone jobs Issue Type: Bug New Feature Priority: Minor Major Labels: multibranch Add Comment
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord updated an issue Jenkins / JENKINS-31019 Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass log of transformation for org.jruby.RubyClass Change By: James Nord Attachment: bytecode.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Title: Message Title
Adrian Price updated an issue
Jenkins / JENKINS-31258
Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Change By:
Adrian Price
The Jenkins Maven plug-in ignores JUnit format files in the test results directory ($\{project.build.directory\}/surefire-reports by default). Debugging revealed the cause to be that maven-plugin knows about certain\* test-capable MOJOs and attempts to support unknown MOJOs by making the following unjustifiable assumptions:# that the MOJO will target the 'test' goal or similar# that the MOJO configuration will have a 'reportsDirectory' property\* maven testing plug-ins known to the Jenkins Maven plug-in / project type as of 2014-12-04 13:40:29:* org.apache.maven.plugins:maven-surefire-plugin* net.kennychua:phantomjs-qunit-runner* org.apache.maven.plugins:maven-failsafe-plugin* com.sun.maven:maven-junit-plugin* org.sonatype.flexmojos:flexmojos-maven-plugin* org.sonatype.tycho:maven-osgi-test-plugin* org.eclipse.tycho:tycho-surefire-plugin* com.jayway.maven.plugins.android.generation2:maven-android-plugin* com.jayway.maven.plugins.android.generation2:android-maven-plugin* org.codehaus.mojo:gwt-maven-plugin* com.smartbear.soapui:soapui-maven-plugin* com.smartbear.soapui:soapui-pro-maven-plugin* com.github.redfish4ktc.soapui:maven-soapui-extension-plugin* com.github.searls:jasmine-maven-plugin* org.terracotta.maven.plugins:toolkit-resolver-plugin* org.scalatest:scalatest-maven-plugin* org.nanoko.playframework:play2-maven-pluginExamples of unknown/unsupported Maven testing plug-ins:* com.github.eirslett:frontend-maven-plugin:karma* com.kelveden:maven-karma-plugin:start* com.github.greengerong:maven-ng-protractor:run* others, doubtless...In the general 'unknown Maven plug-in' case neither of these assumptions are likely to be valid e.g., com.github.eirslett:frontend-maven-plugin running Karma tests, the goal is 'karma' (phase = 'test' or 'integration-test', typically) and the test output directory is configured in a separate karma.conf.js file.Overall, this means there is no general solution for reporting standard JUnit-format results that have been placed in the Maven-standard location for such results, other than to use only plug-ins that the Jenkins Maven plugin actually knows about! This is inflexible and an unreasonable limitation for a general-purpose CI tool and a highly extensible build tool. I see three possible solutions:# The Jenkins Job configuration for Maven projects provides some declarative means to identify additional test reports.-- PROs:--- straightforward to configure--- no Jenkins-specific POM changes required--- only one set of changes required-- CONs:--- requires explicit configuration in every Jenkins Maven job# Develop a Maven plug-in that could be incorporated into a POM's pluginManagement section purely as the means to indicate that a given plug-in execution (specified as the groupdId, artifactId, version, goal and phase of the otherwise unknown-to-Jenkins Maven test plug-in) produces test results in the specified directory).-- PROs:--- should work OOTB in any up-to-date Jenkins installation--- the Maven plug-in could be extended to cover additional capabilities where Jenkins' built-in Maven integration is inadquate-- CONs:--- additional POM
[JIRA] [docker-plugin] (JENKINS-31397) Docker plugin does not provision container
Title: Message Title sébastien glon created an issue Jenkins / JENKINS-31397 Docker plugin does not provision container Issue Type: Bug Assignee: magnayn Components: docker-plugin Created: 04/Nov/15 3:06 PM Environment: jenkins:1.625.1 docker: 1.8.1 docker plugin 0.15.0 Priority: Major Reporter: sébastien glon My jenkins is docker image jenkins:latest I have configured access to my docker remote api and test pass. I have adding template image: evarga/jenkins-slave but i have always this line: ov 04, 2015 3:01:42 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFO: Will provision 'evarga/jenkins-slave', for label: 'jenkins-slave', in cloud: 'api-docker' Nov 04, 2015 3:01:42 PM com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlave INFO: Not Provisioning 'evarga/jenkins-slave'; Server 'api-docker' full with '1' container(s)
[JIRA] [workflow-plugin] (JENKINS-31391) Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Title: Message Title
Olli Sivonen updated an issue
Jenkins / JENKINS-31391
Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Change By:
Olli Sivonen
URL:
https://groups.google.com/ forum d / #!searchin topic /jenkinsci-users/ workflow$20EXECUTOR/jenkinsci-users/ 2pPu8s25yDE/ zD7VOX8NgU4J discussion
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title
Matthew Skevington edited a comment on JENKINS-30317
Re: api should return the queue url in location header for parameterized builds
I am having the same problem. It appears to be happening when you POST to a build containing multipart form data. For example:{code:java}curl -i curl.log -X POST http://localhost:8080/jenkins/job/TestProject1/build?BuildType=UsingBuild --user mskevington user :password --form file0=@Documents/buildTest1.xml --form json='{"parameter": [{"name":"build.xml", "file":"file0"},{"name" : "BuildType", "value" : "JSON_BUILD"}]}'{code}*Returns:*{code:java}HTTP/1.1 200 OKDate: Wed, 04 Nov 2015 11:50:47 GMTServer: ApacheLast-Modified: Wed, 13 Feb 2013 14:51:29 GMTETag: "38c26e-0-4d59c46f63e40"Accept-Ranges: bytesContent-Length: 0Vary: Accept-EncodingContent-Type: text/htmlHTTP/1.1 100 ContinueHTTP/1.1 201 CreatedServer: Apache-Coyote/1.1X-Content-Type-Options: nosniffLocation: http://localhost:8080/jenkins/job/TestProject1/Content-Length: 0Date: Wed, 04 Nov 2015 11:51:05 GMT{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord updated an issue Jenkins / JENKINS-31019 Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Change By: James Nord Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31391) Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Title: Message Title
Olli Sivonen created an issue
Jenkins / JENKINS-31391
Environment variable EXECUTOR_NUMBER should be usable inside node{} block
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
04/Nov/15 11:59 AM
Environment:
workflow-plugin 1.10.1
Labels:
environment-variables
Priority:
Minor
Reporter:
Olli Sivonen
Among few other environment variables that are generally available in freestyle job, EXECUTOR_NUMBER is not exposed in workflows.
Referencing to the discussion in the attached URL, I would like to see this environment variable exposed especially inside node{} blocks where it makes the most sense. We have a similar use case as described in the discussion where workspaces are allocated based on the executor number, and currently workflow cannot handle this situation.
[JIRA] [job-dsl-plugin] (JENKINS-31387) CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild'
Title: Message Title Gabor Vasko-Szedlar edited a comment on JENKINS-31387 Re: CopyArtifact: add option 'allowUpstreamDependencies' to 'upstreamBuild' I can send a have sent the pull request if you think . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title
Matthew Skevington edited a comment on JENKINS-30317
Re: api should return the queue url in location header for parameterized builds
I am having the same problem. It appears to be happening when you POST to a build containing multipart form data. For example:{code:java}curl -i curl.log -X POST http://localhost:8080/jenkins/job/TestProject1/build? BuildType=UsingBuild --user user:password --form file0=@Documents/buildTest1.xml --form json='{"parameter": [{"name":"build.xml", "file":"file0"},{"name" : "BuildType", "value" : "JSON_BUILD"}]}'{code}*Returns:*{code:java}HTTP/1.1 200 OKDate: Wed, 04 Nov 2015 11:50:47 GMTServer: ApacheLast-Modified: Wed, 13 Feb 2013 14:51:29 GMTETag: "38c26e-0-4d59c46f63e40"Accept-Ranges: bytesContent-Length: 0Vary: Accept-EncodingContent-Type: text/htmlHTTP/1.1 100 ContinueHTTP/1.1 201 CreatedServer: Apache-Coyote/1.1X-Content-Type-Options: nosniffLocation: http://localhost:8080/jenkins/job/TestProject1/Content-Length: 0Date: Wed, 04 Nov 2015 11:51:05 GMT{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title James Nord updated an issue Jenkins / JENKINS-31019 Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Change By: James Nord Labels: bytecode-compatibility-transformer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-31393) Git plugin fetches all branches before fetching the specified refspec
Title: Message Title Marco Sacchetto created an issue Jenkins / JENKINS-31393 Git plugin fetches all branches before fetching the specified refspec Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 04/Nov/15 12:59 PM Environment: Jenkins 1.609.1, Git plugin 2.4.0, Git Client plugin 1.18.0, Centos 6 Labels: git plugin jenkins Priority: Major Reporter: Marco Sacchetto We have a project in several branches where just one branch is needed to build at a time. Some other branches contain a lot of unneeded data. The correct refspec is specified in the job's configuration. But when the job is run, Jenkins first downloads all the refs: > /usr/bin/git -c core.askpass=true fetch --tags --progress **url here** +refs/heads/:refs/remotes/origin/ # timeout=30 Only then, after adding the remote and other operations, it uses the specified ref: > /usr/bin/git -c core.askpass=true fetch --tags --progress **url here** +refs/heads/master:refs/remotes/origin/master # timeout=30 This leads to a big waste of time, as lots of data is actually downloaded but not
[JIRA] [maven-plugin] (JENKINS-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Title: Message Title
Adrian Price updated an issue
Jenkins / JENKINS-31258
Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Change By:
Adrian Price
The Jenkins Maven plug-in ignores JUnit format files in the test results directory ($\{project.build.directory\}/surefire-reports by default). Debugging revealed the cause to be that maven-plugin knows about certain\* test-capable MOJOs and attempts to support unknown MOJOs by making the following unjustifiable assumptions:# that the MOJO will target the 'test' goal or similar# that the MOJO configuration will have a 'reportsDirectory' property\* maven testing plug-ins known to the Jenkins Maven plug-in / project type as of 2014-12-04 13:40:29:* org.apache.maven.plugins:maven-surefire-plugin* net.kennychua:phantomjs-qunit-runner* org.apache.maven.plugins:maven-failsafe-plugin* com.sun.maven:maven-junit-plugin* org.sonatype.flexmojos:flexmojos-maven-plugin* org.sonatype.tycho:maven-osgi-test-plugin* org.eclipse.tycho:tycho-surefire-plugin* com.jayway.maven.plugins.android.generation2:maven-android-plugin* com.jayway.maven.plugins.android.generation2:android-maven-plugin* org.codehaus.mojo:gwt-maven-plugin* com.smartbear.soapui:soapui-maven-plugin* com.smartbear.soapui:soapui-pro-maven-plugin* com.github.redfish4ktc.soapui:maven-soapui-extension-plugin* com.github.searls:jasmine-maven-plugin* org.terracotta.maven.plugins:toolkit-resolver-plugin* org.scalatest:scalatest-maven-plugin* org.nanoko.playframework:play2-maven-pluginExamples of unknown/unsupported Maven testing plug-ins:* com.github.eirslett:frontend-maven-plugin:karma* com.kelveden:maven-karma-plugin:start* com.github.greengerong:maven-ng-protractor:run* others, doubtless...In the general 'unknown Maven plug-in' case neither of these assumptions are likely to be valid e.g., com.github.eirslett:frontend-maven-plugin running Karma tests, the goal is 'karma' (phase = 'test' or 'integration-test', typically) and the test output directory is configured in a separate karma.conf.js file.Overall, this means there is no general solution for reporting standard JUnit-format results that have been placed in the Maven-standard location for such results, other than to use only plug-ins that the Jenkins Maven plugin actually knows about! This is inflexible and an unreasonable limitation for a general-purpose CI tool and a highly extensible build tool. I see two possible solutions:# The Jenkins Job configuration for Maven projects provides some declarative means to identify additional test reports.-- PROs:--- straightforward to configure--- no Jenkins-specific POM changes required-- - only one set of changes required-- CONs:--- requires explicit configuration in every Jenkins Maven job# Develop a Maven plug-in that could be incorporated into a POM's pluginManagement section purely as the means to indicate that a given plug-in execution (specified as the groupdId, artifactId, version, goal and phase of the otherwise unknown-to-Jenkins Maven test plug-in) produces test results in the specified directory).-- PROs:--- should work OOTB in any up-to-date Jenkins installation--- the Maven plug-in could be extended to cover additional capabilities where Jenkins' built-in Maven integration is inadquate-- CONs:--- additional POM
[JIRA] [maven-plugin] (JENKINS-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Title: Message Title
Adrian Price updated an issue
Jenkins / JENKINS-31258
Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins
Change By:
Adrian Price
The Jenkins Maven plug-in ignores JUnit format files in the test results directory ($\{project.build.directory\}/surefire-reports by default). Debugging revealed the cause to be that maven-plugin knows about certain\* test-capable MOJOs and attempts to support unknown MOJOs by making the following unjustifiable assumptions:# that the MOJO will target the 'test' goal or similar# that the MOJO configuration will have a 'reportsDirectory' property\* maven testing plug-ins known to the Jenkins Maven plug-in / project type as of 2014-12-04 13:40:29:* org.apache.maven.plugins:maven-surefire-plugin* net.kennychua:phantomjs-qunit-runner* org.apache.maven.plugins:maven-failsafe-plugin* com.sun.maven:maven-junit-plugin* org.sonatype.flexmojos:flexmojos-maven-plugin* org.sonatype.tycho:maven-osgi-test-plugin* org.eclipse.tycho:tycho-surefire-plugin* com.jayway.maven.plugins.android.generation2:maven-android-plugin* com.jayway.maven.plugins.android.generation2:android-maven-plugin* org.codehaus.mojo:gwt-maven-plugin* com.smartbear.soapui:soapui-maven-plugin* com.smartbear.soapui:soapui-pro-maven-plugin* com.github.redfish4ktc.soapui:maven-soapui-extension-plugin* com.github.searls:jasmine-maven-plugin* org.terracotta.maven.plugins:toolkit-resolver-plugin* org.scalatest:scalatest-maven-plugin* org.nanoko.playframework:play2-maven-pluginExamples of unknown/unsupported Maven testing plug-ins:* com.github.eirslett:frontend-maven-plugin:karma* com.kelveden:maven-karma-plugin:start* com.github.greengerong:maven-ng-protractor:run* others, doubtless...In the general 'unknown Maven plug-in' case neither of these assumptions are likely to be valid e.g., com.github.eirslett:frontend-maven-plugin running Karma tests, the goal is 'karma' (phase = 'test' or 'integration-test', typically) and the test output directory is configured in a separate karma.conf.js file.Overall, this means there is no general solution for reporting standard JUnit-format results that have been placed in the Maven-standard location for such results, other than to use only plug-ins that the Jenkins Maven plugin actually knows about! This is inflexible and an unreasonable limitation for a general-purpose CI tool and a highly extensible build tool. I see two possible solutions:# The Jenkins Job configuration for Maven projects should provide provides some declarative means to identify additional test reports. -- PROs:--- straightforward to configure--- no Jenkins-specific POM changes required-- CONs:--- requires explicit configuration in every Jenkins Maven job# Develop a Maven plug-in that could be incorporated into a POM's pluginManagement section purely as the means to indicate that a given plug-in execution (specified as the groupdId, artifactId, version, goal and phase of the otherwise unknown-to-Jenkins Maven test plug-in) produces test results in the specified directory).-- PROs:--- should work OOTB in any up-to-date Jenkins installation--- the Maven plug-in could be extended to cover additional capabilities where Jenkins' built-in Maven integration is inadquate-- CONs:--- additional POM complexity purely to
[JIRA] [htmlpublisher-plugin] (JENKINS-31366) MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget'
Title: Message Title Daniel Spilker commented on JENKINS-31366 Re: MissingFieldException: No field 'wrapperName' found in class 'htmlpublisher.HtmlPublisherTarget' See https://github.com/jenkinsci/htmlpublisher-plugin/pull/21 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-31392) Jenkins groovy script to get triggered build number
Title: Message Title
Amir Sinay created an issue
Jenkins / JENKINS-31392
Jenkins groovy script to get triggered build number
Issue Type:
Task
Assignee:
vjuranek
Components:
groovy-plugin
Created:
04/Nov/15 12:03 PM
Labels:
jenkins groovy
Priority:
Minor
Reporter:
Amir Sinay
I'm trying to write down a script that will get the Build Number of a Build that has been triggered by another job. For example: I have a build job that calls two other jobs(Call/trigger builds on other project). When the main job is finished with success I would like to get the number of the first build job that was triggered from within. The script I'm trying to run founds the main job, however I can't get in any way the build number of the triggered job.
def job = jenkins.model.Jenkins.instance.getItem("Hourly")
job.builds.each {
def build = it
if (it.getResult().toString().equals("SUCCESS")) {The rest of the code should go here!}
I was trying to find it in the Jenkins java-doc API and online, however without any luck. Can somebody please help me with that?
P.S. The script runs
[JIRA] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title
Matthew Skevington commented on JENKINS-30317
Re: api should return the queue url in location header for parameterized builds
I am having the same problem. It appears to be happening when you POST to a build containing multipart form data. For example:
curl -i curl.log -X POST http://localhost:8080/jenkins/job/TestProject1/build?BuildType=UsingBuild --user mskevington:password --form file0=@Documents/buildTest1.xml --form json='{"parameter": [{"name":"build.xml", "file":"file0"},{"name" : "BuildType", "value" : "JSON_BUILD"}]}'
Returns:
HTTP/1.1 200 OK
Date: Wed, 04 Nov 2015 11:50:47 GMT
Server: Apache
Last-Modified: Wed, 13 Feb 2013 14:51:29 GMT
ETag: "38c26e-0-4d59c46f63e40"
Accept-Ranges: bytes
Content-Length: 0
Vary: Accept-Encoding
Content-Type: text/html
HTTP/1.1 100 Continue
HTTP/1.1 201 Created
Server: Apache-Coyote/1.1
X-Content-Type-Options: nosniff
Location: http://localhost:8080/jenkins/job/TestProject1/
Content-Length: 0
Date: Wed, 04 Nov 2015 11:51:05 GMT
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [external-resource-dispatcher-plugin] (JENKINS-28027) Allow Parameter Values to be used for Selection Criteria Value
Title: Message Title Sean Jones assigned an issue to Sean Jones Jenkins / JENKINS-28027 Allow Parameter Values to be used for Selection Criteria Value Change By: Sean Jones Assignee: rsandell Sean Jones Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
