[JIRA] [view-job-filters-plugin] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Title: Message Title Tony Wallace commented on JENKINS-21862 Re: Build Filter (Wrapper) column not properly showing results for Parameterized builds If interested, this is what I am trying to accomplish. I do not wish to maintain multiple, mostly redundant projects where the only difference is GERRIT_BRANCH or some other build Parameter value. However, I do wish to provide users with a convenient way to visually review recent build results for just the projects and GERRIT_BRANCHes of interest to them, including the values of the important build Parameters all on the same page, without being overwhelmed. To that end, I have already configured a customized Build Description for all projects. This build Description appears in the build History that appears on the RHS of any individual project page. Now I am trying to make Jenkins display a View showing the build History for multiple projects in one page, where (in order of highest-to-lowest priority), (a) The View's Build History only includes builds which satisfy a Parameterized builds filter - e.g., the value of GERRIT_BRANCH in that build matched RB12.34. If there was a filter based on regex match against Build Description, I could use that instead of Parameterized builds filter. (b) The main view (Project list with columns) should only include projects for which at least one completed build satisfied the Parameterized builds filter, e.g. GERRIT_BRANCH matched RB12.34. More importantly, for each project included in the main view, the Build Filter (wrapper) column would display Status, Weather, Build Description, Build parameters, etc values corresponding to the last completed build which satisfied the Parameterized builds filter. (c) As above, and the Build Filter (wrapper) column would also display accurate values for Last success, Last failure, etc, based on the subset of builds which satisfied the Parameterized builds filter. Thanks for reading. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [delivery-pipeline-plugin] (JENKINS-29806) Ability to split sequence of jobs into multiple pipelines
Title: Message Title Dawid Malinowski resolved as Fixed Jenkins / JENKINS-29806 Ability to split sequence of jobs into multiple pipelines Change By: Dawid Malinowski 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] [delivery-pipeline-plugin] (JENKINS-30051) Extend description with more build results
Title: Message Title Dawid Malinowski commented on JENKINS-30051 Re: Extend description with more build results Fixed in https://github.com/Diabol/delivery-pipeline-plugin/pull/148 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-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs created an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 25/Aug/15 4:55 PM Environment: Jenkins version: 1.609.2 GIT Plugin version: 2.4.0 git version: 1.7.10.4 Labels: polling pollscm git-plugin Priority: Minor Reporter: Ferenc Kovacs I have a job which is set to poll a repository, and also uses the Polling uses certain paths behavior (include) along with the Force polling using workspace behavior. Polling worked properly when the workspace was already present, but fter wiping the workspace it did trigger a build. When I made jenkins to poll the repo via calling /git/notifyCommit?url="" I got the following response: Scheduled polling of chef-diff-app-apt-mirror-manual but my job was not built looking into the git polling log for this job I've seen this: Started on Aug 25, 2015 9:43:02 AM No workspace is available, so can’t check for updates.
[JIRA] [test1] (TEST-51) BUg1
Title: Message Title Kunal Samel created an issue test / TEST-51 BUg1 Issue Type: Bug Assignee: Kunal Samel Attachments: Issue List _ 01_Jul_15.xlsx Components: test1 Created: 25/Aug/15 3:40 PM Labels: exception Priority: Critical Reporter: Kunal Samel Add Comment
[JIRA] [scriptler-plugin] (JENKINS-30130) Reload/update scriptler catalog from disk without need to restart Jenkins server
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-30130 Reload/update scriptler catalog from disk without need to restart Jenkins server Issue Type: Improvement Assignee: Dominik Bartholdi Components: scriptler-plugin Created: 25/Aug/15 3:43 PM Priority: Minor Reporter: Ioannis Moutsatsos Scriprler scripts are code. As such, they are frequently managed using a code management repository SVN, git etc. However, when a new scriptlet is checked out in the scripts folder, it does not become available until the Jenkins server is restarted. Restarting the server in a busy environment, is a hassle. Please, provide an option to reload/update the local Scriptler catalog (the config.xml file) from disk without the need to restart the server. Something similar to the job reload approach should be fine! Add Comment
[JIRA] [core] (JENKINS-30128) Plugin manager reports wrong dependencies in rest api
Title: Message Title Daniel Beck commented on JENKINS-30128 Re: Plugin manager reports wrong dependencies in rest api A corollary is that you will never have any implied dependencies when running the plugin using hpi:run, because then Jenkins is the exact version the plugin is developed for. Given the information above, is there still a bug left here? It doesn't really look like it to me. Note that mapdb-api is in fact part of the first list. 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-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs updated an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Change By: Ferenc Kovacs Ihaveajobwhichissettopollarepository,andalsousesthePollingusescertainpathsbehavior(include)alongwiththeForcepollingusingworkspacebehavior.Pollingworkedproperlywhentheworkspacewasalreadypresent,butfterwipingtheworkspaceitdidtriggerabuild.WhenImadejenkinstopolltherepoviacalling/git/notifyCommit?url="" />Scheduledpollingofchef-diff-app-apt-mirror-manualbutmyjobwasnotbuiltlookingintothegitpollinglogforthisjobI'veseenthis:StartedonAug25,20159:43:02AMNoworkspaceisavailable,socan’tcheckforupdates.(nonexisting_workspace)Done.Took2msNochanges I'vetriedtosimplifymybuildtoseeifthatresolvestheissue,andrealizedthatremovingtheRestrictwherethisprojectcanberunsettingssolvestheissue,eventhoughtthatinmysetupthissettingwasredundantastheonlynodeavailable/allowedtorunjobswithoutexplicitnoderestrictionswasthesameasIwasspecifyingwithmylabel. AfterIremovedtherestrictlabelandcurled/git/notifyCommitagainIgotabuildstartedandthisinmygitpollinglog:StartedonAug25,20159:55:41AMNoworkspaceisavailable,socan’tcheckforupdates.Schedulinganewbuildtogetaworkspace.(nonexisting_workspace)Done.Took1msChangesfound I'vetriedtosimplifymybuildtoseeifthatresolvestheissue,andrealizedthatremovingtheRestrictwherethisprojectcanberunsettingssolvestheissue,eventhoughtthatinmysetupthissettingwasredundantastheonlynodeavailable/allowedtorunjobswithoutexplicitnoderestrictionswasthesameasIwasspecifyingwithmylabel. Letmeknowifyouneedanymoreinfotoreproducetheissue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-30131) build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label
Title: Message Title Ferenc Kovacs updated an issue Jenkins / JENKINS-30131 build won't trigger on an empty workspace if workspace is needed for polling but build is restricted to a label Change By: Ferenc Kovacs Ihaveajobwhichissettopollarepository,andalsousesthePollingusescertainpathsbehavior(include)alongwiththeForcepollingusingworkspacebehavior.Pollingworkedproperlywhentheworkspacewasalreadypresent,butfterwipingtheworkspaceitdidtriggerabuild.WhenImadejenkinstopolltherepoviacalling/git/notifyCommit?url="" />Scheduledpollingofchef-diff-app-apt-mirror-manualbutmyjobwasnotbuiltlookingintothegitpollinglogforthisjobI'veseenthis:StartedonAug25,20159:43:02AMNoworkspaceisavailable,socan’tcheckforupdates.(nonexisting_workspace)Done.Took2msNochanges After I removedtherestrictlabelandcurled/git/notifyCommitagainIgotabuildstartedandthisinmygitpollinglog:StartedonAug25,20159:55:41AMNoworkspaceisavailable,socan’tcheckforupdates.Schedulinganewbuildtogetaworkspace.(nonexisting_workspace)Done.Took1msChangesfoundI 'vetriedtosimplifymybuildtoseeifthatresolvestheissue,andrealizedthatremovingtheRestrictwherethisprojectcanberunsettingssolvestheissue,eventhoughtthatinmysetupthissettingwasredundantastheonlynodeavailable/allowedtorunjobswithoutexplicitnoderestrictionswasthesameasIwasspecifyingwithmylabel.Letmeknowifyouneedanymoreinfotoreproducetheissue. 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,
[JIRA] [core] (JENKINS-26398) Fix createSlave for RestartableJenkinsRule
Title: Message Title Jesse Glick commented on JENKINS-26398 Re: Fix createSlave for RestartableJenkinsRule I think would suffice to add methods to JenkinsRule. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-30120) Plugin does not work with Mercurial 3.4.2
Title: Message Title Jesse Glick started work on JENKINS-30120 Change By: Jesse Glick Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-30122) CopyArtifact does not work in a secured environment with Workflow and Authorize Project
Title: Message Title Jesse Glick started work on JENKINS-30122 Change By: Jesse Glick Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test1] (TEST-51) BUg1
Title: Message Title Kunal Samel commented on TEST-51 Re: BUg1 HI I'm very new to Jira 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] [test1] (TEST-51) BUg1
Title: Message Title Kunal Samel started work on TEST-51 Change By: Kunal Samel Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test1] (TEST-51) BUg1
Title: Message Title Kunal Samel updated an issue test / TEST-51 BUg1 Change By: Kunal Samel Tasktasktasks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-29806) Ability to split sequence of jobs into multiple pipelines
Title: Message Title Noah Nordrum commented on JENKINS-29806 Re: Ability to split sequence of jobs into multiple pipelines I think I've got a decent first crack at this. Here's my strategy: I added a lastJobRegex where I terminate searching for jobs/tasks when a task id matches the specified regex. I'm also looking at adding a hideJobRegex to satisfy JENKINS-26210. Thoughts? PR coming shortly (hopefully). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-29806) Ability to split sequence of jobs into multiple pipelines
Title: Message Title Dawid Malinowski commented on JENKINS-29806 Re: Ability to split sequence of jobs into multiple pipelines Fixed in https://github.com/Diabol/delivery-pipeline-plugin/pull/144 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-22843) Show test result in task if any
Title: Message Title Dawid Malinowski closed an issue as Duplicate Fixed in https://issues.jenkins-ci.org/browse/JENKINS-30051 Jenkins / JENKINS-22843 Show test result in task if any Change By: Dawid Malinowski Status: Open Closed Assignee: DawidMalinowski 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] [cloudfoundry-plugin] (JENKINS-29514) Temporary files aren't cleaned before Jenkins master is restarted
Title: Message Title William Gautier closed an issue as Fixed Jenkins / JENKINS-29514 Temporary files aren't cleaned before Jenkins master is restarted Change By: William Gautier Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28602) Error: Default domain calculated from api domain
Title: Message Title William Gautier closed an issue as Fixed Jenkins / JENKINS-28602 Error: Default domain calculated from api domain Change By: William Gautier Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier closed an issue as Fixed Jenkins / JENKINS-28311 Create CloudFoundry services via Plug-in Change By: William Gautier Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete Not quite sure I followed that. It sounds like you know of a way of a way to reproduce this from scratch. If so, that would be very valuable 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] [job-dsl-plugin] (JENKINS-30127) Job DSL syntax should allow nextBuildNumber to be set at create/update time
Title: Message Title
Alexander Komarov created an issue
Jenkins / JENKINS-30127
Job DSL syntax should allow nextBuildNumber to be set at create/update time
Issue Type:
New Feature
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
25/Aug/15 2:27 PM
Priority:
Minor
Reporter:
Alexander Komarov
Currently the Jenkins Next Build Number plugin permits one to set the value for the next $BUILD_NUMBER through user interaction (it is an action). For Job DSL users, the natural place to set job configuration details would be through the DSL.
Proposing extending the DSL as follows:
freeStyleJob(String name) { name(String name) *nextBuildNumber(int nextBuildNumber)* // etc... }
Add Comment
[JIRA] [workflow-plugin] (JENKINS-29739) Build step generator not including parameter when there is only one
Title: Message Title Jesse Glick started work on JENKINS-29739 Change By: Jesse Glick Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30127) Job DSL syntax should allow nextBuildNumber to be set at create/update time
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-30127
Job DSL syntax should allow nextBuildNumber to be set at create/update time
Change By:
Alexander Komarov
CurrentlytheJenkinsNextBuildNumberpluginpermitsonetosetthevalueforthenext$BUILD_NUMBERthroughuserinteraction(itisanaction).ForJobDSLusers,thenaturalplacetosetjobconfigurationdetailswouldbethroughtheDSL.ProposingextendingtheDSLasfollows:{code:title=DSLExample}freeStyleJob(Stringname){name(Stringname)nextBuildNumber(intnextBuildNumber)//Thisisnew//etc...}{code} Valueslowerthanthecurrentlypendingbuildnumberwillbeignored.Valueslessthan1willraiseaDSLvalidationerror.
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-30128) Plugin manager reports wrong dependencies in rest api
Title: Message Title Christopher Orr commented on JENKINS-30128 Re: Plugin manager reports wrong dependencies in rest api Move from INFRA to JENKINS, as this does not appear to be an infrastructure bug. The wiki is showing the correct dependencies, according to the Subversion Plugin pom.xml, and this data matches with the Update Centre JSON. The /pluginManager/api/json endpoint appears to show information about installed plugins, rather than available plugins. The URL in the original report here is CloudBees-internal, but the same issue can be reproduced here (Jenkins 1.609.1.2): https://jenkins.ci.cloudbees.com/pluginManager/api/json?depth=3 Looking through the list, this isn't limited to only the Subversion plugin — these same five plugins keep appearing as dependencies for lots of plugins, even for ones with no dependencies (e.g. external-monitor-job): matrix-auth, windows-slaves, antisamy-markup-formatter, matrix-project, junit This can also be reproduced on J-o-J (Jenkins 1.606): https://ci.jenkins-ci.org/pluginManager/api/json?depth=3 I could not reproduce this on my local Jenkins instance (running Jenkins 1.596.3). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30128) Plugin manager reports wrong dependencies in rest api
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-30128 Plugin manager reports wrong dependencies in rest api Change By: Christopher Orr Labels: plugin plugin -manager wiki 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-29169) RunWrapper.buildVariables should reflect downstream env vars
Title: Message Title Jesse Glick started work on JENKINS-29169 Change By: Jesse Glick Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. alexandre aubert, I'll have to configure a similar scenario using externals. 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-30127) Job DSL syntax should allow nextBuildNumber to be set at create/update time
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-30127
Job DSL syntax should allow nextBuildNumber to be set at create/update time
Change By:
Alexander Komarov
CurrentlytheJenkinsNextBuildNumberpluginpermitsonetosetthevalueforthenext$BUILD_NUMBERthroughuserinteraction(itisanaction).ForJobDSLusers,thenaturalplacetosetjobconfigurationdetailswouldbethroughtheDSL.ProposingextendingtheDSLasfollows:{code:title=DSLExample}freeStyleJob(Stringname){name(Stringname) * nextBuildNumber(intnextBuildNumber) * //Thisisnew //etc...}{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] [job-dsl-plugin] (JENKINS-30127) Job DSL syntax should allow nextBuildNumber to be set at create/update time
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-30127
Job DSL syntax should allow nextBuildNumber to be set at create/update time
Change By:
Alexander Komarov
CurrentlytheJenkinsNextBuildNumberpluginpermitsonetosetthevalueforthenext$BUILD_NUMBERthroughuserinteraction(itisanaction).ForJobDSLusers,thenaturalplacetosetjobconfigurationdetailswouldbethroughtheDSL.ProposingextendingtheDSLasfollows: bq. {code:title=DSLExample} freeStyleJob(Stringname){ bq. name(Stringname) bq. *nextBuildNumber(intnextBuildNumber)* bq. //etc... bq. } bq. {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] [extra-columns-plugin] (JENKINS-30129) 'Build Parameters' column displays uresolved environment variable
Title: Message Title
erikgb created an issue
Jenkins / JENKINS-30129
'Build Parameters' column displays uresolved environment variable
Issue Type:
Bug
Assignee:
Fred G
Components:
extra-columns-plugin
Created:
25/Aug/15 3:27 PM
Priority:
Major
Reporter:
erikgb
We are using environment variables (Jenkins-configuration-Global properties--Environment variables) as default values of build parameters to our Jenkins deploy application builds: APPLICATION_DEPLOY_VERSION=x.y.z
Somehow there is a requirement to indicate the latest deployed application version, per application deploy job. Introducing a 'Build parameters' column in the Jenkins view seems to fulfill this requirement. This works fine if the user overrides the default value of the version build parameter ($ {APPLICATION_DEPLOY_VERSION}). But if the user accepts the default value (${APPLICATION_DEPLOY_VERSION}
), the 'Build parameters' column indicates that the latest build was invoked with the parameter value '$ {APPLICATION_DEPLOY_VERSION}
'.
I think the 'Build parameters' column should show the resolved build parameter value, if based on an environment variable, or any other parameter substitution mechanism.
[JIRA] [core] (JENKINS-30128) Plugin manager reports wrong dependencies in rest api
Title: Message Title Christopher Orr assigned an issue to Unassigned Jenkins / JENKINS-30128 Plugin manager reports wrong dependencies in rest api Change By: Christopher Orr Assignee: R.TylerCroy 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-30128) Plugin manager reports wrong dependencies in rest api
Title: Message Title Christopher Orr moved an issue Jenkins / JENKINS-30128 Plugin manager reports wrong dependencies in rest api Change By: Christopher Orr Project: Infrastructure Jenkins Key: INFRA JENKINS - 352 30128 Workflow: classicdefaultworkflow JNJira Component/s: core Component/s: wiki Component/s: ci Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [extra-columns-plugin] (JENKINS-30129) 'Build Parameters' column displays uresolved environment variable
Title: Message Title
Erik Godding Boye updated an issue
Jenkins / JENKINS-30129
'Build Parameters' column displays uresolved environment variable
Change By:
Erik Godding Boye
Weareusingenvironmentvariables(Jenkins-configuration-Globalproperties--Environmentvariables)asdefaultvaluesofbuildparameterstoourJenkinsdeployapplicationbuilds:APPLICATION_DEPLOY_VERSION=x.y.zSomehowthereisarequirementtoindicatethelatestdeployedapplicationversion,perapplicationdeployjob.Introducinga'Buildparameters'columnintheJenkinsviewseemstofulfillthisrequirement.Thisworksfineiftheuseroverridesthedefaultvalueoftheversionbuildparameter($ \ {APPLICATION_DEPLOY_VERSION \ }).Butiftheuseracceptsthedefaultvalue($ \ {APPLICATION_DEPLOY_VERSION \ }),the'Buildparameters'columnindicatesthatthelatestbuildwasinvokedwiththeparametervalue'$ \ {APPLICATION_DEPLOY_VERSION \ }'.Ithinkthe'Buildparameters'columnshouldshowthe*resolvedbuildparametervalue*,ifbasedonanenvironmentvariable,oranyotherparametersubstitutionmechanism.
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] [xvnc-plugin] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-19139 Re: Xvnc plugin fails if the job has a space in the name Code changed in jenkins User: Robert Sandell Path: src/main/java/hudson/plugins/xvnc/Xvnc.java src/main/resources/hudson/plugins/xvnc/Xvnc/global.jelly src/main/resources/hudson/plugins/xvnc/Xvnc/help-xauthorityInFsRoot.html src/test/java/hudson/plugins/xvnc/XvncTest.java http://jenkins-ci.org/commit/xvnc-plugin/1ce66992dbc518d460943b31a640055d4ff9543a Log: Configuration for placing the xauthority file in node fs root Added a configuration option to place the temporary xauthority file on the fs root of the node instead of the in the build's workspace. This can be used as a workaround for JENKINS-19139 if the path to the fs root doesn't contain any spaces but for example the folder to the job does. 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] [analysis-collector-plugin] (JENKINS-30125) Add Workflow compatibility
Title: Message Title Antonio Muiz commented on JENKINS-30125 Re: Add Workflow compatibility PR sent: https://github.com/jenkinsci/analysis-collector-plugin/pull/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] [xvnc-plugin] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Title: Message Title Jesse Glick commented on JENKINS-19139 Re: Xvnc plugin fails if the job has a space in the name Fix/report that bug in vncserver …and did anyone ever actually do that? If so, is there a link? Status of fix in various distributions? Should this be assigned to rsandell who is apparently working on a fix in https://github.com/jenkinsci/xvnc-plugin/pull/8 ? 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-30128) Plugin manager reports wrong dependencies in rest api
Title: Message Title Daniel Beck commented on JENKINS-30128 Re: Plugin manager reports wrong dependencies in rest api The weird additional dependencies are from detached (bundled) plugins. Basically, when a plugin depends on an older Jenkins release, you're running a newer release, and a feature that used to be in core was detached from it since then, the plugin will get these (implied) dependencies injected during runtime. Otherwise, the detached plugin would not be on the plugin's class path and you'll get ClassNotFoundExceptions and the like if the plugin actually uses those former core features. (Of course this is a mess when users disable the detached plugins, because the UI does not prevent dependencies from being disabled, but that's a different issue.) The newer your plugin release (and therefore presumably the Jenkins parent release) is, the fewer additional entries you'll get. So while some plugins may have one or even none such entries, others will have a dozen or so implied dependencies. 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] [analysis-collector-plugin] (JENKINS-30125) Add Workflow compatibility
Title: Message Title Antonio Muiz updated an issue Jenkins / JENKINS-30125 Add Workflow compatibility Change By: Antonio Muiz Summary: AddWorkflow compatiility compatibility 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] [view-job-filters-plugin] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Title: Message Title Tony Wallace reopened an issue Jenkins 1.609.2 with View job filters 1.27. Other plugins are up-to-date w.r.t. LTS versions. 1. Add a new list view (in My Views) Select filter build queue and filter build executors job filters - All selected jobs. Do not select projects by checkbox. Do select Use regex to include jobs into the view and enter regex. Add new column build parameters, showing value of parameter GERRIT_BRANCH. Result: (a) The view includes the expected list of projects selected by job name, with GERRIT_BRANCH column showing different values depending on the last completed build of each project. Good. 2. Edit view and add a new parameterized jobs filter - parameter name is GERRIT_BRANCH, matching value is RB12.34, all options un-checked, match type is exclude unmatched Result: (a) The view's project list includes fewer projects, only those where GERRIT_BRANCH matched RB12.34 in the last completed build. Good. (b) The Build History only includes builds where GERRIT_BRANCH matched. Good. 3. Edit view, go to parameterized jobs filter, select match against this many previous builds, blank or zero for all Result: (a) The view's project list includes more projects, with GERRIT_BRANCH column showing different values depending on the last completed build of each project. Good. (b) The Build History now includes builds that should have been filtered by the parameterized jobs filter. Bad. 4. Edit view and add a new build filter (wrapper) column, select build parameters, show the single parameter GERRIT_BRANCH. This is the same as the column we added before, except this is inside the build filter wrapper. Result: (a) the new filtered build parameters column is empty, when it should show the same GERRIT_BRANCH as the unfiltered Build Parameters column. Bad. (b) The jenkins server log shows exceptions like below, one for each project in the View's project list: Aug 25, 2015 9:35:10 AM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.getBuildParameters(job) in /user/haha/my-views/view/hoho/. Reason: java.lang.IllegalStateException: /local/opt/jenkins/8060/jenkins_home/jobs/full-SC-w2012-vc12-x86/builds/833 already existed; will not overwite with full-SC-w2012-vc12-x86 #833 java.lang.IllegalStateException: /local/opt/jenkins/8060/jenkins_home/jobs/full-SC-w2012-vc12-x86/builds/833 already existed; will not overwite with full-SC-w2012-vc12-x86 #833 at hudson.model.RunMap.put(RunMap.java:187) at hudson.views.BuildFilterColumn$JobWrapper._getRuns(BuildFilterColumn.java:125) at hudson.model.Job.getLastBuild(Job.java:858) at jenkins.plugins.extracolumns.BuildParametersColumn.getBuildParameters(BuildParametersColumn.java:63) ... much more traceback Jenkins / JENKINS-21862 Build Filter (Wrapper) column not properly showing results for Parameterized builds Change By: Tony Wallace
[JIRA] [job-dsl-plugin] (JENKINS-30127) Job DSL syntax should allow nextBuildNumber to be set at create/update time
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-30127
Job DSL syntax should allow nextBuildNumber to be set at create/update time
Change By:
Alexander Komarov
CurrentlytheJenkinsNextBuildNumberpluginpermitsonetosetthevalueforthenext$BUILD_NUMBERthroughuserinteraction(itisanaction).ForJobDSLusers,thenaturalplacetosetjobconfigurationdetailswouldbethroughtheDSL.ProposingextendingtheDSLasfollows: bq. freeStyleJob(Stringname){ bq. name(Stringname) bq. *nextBuildNumber(intnextBuildNumber)* bq. //etc... bq. } bq.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30132) Null Pointer Exception with disabled downstream job
Title: Message Title Greg Kresge created an issue Jenkins / JENKINS-30132 Null Pointer Exception with disabled downstream job Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 25/Aug/15 5:12 PM Environment: Jquery plugin: 1.7.2-1 Parameterized trigger plugin: 2.28 Build Pipeline Plugin: 1.4.7 Jenkins version: 1.624 Priority: Major Reporter: Greg Kresge Scenario: upstream job completing successfully, and it has multiple downstream jobs, some of which are disabled Result: Null pointer exception and no downstream jobs are started Output: Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered FATAL: null java.lang.NullPointerException at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687) at hudson.model.Build$BuildExecution.cleanUp(Build.java:200) at hudson.model.Run.execute(Run.java:1788) at
[JIRA] [maven-plugin] (JENKINS-24788) Cannot run program /bin/java on maven 3 projects
Title: Message Title
杨 唐 commented on JENKINS-24788
Re: Cannot run program /bin/java on maven 3 projects
try : ln -s $ {which java}
/bin/java
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-27902) Allow to pass additional request parameter for notifyCommit
Title: Message Title Bruce Yang commented on JENKINS-27902 Re: Allow to pass additional request parameter for notifyCommit Can anyone help show me how I can get the additional parameters in Jenkins Job? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-30112) Build-Blocker-Plugin does not work with Batch-Task-Plugin
Title: Message Title Dominik Jaeger updated an issue Jenkins / JENKINS-30112 Build-Blocker-Plugin does not work with Batch-Task-Plugin Change By: Dominik Jaeger Priority: Critical Blocker Suddenlyweseealotofthoseexceptions : .Afterithappensnobuildcanbescheduledanymore. Aug24,20155:00:04PMhudson.triggers.SafeTimerTaskrunSEVERE:Timertaskhudson.model.Queue$MaintainTask@1f721901failedjava.lang.ClassCastException:hudson.plugins.batch_task.BatchTaskcannotbecasttohudson.model.AbstractProjectathudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlockerQueueTaskDispatcher.java:199)athudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:108)athudson.model.Queue$JobOffer.canTake(Queue.java:300)athudson.model.Queue.maintain(Queue.java:1476)athudson.model.Queue$MaintainTask.doRun(Queue.java:2576)athudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)atjava.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)atjava.lang.Thread.run(Thread.java:744) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore
Title: Message Title Dominik Acri commented on JENKINS-29329 Re: Visual Studio/MSBuild projects can not be built implicitly anymore ahh sorry, Yes, it works now !! I did not add the cmake build step in jenkins because of the same error log but I missed that the cmake config step was now successfull. Thanks! – Build files have been written to: C:/Jenkins/workspace/Piratol/build ERROR: Failed to get value for CMAKE_BUILD_TOOL from c:\Jenkins\workspace\Piratol\build\CMakeCache.txt [build] $ cmake --build c:\Jenkins\workspace\Piratol\build Microsoft (R)-Buildmodul, Version 14.0.23107.0 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. Der Buildvorgang wurde am 25.08.2015 09:17:23 gestartet. ... c:/Jenkins/workspace/Piratol/source/source/base/baselib/CMakeLists.txt CMake does not need to re-run because C:\Jenkins\workspace\Piratol\build\source\base\baselib\CMakeFiles\generate.stamp is up-to-date. ClCompile: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\CL.exe /c /IC:\Jenkins\workspace\Piratol\build\source\base\baselib /Ic:\Jenkins\workspace\Piratol\source\source\base\baselib /Ic:\Jenkins\workspace\Piratol\source\source\base\baselib\src /Ic:\Jenkins\workspace\Piratol\source\source\base\baselib\include /Ic:\Jenkins\workspace\Piratol\3rdparty_3\3rdparty\x86\boost_1_59_0\include\boost-1_59 /Ic:\Jenkins\workspace\Piratol\3rdparty_3\3rdparty\x86\log4cpp-1.1.1 /Zi /nologo /W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D UNICODE /D _UNICODE /D _CRT_SECURE_NO_WARNINGS /D BOOST_ALL_NO_LIB /D BOOST_LIB_DIAGNOSTIC /D CMAKE_INTDIR=\Debug\ /D BaseLib_EXPORTS /D _WINDLL /D _UNICODE /D UNICODE /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR /FoBaseLib.dir\Debug /FdBaseLib.dir\Debug\vc140.pdb /Gd /TP /wd4290 /wd4251 /wd4275 /wd4996 /analyze- /errorReport:queue Link: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\link.exe /ERRORREPORT:QUEUE /OUT:C:\Jenkins\workspace\Piratol\build\build\debug\bin\BaseLibD.dll /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib c:\Jenkins\workspace\Piratol\3rdparty_3\3rdparty\x86\boost_1_59_0\lib\boost_filesystem-vc140-mt-gd-1_59.lib c:\Jenkins\workspace\Piratol\3rdparty_3\3rdparty\x86\boost_1_59_0\lib\boost_system-vc140-mt-gd-1_59.lib ... FinalizeBuildStatus: Die Datei Service.dir\Debug\Service.tlog\unsuccessfulbuild wird gel”scht. Aktualisieren des Timestamps von Service.dir\Debug\Service.tlog\Service.lastbuildstate. Die Erstellung von Projekt C:\Jenkins\workspace\Piratol\build\source\service\Service.vcxproj ist abgeschlossen (Standardziele). PrepareForBuild: Das Verzeichnis Win32\Debug\ALL_BUILD\ wird erstellt. Das Verzeichnis Win32\Debug\ALL_BUILD\ALL_BUILD.tlog\ wird erstellt. InitializeBuildStatus: Win32\Debug\ALL_BUILD\ALL_BUILD.tlog\unsuccessfulbuild wird erstellt, da AlwaysCreate angegeben wurde. CustomBuild: Building Custom Rule c:/Jenkins/workspace/Piratol/source/CMakeLists.txt CMake does not need to re-run because C:\Jenkins\workspace\Piratol\build\CMakeFiles\generate.stamp is up-to-date. FinalizeBuildStatus: Die Datei Win32\Debug\ALL_BUILD\ALL_BUILD.tlog\unsuccessfulbuild wird gel”scht. Aktualisieren des Timestamps von Win32\Debug\ALL_BUILD\ALL_BUILD.tlog\ALL_BUILD.lastbuildstate. Die Erstellung von Projekt c:\Jenkins\workspace\Piratol\build\ALL_BUILD.vcxproj ist abgeschlossen (Standardziele). Der Buildvorgang wurde erfolgreich ausgef�hrt. 0 Warnung(en) 0 Fehler Verstrichene Zeit 00:00:59.10 Finished: SUCCESS
[JIRA] [job-dsl-plugin] (JENKINS-29972) Unable to use custom SCM plugin Extension Point
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-29972 Unable to use custom SCM plugin Extension Point I attached the HPI with the fix. Change By: Daniel Spilker Attachment: job-dsl.hpi 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] [ec2-plugin] (JENKINS-5867) Allow Amazon EC2 Plugin to not require root access
Title: Message Title
YC Lian edited a comment on JENKINS-5867
Re: Allow Amazon EC2 Plugin to not require root access
Hi,Icanconfirmwhat[~nvitius]said.IamusingtheEC2pluginandhavingproblemtobuildfromanon-rootuseronaspotinstance. *Updated*:IretractwhatIsaid,itcouldbemanagedbycontrollingtheuserexecutingthe{{userdata}}script.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-30119) ERROR: svn: E155010: The node '/x/y/z' was not found. org.tmatesoft.svn.core.SVNException: svn: E155010: The node '/x/y/z' was not found. when building wit
Title: Message Title Martin Jost created an issue Jenkins / JENKINS-30119 ERROR: svn: E155010: The node '/x/y/z' was not found. org.tmatesoft.svn.core.SVNException: svn: E155010: The node '/x/y/z' was not found. when building with no workspace Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 25/Aug/15 8:42 AM Environment: Jenkins ver. 1.593 on RH6 (Red Hat Enterprise Linux Server release 6.5 (Santiago)) using jdk1.8.0_45 Subversion Plug-in 2.5.1 (SVN version set to 1.8) jenkins started directly; no reverse proxy or some such Labels: subversion workspace Priority: Minor Reporter: Martin Jost My job is configured with Repository depth immediates Use SVN update as much as possible
[JIRA] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Title: Message Title Gurvan Le Dromaguet commented on JENKINS-27547 Re: Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException Duplicated by JENKINS-27671 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title Sebastian Troy commented on JENKINS-29938 Re: Unable to serialize is reported when publishing doxygen generate html files I can reaffirm Marcel Beister's issue. As he is, I'm specifying a path to my Doxyfile (which is in the root directory) and I'm getting the exact same exception. I cannot confirm whether switching back a version fixes this as I do not have the permission to do so! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title
Sebastian Troy edited a comment on JENKINS-29938
Re: Unable to serialize is reported when publishing doxygen generate html files
IcanreaffirmMarcelBeister'sissue.Asheis,I'mspecifyingapathtomyDoxyfile(whichisintherootdirectory)andI'mgettingtheexactsameexception.IcannotconfirmwhetherswitchingbackaversionfixesthisasIdonothavethepermissiontodoso!{code:java}PublishingDoxygenHTMLresults.FATAL:errorjava.io.IOException:remotefileoperationfailed:/home/jenkins/build/workspace/QxTrunkDoxygenathudson.remoting.Channel@1096170:QxBuilder:java.io.IOException:Unabletoserializehudson.FilePath$FileCallableWrapper@5267bc athudson.FilePath.act(FilePath.java:987) athudson.FilePath.act(FilePath.java:969) athudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:223) athudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:177) athudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) athudson.model.Build$BuildExecution.post2(Build.java:185) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) athudson.model.Run.execute(Run.java:1766) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:381)Causedby:java.io.IOException:Unabletoserializehudson.FilePath$FileCallableWrapper@5267bc athudson.remoting.UserRequest.serialize(UserRequest.java:169) athudson.remoting.UserRequest.init(UserRequest.java:63) athudson.remoting.Channel.call(Channel.java:776) athudson.FilePath.act(FilePath.java:980) ...12moreCausedby:java.io.NotSerializableException:hudson.plugins.doxygen.DoxygenEnvironmentVariableExpander atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) atjava.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) athudson.remoting.UserRequest._serialize(UserRequest.java:158) athudson.remoting.UserRequest.serialize(UserRequest.java:167) ...15moreBuildstep'PublishDoxygen'changedbuildresulttoFAILURE{code} Asaninterestingextra,ourJenkinsguyseemstothinkthatthereisonlyanissuebecausewearerunningDoxygenonaslave,anythoughts?
Add Comment
[JIRA] [mercurial-plugin] (JENKINS-30120) Plugin does not work with Mercurial 3.4.2
Title: Message Title Mads Nielsen created an issue Jenkins / JENKINS-30120 Plugin does not work with Mercurial 3.4.2 Issue Type: Bug Assignee: Jesse Glick Attachments: hgerror.txt Components: mercurial-plugin Created: 25/Aug/15 8:56 AM Priority: Critical Reporter: Mads Nielsen We recently upgraded to mercurial 3.4.2 on our masters and slaves. Now when you try and build a project with the mercurial scm enabled we get this error, when the changelog is being computed. I've attached the console log, and it seems that the --follow flag is the culprit when hg log is run. Add Comment
[JIRA] [mercurial-plugin] (JENKINS-30120) Plugin does not work with Mercurial 3.4.2
Title: Message Title Mads Nielsen updated an issue Jenkins / JENKINS-30120 Plugin does not work with Mercurial 3.4.2 Change By: Mads Nielsen Werecentlyupgradedtomercurial3.4.2onourmastersandslaves.Nowwhenyoutryandbuildaprojectwiththemercurialscmenabledwegetthiserror,whenthechangelogisbeingcomputed.I'veattachedtheconsolelog,anditseemsthatthe--followflagistheculpritwhenhglogisrun. DowngradingtoMercurial3.3.3fixestheissues. 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-29909) New method to force setResult
Title: Message Title
James Nord commented on JENKINS-29909
Re: New method to force setResult
Have you looked at any alternative job type.? Eg with workflow
node ('linux') {
sh 'mvn install'
archive '**/target/*.war's
sh 'scp project/target/*.war remote.server/path
sh 'ssh remote.server Runtestsinbackground.sh'
}
// Wait forcompletion - no executor used here
Input 'waitfor job complete' // trigger this with a curl call
node ('blah') {
// get the results from remote server
// parse them
// set result
}
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] [performance-plugin] (JENKINS-27671) java.lang.Error: Unresolved compilation problem: Messages cannot be resolved
Title: Message Title Gurvan Le Dromaguet commented on JENKINS-27671 Re: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved Same stack 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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Title: Message Title Igor Iric commented on JENKINS-27547 Re: Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException No this one is not Duplicated the other one is JENKINS-27671 Just take a look which one is older You people only know to say it duplicate and don't know to provide solution. 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] [ec2-plugin] (JENKINS-5867) Allow Amazon EC2 Plugin to not require root access
Title: Message Title YC Lian commented on JENKINS-5867 Re: Allow Amazon EC2 Plugin to not require root access Hi, I can confirm what Mauricio Walters said. I am using the EC2 plugin and having problem to build from a non-root user on a spot instance. 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] [jira-plugin] (JENKINS-30118) Jira Plugin gets 404 when creating new JIRA version
Title: Message Title Michael Power created an issue Jenkins / JENKINS-30118 Jira Plugin gets 404 when creating new JIRA version Issue Type: Bug Assignee: Unassigned Attachments: - https___elosystemsteam.ci.cloudbees.com_, config.xml Components: jira-plugin Created: 25/Aug/15 7:53 AM Environment: Cloudbees Jenkins: com.cloudbees.dev-at-cloud.main:jenkins-war:1.609.1.2 JIRA Plugin: org.jenkins-ci.plugins:jira:1.41 JIRA Hosted in their cloud: JIRA v7.0.0-OD-02-247 Priority: Blocker Reporter: Michael Power When I configure a job to create a new JIRA version it fails. This has been working for some time, the job configuration did not change and the builds started breaking. I am guessing the is a breaking change in JIRA that needs to be integrated into the plugin. Steps to reproduce 1) Get a cloud hosted JIRA from atlassian.net 2) Get a cloud hosted cloudbess 3) Integrate the two 4) Create a new job 5) Add post build action: Create JIRA Version 6) Put in JIRA Project Key:
[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title
Sebastian Troy edited a comment on JENKINS-29938
Re: Unable to serialize is reported when publishing doxygen generate html files
IcanreaffirmMarcelBeister'sissue.Asheis,I'mspecifyingapathtomyDoxyfile(whichisintherootdirectory)andI'mgettingtheexactsameexception.IcannotconfirmwhetherswitchingbackaversionfixesthisasIdonothavethepermissiontodoso! {code:java}PublishingDoxygenHTMLresults.FATAL:errorjava.io.IOException:remotefileoperationfailed:/home/jenkins/build/workspace/QxTrunkDoxygenathudson.remoting.Channel@1096170:QxBuilder:java.io.IOException:Unabletoserializehudson.FilePath$FileCallableWrapper@5267bc athudson.FilePath.act(FilePath.java:987) athudson.FilePath.act(FilePath.java:969) athudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:223) athudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:177) athudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) athudson.model.Build$BuildExecution.post2(Build.java:185) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) athudson.model.Run.execute(Run.java:1766) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:381)Causedby:java.io.IOException:Unabletoserializehudson.FilePath$FileCallableWrapper@5267bc athudson.remoting.UserRequest.serialize(UserRequest.java:169) athudson.remoting.UserRequest.init(UserRequest.java:63) athudson.remoting.Channel.call(Channel.java:776) athudson.FilePath.act(FilePath.java:980) ...12moreCausedby:java.io.NotSerializableException:hudson.plugins.doxygen.DoxygenEnvironmentVariableExpander atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) atjava.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) athudson.remoting.UserRequest._serialize(UserRequest.java:158) athudson.remoting.UserRequest.serialize(UserRequest.java:167) ...15moreBuildstep'PublishDoxygen'changedbuildresulttoFAILURE{code}
Add Comment
[JIRA] [cmakebuilder-plugin] (JENKINS-30114) CMake builder cannot find NMake
Title: Message Title Eric Beuque commented on JENKINS-30114 Re: CMake builder cannot find NMake I tested with defining the project without template, but problem is the same. 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-30085) SVN- authentication fails
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-30085 Re: SVN- authentication fails Loganathan C It would be interesting if you review the title and description of this ticket in order to describe a new feature/improvement. By now, the main goal in Subversion Plugin is to reach a stable version: http://jenkins-ci.org/content/reinforcements-subversion-plugin Regards, 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] [embeddable-build-status-plugin] (JENKINS-17798) build badge icon requires authentication
Title: Message Title retronym commented on JENKINS-17798 Re: build badge icon requires authentication Mani Soundararajan I think either: 1) the `GitHub OAuth` plugin would need to be changed to allow anoynmous access to the ViewStatus permission https://github.com/jenkinsci/embeddable-build-status-plugin/compare/11843c79f8e3...3a6e78d3e0a4#diff-25df045777dd8f7465c9cbac4dea6416R63, or 2) this plugin would need to change to use the standard hudson.model.Hudson.Read / hudson.model.Item.Read permissions: https://github.com/jenkinsci/embeddable-build-status-plugin/compare/11843c79f8e3...3a6e78d3e0a4#diff-25df045777dd8f7465c9cbac4dea6416R103 (Disclaimer: I'm not a Jenkins plugin expert, I just had a quick browse of the two code bases) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-10871) Enabling Project Matrix Athorization Locks Out Users
Title: Message Title Oleg Nenashev commented on JENKINS-10871 Re: Enabling Project Matrix Athorization Locks Out Users Yes, you can enable and even install the plugin using the filesystem 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-30122) CopyArtifact does not work in a secured environment with Workflow and Authorize Project
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30122 CopyArtifact does not work in a secured environment with Workflow and Authorize Project Change By: Jesse Glick Labels: authenticationregression 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-30122) CopyArtifact does not work in a secured environment with Workflow and Authorize Project
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30122 CopyArtifact does not work in a secured environment with Workflow and Authorize Project Change By: Jesse Glick Component/s: copyartifact-plugin Component/s: authorize-project-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] [view-job-filters-plugin] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Title: Message Title Tony Wallace edited a comment on JENKINS-21862 Re: Build Filter (Wrapper) column not properly showing results for Parameterized builds Ifinterested,thisiswhatIamtryingtoaccomplish.Idonotwishtomaintainmultiple,mostlyredundantprojectswheretheonlydifferenceisGERRIT_BRANCHorsomeotherbuildParametervalue.However,IdowishtoprovideuserswithaconvenientwaytovisuallyreviewrecentbuildresultsforjusttheprojectsandGERRIT_BRANCHesofinteresttothem,includingthevaluesoftheimportantbuildParametersallonthesamepage,withoutbeingoverwhelmed.Tothatend,IhavealreadyconfiguredacustomizedBuildDescriptionforallprojects.ThisbuildDescriptionappearsinthebuildHistorythatappearsontheRHSofanyindividualprojectpage.NowIamtryingtomakeJenkinsdisplayaViewshowingthebuildHistoryformultipleprojectsinonepage,where(inorderofhighest-to-lowestpriority),(a)TheView'sBuildHistoryonlyincludesbuildswhichsatisfyaParameterizedbuildsfilter-e.g.,thevalueofGERRIT_BRANCHinthatbuildmatchedRB12.34.IftherewasafilterbasedonregexmatchagainstBuildDescription,IcouldusethatinsteadofParameterizedbuildsfilter.(b) Asabove,butyoucanaddmoreconfigurablecolumnstotheView'sBuildHistory,similartothewayyoucanaddcolumnstothemainview.Especially,BuildDescription.(c) Themainview(Projectlistwithcolumns)shouldonlyincludeprojectsforwhichatleastonecompletedbuildsatisfiedtheParameterizedbuildsfilter,e.g.GERRIT_BRANCHmatchedRB12.34.Moreimportantly,foreachprojectincludedinthemainview,theBuildFilter(wrapper)columnwoulddisplay accuratevaluesfor Status,Weather,BuildDescription,Buildparameters,etc valuescorrespondingto ,basedon thelastcompletedbuildwhichsatisfiedtheParameterizedbuildsfilter.( c d )Asabove, and but theBuildFilter(wrapper)columnwouldalsodisplayaccuratevaluesforLastsuccess,Lastfailure,etc,basedonthesubsetofbuildswhichsatisfiedtheParameterizedbuildsfilter.Thanksforreading. 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-29329) Visual Studio/MSBuild projects can not be built implicitly anymore
Title: Message Title Martin Weber commented on JENKINS-29329 Re: Visual Studio/MSBuild projects can not be built implicitly anymore Thank you for testing the snapshot version under windows. So I will close this and JENKINS-29267 and publish the next release. 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-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title Martin Weber resolved as Fixed Verified by JENKINS-29329 Jenkins / JENKINS-29267 CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 Change By: Martin Weber Status: Reopened 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] [delivery-pipeline-plugin] (JENKINS-29806) Ability to split sequence of jobs into multiple pipelines
Title: Message Title Dawid Malinowski commented on JENKINS-29806 Re: Ability to split sequence of jobs into multiple pipelines What exactly use cases are not covered. Please keep in mind that my change is not working with regexp. 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-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title Martin Weber closed an issue as Fixed Jenkins / JENKINS-29267 CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 Change By: Martin Weber Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2-plugin] (JENKINS-17957) Crowd plugin - remember me doesn't work
Title: Message Title Rob Duff commented on JENKINS-17957 Re: Crowd plugin - remember me doesn't work Kanstantsin Shautsou and Arnaud Hritier, does it make sense to assign this to Arnaud Hritier for now? Would it also make sense to Stop Progress on this until there is sufficient time to tackle the issue? Also, have there been any code reviews or code changes checked in publicly (say, on a branch) yet? Perhaps others can help by leveraging what has already been coded. 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] [nodejs-plugin] (JENKINS-30134) java.lang.ArrayIndexOutOfBoundsException: 2 error
Title: Message Title kavan puranik created an issue Jenkins / JENKINS-30134 java.lang.ArrayIndexOutOfBoundsException: 2 error Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 25/Aug/15 6:54 PM Priority: Blocker Reporter: kavan puranik Jenkins is blowing up on all our node.js based builds this morning. They were working fine yesterday. We are using version org.jenkins-ci.plugins:nodejs:0.2.1 Stack Trace: FATAL: 2 java.lang.ArrayIndexOutOfBoundsException: 2 at jenkins.plugins.nodejs.tools.NodeJSVersion.init(NodeJSVersion.java:15) at jenkins.plugins.nodejs.tools.InstallerPathResolver$Factory.isVersionBlacklisted(InstallerPathResolver.java:23) at jenkins.plugins.nodejs.tools.NodeJSInstaller$DescriptorImpl$1.apply(NodeJSInstaller.java:370) at jenkins.plugins.nodejs.tools.NodeJSInstaller$DescriptorImpl$1.apply(NodeJSInstaller.java:368) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:649) 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.size(Iterators.java:151) at com.google.common.collect.Collections2$FilteredCollection.size(Collections2.java:222) at java.util.TreeSet.addAll(TreeSet.java:300) at jenkins.plugins.nodejs.tools.NodeJSInstaller$DescriptorImpl.getInstallables(NodeJSInstaller.java:378) at hudson.tools.DownloadFromUrlInstaller.getInstallable(DownloadFromUrlInstaller.java:52) at
[JIRA] [delivery-pipeline-plugin] (JENKINS-29806) Ability to split sequence of jobs into multiple pipelines
Title: Message Title Noah Nordrum commented on JENKINS-29806 Re: Ability to split sequence of jobs into multiple pipelines According to the testing I did for my implementation, this is missing some key logic. I'll track on the PR. 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] [view-job-filters-plugin] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Title: Message Title Jesse Glick commented on JENKINS-21862 Re: Build Filter (Wrapper) column not properly showing results for Parameterized builds BuildFilterColumn$JobWrapper._getRuns is clearly wrong. It should not be using RunMap, which is only expected to be implemented by Jenkins core. At any rate, it looks like an unrelated issue; better to reclose this one as fixed and file separately (link as needed). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rake-plugin] (JENKINS-26436) Rake Plugin Does Not Find All RVM Installed Ruby Instances
Title: Message Title M K commented on JENKINS-26436 Re: Rake Plugin Does Not Find All RVM Installed Ruby Instances find | grep specifications | grep /rake- | sort ./gems/jruby-1.7.4@gemset/specifications/rake-10.4.2.gemspec ./gems/ruby-1.9.3-p551@gemset/specifications/rake-10.4.2.gemspec ./gems/ruby-2.0.0-p598@gemset/specifications/rake-10.4.2.gemspec ./gems/ruby-2.1.1@gemset/specifications/rake-10.3.2.gemspec ./gems/ruby-2.1.5@gemset/specifications/rake-10.4.2.gemspec ./gems/ruby-2.1.5/specifications/rake-0.9.2.2.gemspec ./gems/ruby-2.1.5/specifications/rake-10.4.2.gemspec ./rubies/jruby-1.7.4/lib/ruby/gems/shared/specifications/rake-10.0.3.gemspec ./rubies/ruby-1.9.3-p551/lib/ruby/gems/1.9.1/specifications/rake-0.9.2.2.gemspec ./rubies/ruby-2.0.0-p598/lib/ruby/gems/2.0.0/specifications/default/rake-0.9.6.gemspec ./rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/specifications/default/rake-10.1.0.gemspec ./rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/specifications/default/rake-10.1.0.gemspec ./rubies/ruby-2.1.6/lib/ruby/gems/2.1.0/specifications/default/rake-10.1.0.gemspec ./rubies/ruby-2.2.0/lib/ruby/gems/2.2.0/specifications/default/rake-10.4.2.gemspec ./rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/specifications/default/rake-10.4.2.gemspec Jenkins does not recognise Ruby environments for Ruby: 2.1.6, 2.2.0, 2.2.2 For other rubies it recognise all available gemsets. 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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Title: Message Title Gurvan Le Dromaguet commented on JENKINS-27547 Re: Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException I said duplicated by , not duplicate of ... 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] [artifactory-plugin] (JENKINS-30121) Workflow build step for Artifactory Plugin
Title: Message Title Stephan Leicht Vogt created an issue Jenkins / JENKINS-30121 Workflow build step for Artifactory Plugin Issue Type: New Feature Assignee: yossis Components: artifactory-plugin Created: 25/Aug/15 10:00 AM Priority: Major Reporter: Stephan Leicht Vogt A way to run deploy artefacts using the artifactory plugin from a workflow using configured Artifactory settings and with support for other features such as licensing checks. Add Comment
[JIRA] [performance-plugin] (JENKINS-27671) java.lang.Error: Unresolved compilation problem: Messages cannot be resolved
Title: Message Title Gurvan Le Dromaguet edited a comment on JENKINS-27671 Re: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved Samestack ,duplicateofJENKINS-27547 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-30122) CopyArtifact does not work in a secured environment with Workflow and Authorize Project
Title: Message Title James Nord created an issue Jenkins / JENKINS-30122 CopyArtifact does not work in a secured environment with Workflow and Authorize Project Issue Type: Bug Assignee: Jesse Glick Attachments: CLEAN_JE.zip Components: authorize-project-plugin, copyartifact-plugin, workflow-plugin Created: 25/Aug/15 10:29 AM Environment: Jenkins 1.609.2 Copy Artifcat 1.35.2 Workflow 1.10-beta1 Authorize Project 1.1.0 Priority: Major Reporter: James Nord If you have a secured environment that does not grant anonymous access to build artifacts then it is impossible to use copyArtifact in a workflow step even when setting the workflow to run as a user that has administration rights. ERROR: Unable to find project for artifact copy: producer This may be due to incorrect project name or permission settings; see help for project name in job configuration.
[JIRA] [subversion-plugin] (JENKINS-30085) SVN- authentication fails
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-30085 Re: SVN- authentication fails Loganathan C The title and description are not clear, do not describe what you need as user. The issue type is invalid... 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-30085) SVN- authentication fails
Title: Message Title Loganathan C updated an issue Jenkins / JENKINS-30085 SVN- authentication fails Change By: Loganathan C Weareabletocheckoutthesvnfolderusingwindowsbatchscripts.Butinthejob,underSubversionPlug-inifentretheSVNrepolink,saytheerroritattachedfor for reference.Note:foraccesssvnrepolink,needtwoauthentication,1,proxyserverauthentication2,SVNserverauthentication. 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-30085) SVN- authentication fails
Title: Message Title Loganathan C commented on JENKINS-30085 Re: SVN- authentication fails I agree, Some more information: Currently using, Subversion Plugin-version: 2.5.1 Jenkins Version: 1.596.2 Kindly do let me know if you need any further 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-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Tomas Zaleniakas commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete So i managed to find the issue with your help. The durable task error was that it cannot acces tje jenkins-log.txt file. And that batch proccess creates some procces that doesn not ecit after it, so we had another batch script to clean it, so i merged those two batch files and now builds doesnt hang. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-30085) SVN- authentication fails
Title: Message Title Loganathan C updated an issue Jenkins / JENKINS-30085 SVN- authentication fails Change By: Loganathan C Issue Type: Bug NewFeature 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-30085) SVN- Authentication Fails
Title: Message Title Loganathan C updated an issue Jenkins / JENKINS-30085 SVN- Authentication Fails Change By: Loganathan C Summary: SVN- authenticationfails AuthenticationFails Issue Type: NewFeature Improvement Weareabletocheckoutthesvnfolderusingwindowsbatchscripts.Butinthejob,under Using SubversionPlug-inifentretheSVNrepolink,saytheerroritattachedforreference. Butabletocheckoutthesvnfolderusingwindowsbatchscripts Note:foraccesssvnrepolink,needtwoauthentication,1,proxyserverauthentication2,SVNserverauthentication. Jenkinsversion:1.596.2SubversionPluginversion:2.5.1 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] [android-lint-plugin] (JENKINS-29870) Make Android Lint Plugin compatible with Workflow
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-29870 Re: Make Android Lint Plugin compatible with Workflow Christopher Orr Sure! Thanks for your help. 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] [android-lint-plugin] (JENKINS-29870) Make Android Lint Plugin compatible with Workflow
Title: Message Title Manuel Jess Recena Soto assigned an issue to Manuel Jess Recena Soto Jenkins / JENKINS-29870 Make Android Lint Plugin compatible with Workflow Change By: Manuel Jess Recena Soto Assignee: ChristopherOrr ManuelJessRecenaSoto 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] [ccm-plugin] (JENKINS-30133) Add Workflow compatibility to CCM Plugin
Title: Message Title Antonio Muiz assigned an issue to Antonio Muiz Jenkins / JENKINS-30133 Add Workflow compatibility to CCM Plugin Change By: Antonio Muiz Assignee: AntonioMuiz 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] [ccm-plugin] (JENKINS-30133) Add Workflow compatibility to CCM Plugin
Title: Message Title Antonio Muiz created an issue Jenkins / JENKINS-30133 Add Workflow compatibility to CCM Plugin Issue Type: Task Assignee: Unassigned Components: ccm-plugin Created: 25/Aug/15 6:35 PM Priority: Major Reporter: Antonio Muiz Adapt the plugin to be usable inside a Workflow script. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ccm-plugin] (JENKINS-30133) Add Workflow compatibility to CCM Plugin
Title: Message Title Antonio Muiz started work on JENKINS-30133 Change By: Antonio Muiz Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-30121) Workflow build step for Artifactory Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30121 Re: Workflow build step for Artifactory Plugin Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/b448a6311ee0b424c92eafbf8b265a40e8bca349 Log: JENKINS-30121 Noting; closes #189. 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-30114) CMake builder cannot find NMake
Title: Message Title Martin Weber commented on JENKINS-30114 Re: CMake builder cannot find NMake I was thinking that nmake is invoked by the cmake plugin. Only if you add a 'Run build tool' (sub-)step to the cmake plugin. Your log shows that cmake finds the compiler. It's unclear, why cmake does not set the absolute path for nmake, at least it does so for the Mingw, MSYS, Makefiles and ninja generators. At least for the ninja generator, cmake will complain and fail at generation time, if it cannot find the ninja tool. (Did not test that with other generators.) Your set-build-env.bat script sets SHELL environment variables. AFAIK, these are visible to the invoked shell only, but not by the calling process (jenkins-slave.exe). Try to replace the 'Use builders from another project' build step by an Invoke Shell step that prints the SHELL environment variables to diagnose that. 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] [android-lint-plugin] (JENKINS-29870) Make Android Lint Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29870 Re: Make Android Lint Plugin compatible with Workflow Code changed in jenkins User: recena Path: .gitignore pom.xml src/main/java/org/jenkinsci/plugins/android_lint/LintMavenResultAction.java src/main/java/org/jenkinsci/plugins/android_lint/LintPublisher.java src/main/java/org/jenkinsci/plugins/android_lint/LintReporterResult.java src/main/java/org/jenkinsci/plugins/android_lint/LintResult.java src/main/java/org/jenkinsci/plugins/android_lint/LintResultAction.java src/test/java/org/jenkinsci/plugins/android_lint/LintResultTest.java src/test/java/org/jenkinsci/plugins/android_lint/LintWorkflowTest.java src/test/java/org/jenkinsci/plugins/android_lint/parser/LintParserTest.java src/test/java/org/jenkinsci/plugins/android_lint/parser/LintResultTest.java src/test/resources/org/jenkinsci/plugins/android_lint/duplicates.zip src/test/resources/org/jenkinsci/plugins/android_lint/parser/duplicates.zip http://jenkins-ci.org/commit/android-lint-plugin/ec7b3810ebddc17d02604228207b78d07fc0be28 Log: JENKINS-29870 Workflow compatible. Added new tests (workflow specific) 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] [artifactory-plugin] (JENKINS-30121) Workflow build step for Artifactory Plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30121 Workflow build step for Artifactory Plugin Change By: Jesse Glick Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-label-assignment-plugin] (JENKINS-30135) Restricting a job to the label of a slave that is offline
Title: Message Title Joshua Shinn created an issue Jenkins / JENKINS-30135 Restricting a job to the label of a slave that is offline Issue Type: Bug Assignee: Unassigned Components: groovy-label-assignment-plugin Created: 25/Aug/15 8:53 PM Priority: Minor Reporter: Joshua Shinn When restricting a job to the label of a slave that is offline, upon running the job, the job will sit in the build queue awaiting that slaves return. If another slave in the meantime, that is online and available, is set to the same label, the job will not run on it(which it should). Steps to recreate: 1. Node1 is assigned label x. Take it offline. 2. Run the job that is assigned to label x. 3. The job is now sitting in the build queue. 3. Remove the label from Node1, and assign Node2 the label x. 4. The job does not run until Node1 is brought back online. Note that Node1 no longer has any label assigned to it. I stepped through the code and realized that this plugin actually assigns the job to the Node1 computer name at build time. So whichever node the label was assigned to at build time, becomes the node the job is attached to. The label is never re-evaluated, and consequently the job never sees that there is in fact a label x available(Node2).
[JIRA] [core] (JENKINS-30123) OutputStream encountered error during write
Title: Message Title Bruce Coveny created an issue Jenkins / JENKINS-30123 OutputStream encountered error during write Issue Type: Bug Assignee: Unassigned Components: core Created: 25/Aug/15 11:36 AM Environment: JENKINS WAR VERSION 1.626 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 6.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5.6 JAVA 1.7.1 Priority: Minor Reporter: Bruce Coveny Getting errors in the for a few versions now. Doesn't seem to impact the viewing of the pages but sometimes pages load slower than normal and the follow stack traces are shown in the server log. My title [8/25/15 7:25:02:027 EDT] 0076 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[Stapler]: org.apache.commons.jelly.JellyTagException: wsjar:file:/%DIRREMOVE%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.626.jar!/lib/layout/layout.jelly:81:26: x:doctype OutputStream encountered error during write at
[JIRA] [core] (JENKINS-30123) OutputStream encountered error during write
Title: Message Title
Bruce Coveny updated an issue
Jenkins / JENKINS-30123
OutputStream encountered error during write
Change By:
Bruce Coveny
Gettingerrorsintheforafewversionsnow.Doesn'tseemtoimpacttheviewingofthepagesbutsometimespagesloadslowerthannormalandthefollowstacktracesareshownintheserverlog.{panel:title= Mytitle StackTrace }[8/25/157:25:02:027EDT]0076webappEcom.ibm.ws.webcontainer.webapp.WebApplogServletErrorSRVE0293E:[ServletError]-[Stapler]:org.apache.commons.jelly.JellyTagException:wsjar:file:/%DIRREMOVE%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.626.jar!/lib/layout/layout.jelly:81:26:x:doctypeOutputStreamencounterederrorduringwrite atorg.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) athudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:27) atorg.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:55) atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) atcom.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3923) atcom.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1006) atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) atcom.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
[JIRA] [subversion-plugin] (JENKINS-30085) SVN- Authentication Fails
Title: Message Title Loganathan C commented on JENKINS-30085 Re: SVN- Authentication Fails Updated the issue type. I hope you understood the issue from the error screenshot attached with 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.
