Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Implement a version control system (git) for Adobe Target Custom Code as part of the lifecycle

HugoNebreda
Level 1
Level 1

Hi!

We are currently using Adobe Target for testing in a complex environment from a technical perspective so the majority of our test are "developed" through custom code

This implies developers manipulate html + js + css code "by hand" in all of the lifecycle (analysis, development, validating, deploy to production) and we want to implement some version control system to this workflow, specifically git, to make it safer and to comply some internal regulations

So here are my questions:

  • Is there any possibility of integration with any major git repository management platforms? Github? Bitbucket?
  • Is there any possibility to get/update custom code programmatically via API?
  • What are some best practices for management a large volume of test done by custom code?

Thanks

1 Accepted Solution
nzchris
Correct answer by
Level 3
Level 3

Hi @HugoNebreda 


Judging from what you described, our situation is also quite similar. We use a build app to compile our separate HTML, CSS and JS and perform any functions to make it Adobe Target offer compatible (e.g. reusing popular tracking functions etc).

 

We'd recommend using your current source control system (we use Bitbucket) and then as part of the build process, send the compiled code to Adobe Target via the Target API as 'offers'

 

  • Is there any possibility of integration with any major git repository management platforms? Github? Bitbucket?
    • Not natively but you should continue to use your current git repository
  • Is there any possibility to get/update custom code programmatically via API?
  • What are some best practices for management a large volume of test done by custom code?
    • Version control or comments in the custom code have been useful for us. Some people like to do a console log statement when the offer drops. Sometimes they restrict this to a debug mode via profiles etc. 

View solution in original post

1 Reply
nzchris
Correct answer by
Level 3
Level 3

Hi @HugoNebreda 


Judging from what you described, our situation is also quite similar. We use a build app to compile our separate HTML, CSS and JS and perform any functions to make it Adobe Target offer compatible (e.g. reusing popular tracking functions etc).

 

We'd recommend using your current source control system (we use Bitbucket) and then as part of the build process, send the compiled code to Adobe Target via the Target API as 'offers'

 

  • Is there any possibility of integration with any major git repository management platforms? Github? Bitbucket?
    • Not natively but you should continue to use your current git repository
  • Is there any possibility to get/update custom code programmatically via API?
  • What are some best practices for management a large volume of test done by custom code?
    • Version control or comments in the custom code have been useful for us. Some people like to do a console log statement when the offer drops. Sometimes they restrict this to a debug mode via profiles etc. 

View solution in original post