[
https://issues.apache.org/jira/browse/SLING-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215295#comment-16215295
]
Robert Munteanu edited comment on SLING-7163 at 10/23/17 3:24 PM:
------------------------------------------------------------------
The canonical solution seems to be to define a shared library and include it
from all projects. We could then define minimal {{Jenkinsfile}}s for each repo,
for instance
{code}
mavenBuild()
{code}
Not ideal, but if we want to have checks on PRs I don't think we can keep using
the maven or freestyle job types.
_edit_: formatting
was (Author: rombert):
The canonical solution seems to be to define a shared library and include it
from all projects. We could then define minimal {{Jenkinsfile}}s for each repo,
for instance
{code:groovy}
mavenBuild()
{code}
Not ideal, but if we want to have checks on PRs I don't think we can keep using
the maven or freestyle job types.
> Update Jenkins jobs to reference the git repositories
> -----------------------------------------------------
>
> Key: SLING-7163
> URL: https://issues.apache.org/jira/browse/SLING-7163
> Project: Sling
> Issue Type: Sub-task
> Components: Best practices
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
>
> As a first step, we should probably disable/delete all 'old' jobs. Then we
> should re-create them pointing to the git repos.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
