[JIRA] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError
Title: Message Title Nickolay Rumyantsev commented on JENKINS-21747 Re: Artifact archiving fails with java.lang.NoClassDefFoundError Slave reconnection heals the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Nickolay Rumyantsev commented on JENKINS-27421 Re: Unserializable iterator & entry classes from Java Collections A little addition to Jesse Glick's comment: the pain point about looping over Map is that standard Map.entrySet() returns list of non-serializable entry objects, i.e. LinkedHashMap.Entry. Despite the Map itself is indeed Serializable. If talking about values() then I am not so sure because new ArrayList(someMap.values()) is Serializable whereas someMap.values() is not. Jesse Glick, am I in danger of getting NonSerializable Exception if I don't use any intermediate variable to store someMap.values() and immediately pass it into ArrayList constructor? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Nickolay Rumyantsev commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Marcus Philip, you are correct, this is the same issue. From my observations it always return the first result of the closure, in your case it's a boolean result of "it == 'key1'". @NonCPS should help you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Nickolay Rumyantsev commented on JENKINS-27421 Re: Unserializable iterator & entry classes from Java Collections Anton B It hasn't been working for a long time already, see JENKINS-26481 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-30121) Workflow build step for Artifactory Plugin
Title: Message Title Nickolay Rumyantsev commented on JENKINS-30121 Re: Workflow build step for Artifactory Plugin Thanks for the great news! Looks nice but not yet released. Should be used with caution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Nickolay Rumyantsev commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file This is my testing instance, it has a hundred of plugins installed for evaluation purposes. I can provide you a list but it should take pretty much time to check them all Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Nickolay Rumyantsev created an issue Jenkins / JENKINS-32925 StackOverflow when trying to get Pipeline GDSL file Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 12/Feb/16 8:36 PM Environment: Jenkins 1.639 (on Windows 7 machine), installed as a service. Pipeline: 1.13 Labels: workflow pipeline Priority: Minor Reporter: Nickolay Rumyantsev I got an error when trying to download IDEA GDSL file from my local Jenkins. No access control is enabled on the host. java.lang.StackOverflowError at java.io.File.(Unknown Source) at java.io.FilePermission$1.run(Unknown Source) at java.io.FilePermission$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.io.FilePermission.init(Unknown Source) at java.io.FilePermission.(Unknown Source) at sun.net.www.protocol.file.FileURLConnection.getPermission(Unknown Source) at
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title
Nickolay Rumyantsev updated an issue
Jenkins / JENKINS-32869
Artifactory plugin creates directories instead of uploading files
Change By:
Nickolay Rumyantsev
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact. Also raised: https://www.jfrog.com/jira/browse/HAP-690 I couldn't find a workaround so this is blocking me at the moment.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title
Nickolay Rumyantsev updated an issue
Jenkins / JENKINS-32869
Artifactory plugin creates directories instead of uploading files
Change By:
Nickolay Rumyantsev
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact.Also raised: https://www.jfrog.com/jira/browse/HAP-690I couldn't find a workaround so this is blocking me at the moment. * UPDATE: * all works fine if I don't use "Deployment properties" option.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title
Nickolay Rumyantsev updated an issue
Jenkins / JENKINS-32869
Artifactory plugin creates directories instead of uploading files
Change By:
Nickolay Rumyantsev
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact.Also raised: https://www.jfrog.com/jira/browse/HAP-690I couldn't find a workaround so this is blocking me at the moment. UPDATE: all works fine if I don't use "Deployment properties" option.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title Nickolay Rumyantsev updated an issue Jenkins / JENKINS-32869 Artifactory plugin creates directories instead of uploading files Change By: Nickolay Rumyantsev Environment: Jenkins 1.625.3Artifactory plugin 2.4.7 (2.2.4 too) Artifactory OSS (latest docker image: 29d2cd2e846a) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title Nickolay Rumyantsev updated an issue Jenkins / JENKINS-32869 Artifactory plugin creates directories instead of uploading files Change By: Nickolay Rumyantsev Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title Nickolay Rumyantsev created an issue Jenkins / JENKINS-32869 Artifactory plugin creates directories instead of uploading files Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 10/Feb/16 2:28 AM Environment: Jenkins 1.625.3 Artifactory plugin 2.4.7 (2.2.4 too) Artifactory OSS (latest docker image: 29d2cd2e846a) Priority: Blocker Reporter: Nickolay Rumyantsev My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance. During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names! Publishing rules are the following (yes, there are version-named directories as the dest): /jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS /jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL I also tried appending the
[JIRA] [artifactory-plugin] (JENKINS-30121) Workflow build step for Artifactory Plugin
Title: Message Title Nickolay Rumyantsev commented on JENKINS-30121 Re: Workflow build step for Artifactory Plugin Actually it would be great to have at least the simplest 'Generic' deployment functionality available (when you specify some deployment rules). Is this possible? It is pain in the neck to call a different job and pass the build artifacts into it just for deployment, also have all build action badges in the different build and keep build rotation policy in sync.. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31926) Jenkins doesn't display graph for test suites, before all tests successfully pass
Title: Message Title Nickolay Rumyantsev commented on JENKINS-31926 Re: Jenkins doesn't display graph for test suites, before all tests successfully pass I made some experiments and for me it seems that the trend graph on the main page is not shown when: Last build has a failed test In the build history there is no consequently reachable build result with this test passed. By consequently reachable I mean that every build without Test results (i.e. failed on git checkout) stops the algorithm from traversing deeper. This is actually really annoying, especially for Jenkins Pipeline: In some cases when the build failed early (preparation or compilation phase) I don't want to run unit tests. I configure the script to avoid JUnit publishing in this case this always causes the trend not to be shown. The graph permalink that I embed on my wiki pages becomes unavailable too. My setup: jenkins 1.639 Jenkins Workflow 1.12 JUnit plugin 1.10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] [junit-plugin] (JENKINS-31926) Jenkins doesn't display graph for test suites, before all tests successfully pass
Title: Message Title Nickolay Rumyantsev updated an issue Jenkins / JENKINS-31926 Jenkins doesn't display graph for test suites, before all tests successfully pass Change By: Nickolay Rumyantsev Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Nickolay Rumyantsev commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Might this be connected with JENKINS-31926 ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-29353) Configurable number of builds for trends generation
Title: Message Title Nickolay Rumyantsev resolved as Fixed Fixed and merged in https://github.com/jenkinsci/robot-plugin/pull/10. Jenkins / JENKINS-29353 Configurable number of builds for trends generation Change By: Nickolay Rumyantsev Status: Open Resolved Assignee: jpiironen Nickolay Rumyantsev Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-11257) Stopping a parent job doesn't stop the triggered child jobs
Title: Message Title Nickolay Rumyantsev commented on JENKINS-11257 Re: Stopping a parent job doesn't stop the triggered child jobs Sebastian Schuberth, I am afraid it's lost now. The problem was that users often clicked the Abort button twice which causes Post build to be aborted too. However the overall idea was the following: In Groovy Postbuild, or System Groovy script Get all currently running builds like here: Find builds currently running that has been executing for more than N seconds For each build follow getUpstream()-getUpstream()... saving the build chain until you meet your current build, where upstream = build.getCause(hudson.model.Cause.UpstreamCause)?.upstreamRun Call doStop() for each build in the resulting chains starting from the earliest build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14713) Cancel permission is granted for users having build permission
Title: Message Title Nickolay Rumyantsev commented on JENKINS-14713 Re: Cancel permission is granted for users having build permission I wonder if it is possible to introduce the discussed permission separation by a plugin or it's only can be done in the Jenkins core? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-29353) Configurable number of builds for trends generation
Title: Message Title Nickolay Rumyantsev commented on JENKINS-29353 Re: Configurable number of builds for trends generation I've created a pull request for this feature: https://github.com/jenkinsci/robot-plugin/pull/10 Although it might be a bit straightforward, please take a look and make your suggestions. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-29353) Configurable number of builds for trends generation
Title: Message Title Nickolay Rumyantsev created an issue Jenkins / JENKINS-29353 Configurable number of builds for trends generation Issue Type: Improvement Assignee: jpiironen Attachments: graph.png Components: robot-plugin Created: 10/Jul/15 7:18 PM Priority: Major Reporter: Nickolay Rumyantsev In my Jenkins job with several hundreds of builds it's pretty difficult to see the latest results on the generated trend, because there are too much of entries. It would be great to have an ability to configure a maximum number of latest test results to show on a graph. This also will somehow tackle the issue JENKINS-15190. Add Comment
[JIRA] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Nickolay Rumyantsev commented on JENKINS-17467 CoverityPublisher aborted due to NullPointerException I have the same issue as Lee does with Coverity 1.3.1, Jenkins 1.543: 02:05:59.836 ERROR: Publisher jenkins.plugins.coverity.CoverityPublisher aborted due to exception 02:05:59.836 java.lang.NullPointerException 02:05:59.836 at jenkins.plugins.coverity.analysis.CoverityToolHandler.getHandler(CoverityToolHandler.java:44) 02:05:59.836 at jenkins.plugins.coverity.CoverityPublisher.perform(CoverityPublisher.java:233) 02:05:59.836 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) 02:05:59.836 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 02:05:59.836 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) 02:05:59.836 at hudson.model.Build$BuildExecution.post2(Build.java:183) 02:05:59.836 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 02:05:59.836 at hudson.model.Run.execute(Run.java:1703) 02:05:59.836 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 02:05:59.836 at hudson.model.ResourceController.execute(ResourceController.java:88) 02:05:59.836 at hudson.model.Executor.run(Executor.java:231) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Nickolay Rumyantsev commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Having the similar issue. Slave is reconnected during the archiving of artifacts, when Jenkins is under load. Jenkins 1.543. 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-21020) Builds disappear from the job after its renaming
Nickolay Rumyantsev commented on JENKINS-21020 Builds disappear from the job after its renaming Thanks for reply but I think this issue duplicates the https://issues.jenkins-ci.org/browse/JENKINS-18678 which is resolved already. I'll close this issue. 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-21020) Builds disappear from the job after its renaming
Nickolay Rumyantsev resolved JENKINS-21020 as Duplicate Builds disappear from the job after its renaming This is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-18678. Change By: Nickolay Rumyantsev (26/Dec/13 4:30 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21020) Builds disappear from the job after its renaming
Nickolay Rumyantsev updated JENKINS-21020 Builds disappear from the job after its renaming Change By: Nickolay Rumyantsev (20/Dec/13 12:13 PM) Priority: Major Minor Description: Whenajobisrenamed,allitsbuildsdisappearfromthebuildhistory(butremainitthe filse file system).Jenkinsrestartorreloadfixesthiscompletely.Toreproduce:-Chooseajobwithbuilds.-Renameit.-RunSystem.gc()severaltimesintheScriptConsole.-Nowjobshowsnobuilds. 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-14713) Cancel permission is granted for users having build permission
Nickolay Rumyantsev commented on JENKINS-14713 Cancel permission is granted for users having build permission Is there any progress with this issue? 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-21097) Add line breaking for columns LastSuccessfulBuild, LastFailedBuild, etc
Nickolay Rumyantsev created JENKINS-21097 Add line breaking for columns LastSuccessfulBuild, LastFailedBuild, etc Issue Type: Improvement Assignee: Unassigned Attachments: Line_breaks.png Components: core Created: 19/Dec/13 4:37 PM Description: Since 1.517 job names and some other long strings that are displayed by Jenkins are splitted with wbr tag which allows to break them into a number of lines. It would be great to do the same for string in other view columns like LastSuccessfulBuild, LastFailedBuild, because sometimes the build name is customised and become very long. In this case most of the visual space is taken by this columns. I've added a screenshot with explanation. Project: Jenkins Priority: Minor Reporter: Nickolay Rumyantsev 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-21020) Builds disappear from the job after its renaming
Nickolay Rumyantsev created JENKINS-21020 Builds disappear from the job after its renaming Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/13 1:40 PM Description: When a job is renamed, all its builds disappear from the build history (but remain it the filse system). Jenkins restart or reload fixes this completely. To reproduce: Choose a job with builds. Rename it. Run System.gc() several times in the Script Console. Now job shows no builds. Environment: 2 envs: - 1.512 RHEL 5.9 - 1.543 win7 Project: Jenkins Priority: Major Reporter: Nickolay Rumyantsev 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] [parameterized-trigger] (JENKINS-11257) Stopping a parent job doesn't stop the triggered child jobs
Nickolay Rumyantsev commented on JENKINS-11257 Stopping a parent job doesnt stop the triggered child jobs I vote for this issue. At the moment we use the workaroud groovy postbuild script which checks if build has been aborted, then gets the chilren and executes build.doStop() on them. 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-15719) Builds and workspace disappear for jobs created after upgrade to 1.487
Nickolay Rumyantsev commented on JENKINS-15719 Builds and workspace disappear for jobs created after upgrade to 1.487 Hi, I have a Jenkins 1.512 workins on the RHEL 5.3 machine. I had a job that worked normally. Once I renamed it. After that everyday at 16.27 EDT all builds disapper from this job. The jenkins log contains nothing like "couldn't load the job" about this job, only records like "Job build SUCCESS" or "Job build FAILURE". The job is configured to run at 16.30 everyday so I thought it is the clue but changes to the schedule doesn't affect the situation. I also tried to enable/disable different strategies of builds discarding - nothing helps. All the builds data remain in the filesystem so the restart helps (all the builds are shown like all is ok) but only until 16.27. There is another job that starts at the 16.30 and it is ok. 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-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
Nickolay Rumyantsev commented on JENKINS-15995 Arguments passed to Managed Script called in Conditional BuildStep could not be saved Thanks, that would be great! 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-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
Nickolay Rumyantsev updated JENKINS-15995 Arguments passed to Managed Script called in Conditional BuildStep could not be saved Change By: Nickolay Rumyantsev (28/Feb/13 11:07 AM) Description: Ihaveamanagedscriptwhichacceptstwoparameters.IhaveajobwhereIwanttocallthisscriptonlywhenthespecificconditionismet.SoIreconfigurethatjobandhitsaveandnoerroroccurs.ThenIreloadwebpageandseethatthebuildstepissavedbutitsargumentsarenot.SavingfailsbothforConditionalstep(Single)andforConditionalstep(Multiple) UPD:jenkins:1.480.3plugins:conditionalstep:1.2managedscripts:1.0.1configfileprovider:2.2.1 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-15466) Fatal Error No Class Definition found for Kernel32
Nickolay Rumyantsev commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 And what is also very important when it could be released in LTS? 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-15466) Fatal Error No Class Definition found for Kernel32
Nickolay Rumyantsev commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 it looks like the error is occured when Jenkins attempts to delete file on Windows machine. 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-15466) Fatal Error No Class Definition found for Kernel32
Nickolay Rumyantsev commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 I have the same issue raised during the workspace cleaning. Jenkins 1.480.3 Slave: Win2003, java 6_22 and 7_15 (both tested) 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-15974) FATAL: Failed to link the library: interface hudson.util.jna.Kernel32
Nickolay Rumyantsev commented on JENKINS-15974 FATAL: Failed to link the library: interface hudson.util.jna.Kernel32 OS: Win2003. Java: 6_22/7_15. Connection method: jnlp/service I have the same error during the cleaning of the workspace: Deleting project workspace... FATAL: Failed to link the library: java.lang.UnsupportedOperationException: Failed to link the library: at hudson.util.jna.InitializationErrorInvocationHandler.invoke(InitializationErrorInvocationHandler.java:27) at com.sun.proxy.$Proxy7.GetFileAttributesW(Unknown Source) at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:61) at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:65) at hudson.Util.isSymlink(Util.java:314) at hudson.Util.deleteRecursive(Util.java:279) at hudson.FilePath$11.invoke(FilePath.java:920) at hudson.FilePath$11.invoke(FilePath.java:918) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.UnsatisfiedLinkError: Unable to load library 'kernel32': com.sun.jna.Native.open(Ljava/lang/String;)J at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) at com.sun.jna.Library$Handler.init(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:366) at com.sun.jna.Native.loadLibrary(Native.java:351) at hudson.util.jna.Kernel32Utils.load(Kernel32Utils.java:70) at hudson.util.jna.Kernel32.clinit(Kernel32.java:37) 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-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
Nickolay Rumyantsev created JENKINS-15995 Arguments passed to Managed Script called in Conditional BuildStep could not be saved Issue Type: Bug Affects Versions: current Assignee: domi Components: conditional-buildstep, managed-scripts Created: 30/Nov/12 1:23 PM Description: I have a managed script which accepts two parameters. I have a job where I want to call this script only when the specific condition is met. So I reconfigure that job and hit 'save' and no error occurs. Then I reload webpage and see that the buildstep is saved but its arguments are not. Saving fails both for 'Conditional step (Single)' and for 'Conditional step (Multiple)' Environment: WinXP, Linux Project: Jenkins Priority: Major Reporter: Nickolay Rumyantsev 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
[JIRA] (JENKINS-14456) Add support for Workspace Cleanup Plugin
Nickolay Rumyantsev created JENKINS-14456 Add support for Workspace Cleanup Plugin Issue Type: New Feature Assignee: mdonohue Components: configurationslicing Created: 17/Jul/12 9:58 AM Description: It would be great if you add new slicer for Workspace Cleanup Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin). I could do it by myself if you tell me how to contribute to your project. Project: Jenkins Priority: Major Reporter: Nickolay Rumyantsev 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
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
Nickolay Rumyantsev edited a comment on JENKINS-14301 Failed to use multiple update sites (plugin repositories) I seek through code and found the reason of that bug: list of updates is generated by UpdateCenter.getUpdates(); UpdateCenter.getUpdates() -(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites. UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version. That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site. I don't know the best way to fix it while preserving architecture integrity, so I ask someone to fix it. UPD. I put this comment's body into the issue description, so it might be deleted now, but I have not such permissions. 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
[JIRA] (JENKINS-14301) Failed to use multiple plugin repositories
Nickolay Rumyantsev commented on JENKINS-14301 Failed to use multiple plugin repositories I seek through code and found the reason of that bug: list of updates is generated by UpdateCenter.getUpdates(); UpdateCenter.getUpdates() -(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites. UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version. That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site. I don't know the best way to fix it to preseve architecture integrity, so I ask someone to fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
Nickolay Rumyantsev updated JENKINS-14301 Failed to use multiple update sites (plugin repositories) Change By: Nickolay Rumyantsev (06/Jul/12 10:48 AM) Summary: Failedtousemultiple updatesites( pluginrepositories ) Affects Version/s: current Due Date: 3/Jul/12 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
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
Nickolay Rumyantsev edited a comment on JENKINS-14301 Failed to use multiple update sites (plugin repositories) I seek through code and found the reason of that bug: list of updates is generated by UpdateCenter.getUpdates(); UpdateCenter.getUpdates() -(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites. UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version. That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site. I don't know the best way to fix it while preserving architecture integrity, so I ask someone to fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14301) Failed to use multiple plugin repositories
Nickolay Rumyantsev created JENKINS-14301 Failed to use multiple plugin repositories Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 03/Jul/12 5:18 PM Description: I tried to configure two plugin repos: internal and updates.jenkins-ci.org (base) on my jenkins instance. For internal server I create my own update-center.json file. If I specify only my repo, or only base repo - I have no problems with plugin manager(plugins are displayed, installed and updated correctly). But if I set two repos at the same time (by groovy script), I have a problem. I can see plugins only from one server but duplicated twice (or any other times depends on how much repos did I add). Jenkins error log says that data was obtained without errors (signature fails or JSON parsing fails and others) from all repos - default and mine. Unfortunately Plugin manager (via User Interface and Groovy scripts) shows that myUpdateSite.getAvailables and defaultUpdateSite.getAvailables contain same data, that is impossible according to contents of JSON update files. Due Date: 03/Jul/12 12:00 AM Environment: winXP and Linux Project: Jenkins Labels: plugins jenkins Priority: Minor Reporter: Nickolay Rumyantsev 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
