Skip to content
This repository has been archived by the owner on Feb 16, 2018. It is now read-only.

allow users to keep their current Jenkinsfile on import #37

Open
jstrachan opened this issue Aug 9, 2017 · 5 comments
Open

allow users to keep their current Jenkinsfile on import #37

jstrachan opened this issue Aug 9, 2017 · 5 comments

Comments

@jstrachan
Copy link
Contributor

right now we override the Jenkinsfile with the chosen selection

@joshuawilson
Copy link

What happens when their current file changes how the build works and things break?

@jstrachan
Copy link
Contributor Author

we replace the Jenkinsfile and use the new Jenkinsfile to run the first pipeline right now.

we've no idea if other Jenkinsfiles would even work inside kubernetes as a Jenkinsfile can do anything and be written for any kind of jenkins server / platform (e.g. doing native docker stuff or assuming old style jenkins slaves)

@joshuawilson
Copy link

That is what I thought, so why suggest keeping their Jenkinsfile?

@jstrachan
Copy link
Contributor Author

Burr suggested we may want this as an option ;)

TBH I see this as pretty low priority really, as few folks will have effective Jenkinsfiles yet that work on OSO and do CI / CD properly - but some advanced user may wanna do their own Jenkinsfiles (at their own risk)

@joshuawilson
Copy link

thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants