[JIRA] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Haris Shahid commented on JENKINS-30271 Re: Jenkins job hangs and cannot be killed after aborting DSL job Both Jenkins my team has set-up use Java 7 so I believe the version of Java is not the culprit. Any more 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] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Haris Shahid commented on JENKINS-30271 Re: Jenkins job hangs and cannot be killed after aborting DSL job I came here and created an account just to log this exact same bug. I can atest this is definitely a bug and it occurs on 2 different Jenkins environments (very beefy multi node environments provisioned through Amazon Cloud) that my DevOps team manages on the Project that I am currently working on. Every time I have to restart Jenkins to fix the issue and then it occurs randomly after a few successful executions. I have used the Job DSL plug-in very extensively on my past two projects and have been an avid user since it's inception and am very familiar with the syntax and how the plugin works. So I assure you it has nothing to do with how I am using or the code that is being executed. This is definitely a bug and I would love for someone to fix it as it is hindering our ability to use an otherwise AWESOME! plugin. Thanks a lot for creating this plugin and continuing to maintain and enhance it at such a rapid pace. Also thank you in advance for fixing this bug ASAP. 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] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts
Haris Shahid commented on JENKINS-15594 CopyArtifact plugin cannot always copy artifacts I would like to add that I have also been experiencing this issue and after doing some extensive tinkering I think it has to do something with permissions. At first I tried giving the job from which the artifacts were to be copied all types of access (anonymous, full access, authenticated group access) anything I read and could come up with on my own I tried. But, the copy artifac plugin would still fail intermittently. The solution I figured out is this; if the copy artifact plugin starts to fail just go to the view that lists the job from which artifacts are to be copied as long as the logged in user sees the job listing, once, the copy artifact plugin will not fail (to copy artifacts) ever again from that job. You do not even have to click on the job just be able to see it in a list in one of your views. I know this sounds strange but I assure you this fixes the problem. Currently I have created a view where I list all of the jobs from which artifacts are to be copied and I have made it my default view. So, now as soon as a user logs-in or hits the Jenkins homepage the first thing they will see is the list of jobs. I have not had a failure since. Can someone please fix this? 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
[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts
Haris Shahid edited a comment on JENKINS-15594 CopyArtifact plugin cannot always copy artifacts I would like to add that I have also been experiencing this issue and after doing some extensive tinkering I think it has to do something with permissions. At first I tried giving the job from which the artifacts were to be copied all types of access (anonymous, full access, authenticated group access) anything I read and could come up with on my own I tried. But, the copy artifact plugin would still fail intermittently. The solution I figured out is this; if the copy artifact plugin starts to fail just go to the view that lists the job from which artifacts are to be copied as long as the logged in user sees the job listing, once, the copy artifact plugin will not fail (to copy artifacts) ever again. You do not even have to click on the job just be able to see it in a list in one of your views. I know this sounds strange but I assure you this fixes the problem. Currently I have created a view where I list all of the jobs from which artifacts are to be copied and I have made it my default view. So, now as soon as a user logs-in or hits the Jenkins homepage the first thing they will see is the list of jobs. I have not had a failure since and I implemented this fix about 1.5 - 2 months ago. Can someone please fix this? 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
[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts
Haris Shahid edited a comment on JENKINS-15594 CopyArtifact plugin cannot always copy artifacts I would like to add that I have also been experiencing this issue and after doing some extensive tinkering I think it has to do something with permissions. At first I tried giving the job from which the artifacts were to be copied all types of access (anonymous, full access, authenticated group access) anything I read and could come up with on my own I tried. But, the copy artifact plugin would still fail intermittently. The solution I figured out is this; if the copy artifact plugin starts to fail just go to the view that lists the job from which artifacts are to be copied as long as the logged in user sees the job listing, once, the copy artifact plugin will not fail (to copy artifacts) ever again for the current session. You do not even have to click on the job just be able to see it in a list in one of your views. I know this sounds strange but I assure you this fixes the problem. Currently I have created a view where I list all of the jobs from which artifacts are to be copied and I have made it my default view. So, now as soon as a user logs-in or hits the Jenkins homepage the first thing they will see is the list of jobs. I have not had a failure since and I implemented this fix about 1.5 - 2 months ago. Can someone please fix this? 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
