sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SLING-7245) Validate pull requests using Jenkins
Date Thu, 31 Jan 2019 11:28:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755434#comment-16755434
] 

Robert Munteanu edited comment on SLING-7245 at 1/31/19 11:27 AM:
------------------------------------------------------------------

I've migrated more modules - 98 now live under [https://builds.apache.org/job/Sling%20(pipeline%20jobs)/]
. Pending any major issues, the plan is to:
 * switch all jobs to the Jenkinsfile approach (/)
 * disable seed job (/)
 * delete old views (/)
 * rename pipeline job folder to "Sling" (/)
 * validate that nothing was lost in the meantime
 * tweak notifications (some starter and the launchpad its should notify dev@sling on failure)
(/)
 * migrate sling-site to new infrastructure (/)
 * decide what to do with sling-ide-tooling - can we at least reuse the common parts of the
current {{slingOsgiBundleBuild}}?
 * merge changes to master (/)
 * update Sling Jenkins wiki page (/)
 * update Sling module descriptor wiki page (/)
 * ensure that PR builds do not deploy artifacts (/)
* set timeouts (/)

Follow-up improvements ( will file separate issues later):

 * {{slingOsgiModuleBuild}} should check that the current SNAPSHOT deploys in the starter
successfully and passes all ITs (if already present in the starter)
 * create a new {{slingMavenModuleBuild}} build type for Maven mojos and archetypes since
they should not be deployed in the starter
 * the "Sling" org folder should be created by the seed job _or_ we should find another way
to store the folder definition in git
 * create another "Sling-Dashboard" or equivalent view to help spotting problems


was (Author: rombert):
I've migrated more modules - 98 now live under [https://builds.apache.org/job/Sling%20(pipeline%20jobs)/]
. Pending any major issues, the plan is to:
 * switch all jobs to the Jenkinsfile approach (/)
 * disable seed job (/)
 * delete old views (/)
 * rename pipeline job folder to "Sling" (/)
 * validate that nothing was lost in the meantime
 * tweak notifications (some starter and the launchpad its should notify dev@sling on failure)
(/)
 * migrate sling-site to new infrastructure (/)
 * decide what to do with sling-ide-tooling - can we at least reuse the common parts of the
current {{slingOsgiBundleBuild}}?
 * merge changes to master (/)
 * update Sling Jenkins wiki page (/)
 * update Sling module descriptor wiki page (/)
 * ensure that PR builds do not deploy artifacts (/)
* set timeouts

Follow-up improvements ( will file separate issues later):

 * {{slingOsgiModuleBuild}} should check that the current SNAPSHOT deploys in the starter
successfully and passes all ITs (if already present in the starter)
 * create a new {{slingMavenModuleBuild}} build type for Maven mojos and archetypes since
they should not be deployed in the starter
 * the "Sling" org folder should be created by the seed job _or_ we should find another way
to store the folder definition in git
 * create another "Sling-Dashboard" or equivalent view to help spotting problems

> Validate pull requests using Jenkins
> ------------------------------------
>
>                 Key: SLING-7245
>                 URL: https://issues.apache.org/jira/browse/SLING-7245
>             Project: Sling
>          Issue Type: Improvement
>          Components: Build and Source Control
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>         Attachments: image-2019-01-30-12-52-54-106.png, image-2019-01-30-12-52-56-248.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We should refine the work done in SLING-7163 and validate PRs using Jenkins.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message