You don't need to preach. Use the workflow that makes you the most productive, mention what you're doing to others, and roll with what happens.
As a personal example, I'm not sure anybody had heard of or used Jenkins when I arrived. We now have an automated build, multiple levels of testing, static analysis, etc. I installed it and did some initial configuration, but others took on the majority of the work because they bought into it.
Couple other thoughts
- For CI, mention it to the team, have examples to back up where it helped, and offer to set it up. Shouldn't take too long and it'll pay back as soon as you catch some busted code (yours or theirs)
- While Subversion may not be as highly regarded as Git, it works just fine. So I wouldn't consider that a negative, just a different tool.
As a personal example, I'm not sure anybody had heard of or used Jenkins when I arrived. We now have an automated build, multiple levels of testing, static analysis, etc. I installed it and did some initial configuration, but others took on the majority of the work because they bought into it.
Couple other thoughts
- For CI, mention it to the team, have examples to back up where it helped, and offer to set it up. Shouldn't take too long and it'll pay back as soon as you catch some busted code (yours or theirs)
- While Subversion may not be as highly regarded as Git, it works just fine. So I wouldn't consider that a negative, just a different tool.