Open tloubrieu-jpl opened 1 year ago
@nutjob4life @tloubrieu-jpl is the pds-expo node in Jenkins setup on-prem or in cloud?
Hi @sjoshi-jpl , pds-expo is running on prem.
@sjoshi-jpl you won't be able to access pds-expo directly. I DM you the wiki on access.
@viviant100 @tloubrieu-jpl I highly recommend we setup a separate node for cloud deployments (unless the idea is to deploy resources on-prem?) and keep these 2 environments separate. Some reasons why :
Thoughts?
If we setup a new node, I'd need help from Jenkins team since I don't have access to manage nodes in Jenkins.
+1 on separate node for cloud deployment. Contact SA to set up new nodes in Jenkins.
@sjoshi-jpl will be working with SA team to get a cloud node setup to do this
@jordanpadams @tloubrieu-jpl @viviant100 @nutjob4life ticket created for cloud node setup - https://itsd-jira.jpl.nasa.gov/servicedesk/customer/portal/16/DSIO-3963
@jordanpadams @viviant100 @tloubrieu-jpl @nutjob4life as per preliminary discussion with SA team on the above ticket, they will need to request a separate VPC / Dev Env for our testing. It will give us more control in terms of what resources we can build / test using terraform within AWS.
SA team will then setup an EC2 instance that we can use as an agent for Jenkins builds within the new VPC.
Waiting for SAs to create a specific dev account and VPC for this node.
Jenkins agent has been configured and getting this work started
We are tabling that for now since it only applies to JPL AWS but the new priority is to deploy on MCP
💡 Description
Jobs should be triggered by changes on the github repositories