Sebastian Bixl

I think it would be best if we can add the new keyword `checkoutUpdateBuildOnly`. I have attached a small example of how a Code-Generator could be inserted, which should also...

We use bob in addition to Jenkins within GitLab CI/CD. It would be nice to have the possibility to check the state of the recipes vs. the artifacts stored in...

We have similar use cases as reported by @rhubert. I often get the question why the layers can't be managed better via bob (in analogy to the SCMs in the...

I had the following scenario in mind (assuming the layers are no longer managed via gitsubmodules): ```yaml layers: - foo: scm: git url: git@foo:/foo.git branch: master #

Hi together, maybe it would be a good solution to carry over the wiki contents into ReStructuredText in order to use Sphinx as documentation generator. This has the advantage, that...

The resulting docs can (if you want) hosted at [Read the Docs](https://readthedocs.org/) but you can als host it by using github.io. The benefit of using the first method is the...

I am also not friend of nested layers and completely agree with your last sentence. **Use case:** The only reason why we use the nested layer feature is that you...

This is exactly the use case in a nutshell. ;-) It would be nice if Bob could recognize this in some way and “bend” it to the new concept. A...

I have tested the new policy and it now works as expected. Many thanks for that! :-) However, I have noticed one more point. If you configure a managed layer...

No, that's not a problem at all. The layer handling, as it is now, is much better than using gitsubmodules before. There you had to update the commit every time....