What is the difference between Application Repository and Team Development ?

Kaleem A
Giga Guru

Hi All,

What is the difference between Application Repository and Team Development ?. How update sets are different from these two?. I checked the wiki page   Getting Started with Update Sets - ServiceNow Wiki . I don't understand with the definition provided in the wiki. can someone help   me to understand these concepts with an example.

Regards,

Kaleemullah Akbar

1 ACCEPTED SOLUTION

Chuck Tomasi
Tera Patron

Hi Kaleemullah,



Here is my version (short answer),



  • Update sets are a mechanism to record configuration changes to your dev system and move them to another system.
  • Team Development allows developers on multiple dev systems to manage their changes to multiple applications and use a code review system.
  • The Application Repository is used with scoped apps as a modern way to update sets for promoting (installing/upgrading) applications between dev, test, and prod.
  • Finally, source control, (Git integration) allows developers to manage multiple revisions of configuration changes on their dev system. Source control and team development are NOT mutually exclusive.


Getting Started with Update Sets - ServiceNow Wiki


Transferring Update Sets - ServiceNow Wiki


Using Update Sets - ServiceNow Wiki  


Team Development - ServiceNow Wiki


Source control integration



Let me know if I have answered your question. If so, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.



If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.



Thank you


View solution in original post

3 REPLIES 3

Chuck Tomasi
Tera Patron

Hi Kaleemullah,



Here is my version (short answer),



  • Update sets are a mechanism to record configuration changes to your dev system and move them to another system.
  • Team Development allows developers on multiple dev systems to manage their changes to multiple applications and use a code review system.
  • The Application Repository is used with scoped apps as a modern way to update sets for promoting (installing/upgrading) applications between dev, test, and prod.
  • Finally, source control, (Git integration) allows developers to manage multiple revisions of configuration changes on their dev system. Source control and team development are NOT mutually exclusive.


Getting Started with Update Sets - ServiceNow Wiki


Transferring Update Sets - ServiceNow Wiki


Using Update Sets - ServiceNow Wiki  


Team Development - ServiceNow Wiki


Source control integration



Let me know if I have answered your question. If so, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.



If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.



Thank you


I would add that the application repository has some caveats. Each version when you "publish" contains a snapshot of ALL application files. It does not look specifically into each update set and what should be in the application at that time.

Update sets are a way of noting what was changed in your application. How you move them is a different problem - whether you move individual update sets to other instances or hit publish using the app repository is different.

Hey Chuck,

 

We are only a Dev > Test > Production architecture and not a Dev <> Dev <> Dev  > Test > Production architecture.

We would really like to do code reviews before a developer puts the update sets in Test. Is there a way to use the Team development module in our single dev environment? Is there another approach in ServiceNow? Currently, we use the update sources in Test and have it pull completed update sets.