[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore I have changed the configuration to use terminate/start instead of stop/start and for a week it works just fine. Maybe it might help solving this issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.5337.1566204720562%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore Yesterday morning I came and it looked fine. This morning, again, all instances were up and all slaves were offline while there were a few jobs in the queue waiting for a long time. It's not just not starting the slaves, it's even worse, the instances are running and wasting money which is the opposite of what this plugin is all about. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.2479.1565765880889%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore OK. Seems like it got worse. Usually it happened during the weekend or after a night. Now slaves fails to start during the day I'm out of ideas Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.1127.1565616420539%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore Installed 1.45 on my Jenkins. Upgraded from 1.43. Hopefully it'll solve the issue of slaves stuck in offline mode. Till today's morning, the issue was that the instances were up and running and the slaves were offline. Today's morning the instances were down as well as the slaves. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194555.1539041035000.905.1565591940935%40Atlassian.JIRA.
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title Gil Shinar commented on JENKINS-54041 Re: EC2 Plugin no longer able to start build slaves I'm facing something similar. Sometimes instances are up and running and all the slaves are offline. Only removing the slaves from the jenkins or launching them again fixes that issue. I saw that there might be a fix in version 1.45 but there's a warning message saying that upgrading to this version might result in configuration issues. Is that right? I've tried to comment in JENKINS-53952 but for some reason I cannot (browser freezes). No matter which browser I'm using. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194656.1539331041000.827.1565522820949%40Atlassian.JIRA.
[JIRA] (JENKINS-54525) java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title David Peleg commented on JENKINS-54525 Re: java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) I suggested a fix in pull request: https://github.com/jenkinsci/cvs-plugin/pull/48 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54656) cvs plugin broken - not possible to add new projects
Title: Message Title David Peleg commented on JENKINS-54656 Re: cvs plugin broken - not possible to add new projects I suggested a fix in pull request: https://github.com/jenkinsci/cvs-plugin/pull/48 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54656) cvs plugin broken - not possible to add new projects
Title: Message Title David Peleg commented on JENKINS-54656 Re: cvs plugin broken - not possible to add new projects Looks like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-54525 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54525) java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title David Peleg commented on JENKINS-54525 Re: java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) Looks like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-54656 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-38825) MultiJob does not build Pipeline jobs
Title: Message Title Yoram Michaeli commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Fixed in 1.32 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-46916) duplicate links on left nav with project inheritance plugin and pipeline jobs
Title: Message Title Yoram Michaeli commented on JENKINS-46916 Re: duplicate links on left nav with project inheritance plugin and pipeline jobs This happens to me as well, and it also make the 'rebuild' button disappear Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title Yoram Michaeli commented on JENKINS-50307 Re: While running in parallel for a loop, the index is wrong for each iteration Someone showed me this: https://jenkins.io/doc/pipeline/examples/#parallel-from-list which explains that this is not a bug but a feature (loopIndex1 byRef not byVal)). Still, I think that intuitively it looks like a bug since I expect it to behave in one way while it acts differently. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title
Yoram Michaeli updated an issue
Jenkins / JENKINS-50307
While running in parallel for a loop, the index is wrong for each iteration
Change By:
Yoram Michaeli
When using a parallel step for an indexed loop, using the loop-iterator-index for internal usage results with wrong value (showing the max-index-value for all iterations). A workaround for it is to set a local variable for saving the current iteration-index and use the local variable. The following pipeline demonstrates the problem (the issue is demonstrated with the internal 'echo' steps):{code:java} // code placeholder{code} pipeline \ { agent any stages \ { stage('Explore bug') \ { steps \ { script \ { int maxIndex1=3 def loopers1 = [:] for (int loopIndex1 = 0; loopIndex1 < maxIndex1; loopIndex1++) \ { echo "loopIndex1=$ \ {loopIndex1}" loopers1["loop-$\{loopIndex1}"] = \ { echo "loopIndex1=$ \ {loopIndex1}" } } parallel loopers1 } } } stage('Bug workaround') \ { steps \ { script \ { int maxIndex2=3 def loopers2 = [:] for (int loopIndex2 = 0; loopIndex2 < maxIndex2; loopIndex2++) \ { int index2=loopIndex2 echo "index2=$ \ {index2}" loopers2["loop-$\{index2}"] = \ { echo "index2=$ \ {index2}" } } parallel loopers2 } } } } } {code}
Add Comment
[JIRA] (JENKINS-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title
Yoram Michaeli updated an issue
Jenkins / JENKINS-50307
While running in parallel for a loop, the index is wrong for each iteration
Change By:
Yoram Michaeli
When using a parallel step for an indexed loop, using the loop-iterator-index for internal usage results with wrong value (showing the max-index-value for all iterations). A workaround for it is to set a local variable for saving the current iteration-index and use the local variable. The following pipeline demonstrates the problem (the issue is demonstrated with the internal 'echo' steps):{code:java}// code placeholder{code}pipeline \{ agent any stages \{ stage('Explore bug') \{ steps \{ script \{ int maxIndex1=3 def loopers1 = [:] for (int loopIndex1 = 0; loopIndex1 < maxIndex1; loopIndex1++) \{ echo "loopIndex1=$\{loopIndex1}" loopers1["loop-$\ \ {loopIndex1}"] = \{ echo "loopIndex1=$\{loopIndex1}" } } parallel loopers1 } } } stage('Bug workaround') \{ steps \{ script \{ int maxIndex2=3 def loopers2 = [:] for (int loopIndex2 = 0; loopIndex2 < maxIndex2; loopIndex2++) \{ int index2=loopIndex2 echo "index2=$\{index2}" loopers2["loop-$\ \ {index2}"] = \{ echo "index2=$\{index2}" } } parallel loopers2 } } } } }
Add Comment
[JIRA] (JENKINS-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title
Yoram Michaeli updated an issue
Jenkins / JENKINS-50307
While running in parallel for a loop, the index is wrong for each iteration
Change By:
Yoram Michaeli
When using a parallel step for an indexed loop, using the loop-iterator-index for internal usage results with wrong value (showing the max-index-value for all iterations).A workaround for it is to set a local variable for saving the current iteration-index and use the local variable.The following pipeline demonstrates the problem (the issue is demonstrated with the internal 'echo' steps): {code:java}// code placeholder{code}pipeline\{ agent any stages \{ stage('Explore bug') \{ steps \{ script \{ int maxIndex1=3 def loopers1 = [:] for (int loopIndex1 = 0; loopIndex1 < maxIndex1; loopIndex1++) \{ echo "loopIndex1=$\{loopIndex1}" loopers1["loop-$\ \ {loopIndex1}"] = \{ echo "loopIndex1=$\{loopIndex1}" } } parallel loopers1 } } } stage('Bug workaround') \{ steps \{ script \{ int maxIndex2=3 def loopers2 = [:] for (int loopIndex2 = 0; loopIndex2 < maxIndex2; loopIndex2++) \{ int index2=loopIndex2 echo "index2=$\{index2}" loopers2["loop-$\ \ {index2}"] = \{ echo "index2=$\{index2}" } } parallel loopers2 } } } }}
[JIRA] (JENKINS-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title
Yoram Michaeli created an issue
Jenkins / JENKINS-50307
While running in parallel for a loop, the index is wrong for each iteration
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Jenkinsfile
Components:
pipeline
Created:
2018-03-21 04:20
Labels:
parallel pipeline
Priority:
Minor
Reporter:
Yoram Michaeli
When using a parallel step for an indexed loop, using the loop-iterator-index for internal usage results with wrong value (showing the max-index-value for all iterations). A workaround for it is to set a local variable for saving the current iteration-index and use the local variable. The following pipeline demonstrates the problem (the issue is demonstrated with the internal 'echo' steps):
// code placeholder
pipeline { agent any stages { stage('Explore bug') { steps { script { int maxIndex1=3 def loopers1 = [:] for (int loopIndex1 = 0; loopIndex1 < maxIndex1; loopIndex1++) { echo "loopIndex1=${loopIndex1}" loopers1["loop-$\{loopIndex1}"] = { echo "loopIndex1=${loopIndex1}" } } parallel loopers1 } } } stage('Bug workaround') { steps { script { int maxIndex2=3 def loopers2 = [:] for (int loopIndex2 = 0; loopIndex2 < maxIndex2; loopIndex2++) { int index2=loopIndex2 echo "index2=${index2}" loopers2["loop-$\{index2}"] = { echo
[JIRA] (JENKINS-49328) MultiJob has a forbidden nested reference to a model object
Title: Message Title Chen Cohen updated JENKINS-49328 fixed on v1.29 Jenkins / JENKINS-49328 MultiJob has a forbidden nested reference to a model object Change By: Chen Cohen Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-37351) running jobs sequentially - ordering
Title: Message Title Chen Cohen closed an issue as Fixed fixed in version 1.24 Jenkins / JENKINS-37351 running jobs sequentially - ordering Change By: Chen Cohen Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen closed an issue as Not A Defect Hi Christoph, I was still unable to reproduce this issue with your config.xml. But once this issue is not reproducible on a new multijob job then it's not a bug. Try creating new job, copy your config.xml to it and restart Jenkins. Jenkins / JENKINS-38859 ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild Change By: Chen Cohen Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen commented on JENKINS-38859 Re: ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild Could you please share your job's config.xml? 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-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen commented on JENKINS-38859 Re: ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild Thanks for your reply. Is this also happening on a newly created multijob? 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-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen commented on JENKINS-38859 Re: ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild I was unable to reproduce your issue. Please add your recreation steps. Thanks, Chen 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-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen assigned an issue to Chen Cohen Jenkins / JENKINS-38859 ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild Change By: Chen Cohen Assignee: hagzag Chen Cohen 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-38311) Disconnected dynamic ec2 slaves reconnected after jenkins restart
Title: Message Title Amos Sonnenwirth created an issue Jenkins / JENKINS-38311 Disconnected dynamic ec2 slaves reconnected after jenkins restart Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Sep/18 10:15 AM Environment: Jenkins v2.7.4 ec2-plugin v1.35 Labels: ec2-plugin Priority: Major Reporter: Amos Sonnenwirth Using ec2-plugin when slaves are disconnected (stopped and not terminated) after idle time, there might be lots of slaves which are disconnected but still in the list of slaves. Once there is restart to Jenkins master (for some reason...) ALL disconnected slaves being connected again, which might cause unexpected cost in AWS account Add Comment
[JIRA] (JENKINS-36124) Build Parameters Corrupted sometimes in MultiJob Project
Title: Message Title Chen Cohen edited a comment on JENKINS-36124 Re: Build Parameters Corrupted sometimes in MultiJob Project Implement new ParameterAction to overcome SECURITY-170 parameters filtering. Fix is reflected in MultiJob v1.22 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-36124) Build Parameters Corrupted sometimes in MultiJob Project
Title: Message Title Chen Cohen resolved as Fixed Implement new ParameterAction to overcome SECURITY-170 parameters filtering. Jenkins / JENKINS-36124 Build Parameters Corrupted sometimes in MultiJob Project Change By: Chen Cohen Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-36124) Build Parameters Corrupted sometimes in MultiJob Project
Title: Message Title Chen Cohen assigned an issue to Chen Cohen Jenkins / JENKINS-36124 Build Parameters Corrupted sometimes in MultiJob Project Change By: Chen Cohen Assignee: hagzag Chen Cohen 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] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Liya Katz commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects I upgraded to Jenkins 2.4 and my matrix jobs just stopped working! 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] [git-plugin] (JENKINS-32998) add condition to the GIT clone/pull step
Title: Message Title Gil Shinar commented on JENKINS-32998 Re: add condition to the GIT clone/pull step Problem is Git plugin does many things that "protect" you from whatever exists in the workspace at the moment the clone/pull occurs and I want that "protection" 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] [thinBackup] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Title: Message Title Liya Katz commented on JENKINS-12096 Re: ThinBackup Worker Thread thread is still running. Execution aborted. Experience this issue as well. Jenkins 1.643 ThinBackup 1.7.4 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] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
Title: Message Title Yoram Michaeli commented on JENKINS-24832 Re: Failed maven builds using -T are showing up as Aborted As a workaround, until this is fixed, you can use a groovy post-build script that changes the status of the build from ABORTED to FAILED in case it finds the error in the log. See a post I've wrote about it: http://www.tikalk.com/devops/JenkinsJobStatusChange 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] [git-plugin] (JENKINS-32998) add condition to the GIT clone/pull step
Title: Message Title Gil Shinar updated an issue Jenkins / JENKINS-32998 add condition to the GIT clone/pull step Change By: Gil Shinar The thing is as follows:I use building blocks, Jenkins jobs, that are usually being used by upstream jobs but I want them to be able to run on their own as well .If I use the Git plugin step in the upstream project, it is no use to run this plugin's procedure again in the downstream job. I would like to be able to pass a Boolean parameter from the upstream job to the downstream job that'll avoid the Git plugin's step, if the parameter evaluates to false. (It can, off course, be a string evaluation or any other comparison parameter or _expression_). 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] [git-plugin] (JENKINS-32998) add condition to the GIT clone/pull step
Title: Message Title Gil Shinar created an issue Jenkins / JENKINS-32998 add condition to the GIT clone/pull step Issue Type: New Feature Assignee: Mark Waite Components: git-plugin Created: 17/Feb/16 1:51 PM Priority: Minor Reporter: Gil Shinar The thing is as follows: I use building blocks, Jenkins jobs, that are usually being used by upstream jobs but I want them to be able to run on their own. If I use the Git plugin step in the upstream project, it is no use to run this plugin's procedure again in the downstream job. I would like to be able to pass a Boolean parameter from the upstream job to the downstream job that'll avoid the Git plugin's step, if the parameter evaluates to false. (It can, off course, be a string evaluation or any other comparison parameter or _expression_). Add Comment
[JIRA] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
Title: Message Title Liya Katz commented on JENKINS-24832 Re: Failed maven builds using -T are showing up as Aborted Any update on this one? 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] [copyartifact-plugin] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Change By: Liya Katz Priority: Major Critical 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-28699) Password type parameterized fields get bogus auto-population of default value despite empty field on job save
Title: Message Title Gil Shinar commented on JENKINS-28699 Re: Password type parameterized fields get bogus auto-population of default value despite empty field on job save At least I have found a workaround. Removing the defaultValue element line from the parameter in the config.xml and reloading jenkins' configuration from disk solves this issue. 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-28699) Password type parameterized fields get bogus auto-population of default value despite empty field on job save
Title: Message Title Gil Shinar edited a comment on JENKINS-28699 Re: Password type parameterized fields get bogus auto-population of default value despite empty field on job save At least I thought I have found a workaround. Removing the defaultValue element line from the parameter in the config.xml and reloading jenkins' configuration from disk solves this issue for the first rerun . After entering a value to the first run, it becomes the default value to next runs. 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] [copyartifact-plugin] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Title: Message Title Liya Katz commented on JENKINS-21905 Re: intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream experience the same issue on rhel slave Jenkins 1.643 CopyArtifacts plugin 1.36.1 ERROR: Failed to archive artifacts: logs/*/ 17:48:30 java.io.IOException: java.io.IOException: Failed to extract xxx transfer of 21 files 17:48:30 at hudson.FilePath.readFromTar(FilePath.java:2300) 17:48:30 at hudson.FilePath.copyRecursiveTo(FilePath.java:2209) 17:48:30 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 17:48:30 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:236) 17:48:30 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) 17:48:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) 17:48:30 at hudson.model.Build$BuildExecution.post2(Build.java:185) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) 17:48:30 at hudson.model.Run.execute(Run.java:1763) 17:48:30 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 17:48:30 at hudson.model.ResourceController.execute(ResourceController.java:98) 17:48:30 at hudson.model.Executor.run(Executor.java:410) 17:48:30 Caused by: java.io.EOFException: Unexpected end of ZLIB input stream 17:48:30 at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186) 17:48:30 at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) 17:48:30 at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.read(TarArchiveInputStream.java:614) 17:48:30 at java.io.InputStream.read(InputStream.java:101) 17:48:30 at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) 17:48:30 at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) 17:48:30 at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) 17:48:30 at hudson.util.IOUtils.copy(IOUtils.java:40) 17:48:30 at hudson.FilePath.readFromTar(FilePath.java:2290) 17:48:30 ... 13 more 17:48:30 17:48:30 at hudson.FilePath.copyRecursiveTo(FilePath.java:2216) 17:48:30 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 17:48:30 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:236) 17:48:30 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) 17:48:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) 17:48:30 at hudson.model.Build$BuildExecution.post2(Build.java:185) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) 17:48:30 at hudson.model.Run.execute(Run.java:1763) 17:48:30 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 17:48:30 at hudson.model.ResourceController.execute(ResourceController.java:98) 17:48:30 at hudson.model.Executor.run(Executor.java:410) 17:48:30 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: This archives contains unclosed entries. 17:48:30 at hudson.remoting.Channel$2.adapt(Channel.java:813) 17:48:30 at hudson.remoting.Channel$2.adapt(Channel.java:808) 17:48:30 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) 17:48:30 at hudson.FilePath.copyRecursiveTo(FilePath.java:2212) 17:48:30 ... 12 more 17:48:30 Caused by: java.io.IOException: This archives contains unclosed entries. 17:48:30 at
[JIRA] [copyartifact-plugin] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Change By: Liya Katz Component/s: copyartifact-plugin 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz created an issue Jenkins / JENKINS-32219 Allure Reports are not visible after upgrading to Jenkins 1.643 Issue Type: Bug Assignee: Artem Eroshenko Components: allure-plugin Created: 29/Dec/15 3:43 PM Environment: Jenkins 1.643 Allure Report plugin 2.8 and 2.10 Priority: Blocker Reporter: Liya Katz When trying to open Allure Report, it stuck on "Loading" forever. Same for new and old reports (those that were ok before Jenkins upgrade) Add Comment
[JIRA] [allure-plugin] (JENKINS-32224) Correct support for matrix job
Title: Message Title Liya Katz created an issue Jenkins / JENKINS-32224 Correct support for matrix job Issue Type: Bug Assignee: Artem Eroshenko Components: allure-plugin Created: 29/Dec/15 10:54 PM Priority: Major Reporter: Liya Katz I have a matrix job that runs on 2 nodes, each one runs the same set of tests and creates the report. The Allure report is shown just fine for each node build. For the "main" build: If both nodes were successful (or unstable), the report just stuck forever on "Loading" If one of them has failed and no report was created, the "main" build report shows the successful node build report. Both are confusing I suggest to add an option to show merged report on the main build - probably should be the default option, alternative should be not to show Allure report on the main build at all Add Comment
[JIRA] [allure-plugin] (JENKINS-32224) Correct support for matrix job
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-32224 Correct support for matrix job Change By: Liya Katz Environment: Jenkins 1.643 Allure Report plugin 2.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 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz commented on JENKINS-32219 Re: Allure Reports are not visible after upgrading to Jenkins 1.643 Thank you! It works. Please update Jenkins plugin wiki page with this info 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz resolved as Fixed Jenkins / JENKINS-32219 Allure Reports are not visible after upgrading to Jenkins 1.643 Change By: Liya Katz Status: Open Resolved 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz closed an issue as Fixed Jenkins / JENKINS-32219 Allure Reports are not visible after upgrading to Jenkins 1.643 Change By: Liya Katz Status: Resolved Closed 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] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
Title: Message Title Liya Katz commented on JENKINS-24832 Re: Failed maven builds using -T are showing up as Aborted Experiencing the same issue with Jenkins 1.627, Maven plugin 2.12.1 It is critical because developers are not notified when builds are aborted (usually manual action) If there is a fix, why is it still not merged? 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] [multijob-plugin] (JENKINS-30226) MultiJob getting "stuck" after all child jobs complete
Title: Message Title itai Or commented on JENKINS-30226 Re: MultiJob getting "stuck" after all child jobs complete It looks like a bug related to this topic: https://issues.jenkins-ci.org/browse/JENKINS-29888 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Gil Shinar edited a comment on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked Tested it with FF but still same behavior. I have tried to set the default value of the Boolean reference to true and now when I press on the "build with parameters" link, it does evaluates to "on" but when I uncheck the Boolean reference, it does not evaluates to other than "on". That is very strange. The only thing that is still different in my environment is the Jenkins version. I have tried to read the changelog but couldn't find anything about Boolean parameters or something like that.I'll try to upgrade the Jenkins version to the latest LTS later on today but I doubt it'll solve my issue.I really have no clue. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Gil Shinar commented on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked Tested it with FF but still same behavior. I have tried to set the default value of the Boolean reference true and now when I press on the "build with parameters" link, it does evaluates to "on" but when I uncheck the Boolean reference, it does not evaluates to other than "on". That is very strange. The only thing that is still different in my environment is the Jenkins version. I have tried to read the changelog but couldn't find anything about Boolean parameters or something like that. I'll try to upgrade the Jenkins version to the latest LTS later on today but I doubt it'll solve my issue. I really have no clue. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Gil Shinar commented on JENKINS-32044 Re: Fail to evaluate Boolean parameter to "on" when checked So maybe the issue is with chrome? I'll test that with FF 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] [promoted-builds-plugin] (JENKINS-32127) Promoted build should not be signed as "keep forever" and not deleted automatically
Title: Message Title Liya Katz created an issue Jenkins / JENKINS-32127 Promoted build should not be signed as "keep forever" and not deleted automatically Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 17/Dec/15 3:40 PM Environment: Jenkins 1.627 promoted-builds-plugin 2.24 Priority: Critical Reporter: Liya Katz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [promoted-builds-plugin] (JENKINS-32127) Promoted build should be signed as "keep forever" and not deleted automatically
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-32127 Promoted build should be signed as "keep forever" and not deleted automatically Change By: Liya Katz Summary: Promoted build should not be signed as "keep forever" and not deleted automatically 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Gil Shinar updated an issue Jenkins / JENKINS-32044 Fail to evaluate Boolean parameter to "on" when checked Change By: Gil Shinar When I try to use a Boolean parameter as a reference parameter to an Active Choice Reactive Parameter, it never evaluates to "on". I am using Jenkins version: 1.625.1I am using latest version of Active Parameter plugin (1.2) I am using jQuery plugin version: 1.11.2-0Attached please find a example config.xml of a job I have tested on. 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] [active-choices-plugin] (JENKINS-32044) Fail to evaluate Boolean parameter to "on" when checked
Title: Message Title Gil Shinar created an issue Jenkins / JENKINS-32044 Fail to evaluate Boolean parameter to "on" when checked Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: config.xml Components: active-choices-plugin Created: 13/Dec/15 7:58 AM Priority: Minor Reporter: Gil Shinar When I try to use a Boolean parameter as a reference parameter to an Active Choice Reactive Parameter, it never evaluates to "on". I am using Jenkins version: 1.625.1 I am using latest version of Active Parameter plugin I am using jQuery plugin version: 1.11.2-0 Attached please find a example config.xml of a job I have tested on. Add Comment
[JIRA] [multijob-plugin] (JENKINS-19680) Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed)
Title: Message Title Chen Cohen commented on JENKINS-19680 Re: Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed) Fail to reproduce this issue with latest version. is anyone still experiencing this one? 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] [multijob-plugin] (JENKINS-19680) Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed)
Title: Message Title Chen Cohen closed an issue as Cannot Reproduce Please reopen if reoccur. Jenkins / JENKINS-19680 Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed) Change By: Chen Cohen Status: Open Closed Resolution: Cannot Reproduce 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] [s3-plugin] (JENKINS-31556) Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off
Title: Message Title Gil Shinar commented on JENKINS-31556 Re: Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off Jenkins version is: 1.625.1 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] [s3-plugin] (JENKINS-31556) Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off
Title: Message Title Liya Katz created an issue Jenkins / JENKINS-31556 Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off Issue Type: Bug Assignee: Michael Watt Components: s3-plugin Created: 15/Nov/15 11:17 AM Priority: Major Reporter: Liya Katz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You
[JIRA] [s3-plugin] (JENKINS-31556) Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-31556 Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off Change By: Liya Katz s3-plugin version is 0.8Works fine if 'Manage artifacts' is off 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen resolved as Fixed Added AbstractBuild to SubBuild. See PR #80 Jenkins / JENKINS-30906 MultiJobBuild.SubBuild does not contain full job name (if using folders) Change By: Chen Cohen Status: Open Resolved 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen updated an issue Jenkins / JENKINS-30906 MultiJobBuild.SubBuild does not contain full job name (if using folders) Hi Vasili, I've added AbstractBuild to SubBuild, so you can call SubBuild.getBuild to get the data you requested. I've uploaded a locally build hpi that I was hoping you can try and confirm that it solves this issue. Please let me know how it worked. Thanks, Chen. Change By: Chen Cohen Attachment: jenkins-multijob-plugin.hpi 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen assigned an issue to Chen Cohen Jenkins / JENKINS-30906 MultiJobBuild.SubBuild does not contain full job name (if using folders) Change By: Chen Cohen Assignee: Chen Cohen 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen commented on JENKINS-30906 Re: MultiJobBuild.SubBuild does not contain full job name (if using folders) Hi Vasili, MultiJobBuild.SubBuild is not aware of its container. You can't do that. Regards, Chen 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen commented on JENKINS-30906 Re: MultiJobBuild.SubBuild does not contain full job name (if using folders) Hi Vasili and thanks for your detailed explanation. Since MultiJobBuild is sub-type of AbstractBuild you can use the following: MultiJobBuild mjb; mjb.getProject().getFullName(); When debugging the example in screenshot-1.png the above code returns: folder1/job1 Please let me know if it worked for you. Thanks, Chen 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen commented on JENKINS-30906 Re: MultiJobBuild.SubBuild does not contain full job name (if using folders) Trying to understand this issue I created the following structure (see screenshot-1) Where exactly do you expect to see 'folder1/job1', is it in this view? Please elaborate. Thanks, Chen. 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] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen updated an issue Jenkins / JENKINS-30906 MultiJobBuild.SubBuild does not contain full job name (if using folders) Change By: Chen Cohen Attachment: screenshot-1.png 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] [maven-plugin] (JENKINS-20413) Maven plugin don't take into account maven-deploy-plugin skip option
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-20413 Maven plugin don't take into account maven-deploy-plugin skip option Change By: Liya Katz Component/s: maven-deployment-linker-plugin 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] [maven-plugin] (JENKINS-20413) Maven plugin don't take into account maven-deploy-plugin skip option
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-20413 Maven plugin don't take into account maven-deploy-plugin skip option Change By: Liya Katz 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] [maven-plugin] (JENKINS-20413) Maven plugin don't take into account maven-deploy-plugin skip option
Title: Message Title Liya Katz commented on JENKINS-20413 Re: Maven plugin don't take into account maven-deploy-plugin skip option While some of my poms have property: true (or skip=true in maven-deploy-plugin configuration) deploy is skipped when running maven commandline, but when using a post-build step 'Deploy artifacts to Maven repository' in Jenkins, all artifacts are deploy, skip is ignored 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] [email-ext-plugin] (JENKINS-30140) quotes become in html content
Title: Message Title Gil Shinar commented on JENKINS-30140 Re: quotes become in html content Worked like a charm Thanks a lot 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] [email-ext-plugin] (JENKINS-30140) quotes become apos in html content
Title: Message Title Gil Shinar commented on JENKINS-30140 Re: quotes become apos in html content OK Will upgrade and report here Thanks 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] [build-flow-plugin] (JENKINS-30149) Add user environment check box
Title: Message Title Gil Shinar created an issue Jenkins / JENKINS-30149 Add user environment check box Issue Type: Improvement Assignee: Nicolas De Loof Components: build-flow-plugin Created: 26/Aug/15 12:37 PM Priority: Minor Reporter: Gil Shinar In a freestyle jenkins job, there's this Set jenkins user build variables check box that adds the started by environment parameter to the job's global parameter so I can send this information in the mail for those who wants to know who had started their jobs. It'll be great if you'll be able to add that as well. Add Comment
[JIRA] [email-ext-plugin] (JENKINS-30140) quotes become apos in html content
Title: Message Title Gil Shinar commented on JENKINS-30140 Re: quotes become apos in html content jenkins 1596.1 email-ext 2.39 I have read release notes for all version from 2.39 to the latest but didn't see any fix related to this Thanks!! 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] [email-ext-plugin] (JENKINS-30140) quotes become apos in html content
Title: Message Title
Gil Shinar created an issue
Jenkins / JENKINS-30140
quotes become apos in html content
Issue Type:
Bug
Assignee:
Alex Earl
Attachments:
ansi2html.sh
Components:
email-ext-plugin
Created:
26/Aug/15 8:39 AM
Priority:
Minor
Reporter:
Gil Shinar
I'm creating a git diff in each CI run and convert the output to html using the attached file. The output looks just fine but still quotes are being generated as apos: var util = requuire('util')
is
var util = require('util'),
Add Comment
[JIRA] [slack-plugin] (JENKINS-27755) Publisher jenkins.plugins.slack.SlackNotifier aborted due to exception
Title: Message Title Yoram Michaeli commented on JENKINS-27755 Re: Publisher jenkins.plugins.slack.SlackNotifier aborted due to exception Got this as well for parallel jobs. Any estimation of when this is going to be resolved? 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Liya Katz commented on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins I meant from specific build you've checked.. The artifacts are not archived there. 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title
Liya Katz edited a comment on JENKINS-27282
Re: Github Webhook not working after upgrade Jenkins and plugins
Latestgit.hpifromthejobworkspace(https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi)doesn'tworkformewithJenkins1.609.1Icanseeinthelog: {{ ReceivedPOSTforhttps://github.com/xxx/vvvJun21,201510:57:47AMINFOcom.cloudbees.jenkins.GitHubWebHookprocessGitHubPayloadReceivedPOSTforhttps://github.com/xxx/vvvJun21,201510:57:47AMWARNINGhudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1errorFailedtoinstantiateoptionalcomponentcom.cloudbees.jenkins.GitHubRepositoryNameContributor$FromMultiSCM;skippingJun21,201510:57:47AMINFOcom.cloudbees.jenkins.GitHubWebHookprocessGitHubPayloadPokedvvvJun21,201510:57:47AMINFOcom.cloudbees.jenkins.GitHubWebHookprocessGitHubPayloadPokedvvv }} Butnothinghappens,thejobvvvdoesn'trun
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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title
Liya Katz edited a comment on JENKINS-27282
Re: Github Webhook not working after upgrade Jenkins and plugins
Latestgit.hpifromthejobworkspace(https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi)doesn'tworkformewithJenkins1.609.1Icanseeinthelog: _Received {{Received POSTforhttps://github.com/xxx/vvvJun21,201510:57:47AMINFOcom.cloudbees.jenkins.GitHubWebHookprocessGitHubPayloadReceivedPOSTforhttps://github.com/xxx/vvvJun21,201510:57:47AMWARNINGhudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1errorFailedtoinstantiateoptionalcomponentcom.cloudbees.jenkins.GitHubRepositoryNameContributor$FromMultiSCM;skippingJun21,201510:57:47AMINFOcom.cloudbees.jenkins.GitHubWebHookprocessGitHubPayloadPokedvvvJun21,201510:57:47AMINFOcom.cloudbees.jenkins.GitHubWebHookprocessGitHubPayloadPoked vvv_ vvv}} Butnothinghappens,thejobvvvdoesn'trun
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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Liya Katz commented on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins Latest git.hpi from the job workspace (https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi) doesn't work for me with Jenkins 1.609.1 I can see in the log: _Received POST for https://github.com/xxx/vvv Jun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Received POST for https://github.com/xxx/vvv Jun 21, 2015 10:57:47 AM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate optional component com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromMultiSCM; skipping Jun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked vvv Jun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked vvv_ But nothing happens, the job vvv doesn't run 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Liya Katz commented on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins Where can I download the version that works? 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Liya Katz commented on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins Had the same problem in Jenkins 1.609.1 (latest stable) with plugins: Git plugin 2.3.5 GitHub plugin 1.11.3 Git Client 1.17.1 GitHub Api 1.68 Downgrade to the previous stable release (Jenkins 1.596.3) without changing any plugin solved the problem - it looks like core and not a plugin problem 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-22578) Nothing happens when POST to jenkins github-webhook url
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-22578 Nothing happens when POST to jenkins github-webhook url Change By: Liya Katz Component/s: 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] [core] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Change By: Liya Katz Component/s: 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] [core] (JENKINS-22578) Nothing happens when POST to jenkins github-webhook url
Title: Message Title Liya Katz commented on JENKINS-22578 Re: Nothing happens when POST to jenkins github-webhook url Had the same problem in Jenkins 1.609.1 (latest stable) with plugins: Git plugin 2.3.5 GitHub plugin 1.11.3 Git Client 1.17.1 GitHub Api 1.68 Downgrade to the previous stable release (Jenkins 1.596.3) without changing any plugin solved the problem - it looks like core and not a plugin problem 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] [build-blocker-plugin] (JENKINS-26850) Add plugin parameter Block only if job run on the same node
Liya Katz created JENKINS-26850 Add plugin parameter Block only if job run on the same node Issue Type: Improvement Assignee: Unassigned Components: build-blocker-plugin Created: 08/Feb/15 9:31 AM Project: Jenkins Priority: Critical Reporter: Liya Katz 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] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Liya Katz commented on JENKINS-18125 Changelog empty or contains all changes Do you have any estimation when it will be 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/d/optout.
[JIRA] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Liya Katz updated JENKINS-18125 Changelog empty or contains all changes Change By: Liya Katz (13/Jan/15 9:41 AM) Environment: Jenkins LTS 1. 509.1 595 Gitplugin: 1 2 . 3. 4 Gitclientplugin1 . 1.5. 0 GitHubAPIplugin1.59GitHubPlugin1.10GitHubPullRequestBuilder1.16-6 Priority: Major Blocker 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] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Liya Katz commented on JENKINS-18125 Changelog empty or contains all changes We also need it for the incremental build, and it's really bad.. 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] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Liya Katz commented on JENKINS-18125 Changelog empty or contains all changes I have a maven job that is configured to run on creating or changing of Pull Request in GitHub (Enterprise), and I would like this job to run maven build incrementally - build and run unit tests only for modules that were changed by this Pull Request. At the moment the changelog is always empty, so build runs for all modules and takes too long. Is there any information that can be helpful? Build log? 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] [build-pipeline-plugin] (JENKINS-23828) Build Pipeline View doesn't show build user id on Downstream Projects
Gilad Judes commented on JENKINS-23828 Build Pipeline View doesnt show build user id on Downstream Projects this happens in other "pipeline" plugins (i.e. Delivery Pipeline Plugin) when setting up a manual step - the user logs in and press the | (play) button the build status in jenkins shows "Started by anonymous user" while the build xml (e.g. /var/lib/jenkins/jobs/Product-1.0.6-promote-to-QA/builds/22/build.xml) au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView_-MyUserIdCause plugin="build-pipeline-plugin@1.4.5" userIdgilad/userId user fullNameGilad Judes/fullName properties BTW we are working with Active Directory authentication 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] [build-flow-plugin] (JENKINS-18088) Build flow execute on slave but write file on master
Gil Shinar commented on JENKINS-18088 Build flow execute on slave but write file on master And how can I print a file content? When I run 'cat /path/to/file'.execute().text I get file not found (obviously not found on the master) 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] [multijob-plugin] (JENKINS-25452) Change implementation of Build Only If SCMChanges to be check just if it's configure
itai Or created JENKINS-25452 Change implementation of Build Only If SCMChanges to be check just if its configure Issue Type: Bug Assignee: itai Or Components: multijob-plugin Created: 05/Nov/14 3:15 PM Description: hudson.scm.SCM.calcRevisionsFromBuild(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/TaskListener;)Lhudson/scm/SCMRevisionState; java.lang.AbstractMethodError: hudson.scm.SCM.calcRevisionsFromBuild(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/TaskListener;)Lhudson/scm/SCMRevisionState; at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.getScmChange(MultiJobBuilder.java:117) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:181) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1706) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Project: Jenkins Priority: Major Reporter: itai Or 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-24898) Job is reported as aborted while it actually fails
Yoram Michaeli created JENKINS-24898 Job is reported as aborted while it actually fails Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Sep/14 10:42 AM Description: We have a build is reported as aborted even that the build fails for compilation error in the maven build (see below build output) and has a 'Finished: FAILURE' as its final output: 00:18:17.412 ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project reports-generator: Compilation failure 00:18:17.416 ERROR /home/builder/workspace/5/reports-generator/src/main/java/com/taboola/reportsv4/monetization/publishers/rpmminguaranteev4/GuaranteeReportRunner.java:44,52 cannot find symbol 00:18:17.418 ERROR symbol : class PublisherMinGuaranteeReportMonthlyV4Test 00:18:17.420 ERROR location: package com.taboola.reportsv4.monetization.publishers 00:18:17.422 ERROR - Help 1 00:18:17.427 ERROR 00:18:17.429 ERROR To see the full stack trace of the errors, re-run Maven with the -e switch. 00:18:17.430 ERROR Re-run Maven using the -X switch to enable full debug logging. 00:18:17.432 ERROR 00:18:17.434 ERROR For more information about the errors and possible solutions, please read the following articles: 00:18:17.436 ERROR Help 1 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException 00:18:17.438 ERROR 00:18:17.439 ERROR After correcting the problems, you can resume the build with the command 00:18:17.442 ERROR mvn goals -rf :reports-generator ... 00:18:20.105 channel stopped 00:18:21.543 Starting to tag 00:18:21.543 No Subversion tagging for unsuccessful build. 00:18:21.543 Email was triggered for: Aborted 00:18:21.544 Sending email for trigger: Aborted 00:18:22.337 Sending email to: ta...@taboola.com michae...@taboola.com nitza...@taboola.com davi...@taboola.com ila...@taboola.com ro...@taboola.com develop...@taboola.com 00:18:22.433 Notifying upstream projects of job completion 00:18:22.433 Finished: FAILURE Environment: Jenkins ver. 1.565.2 Centos Maven 3.0.4 Project: Jenkins Priority: Major Reporter: Yoram Michaeli 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] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9
Yoram Michaeli edited a comment on JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 Can you send some details about your multi-job and the jobs which you activates in the phases? Also, can you send the console output of the multijob session? I've tried to reproduce the bug (the first reported with the 2 phases) and all looks as working 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/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9
Yoram Michaeli commented on JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 @imakowski, can you send some details about your multi-job and the jobs which you activates in the phases? Also, can you send the console output of the multijob session? I've tried to reproduce the bug (the first reported with the 2 phases) and all looks as working 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/d/optout.
[JIRA] [matrix] (JENKINS-7825) Cannot restrict a matrix build job to one node/label
Gilad Judes resolved JENKINS-7825 as Duplicate Cannot restrict a matrix build job to one node/label created a new issue as requested: https://issues.jenkins-ci.org/browse/JENKINS-23459 Change By: Gilad Judes (17/Jun/14 7:07 AM) Status: Reopened 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/d/optout.
[JIRA] [matrix-project] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Gilad Judes created JENKINS-23459 Cannot restrict a matrix build job to one node/label Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: matrix-project Created: 17/Jun/14 7:06 AM Description: Got the Matrix Job set this under Advanced: "Restrict where this project can be run" to "master" But when I run the Matrix only the first job runs on the Master - the rest run on any of the Slaves available Environment: Jenkins ver. 1.562 Matrix Project Plugin 1.2 Project: Jenkins Priority: Major Reporter: Gilad Judes 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] [matrix] (JENKINS-7825) Cannot restrict a matrix build job to one node/label
Gilad Judes reopened JENKINS-7825 Cannot restrict a matrix build job to one node/label Still happens Jenkins ver. 1.562 Matrix Project Plugin 1.2 Got the Matrix Job set this under Advanced: "Restrict where this project can be run" to "master" But when I run the Matrix only the first job runs on the Master - the rest run on any of the Slaves available Change By: Gilad Judes (17/Jun/14 5:55 AM) 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/d/optout.
[JIRA] [metadata-plugin] (JENKINS-21878) jenkins-multijob-plugin
chaim turkel created JENKINS-21878 jenkins-multijob-plugin Issue Type: Bug Affects Versions: current Assignee: rsandell Components: metadata-plugin Created: 19/Feb/14 3:10 PM Description: If you have a job that the multijob calls, and it has checked "Block build when upstream project is building", then you are in a deadlock' since it is blocking on the multijob Project: Jenkins Priority: Major Reporter: chaim turkel 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-21878) jenkins-multijob-plugin
chaim turkel updated JENKINS-21878 jenkins-multijob-plugin Change By: chaim turkel (19/Feb/14 3:12 PM) Component/s: jenkins-multijob-plugin Component/s: metadata-plugin 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.
