You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
First, please be gentle with any assumptions about my product knowledge: it's just not there. I'm a database dinosaur but also a noob at Agile tools. Secondly, I may be hard to understand: it's a Spectrum thing. TIA for showing patience.
The rest of my development team works on single, discrete features. As a DBA, my contribution to a Sprint is a set of several dozen Linux scripts, SQL scripts, and data files. Over a dozen file folders are involved, albeit in one tree. Together, deliverable code set steps through a Jenkins script to build an artifact and to deploy it. The developers get to write up a JIRA ticket, create a bitbucket branch, touch one piece of code, and push it up when ready. I don't have that simplicity.
I "think" what I should be doing is to create a local branch, populate it with the tree, and commit the whole thing back to the remote. This doesn't sit well with the SCM, but I don't have a better method. If this makes sense, let's talk.