Skip to main content
Tweeted twitter.com/#!/StackGameDev/status/220510908856799233
added 5 characters in body
Source Link
sebas
  • 490
  • 2
  • 7

Currently we are testing various configurations between Feature Branching and CI with Feature toggling,.

I can see there are several viable options out there for the code, but I also know that CI totally relies on the possibility to merge the code.

So I wonder, how do you manage CI with binary data, like art assetassets?

I can also see another problem. All: all the code can be tested before to commit, I can even validate the data before to commit, but how can I test the art?!

Should I use another methodology for art content?

Currently we are testing various configurations between Feature Branching and CI with Feature toggling, I can see there are several viable options out there for the code, but I also know that CI totally relies on the possibility to merge the code.

So I wonder, how do you manage CI with binary data, like art asset?

I can also see another problem. All the code can be tested before to commit, I can even validate the data before to commit, but how can I test the art?!

Should I use another methodology for art content?

Currently we are testing various configurations between Feature Branching and CI with Feature toggling.

I can see there are several viable options out there for the code, but I also know that CI totally relies on the possibility to merge the code.

So I wonder, how do you manage CI with binary data, like art assets?

I can also see another problem: all the code can be tested before to commit, I can even validate the data before to commit, but how can I test the art?!

Should I use another methodology for art content?

Source Link
sebas
  • 490
  • 2
  • 7

Continuous Integration, what are the strategies to manage binary content?

Currently we are testing various configurations between Feature Branching and CI with Feature toggling, I can see there are several viable options out there for the code, but I also know that CI totally relies on the possibility to merge the code.

So I wonder, how do you manage CI with binary data, like art asset?

I can also see another problem. All the code can be tested before to commit, I can even validate the data before to commit, but how can I test the art?!

Should I use another methodology for art content?