Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Jenkinsfile to put deployment configuration in version control #17

Merged
merged 1 commit into from Jul 28, 2020

Conversation

rlenferink
Copy link
Member

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:


/cc @afs

Copy link
Member

@kinow kinow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar discussion ongoing in Commons about using a Jenkinsfile, GitHub actions, etc.

I'm a bit rusty on Jenkins, but looks good to me 👍

@rlenferink
Copy link
Member Author

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 we're using GH actions as well if you need examples :) )

@kinow
Copy link
Member

kinow commented Jul 25, 2020

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 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 👍

@afs
Copy link
Member

afs commented Jul 27, 2020

Excellent! Much better way to manage the job.

@afs afs merged commit 9274fde into apache:master Jul 28, 2020
@afs
Copy link
Member

afs commented Jul 28, 2020

Thanks Roy - I'm also taking the setup notes and putting them in a txt file in the jena-site repo.

@rlenferink rlenferink deleted the add-jenkinsfile branch July 28, 2020 18:31
@rlenferink
Copy link
Member Author

Happy to help 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants