[
https://issues.apache.org/jira/browse/HBASE-22167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815496#comment-16815496
]
Allen Wittenauer edited comment on HBASE-22167 at 4/11/19 3:14 PM:
-------------------------------------------------------------------
Definitely not supported yet.
Jenkins auth tokens aren't supported by Pipeline jobs. This means that the
jenkins-admin code needs to actually have a real user to auth against jenkins
in order to submit jobs. The alternative is to have jenkins-admin write
something that can be read by groovy code sitting in a Jenkins pipeline that
does a job submission without needing to auth. If that path is taken, then it
also needs to have a {project list} -> {job list} mapping, since there is no
real 1:1 mapping anymore. (e.g., HADOOP, HDFS, YARN, ... ->
hadoop-multibranch-pipeline)
Yet Another Alternative is to try and replace jenkins-admin with the
jenkins-jira plugin. It's loaded on our Jenkins server, but my attempts to use
it in any meaningful way fell apart since it didn't seem to understand
attachments very well. But the theory was that a pipeline job could be written
that would take that plugins input and just resubmit to the appropriate the
multibranch job.
All-in-all, it's a lot of work. I had some same code written to implement the
jenkins-admin-as-a-pipeline-job but I can't seem to find it. Plus I'm not
doing much with the ASF anymore so it sort of fell off my priority list.
was (Author: aw):
Definitely not supported yet.
Jenkins auth tokens aren't supported by Pipeline jobs. This means that the
jenkins-admin code needs to actually have a real user to auth against jenkins
in order to submit jobs. The alternative is to have jenkins-admin write
something that can be read by groovy code sitting in a Jenkins pipeline that
does a job submission without needing to auth. If that path is taken, then it
also needs to have a {project list} -> {job list} mapping, since there is no
real 1:1 mapping anymore. (e.g., HADOOP, HDFS, YARN, ... ->
hadoop-multibranch-pipeline)
Yet Another Alternative is to try and replace jenkins-admin with the
jenkins-jira plugin. It's loaded on our Jenkins server, but my attempts to use
it in any meaningful way fell apart since it didn't seem to understand
attachments very well. But the theory was that a pipeline job could be written
that would take that plugins input and just resubmit to the appropriate the
multibranch job.
All-in-all, it's a lot of work. I had some same code written to implement the
latter but I can't seem to find it. Plus I'm not doing much with the ASF
anymore so it sort of fell off my priority list.
> Unify the new github based pre commit job and our nightly job
> -------------------------------------------------------------
>
> Key: HBASE-22167
> URL: https://issues.apache.org/jira/browse/HBASE-22167
> Project: HBase
> Issue Type: Improvement
> Reporter: Duo Zhang
> Priority: Minor
>
> Now we use two jenkins files and set up two jobs on jenkins. They both use
> yetus and seems yetus 0.9.0 can have a PR tab and a branch tab in the same
> job. So we can unify them together.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
