[JIRA] (JENKINS-14018) NullPointerException using Cpplint parser in warnings plugin on console log.

Fabian Pachner created JENKINS-14018: Summary: NullPointerException using Cpplint parser in warnings plugin on console log. Key: JENKINS-14018 URL: https://issues.jenkins-ci.org/browse/JENKINS-14018

[JIRA] (JENKINS-13909) Plugin update via manual upload fails on recent Jenkins version ?

[ https://issues.jenkins-ci.org/browse/JENKINS-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163501#comment-163501 ] SCM/JIRA link daemon commented on JENKINS-13909: Code changed in jenkins

[JIRA] (JENKINS-13909) Plugin update via manual upload fails on recent Jenkins version ?

[ https://issues.jenkins-ci.org/browse/JENKINS-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163502#comment-163502 ] SCM/JIRA link daemon commented on JENKINS-13909: Code changed in jenkins

[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building

Andreas created JENKINS-14019: - Summary: Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building Key: JENKINS-14019 URL: https://issues.jenkins-ci.org/browse/JENKINS-14019

[JIRA] (JENKINS-14020) Exception during workspace synchronize

Cyril Jean created JENKINS-14020: Summary: Exception during workspace synchronize Key: JENKINS-14020 URL: https://issues.jenkins-ci.org/browse/JENKINS-14020 Project: Jenkins Issue Type: Bug

[JIRA] (JENKINS-13990) Polling find old already considered baselines

[ https://issues.jenkins-ci.org/browse/JENKINS-13990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13990 started by Bue Petersen. Polling find old already considered baselines - Key:

[JIRA] (JENKINS-13990) Polling find old already considered baselines

[ https://issues.jenkins-ci.org/browse/JENKINS-13990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13990 stopped by Bue Petersen. Polling find old already considered baselines - Key:

[JIRA] (JENKINS-13990) Polling find old already considered baselines

[ https://issues.jenkins-ci.org/browse/JENKINS-13990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13990 started by Bue Petersen. Polling find old already considered baselines - Key:

[JIRA] (JENKINS-11598) Updating Plugins from plugins mirror and own update-center.json does not work

[ https://issues.jenkins-ci.org/browse/JENKINS-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163503#comment-163503 ] cforce commented on JENKINS-11598: -- I think i found the cause Jun 5, 2012 8:35:35 AM

[JIRA] (JENKINS-13670) Use Action instead of state object

[ https://issues.jenkins-ci.org/browse/JENKINS-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Wolfgang resolved JENKINS-13670. -- Resolution: Fixed Use Action instead of state object

[JIRA] (JENKINS-13670) Use Action instead of state object

[ https://issues.jenkins-ci.org/browse/JENKINS-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13670 started by Christian Wolfgang. Use Action instead of state object -- Key: JENKINS-13670

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

[ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Villanueva reopened JENKINS-11933: -- it is not resolved Subversion plugin doesn't probably work

[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7

[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Villanueva reopened JENKINS-11381: -- It is not resolved Subversion Plugin does not support

[JIRA] (JENKINS-14021) readlink not working on HP Itanium

Fulvio Cavarretta created JENKINS-14021: --- Summary: readlink not working on HP Itanium Key: JENKINS-14021 URL: https://issues.jenkins-ci.org/browse/JENKINS-14021 Project: Jenkins Issue

[JIRA] (JENKINS-13970) Build variable CC_BASELINE not populated with used baseline

[ https://issues.jenkins-ci.org/browse/JENKINS-13970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163509#comment-163509 ] Christian Wolfgang commented on JENKINS-13970: -- Ok, I have been able to

[JIRA] (JENKINS-13970) Build variable CC_BASELINE not populated with used baseline

[ https://issues.jenkins-ci.org/browse/JENKINS-13970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163513#comment-163513 ] Christian Wolfgang commented on JENKINS-13970: -- I have identified the problem.

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Searle reopened JENKINS-12176: -- The file handles plugin reports that it is coming from xtrigger: #4

[JIRA] (JENKINS-13957) Matrix builds disappear after Jenkins upgrade

[ https://issues.jenkins-ci.org/browse/JENKINS-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163516#comment-163516 ] Antonios Chalkiopoulos commented on JENKINS-13957: -- Same behaviour on

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Searle updated JENKINS-12176: - Component/s: xtrigger (was: fstrigger) Unable to delete a job that

[JIRA] (JENKINS-13413) Git icon(git-48x48.png) missing in job page.

[ https://issues.jenkins-ci.org/browse/JENKINS-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163517#comment-163517 ] Joe Hansche commented on JENKINS-13413: --- This appears to still be happening, except

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163515#comment-163515 ] Jim Searle edited comment on JENKINS-12176 at 6/5/12 7:57 PM: --

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163518#comment-163518 ] Gregory Boissinot commented on JENKINS-12176: - I'm afraid I can't reproduce. I

[JIRA] (JENKINS-13413) Git icon(git-48x48.png) missing in job page.

[ https://issues.jenkins-ci.org/browse/JENKINS-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163519#comment-163519 ] sogabe commented on JENKINS-13413: -- Not released yet. Git

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Boissinot updated JENKINS-12176: Component/s: fstrigger (was: xtrigger) Unable to

[JIRA] (JENKINS-13967) Xunit don't recognize cppunit report with time execution

[ https://issues.jenkins-ci.org/browse/JENKINS-13967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas JAN reopened JENKINS-13967: --- XUnit parse the XML report without error. But the time execution of tests in xunit are always

[JIRA] (JENKINS-10025) Calling rebuildDependencyGraph() in cycle

[ https://issues.jenkins-ci.org/browse/JENKINS-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eguess74 updated JENKINS-10025: --- Assignee: abayer (was: Timothy Bingaman) Andrew, I took freedom to reassign it to you hoping

[JIRA] (JENKINS-14023) System.exit (13) in a groovy script causes Jenkins shutdown

[ https://issues.jenkins-ci.org/browse/JENKINS-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vjuranek resolved JENKINS-14023. Resolution: Not A Defect Hi, system groovy scripts (which also is groovy scripts called via CLI)

[JIRA] (JENKINS-14024) Disable resolving relative to absolute paths

Kevin Neal created JENKINS-14024: Summary: Disable resolving relative to absolute paths Key: JENKINS-14024 URL: https://issues.jenkins-ci.org/browse/JENKINS-14024 Project: Jenkins Issue

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163523#comment-163523 ] Jim Searle commented on JENKINS-12176: -- What about: lsof | grep

[JIRA] (JENKINS-13904) EnvInject Plugin: option to replace invalid characters in env var names with underscores

[ https://issues.jenkins-ci.org/browse/JENKINS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Boissinot updated JENKINS-13904: Component/s: core (was: envinject) In my opinion, EnvInject

[JIRA] (JENKINS-13967) Xunit don't recognize cppunit report with time execution

[ https://issues.jenkins-ci.org/browse/JENKINS-13967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163526#comment-163526 ] Gregory Boissinot commented on JENKINS-13967: - Sure, this is the expected

[JIRA] (JENKINS-13967) Xunit don't recognize cppunit report with time execution

[ https://issues.jenkins-ci.org/browse/JENKINS-13967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Boissinot updated JENKINS-13967: Issue Type: New Feature (was: Bug) Priority: Minor (was: Major)

[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger

[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163528#comment-163528 ] Jim Searle commented on JENKINS-12176: -- It's a UNIX thing, there is a directory in

[JIRA] (JENKINS-8440) subversion plugin incorrectly reports 'no changes' if previous checkout/update fails

[ https://issues.jenkins-ci.org/browse/JENKINS-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163529#comment-163529 ] Valerie Wagner commented on JENKINS-8440: - We had a random Subversion update fail,

[JIRA] (JENKINS-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks

[ https://issues.jenkins-ci.org/browse/JENKINS-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163530#comment-163530 ] SCM/JIRA link daemon commented on JENKINS-13647: Code changed in jenkins

[JIRA] (JENKINS-13742) Field validation does not pass required query parameters when some fields are specified in a nested Describable

[ https://issues.jenkins-ci.org/browse/JENKINS-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi updated JENKINS-13742: Description: The collabnet plugin was updated/modernized a couple years ago to

[JIRA] (JENKINS-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks

[ https://issues.jenkins-ci.org/browse/JENKINS-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Boissinot resolved JENKINS-13647. - Resolution: Fixed Environment variables from EnvInject plugin are not

[JIRA] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)

Yi Wen created JENKINS-14026: Summary: git plugin doesn't support branch name contains slash (/) Key: JENKINS-14026 URL: https://issues.jenkins-ci.org/browse/JENKINS-14026 Project: Jenkins