You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/12/17 17:45:00 UTC

[jira] [Resolved] (SLING-7180) Set up a Jenkins job for automatically publishing the Sling site

     [ https://issues.apache.org/jira/browse/SLING-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-7180.
------------------------------------
    Resolution: Fixed

Fixed via https://github.com/apache/sling-site/pull/33 and verified that commit https://github.com/apache/sling-site/commit/8aa9d739a894cb1613d5bfffdc23a4058e2b4ad6 was generated by Jenkins and the website was deployed correctly.

Note that [~kwin] raised a comment in the PR that may require changes but for now this is "done".

> Set up a Jenkins job for automatically publishing the Sling site
> ----------------------------------------------------------------
>
>                 Key: SLING-7180
>                 URL: https://issues.apache.org/jira/browse/SLING-7180
>             Project: Sling
>          Issue Type: Improvement
>          Components: Site
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Once we move to gitbox we should also automatically build + push the site from a Jenkins job so that all we need to do is {{git push}} from the master branch.



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