>> Do you have to shell out and cp everything? If that's the case, how do
you properly handle errors etc?
The sh/bat have the returnStatus and returnStdout. Sadly no returnStdError,
so you need to pipe and I suggest to use 'tee' to duplicate it if need such
feature.
I should mention that I'm specifically trying to perform file operations
within a workspace using global pipeline libraries. I'm not following how a
global pipeline library would even make sense if it can only run on master
- am I missing something here?
On Thursday, August 3, 2017 at 3:06:23
I totally agree with Stephen here, the pipeline script engine is a lock
down groovy with many quirks and approval mess. Making it a painful
experience. Do as much as possible into your build scripts (.vcxproj,
makefile, shell script, python...). Just launch them and take light
decision into
On 2 August 2017 at 08:14, bbyjenkns wrote:
> Ok - understood. That does clear some things up. Where can I find more
> info on what is and is not allowed in global pipelines libraries? I'm
> writing one now, and have defaulted to using the 'sh' step and returning
> status codes
Ok - understood. That does clear some things up. Where can I find more info
on what is and is not allowed in global pipelines libraries? I'm writing
one now, and have defaulted to using the 'sh' step and returning status
codes to do most every file operation because what I try to do in base
On 2 August 2017 at 06:10, bbyjenkns wrote:
> I'm struggling with the same thing - doc is very light or wants you to
> shell out for everything. I want to write groovy for everything, but it
> seems like simple things, such as using AntBuilder for it's file operation
> magic is
I'm struggling with the same thing - doc is very light or wants you to
shell out for everything. I want to write groovy for everything, but it
seems like simple things, such as using AntBuilder for it's file operation
magic is very difficult if not impossible.
On Tuesday, August 1, 2017 at
+1 for this question.
On Wed, Aug 2, 2017 at 3:24 AM, Carruth, Rusty
wrote:
> I’ve read the “getting started with pipeline” pages (
> https://jenkins.io/doc/book/pipeline/getting-started/).
>
>
>
> I’ve spent literally hours looking for something really helpful, in one
On Wed 2 Aug 2017 at 00:24, Carruth, Rusty wrote:
> I’ve read the “getting started with pipeline” pages (
> https://jenkins.io/doc/book/pipeline/getting-started/).
>
>
>
> I’ve spent literally hours looking for something really helpful, in one
> place, for someone who
I've read the "getting started with pipeline" pages
(https://jenkins.io/doc/book/pipeline/getting-started/).
I've spent literally hours looking for something really helpful, in one place,
for someone who wants to write CODE in the pipeline script.
I did just find
10 matches
Mail list logo