Hi, Did you get this to work? I need to do something similar, I need to transfer artifacts from one runner to another. I'm running a Windows build system and a raspberry-pi test system.
Den torsdag 13 augusti 2015 kl. 03:30:21 UTC+2 skrev Jeff Scaparra: > > I am aware of the tag features and we are using them. My question was more > I want to have build steps and separate test steps and packaging. When the > test run I have it set to do a fresh clone to ensure there aren't artifacts > that are causing problems. In the test and deployment steps I don't want to > have to rebuild the project. Is there a way to archive off build artifacts > for follow on testing and deployment packages. > > Jeff > On Aug 12, 2015 7:34 PM, "Sytse Sijbrandij" <sy...@gitlab.com > <javascript:>> wrote: > >> You can tag/label runners so they are on the right platform. >> >> >> Best regards, >> Sytse 'Sid' Sijbrandij >> CEO GitLab B.V. >> >> On Fri, Aug 7, 2015 at 8:58 PM, Jeff Scaparra <je...@scaparra.com >> <javascript:>> wrote: >> >>> I am just getting started with using the ci server. I want to have lots >>> of different runners that projects can use but I have some concerns. >>> >>> If I have separate steps for various builds on different platforms and >>> then separate tests how can I be assured that the tests will run on the >>> runner that has actually compiled the binary if there are multiple eligible >>> runners? >>> >>> Thinking about something like >>> >>> build32: >>> tags: >>> - Win32 >>> - VS2015 >>> script: >>> - MsBuild <options for 32 bit> >>> only: >>> - branches >>> >>> build64: >>> <similar to above> >>> >>> >>> test32: >>> < This would need to run on the same runner that built build32 >>> even if multiple runners had the right tags> >>> >>> >>> test64: >>> <same type of deal> >>> >>> >>> Hope that is clear. >>> >>> Jeff >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "GitLab" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to gitlabhq+u...@googlegroups.com <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/gitlabhq/CALWgEa0WuGZ0mzSqAufL-UfU8ye_thRsd0V99AiDxqoD%2BHt6PQ%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/gitlabhq/CALWgEa0WuGZ0mzSqAufL-UfU8ye_thRsd0V99AiDxqoD%2BHt6PQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "GitLab" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gitlabhq+u...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/CAJTzhG-1pBMVmRgSucb535g9P5fv-0QSrJmQoCFCWQDABa8oLg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/gitlabhq/CAJTzhG-1pBMVmRgSucb535g9P5fv-0QSrJmQoCFCWQDABa8oLg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/470855ba-806d-45b8-9061-d50af02320b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
