Any ideas on how to design this Jenkins slave provisioning capability?
I want to be able to build on specified versions of the Linux kernel
(x.y.z-ABI). On a given kernel, I want to specify a docker container having
the build environment to run the build in. I want to provision the node,
build,
ase.
>
> 2016-05-31 20:02 GMT+02:00 Brian Jones >:
>
>> I want to have a pipeline where segments of the pipeline are only
>> executed upon a human decision, possibly hours or days after the job is
>> started. What is the recommended way to do this using the pipeline plug
I want to have a pipeline where segments of the pipeline are only executed
upon a human decision, possibly hours or days after the job is
started. What is the recommended way to do this using the pipeline plugin?
pipeline:
Decide to continue case:
build step A - build step B - < human decision
Kevin,
I agree with you. How can that be implemented?
All,
It appears to me that Jenkins does not work well with this use case:
* master HEAD is release version 1 (v1) of product.
* 4 features ABCD that are implemented on git branches ABCD respectively
based on v1
* Jenkins project to build
Is it possible to get Jenkins to detect and report "Changes" for the first
commit on a new branch/build?
I'm setting up feature based development in git:
* Feature branches are named after an issue ID (e.g., JIRA issue ID)
* Feature branches based on git master branch
* Commits to feature branch