Hi Monica!
From the message I’d guess you don’t have the repo ready.
One thing is to have assets in GIT, another thing is to create a build using ABE - that is the repository. Index is automatically created when you build with ABE.
ABE takes the source directory (assets you should have in GIT), zip them etc and prepares this “repository index”.
ProjectAutomator is just a next step and it is there for preparing “deployer project” which you would/could otherwise create manually through Integration sever/Solutions/Deployer. One option is to take repository as a source - and repository is exactly that ABE-built stuff…
Jenkins can be just a orchestration tool for running those tools, but it also can do much more - like store the repository of builds, promote them etc. That depends on how complex you set it up.
Let me know if that helped…