Commiting to GIT (my CAS Overlay)

[Y Levine]

I have the CAS Overlay building and configures on my server.

We have a University gitlab, what is the best practices to commit this to the local gitlab? We would need to commit the pom.xml, cas.properties etc.

[David Curry]

Personally, I made branches for our Dev, Test, and Prod deployments, and pushed the whole thing to our gitlab. Adding features in Dev and moving them through Test and Prod then just becomes an exercise in merging.

--Dave

David A. Curry,  CISSP
Director of Information Security
The New School - Information Technology
71 Fifth Ave., 9th Fl. ~ New York, NY 10003
+1 212 229-5300 x4728 ~ david...@newschool.edu
Sent from my phone; please excuse typos and inane auto-corrections.
   

On Fri, May 18, 2018, 18:53 Y Levine <ylev...@gmail.com> wrote:

I have the CAS Overlay building and configures on my server.

We have a University gitlab, what is the best practices to commit this to the local gitlab? We would need to commit the pom.xml, cas.properties etc.

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/da1d7823-e6ab-486e-9ea2-bacdc7165d3b%40apereo.org.