[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Ben I think the whole problem is that no one is working on this plugin, so someone needs to step forward with the time available to do it. In my opinion, the job here is not to "upgrade svnkit". That part is trivial. The real work is to unravel the customisations made to svnkit and remove them from this project, finding other ways to solve the problems they were put in there to solve. Once we are using plain vanilla svnkit, the rest is simple. The problem is that in my cursory review it wasn't obvious why the svnkit fork was made. Some were clearer (like making some classes serializable presumably to handle Jenkins slaves) but others not. It will need some time to review if the original person who made those changes is not available to help. Here is the beginning of the analysis of the changes: https://gist.github.com/ari/f1fc75c22b92ab17a73d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-17702) CopyArtifact with parameter selection fails when parameters changed
ikedam
resolved JENKINS-17702 as Cannot Reproduce
CopyArtifact with parameter selection fails when parameters changed
Could not reproduce even with the new information. I tested with Jenkins 1.480.3 + Copyartifact 1.26 + Subversion 1.39 (bundled with Jenkins 1.480.3):
Create a free style project "ProjectX"
Create a file "artifact.txt" with its content "without_parameter"
Archive artifact.txt
Run ProjectX
Update ProjectX
Add a List Subversion tags parameter:
Name: MY_X_PARAM
Repository URL: https://svn.jenkins-ci.org/branches/
Change the name of the artifact to "artifact2.txt" (both copyartifact and archive) and its content to "parameter=${MY_X_PARAM}"
Run ProjectX with MY_X_PARAM=HUDSON-1467
Create a free style project "ProjectY"
Add a string parameter "USE_X_PARAM"
Add a Build selector for Copy Artifact parameter "PROJECT_X_BUILD"
Add "Copy artifact from another project"
Project name: "ProjectX"
Which build: Specified by a build parameter
Parameter Name: PROJECT_X_BUILD
Artifacts to copy: artifact2.txt
Target directory: packages
Parameter filters: MY_X_PARAM=${USE_X_PARAM}
Output the contents of packages/artifact2.txt
Run ProjectY with USE_X_PARAM=HUDSON-1467 and PROJECT_X_BUILD=Latest successful build
Result:
The build of ProjectY succeeded.
The output was: parameter=HUDSON-1467
Change By:
ikedam
(17/Aug/14 10:23 AM)
Status:
Open
Resolved
Resolution:
CannotReproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström resolved JENKINS-24019 as Fixed Absolute URLs in delivery pipeline break reverse proxy setups Change By: Patrik Boström (17/Aug/14 10:36 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström commented on JENKINS-24019 Absolute URLs in delivery pipeline break reverse proxy setups Merged to master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström closed JENKINS-22654 as Fixed Multi-configuration projects display with wrong Delivery Pipeline Stage Name Released in 0.8.5 Change By: Patrik Boström (17/Aug/14 11:06 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström closed JENKINS-24019 as Fixed Absolute URLs in delivery pipeline break reverse proxy setups Released in 0.8.5 Change By: Patrik Boström (17/Aug/14 11:07 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24173) Show Views TabBar in pipeline default view
Patrik Boström closed JENKINS-24173 as Fixed Show Views TabBar in pipeline default view Released in 0.8.5 Change By: Patrik Boström (17/Aug/14 11:06 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-23752) Duplicated Warnings links when used with Flexible Publish plugin
ikedam
updated JENKINS-23752
Duplicated Warnings links when used with Flexible Publish plugin
I know this behavior well.
I conclude that it's not a bug (a behavior to be fixed), but a limitation (a behavior not to be fixed).
As it is very complicated, I'm not sure I can exactly explain the details (I know my English is poor). But I try that:
Post build steps (Publisher) displays links in the left side of project pages by implementing Publisher#getProjectActions.
You can use each Publisher at most only once in a project. For example, if you added "Archiving artifacts" to a project, you cannot add more new "Archiving artifacts" to that project.
Using Flexible Publish, you can define a same Publisher for multiple times. This is an irregular case. For example, you can add two "Archiving artifacts" for condition A and condition B. This results Publisher#getProjectActions of a same Publisher are called multiple times for a project. This results duplicated links in a project page.
As described before, Publisher should be defined only one in a project. So it's not a bug of Publisher to display duplicated links.
At the same time, Flexible Publish does not know how to handle links. Those links may be better to be displayed for each definition, or may be better to be displayed only once (like Warnings plugin).
As far as I know, this behavior doesn't results harmful, and I don't plan to fix it.
If you try to fix that, the way of SubProjectsAction of parameterized-trigger plugin may be helpful.
https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/SubProjectsAction.java
https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/resources/hudson/plugins/parameterizedtrigger/SubProjectsAction/jobMain.groovy
If multiple {{SubProjectsAction}}s are defined to a build, it aggregates all {{SubProjectsAction}}s to display.
I think aggregating WarningsProjectAction and displaying a link only for the first one would fix the behavior.
But it would get so complicated, and may cause other problems.
And you need to fix not warnings-plugin, but analysis-core-plugin. It may affect other plugins using analysis-core-plugin.
Change By:
ikedam
(17/Aug/14 11:29 AM)
Summary:
MSBuild
Duplicated
Warnings
linkdisplaystwiceonbuildsifaddedasconditionalbuildstep
linkswhenusedwithFlexiblePublishplugin
Issue Type:
Bug
Improvement
Assignee:
ikedam
UlliHafner
Component/s:
analysis-core
Component/s:
conditional-buildstep
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Vincent Massol updated JENKINS-24294 Very slow UI Change By: Vincent Massol (17/Aug/14 11:55 AM) Description: WevebeenusingJenkinsforalongtimeontheXWikiproject.Itsavailableathttp://ci.xwiki.org.Howeverwevebeenhavingspeedissuesforseveralyearsnow.Weveregularlyupdatedthejenkinsversionweuseinthehopethatitwouldgetfixedbutitseemsitdoesntimprovemuch.RightnowIvenoticedthatifhttp://ci.xwiki.orghasntbeenaccessedforsometime(afewminutes),itloadsveryslow(thispagepointstothedashboardpluginview).ByveryslowImeanseveralminutes.ImattachingathreaddumpIvejusttakennow. Thanksalotforlookingintothis! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Vincent Massol updated JENKINS-24294 Very slow UI Change By: Vincent Massol (17/Aug/14 11:55 AM) Attachment: jenkins.dump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Vincent Massol created JENKINS-24294 Very slow UI Issue Type: Bug Assignee: Unassigned Attachments: jenkins.dump Components: core Created: 17/Aug/14 11:54 AM Description: We've been using Jenkins for a long time on the XWiki project. It's available at http://ci.xwiki.org. However we've been having speed issues for several years now. We've regularly updated the jenkins version we use in the hope that it would get fixed but it seems it doesn't improve much. Right now I've noticed that if http://ci.xwiki.org hasn't been accessed for some time (a few minutes), it loads very slow (this page points to the dashboard plugin view). By very slow I mean several minutes. I'm attaching a thread dump I've just taken now. Environment: 1.564 Project: Jenkins Priority: Critical Reporter: Vincent Massol This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: Olivier Lamy Path: src/main/resources/hudson/maven/Messages.properties http://jenkins-ci.org/commit/maven-plugin/07685bd11677bd2d53cca6f8a7ae70d5832f9e05 Log: Merge pull request #27 from jenkinsci/JENKINS-24282 Use noun phrases for new items JENKINS-24282 Compare: https://github.com/jenkinsci/maven-plugin/compare/af7b3857ad7a...07685bd11677 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken Thank you so much for looking into this issue. I will try to build the sample project with our setup to see whether it fails and report any findings. I don't know if this affects anything but the slave executors are running on the same machine as the master in our current setup, so the SSH connections never go over the network. I will try to set up a repository with the sample project as quickly as possible to help you get more data. Thanks, Tommi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work Matrix job
Roland Schulz created JENKINS-24295 Gerrit Cancel doesnt work Matrix job Issue Type: Bug Assignee: rsandell Components: gerrit-trigger, matrix Created: 17/Aug/14 4:54 PM Description: The "Build Current Patches Only" feature works great for all normal jobs. But matrix jobs are not canceled when they are still running and a new patch is uploaded. Environment: Linux, Jenkins 1.552, Gerrit Trigger 2.11.0 Project: Jenkins Priority: Major Reporter: Roland Schulz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
Roland Schulz updated JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs Change By: Roland Schulz (17/Aug/14 4:55 PM) Summary: GerritCanceldoesntwork for Matrix job jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
Roland Schulz commented on JENKINS-24295 Gerrit Cancel doesnt work for Matrix jobs It seems to work correctly for matrix jobs as long as all the sub-jobs have been started at the time the patch is uploaded. But if some sub-jobs are still waiting on an executor to become available, than those waiting jobs are not deleted from the queue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Daniel Beck commented on JENKINS-24294 Very slow UI Jira is not the site to use for what amounts to a support request. Please direct further questions to the jenkinsci-users mailing ist, or #jenkins on Freenode. That said, you seem to be using the Maven project type very heavily. There are certain inefficiencies in that (and Matrix/multi-config projects) that cause loading of all (usually lazily loaded) builds. Coupled with the fact that Maven projects and builds have a disk footprint of 1+N freestyle projects/builds (N being the number of modules built), these are very resource (disk) intensive. Some inefficiencies have been improved in more recent Jenkins versions, so upgrading may be worth a try. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Daniel Beck edited a comment on JENKINS-24294 Very slow UI Jira is not the site to use for what amounts to a support request. Please direct further questions to the jenkinsci-users mailing ist, or #jenkins on Freenode. That said, you seem to be using the Maven project type very heavily. There are certain inefficiencies in that (and Matrix/multi-config projects) that cause loading of all (usually lazily loaded) builds. Coupled with the fact that Maven projects and builds have a disk footprint of 1+N freestyle projects/builds (N being the number of modules built), these are very resource (disk) intensive. Also, the Dashboard with its aggregate statistics forces loading of all builds. Get rid of that, or get a faster disk. Some inefficiencies have been improved in more recent Jenkins versions, so upgrading may be worth a try. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24296) Drop dependency to jQuery-UI
Patrik Boström created JENKINS-24296 Drop dependency to jQuery-UI Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline Created: 17/Aug/14 5:27 PM Description: Drop dependency to jQuery-UI since we don’t use drag and drop. More info on dependencies for Query-UI: http://www.youmeb.com/assets/modules/ui/jsPlumb/demo/doc/content.html Project: Jenkins Priority: Major Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Daniel Beck resolved JENKINS-24294 as Not A Defect Very slow UI Not a bug report. Change By: Daniel Beck (17/Aug/14 5:29 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
ikedam resolved JENKINS-24279 as Duplicate run custom shell script on Build timeout as pre-on-timeout hook Duplicates JENKINS-12744 Change By: ikedam (17/Aug/14 10:48 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-23717) Add link to specific build ID in console output
ikedam resolved JENKINS-23717 as Wont Fix Add link to specific build ID in console output Downstream build numbers is to be removed as they can be wrong. Have a look at JENKINS-24257. Change By: ikedam (18/Aug/14 12:17 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19806) Parameters passed to downstream jobs hiding option at downstream queue list
ikedam updated JENKINS-19806 Parameters passed to downstream jobs hiding option at downstream queue list That displays are handled not by parameterized-trigger plugin but by Jenkins core. I changed the component to core. Change By: ikedam (18/Aug/14 12:23 AM) Assignee: huybrechts Component/s: core Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-17275) Use Environment Variable when triggering downstream jobs.
ikedam resolved JENKINS-17275 as Duplicate Use Environment Variable when triggering downstream jobs. Duplicates JENKINS-11280 . Though I agree that this is an improvement and not a bug, I merge issues to the older one. Change By: ikedam (18/Aug/14 12:32 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-8141) Allow re-triggering of downstream projects with parameters from a prior source build.
ikedam resolved JENKINS-8141 as Wont Fix Allow re-triggering of downstream projects with parameters from a prior source build. Rebuild plugin allows you relaunch a build with the same parameters. Let's try that. https://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin Change By: ikedam (18/Aug/14 12:46 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-23564) PHPUnit test results from dataProvider tests are not parsed by xUnit
Robin Lott closed JENKINS-23564 as Not A Defect PHPUnit test results from dataProvider tests are not parsed by xUnit I'm closing this as 'not a defect' because it looks like the problem I'm experiencing is actually being caused by Paratest (https://github.com/brianium/paratest/issues/94) and not by xUnit. The xml I included above was from a local run on my machine, which is why it is okay. The results xml from paratest is like this: ?xml version="1.0" encoding="UTF-8"? testsuites testsuite name="" tests="2" assertions="95" failures="0" errors="0" time="69.747635" file="" testcase name="testDeleteItemFromExistingStockOrder with data set #0" class="" file="" line="" assertions="48" time="39.951086"/ testcase name="testDeleteItemFromExistingStockOrder with data set #1" class="" file="" line="" assertions="47" time="29.796549"/ /testsuite /testsuites Now I know what's causing the problem, I should be able to find a solution. Change By: Robin Lott (18/Aug/14 1:13 AM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24297) Jobs DSL Plugin Master Branch tests failing
Joseph Hughes created JENKINS-24297 Jobs DSL Plugin Master Branch tests failing Issue Type: Bug Affects Versions: current Assignee: Daniel Spilker Components: job-dsl-plugin Created: 18/Aug/14 1:18 AM Description: Master Branch of the plugin currently failing tests due to this commit. https://github.com/jenkinsci/job-dsl-plugin/commit/f08528fce4ad14e950e9f6bcf9162632eb5ca6da Project: Jenkins Priority: Critical Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24261) Assembla browser breaks config page
Michael Neale commented on JENKINS-24261 Assembla browser breaks config page Thanks Mark - yes I assumed it was tiny mistake. Given enough users we see all bugs like that if it is likely to happen again - could a reflection based test look for the occurrence of appropriately named resources along with the classes? (if it is unlikely to happen again, don't bother). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24297) Jobs DSL Plugin Master Branch tests failing
Joseph Hughes commented on JENKINS-24297 Jobs DSL Plugin Master Branch tests failing Seems like the build should be doing a clean before test. With a clean workspace I can get all the tests to pass. With a workspace that has been build with commit before the commit mentioned in this issue, the tests fail because the Message class is not generated from Message.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24283) Empty environment variables are deleted
Magnus Jacobsson commented on JENKINS-24283 Empty environment variables are deleted The config in the description was wrong, but I've edited it so it is now the correct one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24283) Empty environment variables are deleted
Magnus Jacobsson updated JENKINS-24283 Empty environment variables are deleted Change By: Magnus Jacobsson (18/Aug/14 5:13 AM) Description: Emptyenvironmentvariablesaredeleted.Threemethodstried:1.Parameter2.Generateenvironmentvariablesfromscript3.InjectenvironmentvariablestothebuildprocessAscanbeseenfromthelogbelow,thenon-emptyvariablesMYVAR1,MYVAR3MYVAR5worksasexpected,buttheemptyvariablesMYVAR2,MYVAR4MYVAR6arenotpresentintheenvironmentwhenthejobexecutes.WhenlookingattheenviromentthroughthelefthandmenuEnvironmentVariablesonthebuildpage,allvariablesarepresent.YoucanactuallyalsoseethatanimplicitenvironmentvariableTEST_NODEisalsodeleted.ImnotsurethattheproblemisinEnvInject.Feelfreetomoveittosomeothercomponent.LookssimilartoJENKINS-15146.log:Startedbyusermagjac[EnvInject]-Loadingnodeenvironmentvariables.Buildingonmasterinworkspace/srv/lhome/jenkins/jobs/empty_env_var_test/workspace[workspace]$/bin/sh-xe/tmp/empty_env_var_test6599764777552559363.sh+echoMYVAR3=world+echoMYVAR4=[environment-script]AddingvariableMYVAR4withvalue[environment-script]AddingvariableMYVAR3withvalueworld[EnvInject]-ExecutingscriptsandinjectingenvironmentvariablesaftertheSCMstep.[EnvInject]-InjectingasenvironmentvariablesthepropertiescontentMYVAR5=fooMYVAR6=[EnvInject]-Variablesinjectedsuccessfully.[workspace]$/bin/sh-xe/tmp/hudson101371634758484537.sh+envJENKINS_HOME=/srv/lhome/jenkinsMAIL=/var/mail/smokerUSER=smokerLC_TIME=en_DK.UTF-8MYVAR1=helloSHLVL=1NODE_LABELS=mastermaster_labelnullHUDSON_URL=http://smoketest.netinsight.se/jenkins/LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64MYVAR3=worldHOME=/home/smokerBUILD_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/6/MYVAR5=fooJENKINS_SERVER_COOKIE=dad1862e4df27e29HUDSON_COOKIE=0cebdd7b-7b7f-4962-a07c-c1dc9a842ca6LC_CTYPE=sv_SE.UTF-8WORKSPACE=/srv/lhome/jenkins/jobs/empty_env_var_test/workspaceLOGNAME=smokerBUILD_CAUSE=MANUALTRIGGER_=/usr/bin/daemonEXECUTOR_NUMBER=380TERM=rxvtBUILD_DISPLAY_NAME=#6LC_COLLATE=sv_SE.UTF-8HUDSON_HOME=/srv/lhome/jenkinsPATH=/home/smoker/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gamesBUILD_ID=2014-08-15_11-35-11BUILD_TAG=jenkins-empty_env_var_test-6DISPLAY=worabu.netinsight.se:0.0JENKINS_URL=http://smoketest.netinsight.se/jenkins/PYTHONUSERBASE=/home/smoker/.localLANG=CJOB_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/BUILD_NUMBER=6NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/_javascript_SHELL=/bin/bashHUDSON_SERVER_COOKIE=dad1862e4df27e29LC_MEASUREMENT=sv_SE.UTF-8JOB_NAME=empty_env_var_testPWD=/srv/lhome/jenkins/jobs/empty_env_var_test/workspaceLC_NUMERIC=sv_SE.UTF-8LC_PAPER=sv_SE.UTF-8BUILD_CAUSE_MANUALTRIGGER=trueFinished:SUCCESSmenuEnvironmentVariables:-_ /usr/bin/daemonBUILD_CAUSE MANUALTRIGGERBUILD_CAUSE_MANUALTRIGGER trueBUILD_DISPLAY_NAME #4BUILD_ID 2014-08-15_10-40-44BUILD_NUMBER 4BUILD_TAG jenkins-magjac-999-dev-smoke-fw025-nosa3-4BUILD_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/4/BUILD_USER magjacBUILD_USER_FIRST_NAME magjacBUILD_USER_ID magjacCONFIG_FILE fw025.rcDISPLAY worabu.netinsight.se:0.0DO_COPY trueDO_INSTALL falseDO_PUBLISH falseDO_TEST trueEXECUTOR_NUMBER 324EXIT_ON_FAILURE falseGIT_ROOT /home/magjac/git_repos2HOME /home/smokerHUDSON_HOME /srv/lhome/jenkinsHUDSON_SERVER_COOKIE dad1862e4df27e29HUDSON_URL http://smoketest.netinsight.se/jenkins/JENKINS_HOME /srv/lhome/jenkinsJENKINS_SERVER_COOKIE dad1862e4df27e29JENKINS_URL http://smoketest.netinsight.se/jenkins/JOB_NAME magjac-999-dev-smoke-fw025-nosa3JOB_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/LANG CLC_COLLATE sv_SE.UTF-8LC_CTYPE sv_SE.UTF-8LC_MEASUREMENT sv_SE.UTF-8LC_NUMERIC sv_SE.UTF-8LC_PAPER sv_SE.UTF-8LC_TIME en_DK.UTF-8LD_LIBRARY_PATH /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64LOGNAME smokerMAIL /var/mail/smokerNETI_BUILDID testingNODE_LABELS mastermaster_labelnullNODE_PATH /usr/lib/nodejs:/usr/lib/node_modules:/usr/share/_javascript_PATH
[JIRA] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Magnus Jacobsson commented on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API I think Daniel already has pointed out where the problem is. Follow his link. You just need to qualify that line with that the job being a matrix job. You can see the problem with any job. If you need a script to upload through the REST API, I may be able to create one for you. Let me know if you need it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24285) Improve commit message (our case 11772)
Jens Brejner updated JENKINS-24285 Improve commit message (our case 11772) Change By: Jens Brejner (18/Aug/14 5:55 AM) Summary: Improvecommitmessage (ourcase11772) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin (our case 11771)
Jens Brejner updated JENKINS-23901 Job SCM changes are not valid after running plugin (our case 11771) Change By: Jens Brejner (18/Aug/14 5:56 AM) Summary: JobSCMchangesarenotvalidafterrunningplugin (ourcase11771) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24284) In the commit message - don't write origin (our case 11769)
Jens Brejner updated JENKINS-24284 In the commit message - dont write origin (our case 11769) Change By: Jens Brejner (18/Aug/14 5:57 AM) Summary: Inthecommitmessage-dontwriteorigin (ourcase11769) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24286) Plugin tries to delete origin/master (our case 11770)
Jens Brejner updated JENKINS-24286 Plugin tries to delete origin/master (our case 11770) Change By: Jens Brejner (18/Aug/14 5:57 AM) Summary: Plugintriestodeleteorigin/master (ourcase11770) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
