Does anyone know how to view the build environment for a pipeline job? Is
this built in to the pipeline job somehow and therefore needs no support
from build-environment-plugin? I'd be happy to submit JIRA ticket for this
and submit a patch if the fix isn't too time-consuming.
It's pretty annoy
really
does seem to fill in at least some of the blanks left by Pipeline.
>
> On Thu, Jul 21, 2016 at 10:17 AM, Wayne Warren > wrote:
>
>>
>> Sorry for chiming in late here, but I have recently been evaluating
>> Jenkins Pipeline Plugin for use at my workplace
Sorry for chiming in late here, but I have recently been evaluating Jenkins
Pipeline Plugin for use at my workplace and have considered the very
problem you are describing in this thread--what if a given source repo has
multiple Pipeline groovy scripts it wants to use for different purposes?
T
There are a couple different ways I would do this but the simplest would be
to have a single job that triggers automatically whose primary function is
to trigger all the jobs you want running in parallel as downstream of
itself.
Another way would be to have this "trigger" job make use of the Mu
So I have been experimenting with Jenkins Pipeline Plugin recently. One of
the requirements I am evaluating it against is the ability to express
complex relationships between the build and test steps of different
projects and to parallelize the execution of those steps where possible.
To visu
On Friday, May 6, 2016 at 11:07:44 AM UTC-7, David Karr wrote:
>
> I work in an OpenStack-related community that uses "Jenkins Job Builder"
> to build Jenkins jobs. I don't know a lot about it, but I did manage,
> with a lot of help from our infra team, to make the changes required to
> build
