[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] [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] [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] [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] [core] (JENKINS-19752) Download build artifacts as zip generates a corrupted file
Yoram Michaeli commented on JENKINS-19752 Download build artifacts as zip generates a corrupted file Happens to me as well in releases 1.536 1.540 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19752) Download build artifacts as zip generates a corrupted file
Yoram Michaeli reopened JENKINS-19752 Download build artifacts as zip generates a corrupted file Happens to me in 1.535, 1.536, 1.539 Change By: Yoram Michaeli (20/Nov/13 3:11 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-19752) Download build artifacts as zip generates a corrupted file
Yoram Michaeli edited a comment on JENKINS-19752 Download build artifacts as zip generates a corrupted file Happens to me in 1.535, 1.536, 1.539 yorammi-macbook:temp Yoram$ unzip ../archive\ 3.zip Archive: ../archive (3).zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of ../archive (3).zip or ../archive (3).zip.zip, and cannot find ../archive (3).zip.ZIP, period. 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Yoram Michaeli commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online I had the same issue and downgrade to 0.22 of the ssh-slaves plugin solved it for me as well. I needed to re-enter the credentials for all the nodes as well. Lucky me that I have only 6 nodes... 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Yoram Michaeli reopened JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Happens to me as well (Master on Linux). No downgrade of SSH plugin or jenkins.war help in any way! Change By: Yoram Michaeli (09/Apr/13 1:24 PM) Resolution: NotADefect Status: Closed 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/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Yoram Michaeli updated JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Change By: Yoram Michaeli (09/Apr/13 1:32 PM) Priority: Blocker Critical 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Yoram Michaeli commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Problem overcome using a workaround: setting user/password to a local server user instead of the default (leaving the user/password setting empty so it uses a special jenkins account) - seems something has been changed reguarding the jenkins local user. 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli closed JENKINS-16976 as Fixed [publish-over-ftp-1.8] upload creates unneeded folders Tested OK with version 1.9. Thanks! Change By: Yoram Michaeli (04/Mar/13 1:31 PM) Status: Resolved Closed 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli updated JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders JENKINS-16976-configuration Change By: Yoram Michaeli (28/Feb/13 1:38 PM) Attachment: ScreenShot2013-02-28at3.35.25PM.png 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli commented on JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders Configuration: = I'll attach a screenshot Log: === FTP: Connecting from host TabBuild1.tabtale.local FTP: Connecting with configuration box-ftp-server ... 220 Service ready for new user. FTP: Logging in, command printing disabled FTP: Logged in, command printing enabled CWD Release/SDK 250 Directory changed to /Release/SDK FTP: Remote root is not absolute, getting absolute directory from PWD PWD 257 "/Release/SDK" is current directory. TYPE I 200 Command TYPE okay. CWD /Release/SDK 250 Directory changed to /Release/SDK CWD 3.3/3.3.41 550 No such directory. MKD 3.3/3.3.41 257 "/Release/SDK/3.3.41" created. CWD 3.3/3.3.41 550 No such directory. CWD 3.3 550 No such directory. MKD 3.3 257 "/Release/SDK/3.3" created. CWD 3.3 250 Directory changed to /Release/SDK/3.3 CWD 3.3.41 550 No such directory. MKD 3.3.41 257 "/Release/SDK/3.3/3.3.41" created. CWD 3.3.41 250 Directory changed to /Release/SDK/3.3/3.3.41 PASV 227 Entering Passive Mode (74,112,184,39,92,57) STOR tabtale-sdk-osx-3.3.41.zip 150 File status okay; about to open data connection. 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli updated JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders JENKINS-16976-configuration Change By: Yoram Michaeli (28/Feb/13 1:39 PM) Attachment: ScreenShot2013-02-28at3.35.25PM.png 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli commented on JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders the created structure - as a result of the above run - is: path #1: /Release/SDK/3.3/3.3.41/tabtale-sdk-osx-3.3.41.zip path #2: /Release/SDK/3.3.41 (empty folder) while path #1 is what I need, path #2 is wrong and mess up the FTP-folder with many empty and unneeded folder. 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-16870) Jenkins cant display multijob view graphically if the multijob phase is wrapped in a conditional buildstep
Yoram Michaeli assigned JENKINS-16870 to Yoram Michaeli Jenkins cant display multijob view graphically if the multijob phase is wrapped in a conditional buildstep Change By: Yoram Michaeli (27/Feb/13 3:24 PM) Assignee: domi YoramMichaeli 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli created JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders Issue Type: Bug Assignee: bap Components: publish-over-ftp Created: 27/Feb/13 6:51 AM Description: There are actually 2 flavors to the same bug (it should be maybe 2 bugs): 1. in non-flaten mode, if the uploaded file path is - for example - dir1/dir2/dir3/file.zip then it creates those folders in the FTP server: dir2, dir3, dir1/dir2/dir3 (where it puts the file). The creation of dir2 and dir3 is wrong! 2. in flaten and non-flaten modes, if the target folder has - for example - the format dir1/dir2/dir3, the created folders in the FTP server are: dir1, dir2 and dir3 while it should create only a structure of dir1/dir2/dir3 and puts it there Environment: upload to ftp.box.com 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/groups/opt_out.
[JIRA] (JENKINS-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli
commented on JENKINS-16976
[publish-over-ftp-1.8] upload creates unneeded folders
About item #1 - the flaten checkbox solved it for me there for it is not critical. Still, seems like a but to be that it created all unneeded folders.
About item #2 - heres the configuration I tried and what it created for me:
Source files: multiPlatform/build/sdk/target/tabtale-sdk-osx-3.6.${BUILD_NUMBER}.zip
Remove prefix:
Remote directory: 3.6/3.6.${BUILD_NUMBER}
I've run it in flaten mode for avoid the first problem, and this is the resulted output:
if BUILD_NUMBER=11 (for example), it creates 2 folders: 3.6 and 3.6.11 (where it puts the zip file) while I expected it to create a 3.6/3.6.11 structure (meaning: a 3.6 folder with 3.6.11 folder in it).
For now I've solved it by avoiding the major-version folder (3.6 in this case) and created a 3.6.11 folder only but this is ugly since after have many versions I'll 3.6 folders in the same level as 3.7 and so on.
I can solve it - for now - by having a different 'ftp server' configuration for each major version (each one will have different 'remote directory') but I prefer to wait for a fix from you.
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
--
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-14955) Wrong links created on summary on a multijob execution
Yoram Michaeli resolved JENKINS-14955 as Fixed Wrong links created on summary on a multijob execution Change By: Yoram Michaeli (14/Feb/13 9:28 AM) Status: Open Resolved Fix Version/s: current Resolution: 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/groups/opt_out.
[JIRA] (JENKINS-15965) Currently building links point to wrong downstream projects when concurent builds are active
Yoram Michaeli resolved JENKINS-15965 as Fixed Currently building links point to wrong downstream projects when concurent builds are active Change By: Yoram Michaeli (14/Feb/13 9:29 AM) Status: Open Resolved Fix Version/s: current Resolution: 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/groups/opt_out.
[JIRA] (JENKINS-14952) Downstream job build links are broken when jenkins is not hosted on the root context
Yoram Michaeli commented on JENKINS-14952 Downstream job build links are broken when jenkins is not hosted on the root context Since I've fixed the 2 issues mentioned in the above comment - can someone check if this is fixed once muttijob 1.8 is released? 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-15183) Creating a multijob plugin to as a template cause error
Yoram Michaeli commented on JENKINS-15183 Creating a multijob plugin to as a template cause error This is not clear since templates plugin is a jenkins-enterprise plugin, so if that what this issue is referring to, we cannot support it. If 'use it as a template' means only copy of an existing multijob job as a new job it worked for me just fine 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-15965) Currently building links point to wrong downstream projects when concurent builds are active
Yoram Michaeli assigned JENKINS-15965 to Yoram Michaeli Currently building links point to wrong downstream projects when concurent builds are active Change By: Yoram Michaeli (14/Feb/13 1:50 AM) Assignee: YoramMichaeli 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.
