You take the Jenkinsfile from e.g. here https://github.com/apache/uima-uimaj/blob/master/Jenkinsfile
and drop it here: https://github.com/apache/uima-async-scaleout/tree/master You might care to briefly skim the contents of the Jenkinsfile to get an idea what it does. Once that's done, the Job here should automatically pick up the branch/pull request: https://ci-builds.apache.org/job/UIMA/job/uima-async-scaleout/ You can also give Jenkins a gentle nudge by clicking on "Scan Repository Now" on the left side (make sure you are logged in to Jenkins). If you do that, you'll also get a report about which branches were found in the repo and whether they matched the criteria for a job to be created for them. If I read it right, the Lucene approach just pulls the job descriptions from the old Jenkins - but on the old Jenkins we used old-fashioned "Maven job" types. I thought it would be a good opportunity to move over to using repo-managed build pipelines (that's what the Jenkinsfile is). Cheers, -- Richard > On 19. Aug 2020, at 17:26, Jaroslaw Cwiklik <[email protected]> wrote: > > Richard, I tried to follow Jenkins migration using Lucene instructions ( > https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees > ) > > Not having much luck. > > Looks like you've migrated UIMA-SDK. Can you share any hints how to do > this? > Appreciate any help you can provide. > Jerry
