You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by GitBox <gi...@apache.org> on 2020/07/25 11:13:57 UTC
[GitHub] [jena-site] rlenferink opened a new pull request #17: Added Jenkinsfile to put deployment configuration in version control
rlenferink opened a new pull request #17:
URL: https://github.com/apache/jena-site/pull/17
This puts the job configuration for deploying the Jena website in version control.
It is created as multi-branch pipeline so that branches other than master will be tested as well (whether they build using Hugo). Deployment (copy from master -> asf-site) only happens on the 'master' branch.
---
Steps to do to correctly setup the Jenkins job:
- Create a new multibranch pipeline (e.g. 'site').
- Set the gitbox url -> `https://gitbox.apache.org/repos/asf/jena-site.git` and use the `jenkins (master pub key)` credentials.
- In the 'Scan Multibranch Pipeline Triggers' check the 'Periodically if not otherwise run' checkbox and enter a sane value (e.g. 15 minutes). This is needed because webhooks are not delivered to ci-builds (yet).
- Save the job and click the 'Scan Multibranch Pipeline Now' button to trigger an initial scan.
Output should be similar to:
- https://ci-builds.apache.org/job/Celix/job/site/
- https://ci-builds.apache.org/job/Celix/job/site/job/master/8/console
---
/cc @afs
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] kinow commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control
Posted by GitBox <gi...@apache.org>.
kinow commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-663846558
> > Similar discussion ongoing in Commons about using a `Jenkinsfile`, GitHub actions, etc.
> > I'm a bit rusty on Jenkins, but looks good to me +1
>
> While GitHub actions could be used in this case for testing whether the setup builds, it won't let us push changes to this repo. That is why I went with Jenkins, because the `git-websites` labeled nodes allow us to push to the `asf-site` branch (which is needed for website deployment).
>
> For e.g. general development GitHub actions works pretty well (e.g. [@celix](https://github.com/apache/celix/tree/master/.github/workflows) we're using GH actions as well if you need examples :) )
I don't have strong preference :-) and I think we are already using Jenkins for CI in Jena, so it'd make sense to have this `Jenkinsfile` in the jena-site repo :+1:
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] afs commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control
Posted by GitBox <gi...@apache.org>.
afs commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-665205467
Thanks Roy - I'm also taking the setup notes and putting them in a txt file in the jena-site repo.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] rlenferink commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control
Posted by GitBox <gi...@apache.org>.
rlenferink commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-663844965
> Similar discussion ongoing in Commons about using a `Jenkinsfile`, GitHub actions, etc.
>
> I'm a bit rusty on Jenkins, but looks good to me 👍
While GitHub actions could be used in this case for testing whether the setup builds, it won't let us push changes to this repo. That is why I went with Jenkins, because the `git-websites` labeled nodes allow us to push to the `asf-site` branch (which is needed for website deployment).
For e.g. general development GitHub actions works pretty well (e.g. [@celix](https://github.com/apache/celix/tree/master/.github/workflows) we're using GH actions as well if you need examples :) )
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] afs merged pull request #17: Added Jenkinsfile to put deployment configuration in version control
Posted by GitBox <gi...@apache.org>.
afs merged pull request #17:
URL: https://github.com/apache/jena-site/pull/17
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] rlenferink commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control
Posted by GitBox <gi...@apache.org>.
rlenferink commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-665205857
Happy to help 😃
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org