[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
akiko_pusu commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I saw the same situation. I have two different version of Jenkins, ver 1.538 and ver 1.542, and now both Jenkins are in the same problem. (These Jenkins were fine at the end of last year…) Both Jenkins are up for 1 or 2 month. I wonder this is because Jetty's behavior. 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-11217) Not all failure cases reported for UnitTest results
Andy Bigos commented on JENKINS-11217 Not all failure cases reported for UnitTest results OK. I'll concat the results before passing to Jenkins. Thanks. 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/groups/opt_out.
[JIRA] [git] (JENKINS-14877) notifyCommit URL requires authentication contrary to dicumentation claim
Joël Joly closed JENKINS-14877 as Not A Defect notifyCommit URL requires authentication contrary to dicumentation claim I tested with a new DNS configuration of my server (the link to the jenkins server is now http://smth.comp.org) and the comment of Israel Tsadok is right on point. The 'jenkins' part of the URL must be removed in such cases and the curl command did work. I guess it was the same problem with my previous configuration. As a side note I tested notifyCommit?url="" but two jobs monitoring a 'integration' and a 'qa' branches were scheduled for polling (not really a problem for me, already happy to have a trigger on push). Change By: Joël Joly (06/Jan/14 11:08 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20068) Multijob Configuration page is not responding for addjobs, help(?) and advanced Buttons
Vamsi Hari commented on JENKINS-20068 Multijob Configuration page is not responding for addjobs, help(?) and advanced Buttons we are using Multijob plugin with version 1.9 i had updated it to version 1.10 and also updated the Jenkins version to 1.542. now its working fine. highly appreciate your response, keep helping. thanks. 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/groups/opt_out.
[JIRA] [downstream-ext] (JENKINS-21233) downstream does not keep the order of projects
Raul Dinegri created JENKINS-21233 downstream does not keep the order of projects Issue Type: Bug Affects Versions: current Assignee: kutzi Components: downstream-ext Created: 06/Jan/14 12:20 PM Description: I have the projects: 01.project 02.project 03.project In the main project I put 01.project, 02.project, 03.project But when I started the main job, they don't keep the order Fix Versions: current Project: Jenkins Priority: Major Reporter: Raul Dinegri 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20068) Multijob Configuration page is not responding for addjobs, help(?) and advanced Buttons
hagzag resolved JENKINS-20068 as Cannot Reproduce Multijob Configuration page is not responding for addjobs, help(?) and advanced Buttons Apparently once you update to 1.10 the issue is resolved. Change By: hagzag (06/Jan/14 12:39 PM) Status: Open Resolved Assignee: LiyaKatz hagzag 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/groups/opt_out.
[JIRA] [core] (JENKINS-10407) builds/1234, lastSuccessful and lastStable symlinks not created
Fabrice Daugan commented on JENKINS-10407 builds/1234, lastSuccessful and lastStable symlinks not created Same issue in 1.545 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/groups/opt_out.
[JIRA] [downstream-ext] (JENKINS-21233) downstream does not keep the order of projects
kutzi commented on JENKINS-21233 downstream does not keep the order of projects By 'they don't keep the order' you mean that Jenkins executes them in another order? a) the order in which downstream jobs are scheduled, is not guaranteed by the plugin b) even if it would be, it still wouldn't mean that Jenkins is running them in this order If you need to have a order in (downstream) jobs, you should enforce it among these jobs themselves - e.g. by defining an up/downstream dependency between these jobs and specify 'block while upstream job is running' 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/groups/opt_out.
[JIRA] [git] (JENKINS-20585) Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy
SCM/JIRA link daemon commented on JENKINS-20585 Git plugin 2.0 prevents project deletion on Windows, changelog.xml is busy Code changed in jenkins User: Mark Waite Path: src/test/java/hudson/plugins/git/GitChangeLogParserTest.java http://jenkins-ci.org/commit/git-plugin/5fd1622bf5cca13feeb9596e9d0451bb948f39dd Log: Delete sample changelog at end of test - check for open file leak JENKINS-20585 reports that changelog.xml cannot be deleted on Windows because it is held busy by a process. This test assumes that process is Jenkins itself, and that the GitChangeLogParser.parse() method is the most likely culprit. 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/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite reopened JENKINS-19994 Unable to delete workspace A new release of the git plugin will also be required before this bug is fixed. There is at least one call in the git plugin which needs to use the ChangelogCommand.abort() method that was added after git client plugin 1.6.0 was released. The git plugin version will need to be newer than 2.0 before this bug fix will be visible, assuming the pull request for the change is accepted. Change By: Mark Waite (06/Jan/14 1:24 PM) Resolution: Fixed Status: Resolved Reopened 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/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-11409) Gerrit-trigger should support waiting for downstream jobs of triggered builds
yannack commented on JENKINS-11409 Gerrit-trigger should support waiting for downstream jobs of triggered builds OK, I have just submitted a pull request adding this feature. I hope it makes it into the plugin soon. It works by adding a "delayed approval" setting to the Gerrit Trigger. When this is selected, the triggered job no longer auto-submits its result. Instead, there is a post-build action available which the downstream job will have to run. It needs to have a job name and a build number as a parameter, so these will need to be passed on as build variables. So as to solve the above problem of waiting forever, the "flexible publish" plugin can be used. Set it so you only do the delayed approval on your upstream project if it fails (thus not triggering downstream). In the most downstream project you can set it to always do the delayed approval. As you see this is still pretty manual, but it is a first draft, and has the benefit of working If there is enough interest, it can always be improved on later 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/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
SCM/JIRA link daemon commented on JENKINS-19994 Unable to delete workspace Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/d267bd6b16fc8d2d9c04b27a9ed805082592bab3 Log: Merge pull request #185 from MarkEWaite/JENKINS-19994-close-changelog-opened-files JENKINS-19994 Close files opened by computeChangeLog, use abort() Compare: https://github.com/jenkinsci/git-plugin/compare/5ac9acd02624...d267bd6b16fc 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/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
SCM/JIRA link daemon commented on JENKINS-19994 Unable to delete workspace Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/2faba2a2604090ffdd978dbe61d268bc05effc66 Log: JENKINS-19994 Close files opened by computeChangeLog, use new abort() method All calls to a changelog instance must conclude with either a call to execute() or a call to abort(). Files will be left open if one of those two methods is not called before the changelog instance goes out of scope. 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-21234) [xUnit] [ERROR] - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read xml file
Dattatrya More
created JENKINS-21234
[xUnit] [ERROR] - The plugin hasnt been performed correctly: hudson.util.IOException2: Failed to read xml file
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
xunit
Created:
06/Jan/14 1:33 PM
Description:
Related plugins that are installed
Behave Hudson Plugin version 3.0
HTML Publisher Plugin version 1.2
xUnit Plugin version 1.62
and created Maven project for automation test execution
Following things are working here -
1. report is generated successfully by Jbehave
2. HTML reports are archived successfully.
3. Jbehave tests are parsed and placed expected location.
4. xUnit ERROR - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read xml file
I have validated mentioned xml file is present and can view through jenkins workspace.
refer console logging for reference -
INFO Generating reports view to '/opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/workspace/target/jbehave' using formats 'stats, html, console, xml' and view properties '{defaultFormats=stats, decorateNonHtml=true, viewDirectory=view, decorated=ftl/jbehave-report-decorated.ftl, reports=ftl/jbehave-reports-with-totals.ftl, maps=ftl/jbehave-maps.ftl, navigator=ftl/jbehave-navigator.ftl, views=ftl/jbehave-views.ftl, nonDecorated=ftl/jbehave-report-non-decorated.ftl}'
INFO Reports view generated with 5 stories (of which 4 pending) containing 13 scenarios (of which 6 pending)
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO:
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: BUILD SUCCESS
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO:
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Total time: 3:45.993s
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Finished at: Fri Jan 03 02:02:28 CST 2014
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Final Memory: 22M/59M
Jan 03, 2014 2:02:28 AM org.apache.maven.cli.event.ExecutionEventLogger sessionEnded
INFO:
JENKINS Archiving /opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/workspace/pom.xml to /opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/modules/com.shc.partsdirect$pd-automation/builds/2014-01-03_01-58-38/archive/com.shc.partsdirect/pd-automation/0.0.1-SNAPSHOT/pd-automation-0.0.1-SNAPSHOT.pom
Waiting for Jenkins to finish collecting data
channel stopped
Archiving artifacts
htmlpublisher Archiving HTML reports...
htmlpublisher Archiving at BUILD level /opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/workspace/target/jbehave to /opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/builds/2014-01-03_01-58-34/htmlreports/HTML_Report
xUnit INFO - Starting to record.
xUnit INFO - Processing JBehave-3.x
xUnit INFO - JBehave-3.x - 7 test report file(s) were found with the pattern '*/jbehave/.xml' relative to '/opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/workspace' for the testing framework 'JBehave-3.x'.
xUnit ERROR - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read /opt/tomcat/.jenkins/jobs/pd_automation_consumer_node_pdapp401pcons1/workspace/generatedJUnitFiles/JBehave/TEST--485270419.xml
Build step 'Publish xUnit test result report' changed build result to FAILURE
Build step 'Publish xUnit test result report' marked build as failure
Sending e-mails to: dm...@searshc.com
Finished: FAILURE
Environment:
Jenkins ver. 1.526
Project:
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite resolved JENKINS-19994 as Fixed Unable to delete workspace Git plugin pull request has been accepted for a Git plugin version after 2.0. Not yet clear what version number that will be, only that the change is not in version 2.0, so it should be in the next version released after 2.0. Change By: Mark Waite (06/Jan/14 1:45 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view How about the following? In newJob page of ListView, a checkbox to control whether to add new job to the view. In config page of ListView, a checkbox to control default status of checkbox in newJob page. Implemented in: https://github.com/yoichi/jenkins/compare/JENKINS-19142-3 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/groups/opt_out.
[JIRA] [junit] (JENKINS-17883) flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56]
Régis Desgroppes commented on JENKINS-17883 flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56] Thanks a lot and merci beaucoup. 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21146) Toolkit path broken in mixed-OS environment
Heather Fraser-Dube commented on JENKINS-21146 Toolkit path broken in mixed-OS environment The failure is occurring on the Jenkins master. The Jenkins master also needs access to the build toolkit when starting the build. If the Master is running on Windows, the /var/appl/... path is not going to be able to be treated as an absolute path. I see from the trace: Local Build toolkit="/var/appl/jenkins/rtctoolkit-4.0.1/jazz/buildsystem/buildtoolkit " Node Build toolkit="/var/appl/jenkins/rtctoolkit-4.0.1/jazz/buildsystem/buildtoolkit" I am wondering if you have setup toolkit directories appropriately. When configuring Team Concert (in the Jenkins configuration) you should be able to test the connection successfully. For the slaves you will need to configure where the toolkits are located. See https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-Master%2FSlaveConfiguration. 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Uldis Karlovs-Karlovskis commented on JENKINS-10313 Fails to copy artifacts from one multi-configuration build to another Oh, this is quite disappointing. I need to have secured jobs for different projects so I can't allow authenticated users to see everything. Now instead of one generic job I must create all builds of possible choices... 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21146) Toolkit path broken in mixed-OS environment
Heather Fraser-Dube assigned JENKINS-21146 to Heather Fraser-Dube Toolkit path broken in mixed-OS environment Change By: Heather Fraser-Dube (06/Jan/14 2:29 PM) Assignee: HeatherFraser-Dube 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/groups/opt_out.
[JIRA] [core] (JENKINS-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation
Barthélémy von Haller commented on JENKINS-18407 Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation I confirm that using the REST API, I get a 200 instead of a 201 when performing a build. The URL I call is : https://hidden/jenkins/job/JOB/buildWithParameters?module=amoreTST 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/groups/opt_out.
[JIRA] [downstream-ext] (JENKINS-21233) downstream does not keep the order of projects
kutzi resolved JENKINS-21233 as Not A Defect downstream does not keep the order of projects Change By: kutzi (06/Jan/14 3:04 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/groups/opt_out.
[JIRA] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Régis Desgroppes commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Thank you for this 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20688) The Windows variant _netrc file is not searched in the home directory
Florian Zschocke closed JENKINS-20688 as Fixed The Windows variant _netrc file is not searched in the home directory Change By: Florian Zschocke (06/Jan/14 3:04 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20688) The Windows variant _netrc file is not searched in the home directory
Florian Zschocke resolved JENKINS-20688 as Fixed The Windows variant _netrc file is not searched in the home directory Fixed indirectly together with JENKINS-20684 Change By: Florian Zschocke (06/Jan/14 3:04 PM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20684) Support for .netrc file limited by strict file format requirement
Florian Zschocke closed JENKINS-20684 as Fixed Support for .netrc file limited by strict file format requirement Change By: Florian Zschocke (06/Jan/14 3:04 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-poll-action] (JENKINS-21231) /poll/ leads to a redirect loop
jieryn updated JENKINS-21231 /poll/ leads to a redirect loop Change By: jieryn (06/Jan/14 3:10 PM) Assignee: jieryn 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/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Mark Ottaviani resolved JENKINS-17058 as Fixed Publish over SSH plugin XML configuration cannot be read on jenkins start up. Fixed in version 1.11 of the Publish over SSH plugin. Change By: Mark Ottaviani (06/Jan/14 3:13 PM) Status: InProgress 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/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Mark Ottaviani assigned JENKINS-17058 to Thomas Van Doren Publish over SSH plugin XML configuration cannot be read on jenkins start up. Change By: Mark Ottaviani (06/Jan/14 3:14 PM) Assignee: bap ThomasVanDoren 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/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani resolved JENKINS-17885 as Fixed Publish over SSH lost main configuration data after jenkins server reboot Fixed in version 1.11 of the Publish over SSH plugin. Change By: Mark Ottaviani (06/Jan/14 3:14 PM) Status: Open Resolved Assignee: bap wearbif 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/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Daniel Beck commented on JENKINS-19142 Dont add jobs to a view From only reading the code, this looks like a reasonable compromise. I added a few comments on the commits. Just an idea, would an additional option 'Allow item creators to choose' be useful? I.e. to change between 'setting the default option' and 'enforcing one behavior' (maybe even in an Advanced… section of the list view configuration to make them less intimidating). This would allow the following: Include new item into the view, and do not offer to change this behavior (today's behavior) By default, include new item into the view, but offer to change this behavior By default, don't include new item into the view, but offer to change this behavior Don't include new item into the view, and do not offer to change this behavior If the user responsible for the view knows better than some item creator who happens to have access to the view, this would allow them to prevent adding entries to the list. 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Heather Fraser-Dube commented on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Removing the .jazz directory is not ideal. It will result in a complete re-load (as opposed to just the files that changed). I have raised 296206: Make "Just accept and fetch from a build workspace" more full featured in jazzdev to help us track this. I am curious, how do you decide if the component is "well-formed"? Is this something you do as part of the build or when setting up the build. Also can you describe how you would use "automated creation of build definitions" if that feature was available? I guess I am wondering when it would be automatically generated, which pieces would be configured? What were the other reasons for not using a build definition? 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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-18445) Local Integration Point
sego commented on JENKINS-18445 Local Integration Point Hi, even though this item was closed long ago, I'm not sure where else to ask the related question.. My setup is as follows: IntegritySCM: 1.19 Server: MKS Integrity 2009 (4.10.0.5679) Client: MKS Source 2009 Build: 8.10.0.5679 Service Pack: 004-01 IntegrityClient.port is set to 3100 in $HOME/.IntegrityClient.rc and an instance is started by running "si about" once before trying to use IntegritySCM plugin. -- On polling/checkout, I only get an "API Exception" without further meaningful errors in the log: DEBUG IntegritySCM - Start execution of checkout() routine...! DEBUG IntegritySCM - buildEnvVars() invoked...! DEBUG IntegritySCM - Creating Integrity API Session... INFO IntegritySCM - API Exception caught... INFO IntegritySCM - Failed to establish a session: OK DEBUG IntegritySCM - returned exit code -1 DEBUG IntegritySCM - buildEnvVars() invoked...! I tried snooping on the TCP connection and got the following from tcpdump -nKvvX -i lo port 3100: 15:58:11.666383 IP (tos 0x0, ttl 64, id 48635, offset 0, flags DF, proto TCP (6), length 60) 127.0.0.1.37696 127.0.0.1.3100: Flags S, seq 1564421816, win 32792, options mss 16396,sackOK,TS val 408261443 ecr 0,nop,wscale 6, length 0 0x: 4500 003c bdfb 4000 4006 7ebe 7f00 0001 E@.@.~. 0x0010: 7f00 0001 9340 0c1c 5d3f 2eb8 .@..]?.. 0x0020: a002 8018 fe30 0204 400c 0402 080a .0@. 0x0030: 1855 9343 0103 0306.U.C 15:58:11.666408 IP (tos 0x0, ttl 64, id 0, offset 0, flags DF, proto TCP (6), length 60) 127.0.0.1.3100 127.0.0.1.37696: Flags S., seq 299930233, ack 1564421817, win 32768, options mss 16396,sackOK,TS val 408261443 ecr 408261443,nop,wscale 6, length 0 0x: 4500 003c 4000 4006 3cba 7f00 0001 E@.@.. 0x0010: 7f00 0001 0c1c 9340 11e0 9279 5d3f 2eb9 ...@...y]?.. 0x0020: a012 8000 fe30 0204 400c 0402 080a .0@. 0x0030: 1855 9343 1855 9343 0103 0306.U.C.U.C 15:58:11.666423 IP (tos 0x0, ttl 64, id 48636, offset 0, flags DF, proto TCP (6), length 52) 127.0.0.1.37696 127.0.0.1.3100: Flags ., seq 1, ack 1, win 513, options nop,nop,TS val 408261443 ecr 408261443, length 0 0x: 4500 0034 bdfc 4000 4006 7ec5 7f00 0001 E..4..@.@.~. 0x0010: 7f00 0001 9340 0c1c 5d3f 2eb9 11e0 927a .@..]?.z 0x0020: 8010 0201 fe28 0101 080a 1855 9343 .(...U.C 0x0030: 1855 9343.U.C 15:58:11.667391 IP (tos 0x0, ttl 64, id 48637, offset 0, flags DF, proto TCP (6), length 298) 127.0.0.1.37696 127.0.0.1.3100: Flags P., seq 1:247, ack 1, win 513, options nop,nop,TS val 408261443 ecr 408261443, length 246 0x: 4500 012a bdfd 4000 4006 7dce 7f00 0001 E..*..@.@.}. 0x0010: 7f00 0001 9340 0c1c 5d3f 2eb9 11e0 927a .@..]?.z 0x0020: 8018 0201 ff1e 0101 080a 1855 9343 .U.C 0x0030: 1855 9343 4845 4144 202f 6963 6170 6920 .U.CHEAD./icapi. 0x0040: 4854 5450 2f31 2e31 0d0a 5072 6f74 6f63 HTTP/1.1..Protoc 0x0050: 6f6c 2d76 6572 7369 6f6e 3a20 312e 310d ol-version:.1.1. 0x0060: 0a43 6f64 6550 6167 653a 2055 5446 2d38 .CodePage:.UTF-8 0x0070: 0d0a 5469 6d65 5a6f 6e65 3a20 4575 726f ..TimeZone:.Euro 0x0080: 7065 2f42 6572 6c69 6e0d 0a41 7574 686f pe/Berlin..Autho 0x0090: 7269 7a61 7469 6f6e 3a20 4261 7369 6320 rization:.Basic. 0x00a0: 5a32 3930 6148 4e6c 4d54 706b 5457 677a Z290aHNlMTpkTWgz 0x00b0: 6247 7730 4951 3d3d 0d0a 4150 4956 6572 bGw0IQ==..APIVer 0x00c0: 7369 6f6e 3a20 342e 3131 2030 3030 2d30 sion:.4.11.000-0 0x00d0: 3020 300d 0a41 7070 5365 7373 696f 6e3a 0.0..AppSession: 0x00e0: 206e 6577 0d0a 5573 6572 2d41 6765 6e74 .new..User-Agent 0x00f0: 3a20 4a61 6b61 7274 6120 436f 6d6d 6f6e :.Jakarta.Common 0x0100: 732d 4874 7470 436c 6965 6e74 2f33 2e31 s-HttpClient/3.1 0x0110: 0d0a 486f 7374 3a20 3132 372e 302e 302e ..Host:.127.0.0. 0x0120: 313a 3331 3030 0d0a 0d0a 1:3100 15:58:11.667432 IP (tos 0x0, ttl 64, id 313, offset 0, flags DF, proto TCP (6), length 52) 127.0.0.1.3100 127.0.0.1.37696: Flags ., seq 1, ack 247, win 512, options nop,nop,TS val 408261443 ecr 408261443, length 0 0x: 4500 0034 0139 4000 4006 3b89 7f00 0001 E..4.9@.@.;. 0x0010: 7f00 0001 0c1c 9340 11e0 927a 5d3f 2faf ...@...z]?/. 0x0020: 8010 0200 fe28 0101 080a
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Goffredo Marocchi commented on JENKINS-21057 Cannot checkout git repository with submodules: FATAL: No remotes found! Manually changing .git/config works, but it is really not sustainable. Was the switch from clone to init+fetch really beneficial? Can we revert that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-21235) Artifactory plugin is configured to run post-build, but actually runs pre-Post-Steps
Rob van Oostrum created JENKINS-21235 Artifactory plugin is configured to run post-build, but actually runs pre-Post-Steps Issue Type: Bug Affects Versions: current Assignee: yossis Components: artifactory, maven, maven2 Created: 06/Jan/14 4:38 PM Description: Even though Artifactory plugin is in post-build, artifact deployment happens before post-steps (and it visually appears to actually be running as part of the main build step). So deployment happens regardless of whether a post-step fails or not, which appears to be broken behavior. the Artifactory plugin should respect the order of go, and not run out of sequence. Environment: Jenkins 1.545, Artifactory plugin 2.2.1, Maven integration plugin 2.1 Project: Jenkins Priority: Critical Reporter: Rob van Oostrum 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/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis created JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem Issue Type: Bug Affects Versions: current Assignee: bklarson Components: prioritysorter Created: 06/Jan/14 5:04 PM Description: Job Priority stopped working when updating Jenkins to LTS v1.532.1. Also, I have version 1.3 of PrioritySorter installed (now it goes at 2.4) and it doesn't shows up the option to update to the latest version of the plugin. I have also uninstalled, deleted PrioritySorter data (old data), restarted Jenkins and installed again, and it only lets install version 1.3. Environment: Ubuntu 8 Project: Jenkins Labels: plugin jenkins job Priority: Critical Reporter: pedro reis 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/groups/opt_out.
[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
cowwoc created JENKINS-21237 Jenkins should use LaunchAgents under OSX Issue Type: Improvement Assignee: Unassigned Components: core, xcode Created: 06/Jan/14 5:20 PM Description: JENKINS-9399 changed the Jenkins from using LaunchAgents to LaunchDaemons because, at the time, there were problems with running as an agent and using LaunchDaemons seems like the right approach. Two years later, it's pretty clear that using LaunchDaemons creates a whole host of problems which (I argue) are worse than using LaunchAgents in the first place. LaunchDaemons cannot launch GUI applications which means you cannot unit test iOS applications or launch with XCode "instructions"... both of which are in high demand. Anyway, I believe I discovered a way for us to have the best of both worlds: using LaunchAgents, having it auto-launch on boot, and preventing it from running under other users. I believe this will solve all outstanding problems. Configure Jenkins to use LaunchAgents (reverse JENKINS-9399). Install the plist into ~/Library/LaunchAgents instead of /Library/LaunchAgents to prevent it from getting triggered by other users logging in. Configure the Jenkins user to auto-login on startup, but return to the login menu immediately: http://www.tuaw.com/2011/03/07/terminally-geeky-use-automatic-login-more-securely/ Project: Jenkins Priority: Major Reporter: cowwoc 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/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-21238) Ability to run the generated job immediately after generation
François Granade created JENKINS-21238 Ability to run the generated job immediately after generation Issue Type: New Feature Assignee: Unassigned Components: jobgenerator Created: 06/Jan/14 5:24 PM Description: I'm using the job generator plugin to generate "re-runnable" jobs - for users to way to make it easy to rerun things later with the same config, the same settings, etc... for non-admin users. But my users wonder why they have to go through 2 steps: first create the job, and then run it. Wouldn't it be a nice improvement to have a checkbox that would immediately run the job after it has been generated ? Project: Jenkins Priority: Major Reporter: François Granade 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/groups/opt_out.
[JIRA] [core] (JENKINS-21239) Trend Graph NPE when no builds
Bruno Meneguello created JENKINS-21239 Trend Graph NPE when no builds Issue Type: Bug Assignee: Bruno Meneguello Components: core Created: 06/Jan/14 5:42 PM Description: I'm getting a NPE for a new project with no builds: Jan 06, 2014 3:27:40 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving http://localhost:8080/job/Teste/buildTimeGraph/png java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at
[JIRA] [teamconcert] (JENKINS-21146) Toolkit path broken in mixed-OS environment
Scott Fisler resolved JENKINS-21146 as Not A Defect Toolkit path broken in mixed-OS environment Sorry, I had configured a second build toolkit. Didn't realize that I could 'override' the Windows version on the agent (or that the controller and agent both need the toolkit). Working now. Change By: Scott Fisler (06/Jan/14 5:43 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/groups/opt_out.
[JIRA] [warnings] (JENKINS-21240) Javac compiler cannot find annotation method warnings are ignored
David Humeniuk created JENKINS-21240 Javac compiler cannot find annotation method warnings are ignored Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 06/Jan/14 5:46 PM Description: I have a few of the following warnings outputted by javac: aaa.class: warning: Cannot find annotation method 'xxx()' in type '': class file for fully.qualified.ClassName not found However, they are not being picked up by the Warnings plug-in. I assume it is because they don't have the typical format of "javac file: warning: type message" (as the type part is not there). Project: Jenkins Priority: Major Reporter: David Humeniuk 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-15507) Environment variables are not injected in parent matrix job
S Stack
edited a comment on JENKINS-15507
Environment variables are not injected in parent matrix job
Reopening/Bug seen in 1.73 - 1.88
We've been stuck at EnvInject version 1.72 for the past year.
Using SharedObjects 0.44
Using Rebuilder 1.20
Simple usage scenario to recreate bug
Create a matrix job with one user-defined axis named SERVICE_NAME; values are A B C
check : Run each configuration sequentially
Rebuild settings
check: Prepare an environment for run
check: Keep Jenkins env var's
check: Keep Jenkins build var's
Evaluated Groovy script
def env = [:]
if ( SERVICE_NAME == 'C' ) {
env = ["ADDITIONAL_SETTINGS" : " xyz " ];
} else {
env = ["ADDITIONAL_SETTINGS" : "" ];
}
Results
1.72
Each axis job runs successfully
Example log for SERVICE_NAME = C
Started by upstream project "test-JENKINS-15507" build number 1
originally caused by:
Started by user sstack
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Adding build parameters as variables.
[EnvInject] - Evaluation the following Groovy script content:
def env = [:]
if (SERVICE_NAME == 'C') {
env = ["ADDITIONAL_SETTINGS" : " xyz "];
} else {
env = ["ADDITIONAL_SETTINGS" : ""];
}
return env;
[EnvInject] - Injecting contributions.
Building in workspace /var/opt/jenkins-data/jobs/test-JENKINS-15507/workspace/SERVICE_NAME/C
[C] $ /usr/bin/env bash /var/tmp/jenkins/hudson8185538443495220535.sh
1.73 and later
Parent matrix job fails and thus no axis children jobs are executed.
Started by user sstack
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Evaluation the following Groovy script content:
def env = [:]
if (SERVICE_NAME == 'C') {
env = ["ADDITIONAL_SETTINGS" : " xyz "];
} else {
env = ["ADDITIONAL_SETTINGS" : ""];
}
return env;
[EnvInject] - [ERROR] - SEVERE ERROR occurs: No such property: SERVICE_NAME for class: Script1
Finished: FAILURE
SERVICE_NAMEC
ADDITIONAL_SETTINGS [ xyz ]
Finished: SUCCESS
In the failed job above, the Evaluated Groovy Script doesn't recognize the axis value SERVICE_NAME as an exported property/env var.
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/groups/opt_out.
[JIRA] [envinject] (JENKINS-15507) Environment variables are not injected in parent matrix job
S Stack
reopened JENKINS-15507
Environment variables are not injected in parent matrix job
Reopening/Bug seen in 1.73 - 1.88
We've been stuck at EnvInject version 1.72 for the past year.
Using SharedObjects 0.44
Using Rebuilder 1.20
Simple usage scenario
Create a matrix job with one user-defined axis named SERVICE_NAME; values are A B C
check : Run each configuration sequentially
Rebuild settings
check: Prepare an environment for run
check: Keep Jenkins env var's
check: Keep Jenkins build var's
Evaluated Groovy script
def env = [:]
if ( SERVICE_NAME == 'C' ) {
env = ["ADDITIONAL_SETTINGS" : " xyz " ];
} else {
env = ["ADDITIONAL_SETTINGS" : "" ];
}
Results
1.72
Each axis job runs successfully
Example log for SERVICE_NAME = C
Started by upstream project "test-JENKINS-15507" build number 1
originally caused by:
Started by user sstack
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Adding build parameters as variables.
[EnvInject] - Evaluation the following Groovy script content:
def env = [:]
if (SERVICE_NAME == 'C') {
env = ["ADDITIONAL_SETTINGS" : " xyz "];
} else {
env = ["ADDITIONAL_SETTINGS" : ""];
}
return env;
[EnvInject] - Injecting contributions.
Building in workspace /var/opt/jenkins-data/jobs/test-JENKINS-15507/workspace/SERVICE_NAME/C
[C] $ /usr/bin/env bash /var/tmp/jenkins/hudson8185538443495220535.sh
h5. 1.73 and later
* Parent matrix job fails and thus no axis children jobs are executed.
Started by user sstack
EnvInject - Loading node environment variables.
EnvInject - Preparing an environment for the build.
EnvInject - Keeping Jenkins system variables.
EnvInject - Keeping Jenkins build variables.
EnvInject - Evaluation the following Groovy script content:
def env = :
if (SERVICE_NAME == 'C') {
env = ["ADDITIONAL_SETTINGS" : " xyz "];
} else {
env = ["ADDITIONAL_SETTINGS" : ""];
}
return env;
EnvInject - ERROR - SEVERE ERROR occurs: No such property: SERVICE_NAME for class: Script1
Finished: FAILURE
SERVICE_NAME[C]
ADDITIONAL_SETTINGS [ xyz ]
Finished: SUCCESS
In the failed job above, the Evaluated Groovy Script doesn't recognize the axis value SERVICE_NAME as an exported property/env var.
Change By:
S Stack
(06/Jan/14 6:08 PM)
Resolution:
Fixed
Status:
Resolved
Reopened
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/groups/opt_out.
[JIRA] [envinject] (JENKINS-15507) Environment variables are not injected in parent matrix job
S Stack
edited a comment on JENKINS-15507
Environment variables are not injected in parent matrix job
Reopening/Bug seen in 1.73 - 1.88
We've been stuck at EnvInject version 1.72 for the past year.
Using SharedObjects 0.44
Using Rebuilder 1.20
Simple usage scenario to recreate bug
Create a matrix job with one user-defined axis named SERVICE_NAME; values are A B C
check : Run each configuration sequentially
Rebuild settings
check: Prepare an environment for run
check: Keep Jenkins env var's
check: Keep Jenkins build var's
Evaluated Groovy script
def env = [:]
if ( SERVICE_NAME == 'C' ) {
env = ["ADDITIONAL_SETTINGS" : " xyz " ];
} else {
env = ["ADDITIONAL_SETTINGS" : "" ];
}
Results
1.72
Each axis job runs successfully
Example log for SERVICE_NAME = C
Started by upstream project "test-JENKINS-15507" build number 1
originally caused by:
Started by user sstack
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Adding build parameters as variables.
[EnvInject] - Evaluation the following Groovy script content:
def env = [:]
if (SERVICE_NAME == 'C') {
env = ["ADDITIONAL_SETTINGS" : " xyz "];
} else {
env = ["ADDITIONAL_SETTINGS" : ""];
}
return env;
[EnvInject] - Injecting contributions.
Building in workspace /var/opt/jenkins-data/jobs/test-JENKINS-15507/workspace/SERVICE_NAME/C
[C] $ /usr/bin/env bash /var/tmp/jenkins/hudson8185538443495220535.sh
1.73 and later
Parent matrix job fails and thus no axis children jobs are executed.
Started by user sstack
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Evaluation the following Groovy script content:
def env = [:]
if (SERVICE_NAME == 'C') {
env = ["ADDITIONAL_SETTINGS" : " xyz "];
} else {
env = ["ADDITIONAL_SETTINGS" : ""];
}
return env;
[EnvInject] - [ERROR] - SEVERE ERROR occurs: No such property: SERVICE_NAME for class: Script1
Finished: FAILURE
In the failed job above, the Evaluated Groovy Script doesn't recognize the axis value SERVICE_NAME as an exported property/env var.
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/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-20837) Differential backups should not cause Jenkins to stop running new jobs
Patrice Matignon commented on JENKINS-20837 Differential backups should not cause Jenkins to stop running new jobs I also run into the same problem for the same scenarios described in this ticket. And I like the proposed solution, as long as only the running builds, and not the whole job where at least one build is currently running, are skipped. In other words, I would want to make sure that my job configuration in particular, is backed up regardless. I believe this is what the description is indeed saying but I wanted to be explicit about that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed
Mark Edington commented on JENKINS-14117 The plugin hasnt been performed correctly: remote file operation failed 1.78 is working without any error for me now. Thanks. 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/groups/opt_out.
[JIRA] [sitemonitor] (JENKINS-13358) Timeout not working
Mark Edington commented on JENKINS-13358 Timeout not working I have a 2 line for for this (setting the read timeout on the connection), shall I submit a pull request? The fix in Pull Request #7 involves quite bit more code change. It's not clear on what is gained from invoking the URL asynchronously. 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/groups/opt_out.
[JIRA] [sitemonitor] (JENKINS-13358) Timeout not working
Mark Edington edited a comment on JENKINS-13358 Timeout not working I have a 2 line fix for this (setting the read timeout on the connection), shall I submit a pull request? The fix in Pull Request #7 involves quite bit more code change. It's not clear on what is gained from invoking the URL asynchronously. 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/groups/opt_out.
[JIRA] [naginator] (JENKINS-21241) Plugin should expose environment variables to tell how many times naginator has restarted the build
aflat created JENKINS-21241 Plugin should expose environment variables to tell how many times naginator has restarted the build Issue Type: New Feature Affects Versions: current Assignee: Nicolas De Loof Attachments: env_vrs.patch Components: naginator Created: 06/Jan/14 7:29 PM Description: I have naginator restarting my build 5 times, after the 5th and final try I need to know that it was the last time it was going to try, so I can do other steps. I would like either naginator to do these steps, or expose an environment variable to say how many times it is going to run, and how many times it has run. I have made the modifications, but not being the best java dev, it's ugly. It works, but it's ugly. Unit tests currently fail as well. It creates 2 env vars NAGINATORCOUNT NAGINATORMAXCOUNT Project: Jenkins Priority: Major Reporter: aflat 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20220) config history diff does not work for jobs in folders
Mirko Friedenhagen resolved JENKINS-20220 as Fixed config history diff does not work for jobs in folders As reported by Walter, this seems to be fixed Change By: Mirko Friedenhagen (06/Jan/14 8:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
Magnus Sandberg assigned JENKINS-21236 to Magnus Sandberg PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem Change By: Magnus Sandberg (06/Jan/14 8:14 PM) Assignee: bklarson MagnusSandberg 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/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
Magnus Sandberg commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem What do you mean with "stopped working" do you get any errors? The update center for LTS is, as far as I can see, not updated - I would not recommend using 1.532.1 until it is officially announced on the web-site. 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
Mirko Friedenhagen commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction I am still not able to reproduce this 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20571) WARNING: Caught exception evaluating: it.showBadge() and it.oldConfigsExist()
Mirko Friedenhagen commented on JENKINS-20571 WARNING: Caught exception evaluating: it.showBadge() and it.oldConfigsExist() Samuel Lopez: so your original error is gone and you now see JENKINS-20511? 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/groups/opt_out.
[JIRA] [core] (JENKINS-21239) Trend Graph NPE when no builds
SCM/JIRA link daemon commented on JENKINS-21239 Trend Graph NPE when no builds Code changed in jenkins User: Bruno Kühnen Meneguello Path: core/src/main/java/hudson/model/Job.java http://jenkins-ci.org/commit/jenkins/6763eb88e87638a05f699152937ff6ba44a8aef9 Log: FIXED JENKINS-21239 Trend Graph NPE when no builds 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/groups/opt_out.
[JIRA] [core] (JENKINS-12734) Add test option for HTTP Proxy Configuration of Plugin Manager
Gwen Georgeault closed JENKINS-12734 as Fixed Add test option for HTTP Proxy Configuration of Plugin Manager A "Validate proxy" button has been added to "Test URL". Tested with build 1.542 Change By: Gwen Georgeault (06/Jan/14 9:09 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21239) Trend Graph NPE when no builds
SCM/JIRA link daemon resolved JENKINS-21239 as Fixed Trend Graph NPE when no builds Change By: SCM/JIRA link daemon (06/Jan/14 9:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fortify360] (JENKINS-21242) fortify360 plugin fails on JBoss AS 5.1.0
Ashwin Venkatasubbaraya created JENKINS-21242 fortify360 plugin fails on JBoss AS 5.1.0 Issue Type: Bug Affects Versions: current Assignee: samngms Attachments: server.log Components: fortify360 Created: 06/Jan/14 9:35 PM Description: After installing the plugin and configuring the token, SSC URL, jarsPath and version, "Test Connection" fails with InvocationTargetException (LinkageError) in the server logs (see attachment). The same configuration and the plugin build works on Tomcat 6/7. Environment: Fortify SSC 3.90 Jenkins 1.509 JBoss AS 5.1.0 Project: Jenkins Priority: Critical Reporter: Ashwin Venkatasubbaraya 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/groups/opt_out.
[JIRA] [rtc] (JENKINS-12066) [RTC Plugin] Load and build single component
muthukrishnan selvaraj commented on JENKINS-12066 [RTC Plugin] Load and build single component Hi I am a new bee and would have the same issue: I have multiple component in a stream. I am able to load all teh components at using the BDF but I would like to update one component instead of all. Can you suggest. I could see in the post 'https://wiki.jenkins-ci.org/display/JENKINS/Rational+Team+Concert+Plugin?focusedCommentId=59508891#comment-59508891 ' you asked to do this 'lscm load "worspaceName" "componentName" -u *** -P *** -r http://foo -d /absolute/path/toJenkinsWorkspace -f' can you suggest me will it work if I add this as a batch command in the jenkins job. Appreciate your help on this. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21239) Trend Graph NPE when no builds
dogfood commented on JENKINS-21239 Trend Graph NPE when no builds Integrated in jenkins_main_trunk #3149 FIXED JENKINS-21239 Trend Graph NPE when no builds (Revision 6763eb88e87638a05f699152937ff6ba44a8aef9) Result = SUCCESS Vojtech Juranek : 6763eb88e87638a05f699152937ff6ba44a8aef9 Files : core/src/main/java/hudson/model/Job.java 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/groups/opt_out.
[JIRA] [core] (JENKINS-21243) Include option to filter 'Run Parameters' based on min and max build numbers
Ioannis Moutsatsos created JENKINS-21243 Include option to filter Run Parameters based on min and max build numbers Issue Type: Improvement Assignee: Unassigned Components: core Created: 06/Jan/14 10:39 PM Description: The builds that appear in the Run Parameter selection box have a few limited filtering options (All, Completed, Successful, Stable). However, build artifacts can evolve well beyond these categories over a period of time, such that a build artifact is no longer suitable for usage as a build run parameter even if it's build completed or was successful. It would be useful to be able to combine these build categories with a minimal and/or maximal build number that is acceptable for inclusion as a run parameter in the current job. This would allow for a single job form to be reused over a much longer period of time by simply changing the filter of acceptable builds. Otherwise we observe that some form of versioning of the jobs and their forms has to be maintained so that appropriate job parameters can be matched. We are developing bioinformatic workflows based on Jenkins, so that artifacts represent various analysis results/data structures which over time may be or may not be suitable for downstream processing. Linked to JENKINS-7280 Project: Jenkins Labels: configuration gui build Priority: Minor Reporter: Ioannis Moutsatsos 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Adrian Blakey created JENKINS-21244 Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer Issue Type: Bug Affects Versions: current Assignee: Raphael CHAUMIER Components: weblogic-deployer Created: 06/Jan/14 10:43 PM Due Date: 17/Jan/14 12:00 AM Project: Jenkins Priority: Minor Reporter: Adrian Blakey 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Adrian Blakey updated JENKINS-21244 Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer Change By: Adrian Blakey (06/Jan/14 10:52 PM) Environment: Linux Description: Mybuildutputproducedbymvninstalllooksabitlikethis:/home/ca31319/archdata/jenkins/jobs/Epdservices/modules/org.delta$org.delta.epd.services/builds/2014-01-06_14-08-56/archive/org.delta/org.delta.epd.services/1.0-SNAPSHOT/org.delta.epd.services-1.0-SNAPSHOT.warNoticethe$inthemoduleresult.Thisfilenameispassedonthecommandlinetoweblogic.jarwithoutthe$beingescaped-hencethefileisnotfound./usr/java/jdk1.7.0_45/jre/bin/java-Xms256M-Xmx256M-cp/opt/oracle/wls12120/wlserver/server/lib/weblogic.jarweblogic.Deployer-debug-stage-remote-verbose-upload-nameEPDServices-source/home/ca31319/archdata/jenkins/jobs/Epdservices/modules/org.delta$org.delta.epd.services/builds/2014-01-06_14-08-56/archive/org.delta/org.delta.epd.services/1.0-SNAPSHOT/org.delta.epd.services-1.0-SNAPSHOT.war-targetsmyserver-adminurlt3://rc-lx433.ut.dentegra.lab:7001-userweblogic-passwordweblogic001-deployIfIcutandpastethisintoaterminalandescapethe$-itworksfine.Pleasecouldyouprovideafix? 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21245) userid to email address lookup
Matthew Kruer created JENKINS-21245 userid to email address lookup Issue Type: Improvement Assignee: Alex Earl Components: email-ext Created: 06/Jan/14 11:43 PM Description: I am dealing with a lot of users that are making commits against a few different repository (cvs, git, svn, etc…) Each repository was setup with a non-standard user id schema, not to mention that the e-mail server was setup with a different id schema as well. The current email-ext plug-in tries to send of emails to the offender based upon the user id it finds and appends the domain to the end. The issue is that user id is not the same as the e-mail. Currently: jdoe = j...@somewhere.com == invalid doejohn = doej...@somewhere.com == invalid johndoe123 = johndoe...@somewhere.com == invalid Should resolve as: jdoe = john@somewhere.com == valid doejohn = john@somewhere.com == valid johndoe123 = john@somewhere.com == valid The real email for all three user ids would be john@somewhere.com any time it sees jdoe doejohn or johndoe123. Project: Jenkins Priority: Major Reporter: Matthew Kruer 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21245) userid to email address lookup
Alex Earl commented on JENKINS-21245 userid to email address lookup If you setup users in Jenkins for each username and associate the email address it should resolve correctly. Not a great solution, but its a pretty horrible problem to have in the first place. 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21245) userid to email address lookup
Matthew Kruer commented on JENKINS-21245 userid to email address lookup If it were only that easy, these things happen when you are part of a start up that gets acquired by another larger start-up who is then acquired again a little later by a multinational company all in the span of 2 yrs. The irony is that the user id is not the same as the e-mail for said multinational company. Still it would be a nice feature to have, something like a user alias. Thanks for looking at this. 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21245) userid to email address lookup
Alex Earl commented on JENKINS-21245 userid to email address lookup What I mean is if you create users in the Jenkins user database for each username and provide an email address, it should resolve correctly. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Dale King
commented on JENKINS-17526
Broken CSS when reloading Jenkins after a time of inactivity
The answer is moving the temp dir for Jetty outside of the normal temp directory which gets periodically cleaned. If you examine Greg's pull request you can see which files to change to move the temp dir for jetty and I can confirm this fixes the problem.
To implement that solution is to edit /Library/Application Support/Jenkins/jenkins-runner.sh (you'll need su priveleges to do so) and add this line to the middle of the file near the lines that are similar:
tmpdir=`$defaults tmpdir` javaArgs="$javaArgs -Djava.io.tmpdir=${tmpdir}"
You'll need to create a temp directory for Jenkins (/Users/Shared/Jenkins/temp in my example) and give ownership to Jenkins:
sudo mkdir -p /Users/Shared/Jenkins/temp
sudo chown jenkins:jenkins /Users/Shared/Jenkins/temp
Then you need to set that directory as default:
defaults write /Library/Preferences/org.jenkins-ci tmpdir /Users/Shared/Jenkins/temp
Restart Jenkins and the problem will be gone for good.
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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Matt Gumbel commented on JENKINS-10313 Fails to copy artifacts from one multi-configuration build to another To work around this in our environment, I just built my own version of the plugin with the check in question commented out. Total hack, but worth it to avoid the alternative... 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/groups/opt_out.
[JIRA] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Markus Helm commented on JENKINS-21104 Confluence Publisher Plugin ignores Jenkins proxy settings Do you see a chance that it'll be fixed in the next release? And when is this release planned? 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-21188) Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access project for not-logged in users
Toshiyuki Kawanishi commented on JENKINS-21188 Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access project for not-logged in users I occurred following errors. Caused by: java.lang.NullPointerException at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.getItems(BuildPipelineView.java:773) at hudson.security.AuthorizationStrategy$1.hasPermission(AuthorizationStrategy.java:104) at hudson.security.ACL.hasPermission(ACL.java:64) at hudson.model.View.hasPermission(View.java:581) at hudson.model.ViewGroupMixIn.getViews(ViewGroupMixIn.java:115) at jenkins.model.Jenkins.getViews(Jenkins.java:1458) 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21246) email-ext serialises concurrent builds waiting for checkpoint
Stephen Morrison created JENKINS-21246 email-ext serialises concurrent builds waiting for checkpoint Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 07/Jan/14 6:28 AM Description: When running concurrent builds of a job, they all block with this message: Editable Email Notification is waiting for a checkpoint on ... Looks to be something that needs to be fixed on a per plugin basis going by JENKINS-9913 Environment: email-ext Plugin version 2.36 Jenkins Version 1.546 Project: Jenkins Labels: email-ext Priority: Critical Reporter: Stephen Morrison 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-21247) [xunit] fails to parse junit test report with a single ignored testcase
jskovjyskebankdk created JENKINS-21247 [xunit] fails to parse junit test report with a single ignored testcase Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 07/Jan/14 6:38 AM Description: xUnit does not like the output below - from a test class with just a single ignored test: ?xml version="1.1" encoding="UTF-8"? testsuite name="dk.jyskebank.jboss.luna.sec.domain.test.LunaJaasSecurityDomainTest" tests="1" failures="0" errors="0" timestamp="2014-01-06T16:11:14" hostname="SF120WS8" time="0.0" properties/ ignored-testcase name="testNativeAliasName" classname="dk.jyskebank.jboss.luna.sec.domain.test.LunaJaasSecurityDomainTest" time="0.0"/ system-out![CDATA[]]/system-out system-err![CDATA[]]/system-err /testsuite Environment: Win7, Java 6, Junit 4.8.2, xunit 0.78 Project: Jenkins Priority: Minor Reporter: jskovjyskebankdk 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/groups/opt_out.
