Check this: https://jenkins.io/doc/book/blueocean/creating-pipelines/#local-repository
The git repo need not be on a server (nor github.com), it can be a local 'git repo'. Simply create a directory for your Jenkinsfile, 'git init', and create/commit your Jenkinsfile. Then point Blue Ocean to this local directory. ( I think -- note, I have not tested this. But the documentation description is pretty straight-forward.) On Thursday, May 11, 2017 at 12:26:47 PM UTC-4, David Aldrich wrote: > > Hi > > > > I am finding it difficult to construct declarative pipelines as code, so I > want to try out Blue Ocean to construct them graphically. > > > > However, we store our project repositories in Subversion not Git. Blue > Ocean wants a Git repository or GitHub. I can’t use the latter because our > IT policy prevents us storing company data on an external server. > > > > We could install a Git server just for Blue Ocean. I imagine that > Jenkinsfiles for our projects would live in the Git server’s bare > repository and would execute actions on our subversion repositories: > checkout build etc. > > > > Furthermore I guess I could copy the Jenkinsfiles to the Subversion > repositories when they are tested, and then just maintain them as code. > > > > Is this a reasonable strategy? I’m not sure I am understanding the > documentation correctly so would be grateful for some guidance. > > > > Best regards > > > > David > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/864f6842-a546-4ee0-9ddd-ce800eea6184%40googlegroups.com.
