We've already created library and clicked "save and build to develoment" button.
So now we are on development stage.
But we have to change the resources again now.
At that time can we just click "add all changed resources" button again and save and build to development button? Is there anything we should be aware of? Or is there any documents that explains these?
Thanks for your attention.
In most cases, yes... "add all changed resources" is going to get you what you need... this does exactly what it says, it will get all changes and create revisions for them in your build...
However, if you have changes that you don't want included... such as things you are still working on / tweaking; or if you have multiple Dev environments and multiple team members working on changes in isolation... then you might not want to create a build with everything....
In these scenarios, you can do a few things depending on the complexity...
You can find more information here: https://experienceleague.adobe.com/docs/experience-platform/tags/publish/libraries.html?lang=en
I hope this helps
Hi, many thanks for your reply. It helps me a lot.
One more question, as we clicked "add all changed resources" again and we can see a lot of revisions. Can we just select "Latest" on top? What do the other latest with square, live and published mean?
Latest: literally latest but not publised yet
Latest with square: It was newest before (not publised yet)
Live: live in product
Published: published but not alive now
Are these correct? Are there any documents regarding this topic?
Thanks again for your help.
Your descriptions are very close, I've added some additional info:
Latest: literally latest but no revision yet
Latest with square: Latest Build with a numbered revision (the last version you have built, which may or may not be live)
Live: Currently published "Live" revision
Published: All previously published to production
"Published" is handy if you need to roll-back to a previous version.. you might have made a number of changes that you tested in dev, then finally deployed to production.. but if there's an issue, you can easily find the last published version (or any previously published version) to make a new revision on (this allows you to back out to a previously working build for that resource.
While you can still choose Latest on top of "add all changed resources", you don't need to...
If you see this:
you should be okay, the "latest" version of the code will already be included.