1

I've the basic idea about the Continuous Integration using Jenkins like- basic project setup, setting up source code management bit-bucket and build the project. I have done this so far and following the same approach, whenever any commit done in bit-bucket, Jenkins trigger the build and i get the build status But in my organization there is no expertise who clearly tell us about how CI tool actually used in real time. So we are not aware of the scope and expansions of the Automation project in terms of CI tool.

Can some one guide us about this and guide us to manage the release using Jenkins ? also somewhere the terms Jenkins pipeline confused me what it is and why it used for?

I'm working on Agile, So after completion on each sprint we have to commit out code in master branch only. We are planning to create new branch for each sprint. The vague in my is, we can create the new branch, sprint wise and also create the Jenkins job as per branch, So after committing the new branch Jenkins will trigger the build for that branch. It is the right approach ?

closed as off-topic by João Farias, c32hedge, NarendraR, Kate Paulk Dec 5 '17 at 18:47

  • This question does not appear to be about software quality assurance or testing within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • continuous integration belongs under devops or software engineering, the test part in CI belongs here. can you rephrase the question to better reflect this SE ? – Rsf Dec 5 '17 at 10:51
  • 1
    For DevOps see here on Stack. In general I would say: there is no one right approach. Only one that works for your needs (and your team). That is the basis of being agile in my book. So what is the actual problem you want to solve? – Ray Oei Dec 5 '17 at 12:00
  • @Ray Oei, Thanks, I want my automation project to be run in modularized way. Let's say I have 100 testcase which already in master branch and integrated with the Jenkins and also running successfully. But in next Sprint m creating 20 more testcase, this time I want these 20 testcase to be release and to be run after those 100 tests. Is it possible to do this kind of configuration? – NarendraR Dec 5 '17 at 16:28
  • 2
    I'm voting to close this question as off-topic because it should be asked on devops.stackexchange.com – c32hedge Dec 5 '17 at 16:35
  • @c32hedge, not an issue m closing it, will post there – NarendraR Dec 5 '17 at 16:39