-
Suggestion
-
Resolution: Duplicate
-
None
-
None
For some types of projects, passing artifacts is not appropriate or efficient. Deployment may include all of the source files and not have a true "build" stage. An example would be a python django project. In our case, we use Heroku for deployment as well, and the deploy is a git push action.
Currently, in my build plan, I check out the code and run a bunch of tests. Then, in order to use the deploy plan, I basically have to zip up the entire repository and pass it up as an artifact. Pull it back down during deploy, unzip, and so on.
Additionally, we work on an agency model and we can't make all nominally "shared" deployment repositories available globally due to confidentiality concerns; we cannot allow one internal team access to environment information that's applicable to other client teams. These may be shared among a number of projects, but we still need to set them up as plan repositories for those security reasons.
Please allow checking out plan repositories during Deployment.
- is duplicated by
-
BAM-13279 Deployment environment checkout task should use same revision as build result
- Gathering Interest