search

walter-cd / walter

Tiny deployment pipeline
http://walter-cd.net
Apache License 2.0
438 stars 39 forks source link

Jenkins Integration: Jenkins Job Builder #59

Closed maxlinc closed 7 years ago

maxlinc commented 9 years ago

Walter looks like a cool project.

I saw this in the future plans at http://ainoya.io/walter:

Integration with Jenkins: Feedback mechanism to tell the progress of executing Walter build pipeline to Jenkins (or other CI service) is provided.

I think an alternate approach that could have some benefits is to use Walter as a generic way to to define pipelines (and test them locally) and then use a tool to import that configuration into Jenkins or other CI/CD servers. This is similar to, or could even delegate to, Jenkins Job Builder (JJB). The advantage I see of Walter over JJB is a much nicer and more portable syntax.

I think this could have some advantages over having Jenkins call walter and receive feedback on the progress. By mapping Walter definitions to existing Jenkins (or Go, TeamCity, etc.) features you'd likely be able to take better advantage of the existing pipeline visualizations, reporting, and agent pools to spread jobs across multiple machines.

ainoya commented 9 years ago

Hi, @maxlinc, Thank you a lot for your advice :smile:

I think an alternate approach that could have some benefits is to use Walter as a generic way to to define pipelines (and test them locally) and then use a tool to import that configuration into Jenkins or other CI/CD servers. This is similar to, or could even delegate to, Jenkins Job Builder (JJB). The advantage I see of Walter over JJB is a much nicer and more portable syntax.

Yes, I agree with your idea, because the motivation of developping walter is also to make pipelines config more portable. Actually I know JJB (and I like it), but I did not want to make the tool depends on a specific CI server at the time. I needed the pipeline executor which was independent of a specific CI server.

I think this could have some advantages over having Jenkins call walter and receive feedback on the progress. By mapping Walter definitions to existing Jenkins (or Go, TeamCity, etc.) features you'd likely be able to take better advantage of the existing pipeline visualizations, reporting, and agent pools to spread jobs across multiple machines.

Mapping Walter definitions to existing Jenkins features is a cool idea! since we can keep Walter simple by taking advantages of CI features (such as visualization, reporting etc).

We follow your advice to provide the integrations with the features of existing CI systems.

Especially, I really desire pipeline visualizations with Walter. Any idea on the implementation of the mapping would be very helpful.

mizzy commented 7 years ago

I close this for cleaning issues.