We have an intern who is working on adding CI on our docs projects. For this he would like to deploy the CI system (jenkins-based) on openshift. I figure the best place for this is our openshift (and thus he will be working on deploying his work via ansible) but I wanted to confirm first that we are ok with this.
I will be working with him on setting things up, in ansible and in openshift.
Soonish would be nice as he has been working over the break so he has some work started.
Thanks :)
This is interesting. We just moved the last part of the docs building scripts on openshift (the translation one), and a CI system may actually be a better place to run this kind of jobs. I will be happy to help on this topic if needed.
@darknao the preliminary work was submitted at: https://pagure.io/fedora-docs/docs-fp-o/pull-request/153#
Would it make sense to do this in centos-ci ?
Or at least not expose this jenkins anywhere, just have it create/run and terminate?
I just don't want us to have to run/manage a jenkins server if we can avoid it...
@richardgreg what do you plan on using exactly? a jenkins pipeline?
@siddharthvipul1 what do you think of ^ ?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
@richardgreg what do you plan on using exactly? a jenkins pipeline? Would it make sense to do this in centos-ci ? @siddharthvipul1 what do you think of ^ ?
If this workflow is container based (which I think it is), we can do it on CentOS CI I also remember Fedora Docs project on legacy CICO cluster so it seems aligned to it. I can create a namespace if needed @pingou just tell me and I can create one and give admin access to you
@pingou yeah, my original idea was to use a jenkins pipeline.
I'm hearing of CentOS CI for the first time so I'm looking into it. Useful links will be helpful.
So this work is now taking place under ci.centos.org.
I'm going to close the ticket here :)
Thanks for your inputs everyone!
Metadata Update from @pingou: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)