[jira] [Comment Edited] (LUCENE-9015) Configure branches, auto build and auto stage/publish

["Jan Høydahl (Jira)" <ji...@apache.org>]

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

Jan Høydahl edited comment on LUCENE-9015 at 11/14/19 10:59 PM:
----------------------------------------------------------------

I think we don't need tasks.py, Makefile, publishconf or similar. Probably this would work:
{code:java}
git checkout master
# prod branch (src)
git checkout -b production
cat << EOF > .asf.yaml
pelican:
  whoami: production
  target: asf-site
EOF
git add .asf.yaml
git commit -m "Production source branch"
git push origin
{code}
Then we get the simple workflow. Once we have a site we're happy with in master, we just merge to production branch and it ends up in the main site, and you can continue working in master with unstable stuff. Note that for major site rewrites or larger work .asf.yaml also supports separate feature branches that can build and publish to separate namespaces on staged.apache.org. Very flexible.


was (Author: janhoy):
I think we don't need tasks.py, Makefile, publishconf or similar. Probably this would work:
{code:java}
git checkout master
# prod branch (src)
git checkout -b production
cat << EOF > .asf.yaml
pelican:
  whoami: production
  target: asf-site
EOF
git add .asf.yaml
git commit -m "Production source branch"
git push origin
# asf-site branch
git checkout master
git checkout --orphan asf-site
git rm --cached -r .
cat << EOF > .asf.yaml
publish:
  whoami: asf-site
EOF
git add .asf.yaml
git commit -m "Production build branch"
git push origin{code}
Then we get the simple workflow. Once we have a site we're happy with in master, we just merge to production branch and it ends up in the main site, and you can continue working in master with unstable stuff. Note that for major site rewrites or larger work .asf.yaml also supports separate feature branches that can build and publish to separate namespaces on staged.apache.org. Very flexible.

> Configure branches, auto build and auto stage/publish
> -----------------------------------------------------
>
>                 Key: LUCENE-9015
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9015
>             Project: Lucene - Core
>          Issue Type: Sub-task
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Commit to master should build and publish the staging site
> Find a simple way to trigger publishing of main site from staging



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org