[JIRA] (JENKINS-3681) Hide Empty Tabs (Views) in the GUI
[ https://issues.jenkins-ci.org/browse/JENKINS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163443#comment-163443 ] Sami Salonen commented on JENKINS-3681: --- This change introduces a small side effect. I use Sectioned View plugin to create a view, which does not contain projects, but informative content in textual format like FAQs, announcements, etc. With this change, this info view became unavailable for end users. As a workaround I added a List View section with one project to the bottom of the view. I also removed all columns from the section. This leaves two empty bars at the end of the view. It does not look pretty, but at least the view is visible to end users again. Jenkins version is 1.460. Hide Empty Tabs (Views) in the GUI -- Key: JENKINS-3681 URL: https://issues.jenkins-ci.org/browse/JENKINS-3681 Project: Jenkins Issue Type: Improvement Components: gui Affects Versions: current Environment: Platform: All, OS: All Reporter: rnell I'd like the ability to hide tabs that have no visible jobs. We use Project Based Security to limit development access to only their projects. I don't like that developers can still see all tabs used by the other groups, even though they are empty due to the security settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4352) Default value of Maven2 build password parameter doesn't get persisted
[ https://issues.jenkins-ci.org/browse/JENKINS-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-4352. -- Resolution: Duplicate yes, it is certainly a duplicate of JENKINS-4333, which is fixed Default value of Maven2 build password parameter doesn't get persisted -- Key: JENKINS-4352 URL: https://issues.jenkins-ci.org/browse/JENKINS-4352 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Environment: Platform: PC, OS: Linux Reporter: sslavic Password parameter default value one enters seems not to be persisted, so jobs which are triggered automatically or run manually without user setting password parameter value, fail with the NPE exception (see [1]). When Hudson (MavenBuilder) tries to set/put all system properties back to the system including a null value I suppose for that password parameter, since system properties are held in a Hashtable which doesn't support null values, we got a NPE. [1] build job execution stack trace snippet ERROR: Processing failed due to a bug in the code. Please report this to us...@hudson.dev.java.net java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:394) at java.util.Hashtable.putAll(Hashtable.java:466) at hudson.maven.MavenBuilder.call(MavenBuilder.java:156) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:685) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:631) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13980) The archive folder gets lost if you also backup archives for builds
[ https://issues.jenkins-ci.org/browse/JENKINS-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fürer resolved JENKINS-13980. Resolution: Fixed The archive folder gets lost if you also backup archives for builds --- Key: JENKINS-13980 URL: https://issues.jenkins-ci.org/browse/JENKINS-13980 Project: Jenkins Issue Type: Bug Components: thinBackup Reporter: Thomas Fürer Assignee: Thomas Fürer Priority: Critical builds 2000-01-01_00-00-00 archive artifact.jar changelog.xml .. will be backuped and restored in builds 2000-01-01_00-00-00 artifact.jar changelog.xml .. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163445#comment-163445 ] Sven Gothel commented on JENKINS-13007: --- This bug hinders us from updating the git plugin for our JogAmp project. The mentioned workaround of using a wrapper and escaping all git arguments seems to be to invasive to our running slaves. Would be great if this could get fixed. Git plugin cannot find revision to build on Windows --- Key: JENKINS-13007 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 2008 Server 64 Bit NTFS Reporter: ritzmann Assignee: Nicolas De Loof Priority: Critical After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on Windows build slaves started failing like this: Started by user anonymous Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.Channel@95ff886:win-slave1 Using strategy: Default Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 (origin/master) Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.LocalChannel@470a4b80 Fetching changes from 1 remote Git repository Fetching upstream changes from d:\hudson\shared\repo.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The builds on our Linux slaves are not affected. Wiping the workspaces on the Windows slaves did not help. Both clones and checkouts/updates seem to fail with the same error. Downgrading back to 1.1.14 made the Windows builds work again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163446#comment-163446 ] vjuranek commented on JENKINS-13007: Hi, I send a pull request [1] which could solve this issue. However, I'm not windows expert and I currently even don't have any win machine available to test it, so it would be nice if someone could test git plugin with this patch and comment under the pull request if it solves the problem or not. Thanks [1] https://github.com/jenkinsci/git-plugin/pull/71 Git plugin cannot find revision to build on Windows --- Key: JENKINS-13007 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 2008 Server 64 Bit NTFS Reporter: ritzmann Assignee: Nicolas De Loof Priority: Critical After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on Windows build slaves started failing like this: Started by user anonymous Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.Channel@95ff886:win-slave1 Using strategy: Default Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 (origin/master) Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.LocalChannel@470a4b80 Fetching changes from 1 remote Git repository Fetching upstream changes from d:\hudson\shared\repo.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The builds on our Linux slaves are not affected. Wiping the workspaces on the Windows slaves did not help. Both clones and checkouts/updates seem to fail with the same error. Downgrading back to 1.1.14 made the Windows builds work again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13953) can't Deploy artifacts to Artifactory
[ https://issues.jenkins-ci.org/browse/JENKINS-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Boissinot updated JENKINS-13953: Component/s: artifactory (was: artifactdeployer) can't Deploy artifacts to Artifactory - Key: JENKINS-13953 URL: https://issues.jenkins-ci.org/browse/JENKINS-13953 Project: Jenkins Issue Type: Bug Components: artifactory Affects Versions: current Reporter: maritzabell suarez Labels: plugin Attachments: ArtifactoryConfigurationOnJenkins.jpg, ArtifactoryConfigurationOnJenkinsTask.jpg hi! i'm trying to deploy artifacts to artifactory and i followed the tutorial, however, i got the same problem no matter what: Waiting for Jenkins to finish collecting data channel stopped Deploying artifacts to http://192.168.1.22/artifactory Deploying artifacts of module: etask.components.security:COM-SecurityGuardEntities ERROR: null java.lang.NullPointerException at org.jfrog.hudson.util.BuildUniqueIdentifierHelper.getUpstreamIdentifier(BuildUniqueIdentifierHelper.java:106) at org.jfrog.hudson.maven2.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:170) at org.jfrog.hudson.maven2.ArtifactsDeployer.deploy(ArtifactsDeployer.java:127) at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:300) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:994) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Build step 'Deploy artifacts to Artifactory' changed build result to FAILURE Finished: FAILURE it doesn't say anything i can use to resolve the problem. i attached the configuration of jenkins thank you so much for the help, Maritzabell Suarez -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 resolved JENKINS-13967. - Resolution: Fixed Xunit don't recognize cppunit report with time execution Key: JENKINS-13967 URL: https://issues.jenkins-ci.org/browse/JENKINS-13967 Project: Jenkins Issue Type: Bug Components: xunit Affects Versions: current Environment: Ubuntu Desktop 12.04 64 bits with Jenkins 1.466 with tomcat7 (from ubuntu package) cppunit -1.12.1-4 (from ubuntu package) Reporter: Nicolas JAN Assignee: Gregory Boissinot Attachments: cppunit-report.xml Hi, Since I have added the clocker plugin to my cppunit code(It is a cppunit plugin which permit to have the time execution, available into the samples of the cppunit archive), xunit don't reconize the format of the cppunit report. In fact, jenkins says that : [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing CppUnit-1.12.1 (default) [xUnit] [INFO] - [CppUnit-1.12.1 (default)] - 1 test report file(s) were found with the pattern 'report/cppunit-report.xml' relative to '/home/nicolas/jenkins/workspace/ProjectA' for the testing framework 'CppUnit-1.12.1 (default)'. [xUnit] [ERROR] - The result file '/home/nicolas/jenkins/workspace/ProjectA/report/cppunit-report.xml' for the metric 'CppUnit' is not valid. The result file has been skipped. [xUnit] [INFO] - Setting the build status to FAILURE [xUnit] [INFO] - Stopping recording. Build step 'Publish xUnit test result report' changed build result to FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13954) Add an option so that the build doesn't fail if cppcheck can't find the XML file.
[ https://issues.jenkins-ci.org/browse/JENKINS-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163447#comment-163447 ] Gregory Boissinot commented on JENKINS-13954: - Any update? Add an option so that the build doesn't fail if cppcheck can't find the XML file. - Key: JENKINS-13954 URL: https://issues.jenkins-ci.org/browse/JENKINS-13954 Project: Jenkins Issue Type: Improvement Components: cppcheck Affects Versions: current Reporter: Verbitan Assignee: Gregory Boissinot Priority: Minor I've got a multi-configuration job which compiles on both Linux and Solaris. The cppcheck binary I use is compiled for Solaris and not Linux, so in the job configuration I only generate the cppcheck XML if the build is being run on Solaris. I want to publish out the cppcheck results, but this always causes the Linux build to fail as it hasn't generated the XML file. Is it possible to add a setting that ignores the file not existing? There's already something similar for when the file is blank... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13863) MSBuild is unable to build projects in a different directory
[
https://issues.jenkins-ci.org/browse/JENKINS-13863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163448#comment-163448
]
SCM/JIRA link daemon commented on JENKINS-13863:
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/webapp/help-BuildFile.html
http://jenkins-ci.org/commit/msbuild-plugin/b92b4c477a75a5e2f3bdb3193928596273ccc537
Log:
Add comment to fix JENKINS-13863
MSBuild is unable to build projects in a different directory
Key: JENKINS-13863
URL: https://issues.jenkins-ci.org/browse/JENKINS-13863
Project: Jenkins
Issue Type: Bug
Components: msbuild
Affects Versions: current
Environment: MS Windows Server 2008
Reporter: Aaron Laws
Assignee: kdsweeney
Priority: Minor
Labels: path, plugin
Attachments: badbuild.txt, badconfig.PNG, betterbuild.txt,
goodbuild.txt, goodconfig.PNG
I use SVN to checkout a project to {{.\proj\}} and a dependency to
{{.\dep\}}. The {{.sln}} file is at {{.\proj\proj.sln}}. I us the MsBuild
plugin with the setting MsBuild Build File = {{proj\proj.sln}} (or a
number of variants such as {{.\proj\proj.sln}}). Msbuild fails with
{{MSB1009: Project file does not exist.}} However, running a similar command
manually succeeds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13765) PTC Integrity Plugin - Restore Timestamp Not Working
[ https://issues.jenkins-ci.org/browse/JENKINS-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163449#comment-163449 ] Cletus D'Souza commented on JENKINS-13765: -- I've reproduced this problem and found the root cause of the issue to be a core product issue. Even though I've specified the --restoreTimestamp option to the si projectco command, it seems like Integrity is not preserving the timestamp. This issue has been reported to Integrity Customer Support. As soon as I've got more information, I can update this JIRA issue. PTC Integrity Plugin - Restore Timestamp Not Working Key: JENKINS-13765 URL: https://issues.jenkins-ci.org/browse/JENKINS-13765 Project: Jenkins Issue Type: Bug Components: integrity-plugin Affects Versions: current Environment: Windows Server 2008 R2, Reporter: Udit Jhalani Assignee: Cletus D'Souza Priority: Blocker Fix For: current Attachments: 1.jpg, Source_Conf.jpg The restore time stamp is not working for me when I poll source to get latest changes. Any help is appreciated! Let me know if any other information is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14000) Add new content token BUILD_LOG_MULTILINE_REGEX, which allows regexes to match line terminators in build logs (in addition to all other characters), by matching against the full
[
https://issues.jenkins-ci.org/browse/JENKINS-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163450#comment-163450
]
Steve Rowe commented on JENKINS-14000:
--
See pull request https://github.com/jenkinsci/email-ext-plugin/pull/40
Add new content token BUILD_LOG_MULTILINE_REGEX, which allows regexes to
match line terminators in build logs (in addition to all other characters),
by matching against the full content of the build log.
---
Key: JENKINS-14000
URL: https://issues.jenkins-ci.org/browse/JENKINS-14000
Project: Jenkins
Issue Type: New Feature
Components: email-ext
Affects Versions: current
Reporter: Steve Rowe
Assignee: Slide-O-Mix
Priority: Minor
Fix For: current
Content token BUILD_LOG_REGEX matches the given regex against each line of
the build log.
I propose to add a new content token BUILD_LOG_MULTILINE_REGEX, just like
BUILD_LOG_REGEX, but with two modifications:
# Matches are against the full content of the build log, rather than
line-at-a-time. As a result, the regex can recognize multiple log lines in a
single match, either by direct specification, or using the DOTALL modifier,
e.g. {{(?s:.*)}}.
# No context arguments ({{linesBefore}} and {{linesAfter}}) - if the user
wants this behavior, their regex can do the job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
