On 1/21/19 8:21 PM, Shawn McKinney wrote:
>> Let me know what you think or if you have objections or questions.
>> Otherwise I'd continue with more Jenkinsfiles :)
>
> +1, sounds like a great idea to me. Is this something we can divide and
> conquer? I’ve never done this, but it’s something I’ve been interested in
> for some time. Also, would be a great introduction to a project for a
> newbie.
Sure :)
Just take the existing Jenkinsfile as a template and adapt it. Then
create a Jenkins pipeline job similar the the LDAP API one. The official
Jenkins pipeline documentation might be useful [1].
You can easily develop the Jenkinsfile within a branch, then just
specify the branch to build in the Jenkins job.
To some extend it's also possible to run such a pipeline on your own
Jenkins server. This is especially useful to avoid long wait cycles when
no build slots are available on the ASF Jenkins. However at some point
that has limits, e.g. when using ASF Jenkins specific labels ("Windows")
or JDK installation paths or deployment credentials.
Kind Regards,
Stefan
[1] https://jenkins.io/doc/book/pipeline/
